Foren

Maven + Wicket 1.4.18 + Liferay Portal CE 6.0.6

Christoph Hennig, geändert vor 12 Jahren.

Maven + Wicket 1.4.18 + Liferay Portal CE 6.0.6

New Member Beiträge: 4 Beitrittsdatum: 01.11.11 Neueste Beiträge
Hello,

I hope sb can help me. Currently Liferay Portal CE 6.0.6 is running on my mashine. I use a Maven project which resolves the dependencies for Wicket, etc...

My intention was to build up a Wicket-Portlet. But when I deploy the Portlet I get following error message:

08:57:19,101 INFO  [PortletAutoDeployListener:81] Portlets for /Users/christoph/Entwicklung/Liferay-Portal-6.0.6/deploy/WicketPortlet-1.0.war copied successfully. Deployment will start in a few seconds.
01.11.2011 08:57:28 org.apache.catalina.startup.HostConfig checkResources
INFO: Reloading context [/WicketPortlet-1.0]
01.11.2011 08:57:28 org.apache.catalina.core.StandardContext stop
INFO: Container org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/WicketPortlet-1.0] has not been started
08:57:28,719 INFO  [PortletHotDeployListener:220] Registering portlets for WicketPortlet-1.0
08:57:28,810 INFO  [PortletHotDeployListener:369] 1 portlet for WicketPortlet-1.0 is available for use
01.11.2011 08:57:28 org.apache.catalina.core.StandardContext start
SCHWERWIEGEND: Error filterStart
01.11.2011 08:57:28 org.apache.catalina.core.StandardContext start
SCHWERWIEGEND: Context [/WicketPortlet-1.0] startup failed due to previous errors
08:57:28,818 INFO  [ExtHotDeployListener:205] Extension environment for WicketPortlet-1.0 will not be undeployed
08:57:28,818 INFO  [PortletHotDeployListener:404] Unregistering portlets for WicketPortlet-1.0
08:57:28,820 INFO  [PortletHotDeployListener:435] 1 portlet for WicketPortlet-1.0 was unregistered


The log files doesn't contain more informations. I have added the eclipse project to this post!!!

I have read a lot of posts about setting up maven/wicket/liferay projects but I could not found a solution for me.

thx

Christoph
Christoph Hennig, geändert vor 12 Jahren.

RE: Maven + Wicket 1.4.18 + Liferay Portal CE 6.0.6

New Member Beiträge: 4 Beitrittsdatum: 01.11.11 Neueste Beiträge
Is their really nobody who can have a look, what is wrong?
thumbnail
Mika Koivisto, geändert vor 12 Jahren.

RE: Maven + Wicket 1.4.18 + Liferay Portal CE 6.0.6

Liferay Legend Beiträge: 1519 Beitrittsdatum: 07.08.06 Neueste Beiträge
It's only 10 hours since you posted your question. You have better change of finding wicket experts from Wicket's forums. It's not the most popular framework for portlet development so finding the right people to help you might take awhile.
Christoph Hennig, geändert vor 12 Jahren.

RE: Maven + Wicket 1.4.18 + Liferay Portal CE 6.0.6

New Member Beiträge: 4 Beitrittsdatum: 01.11.11 Neueste Beiträge
then i will waiting :-).

wicket is cool stuff ;-)...
thumbnail
Mika Koivisto, geändert vor 12 Jahren.

RE: Maven + Wicket 1.4.18 + Liferay Portal CE 6.0.6

Liferay Legend Beiträge: 1519 Beitrittsdatum: 07.08.06 Neueste Beiträge
Hey Christoph,

Did you get the exception causing the the startup of the webapp to fail? If you didn't you might want to modify the logging.properties in your webapp and set:

org.apache.catalina.core.ContainerBase.[Catalina].level = INFO
org.apache.catalina.core.ContainerBase.[Catalina].handlers = java.util.logging.ConsoleHandler


See http://www.liferay.com/community/forums/-/message_boards/message/8578278
Christoph Hennig, geändert vor 12 Jahren.

RE: Maven + Wicket 1.4.18 + Liferay Portal CE 6.0.6

New Member Beiträge: 4 Beitrittsdatum: 01.11.11 Neueste Beiträge
Thx:


SCHWERWIEGEND: Exception starting filter WicketApplication
java.lang.ClassNotFoundException: org.apache.wicket.protocol.http.portlet.WicketFilter
	at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1645)
	at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1491)
	at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:269)
	at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:422)
	at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:115)
	at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:4001)
	at org.apache.catalina.core.StandardContext.start(StandardContext.java:4651)
	at org.apache.catalina.startup.HostConfig.checkResources(HostConfig.java:1244)
	at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1342)
	at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:303)
	at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
	at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1337)
	at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1601)
	at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1610)
	at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1590)
	at java.lang.Thread.run(Thread.java:680)
</init>


I must review my maven dependency. sth is missing :-O
thumbnail
Mika Koivisto, geändert vor 12 Jahren.

RE: Maven + Wicket 1.4.18 + Liferay Portal CE 6.0.6

Liferay Legend Beiträge: 1519 Beitrittsdatum: 07.08.06 Neueste Beiträge
I hate it when tomcat doesn't print the stacktrace. I have tomcat source and in StandardContext class inside listenerStart() method I have a breakpoint where it's supposed to log the exception. Then I just start tomcat in debugging mode and connect eclipse to it. That way I can always find out what's the cause regardless of how logging is configured.