Wicket and Tomcat: Error deploying configuration descriptor ROOT.xml
When I launch our wicket application in Tomcat 5.5.27 I'm getting following output in the IDEA console: cmd /c C:\apache-tomcat-5.5.27\bin\catalina.bat run Using CATALINA_BASE: C:\Dokumente und Einstellungen\tom\.IntelliJIdea8x\system\tomcat\tomcat_Unnamed_websitecaa32f44 Using CATALINA_HOME: C:\apache-tomcat-5.5.27 Using CATALINA_TMPDIR: C:\apache-tomcat-5.5.27\temp Using JRE_HOME:C:\Programme\Java\jdk1.6.0_14 04.08.2009 11:19:04 org.apache.coyote.http11.Http11BaseProtocol init INFO: Initializing Coyote HTTP/1.1 on http-8080 04.08.2009 11:19:04 org.apache.catalina.startup.Catalina load INFO: Initialization processed in 234 ms 04.08.2009 11:19:04 org.apache.catalina.core.StandardService start INFO: Starting service Catalina 04.08.2009 11:19:04 org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/5.5.27 04.08.2009 11:19:04 org.apache.catalina.core.StandardHost start INFO: XML validation disabled 04.08.2009 11:19:04 org.apache.catalina.startup.HostConfig deployDescriptor SCHWERWIEGEND: Error deploying configuration descriptor ROOT.xml org.apache.commons.logging.LogConfigurationException: User-specified log class 'org.apache.commons.logging.impl.Log4JLogger' cannot be found or is not useable. at org.apache.commons.logging.impl.LogFactoryImpl.discoverLogImplementation(LogFactoryImpl.java:874) at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:604) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:336) at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:704) at org.apache.catalina.core.ContainerBase.getLogger(ContainerBase.java:381) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4119) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:760) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:740) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:544) at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:626) at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:553) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:488) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1150) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:120) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1022) at org.apache.catalina.core.StandardHost.start(StandardHost.java:736) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:448) at org.apache.catalina.core.StandardServer.start(StandardServer.java:700) at org.apache.catalina.startup.Catalina.start(Catalina.java:552) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433) My Wicket module depends on log4j-1.2.13.jar, portlet-api-2.0.jar, slf4j-api-1.4.2.jar and slf4j-log4j12-1.4.2.jar. I had replaced Tomcat's conf/server.xml with the conf/server-minimal.xml. I'm not using Maven. Any one knows what to do to fix it? Thanks in advance. Tom - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket and Tomcat: Error deploying configuration descriptor ROOT.xml
Hi Thomas, On Tue, Aug 4, 2009 at 3:54 PM, Thomas Singerwic...@regnis.de wrote: OK, this was caused by having removed commons-logging-1.1.jar from the classpath. I still don't understand why it is required. The wicket 1.4.0 readme says: You only need to include the Servlet API (2.3, just for compiling) and the SLF4J logging implementation you want. Hence I assumed, that commons-logging-1.1.jar is NOT required. I'm confused. I.e. in addition to SLF4J (the API) you also need an imlementation of that API, such as commons logging. Cheers, Erik - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicket and Tomcat: Error deploying configuration descriptor ROOT.xml
run mvn dependency:tree to see where you get clogging-1.1 from If you find out which dependency includes it, either * exclude clogging with that dependency in your pom, or * use 99-version-does-not-exists from Erik van Oosten (search google) Martijn On Tue, Aug 4, 2009 at 3:54 PM, Thomas Singerwic...@regnis.de wrote: OK, this was caused by having removed commons-logging-1.1.jar from the classpath. I still don't understand why it is required. The wicket 1.4.0 readme says: You only need to include the Servlet API (2.3, just for compiling) and the SLF4J logging implementation you want. You cannot use Wicket without adding a SLF4J logging implementation to your classpath. Most people use log4j. If you do, just include slf4j-log4j12.jar on your classpath to get Wicket to use log4j too. If you want to use commons-logging or JDK14 logging or something else, please see the SLF4J site (http://www.slf4j.org/) for more information. Hence I assumed, that commons-logging-1.1.jar is NOT required. I'm confused. Tom Thomas Singer wrote: When I launch our wicket application in Tomcat 5.5.27 I'm getting following output in the IDEA console: cmd /c C:\apache-tomcat-5.5.27\bin\catalina.bat run Using CATALINA_BASE: C:\Dokumente und Einstellungen\tom\.IntelliJIdea8x\system\tomcat\tomcat_Unnamed_websitecaa32f44 Using CATALINA_HOME: C:\apache-tomcat-5.5.27 Using CATALINA_TMPDIR: C:\apache-tomcat-5.5.27\temp Using JRE_HOME: C:\Programme\Java\jdk1.6.0_14 04.08.2009 11:19:04 org.apache.coyote.http11.Http11BaseProtocol init INFO: Initializing Coyote HTTP/1.1 on http-8080 04.08.2009 11:19:04 org.apache.catalina.startup.Catalina load INFO: Initialization processed in 234 ms 04.08.2009 11:19:04 org.apache.catalina.core.StandardService start INFO: Starting service Catalina 04.08.2009 11:19:04 org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/5.5.27 04.08.2009 11:19:04 org.apache.catalina.core.StandardHost start INFO: XML validation disabled 04.08.2009 11:19:04 org.apache.catalina.startup.HostConfig deployDescriptor SCHWERWIEGEND: Error deploying configuration descriptor ROOT.xml org.apache.commons.logging.LogConfigurationException: User-specified log class 'org.apache.commons.logging.impl.Log4JLogger' cannot be found or is not useable. at org.apache.commons.logging.impl.LogFactoryImpl.discoverLogImplementation(LogFactoryImpl.java:874) at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:604) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:336) at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:704) at org.apache.catalina.core.ContainerBase.getLogger(ContainerBase.java:381) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4119) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:760) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:740) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:544) at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:626) at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:553) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:488) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1150) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:120) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1022) at org.apache.catalina.core.StandardHost.start(StandardHost.java:736) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:448) at org.apache.catalina.core.StandardServer.start(StandardServer.java:700) at org.apache.catalina.startup.Catalina.start(Catalina.java:552) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433) My Wicket module depends on log4j-1.2.13.jar, portlet-api-2.0.jar, slf4j-api-1.4.2.jar and slf4j-log4j12-1.4.2.jar. I had replaced Tomcat's conf/server.xml with the conf/server-minimal.xml. I'm not using Maven. Any one knows what to do to fix it? Thanks in advance.
Re: Wicket and Tomcat: Error deploying configuration descriptor ROOT.xml
OK, this was caused by having removed commons-logging-1.1.jar from the classpath. I still don't understand why it is required. The wicket 1.4.0 readme says: You only need to include the Servlet API (2.3, just for compiling) and the SLF4J logging implementation you want. You cannot use Wicket without adding a SLF4J logging implementation to your classpath. Most people use log4j. If you do, just include slf4j-log4j12.jar on your classpath to get Wicket to use log4j too. If you want to use commons-logging or JDK14 logging or something else, please see the SLF4J site (http://www.slf4j.org/) for more information. Hence I assumed, that commons-logging-1.1.jar is NOT required. I'm confused. Tom Thomas Singer wrote: When I launch our wicket application in Tomcat 5.5.27 I'm getting following output in the IDEA console: cmd /c C:\apache-tomcat-5.5.27\bin\catalina.bat run Using CATALINA_BASE: C:\Dokumente und Einstellungen\tom\.IntelliJIdea8x\system\tomcat\tomcat_Unnamed_websitecaa32f44 Using CATALINA_HOME: C:\apache-tomcat-5.5.27 Using CATALINA_TMPDIR: C:\apache-tomcat-5.5.27\temp Using JRE_HOME:C:\Programme\Java\jdk1.6.0_14 04.08.2009 11:19:04 org.apache.coyote.http11.Http11BaseProtocol init INFO: Initializing Coyote HTTP/1.1 on http-8080 04.08.2009 11:19:04 org.apache.catalina.startup.Catalina load INFO: Initialization processed in 234 ms 04.08.2009 11:19:04 org.apache.catalina.core.StandardService start INFO: Starting service Catalina 04.08.2009 11:19:04 org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/5.5.27 04.08.2009 11:19:04 org.apache.catalina.core.StandardHost start INFO: XML validation disabled 04.08.2009 11:19:04 org.apache.catalina.startup.HostConfig deployDescriptor SCHWERWIEGEND: Error deploying configuration descriptor ROOT.xml org.apache.commons.logging.LogConfigurationException: User-specified log class 'org.apache.commons.logging.impl.Log4JLogger' cannot be found or is not useable. at org.apache.commons.logging.impl.LogFactoryImpl.discoverLogImplementation(LogFactoryImpl.java:874) at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:604) at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:336) at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:704) at org.apache.catalina.core.ContainerBase.getLogger(ContainerBase.java:381) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4119) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:760) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:740) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:544) at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:626) at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:553) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:488) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1150) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:120) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1022) at org.apache.catalina.core.StandardHost.start(StandardHost.java:736) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:448) at org.apache.catalina.core.StandardServer.start(StandardServer.java:700) at org.apache.catalina.startup.Catalina.start(Catalina.java:552) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433) My Wicket module depends on log4j-1.2.13.jar, portlet-api-2.0.jar, slf4j-api-1.4.2.jar and slf4j-log4j12-1.4.2.jar. I had replaced Tomcat's conf/server.xml with the conf/server-minimal.xml. I'm not using Maven. Any one knows what to do to fix it? Thanks in advance. Tom - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail:
