Kombinierte Ansicht Flache Ansicht Baumansicht
Threads [ Zurück | Nächste ]
toggle
Christoph Hennig
Maven + Wicket 1.4.18 + Liferay Portal CE 6.0.6
1. November 2011 02:03
Antwort

Christoph Hennig

Rang: New Member

Nachrichten: 4

Eintrittsdatum: 1. November 2011

Neue 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:

 108: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.
 201.11.2011 08:57:28 org.apache.catalina.startup.HostConfig checkResources
 3INFO: Reloading context [/WicketPortlet-1.0]
 401.11.2011 08:57:28 org.apache.catalina.core.StandardContext stop
 5INFO: Container org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/WicketPortlet-1.0] has not been started
 608:57:28,719 INFO  [PortletHotDeployListener:220] Registering portlets for WicketPortlet-1.0
 708:57:28,810 INFO  [PortletHotDeployListener:369] 1 portlet for WicketPortlet-1.0 is available for use
 801.11.2011 08:57:28 org.apache.catalina.core.StandardContext start
 9SCHWERWIEGEND: Error filterStart
1001.11.2011 08:57:28 org.apache.catalina.core.StandardContext start
11SCHWERWIEGEND: Context [/WicketPortlet-1.0] startup failed due to previous errors
1208:57:28,818 INFO  [ExtHotDeployListener:205] Extension environment for WicketPortlet-1.0 will not be undeployed
1308:57:28,818 INFO  [PortletHotDeployListener:404] Unregistering portlets for WicketPortlet-1.0
1408: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
Anhänge: WicketPortlet.zip (17,7k)
Christoph Hennig
RE: Maven + Wicket 1.4.18 + Liferay Portal CE 6.0.6
1. November 2011 12:08
Antwort

Christoph Hennig

Rang: New Member

Nachrichten: 4

Eintrittsdatum: 1. November 2011

Neue Beiträge

Is their really nobody who can have a look, what is wrong?
Mika Koivisto
RE: Maven + Wicket 1.4.18 + Liferay Portal CE 6.0.6
1. November 2011 16:25
Antwort

Mika Koivisto

LIFERAY STAFF

Rang: Liferay Legend

Nachrichten: 1513

Eintrittsdatum: 7. August 2006

Neue 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.
Mika Koivisto
RE: Maven + Wicket 1.4.18 + Liferay Portal CE 6.0.6
1. November 2011 16:29
Antwort

Mika Koivisto

LIFERAY STAFF

Rang: Liferay Legend

Nachrichten: 1513

Eintrittsdatum: 7. August 2006

Neue 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
RE: Maven + Wicket 1.4.18 + Liferay Portal CE 6.0.6
3. November 2011 01:28
Antwort

Christoph Hennig

Rang: New Member

Nachrichten: 4

Eintrittsdatum: 1. November 2011

Neue Beiträge

then i will waiting :-).

wicket is cool stuff ;-)...
Mika Koivisto
RE: Maven + Wicket 1.4.18 + Liferay Portal CE 6.0.6
3. November 2011 10:39
Antwort

Mika Koivisto

LIFERAY STAFF

Rang: Liferay Legend

Nachrichten: 1513

Eintrittsdatum: 7. August 2006

Neue 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:

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


See http://www.liferay.com/community/forums/-/message_boards/message/8578278
Christoph Hennig
RE: Maven + Wicket 1.4.18 + Liferay Portal CE 6.0.6
3. November 2011 11:26
Antwort

Christoph Hennig

Rang: New Member

Nachrichten: 4

Eintrittsdatum: 1. November 2011

Neue Beiträge

Thx:

 1
 2SCHWERWIEGEND: Exception starting filter WicketApplication
 3java.lang.ClassNotFoundException: org.apache.wicket.protocol.http.portlet.WicketFilter
 4    at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1645)
 5    at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1491)
 6    at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:269)
 7    at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:422)
 8    at org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:115)
 9    at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:4001)
10    at org.apache.catalina.core.StandardContext.start(StandardContext.java:4651)
11    at org.apache.catalina.startup.HostConfig.checkResources(HostConfig.java:1244)
12    at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1342)
13    at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:303)
14    at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
15    at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1337)
16    at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1601)
17    at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1610)
18    at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1590)
19    at java.lang.Thread.run(Thread.java:680)


I must review my maven dependency. sth is missing :-O