掲示板

Liferay7 How to find out why a portlet wasn't deployed

7年前 に Thomas Kellerer によって更新されました。

Liferay7 How to find out why a portlet wasn't deployed

Expert 投稿: 490 参加年月日: 08/06/09 最新の投稿
With the introduction of OSGi in Liferay 7 writing portlets seems to be getting harder then ever.

Currently I have the problem that my portlets (a simple Liferay MVC portlet) isn't deployed, but all I can see in the logfile is:

14:04:30,178 INFO [com.liferay.portal.kernel.deploy.auto.AutoDeployScanner][AutoDeployDir:252] Processing my-portlet.jar

No error message no nothing and I never see the "STARTED" message.

I suspect this has to do with missing (or wrong) dependencies - but I can't figure out how to debug that. I tried changing the log level in ROOT/WEB-INF/classes/log4j.properties and logging.properties to DEBUG (and FINER respectively) but I still only see INFO messages in the liferay logfile (and catalina.out).

How do I find out why Liferay doesn't deploy my portlet?
There doesn't seem to be a separate logfile for the OSGi container.
thumbnail
7年前 に David H Nebinger によって更新されました。

RE: Liferay7 How to find out why a portlet wasn't deployed

Liferay Legend 投稿: 14914 参加年月日: 06/09/02 最新の投稿
When this happens, log into gogo, list your beans and start the one that is deployed but not started. This will give you the "unresolved references" that you need to satisfy for your module to start.
7年前 に Thomas Kellerer によって更新されました。

RE: Liferay7 How to find out why a portlet wasn't deployed

Expert 投稿: 490 参加年月日: 08/06/09 最新の投稿
Sorry, but what is "gogo"?
thumbnail
7年前 に Olaf Kock によって更新されました。

RE: Liferay7 How to find out why a portlet wasn't deployed

Liferay Legend 投稿: 6396 参加年月日: 08/09/23 最新の投稿
Thomas Kellerer:
Sorry, but what is "gogo"?


Gogo Shell, gives you quite some understanding of the OSGi infrastructure.

telnet localhost 11311
and you're in.
thumbnail
7年前 に Alexandr Kozhin によって更新されました。

RE: Liferay7 How to find out why a portlet wasn't deployed

New Member 投稿: 17 参加年月日: 17/02/16 最新の投稿
If you will deploy with "blade deploy" or via gogo "install " - you will se result of install and dependency resolving.