What is the expected output? What do you see instead?
When adding the Apache Orchestra dependency in the pom.xml I get the following
exception when starting with run-jetty-run:
Critical error during deployment:
com.sun.faces.config.ConfigurationException: java.lang.ClassNotFoundException:
org.apache.myfaces.orchestra.conversation.jsf.components.facelets.ConverterTagHa
ndler
at com.sun.faces.config.processor.FaceletTaglibConfigProcessor.processHandlerClass(FaceletTaglibConfigProcessor.java:436)
at com.sun.faces.config.processor.FaceletTaglibConfigProcessor.processTags(FaceletTaglibConfigProcessor.java:371)
at com.sun.faces.config.processor.FaceletTaglibConfigProcessor.processTagLibrary(FaceletTaglibConfigProcessor.java:314)
at com.sun.faces.config.processor.FaceletTaglibConfigProcessor.process(FaceletTaglibConfigProcessor.java:263)
at com.sun.faces.config.ConfigManager.initialize(ConfigManager.java:362)
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:225)
at org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:549)
at org.mortbay.jetty.servlet.Context.startContext(Context.java:136)
at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1282)
at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:518)
at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:499)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
at org.mortbay.jetty.Server.doStart(Server.java:224)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at runjettyrun.Bootstrap.main(Bootstrap.java:97)
Caused by: java.lang.ClassNotFoundException:
org.apache.myfaces.orchestra.conversation.jsf.components.facelets.ConverterTagHa
ndler
at runjettyrun.ProjectClassLoader.loadClass(ProjectClassLoader.java:91)
at com.sun.faces.util.Util.loadClass(Util.java:293)
at com.sun.faces.config.processor.AbstractConfigProcessor.loadClass(AbstractConfigProcessor.java:311)
at com.sun.faces.config.processor.FaceletTaglibConfigProcessor.processHandlerClass(FaceletTaglibConfigProcessor.java:420)
... 15 more
2012-06-22 08:11:19.692:WARN::Failed startup of context
org.mortbay.jetty.webapp.WebAppContext@132d9844{/TestJsfComponents,D:\workspace\
JettyOrchestraBug\src\main\webapp}
java.lang.RuntimeException: com.sun.faces.config.ConfigurationException:
java.lang.ClassNotFoundException:
org.apache.myfaces.orchestra.conversation.jsf.components.facelets.ConverterTagHa
ndler
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:292)
at org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:549)
at org.mortbay.jetty.servlet.Context.startContext(Context.java:136)
at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1282)
at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:518)
at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:499)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
at org.mortbay.jetty.Server.doStart(Server.java:224)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at runjettyrun.Bootstrap.main(Bootstrap.java:97)
If I remove the dependency from the pom.xml, all works fine. Also if I run
jetty directly from the console with mvn jetty:run it will run fine, the issue
appears only with run-jetty-run.
What steps will reproduce the problem?
1. Create a jsf project with maven
2. Add the Apache Orchestra dependency:
<dependency>
<groupId>org.apache.myfaces.orchestra</groupId>
<artifactId>myfaces-orchestra-core</artifactId>
<version>1.4</version>
</dependency>
3. Run the application with run-jetty-run
What Eclipse version are you using ?
3.6 & 3.7
What Run-Jetty-Run version are you using?
1.3.2
What OS are you using ? 32bit or 64 bit?
64bit
Original issue reported on code.google.com by freaky-s...@gmx.net on 22 Jun 2012 at 6:19
Original issue reported on code.google.com by
freaky-s...@gmx.net
on 22 Jun 2012 at 6:19