I found the same exact issue with a simple myface 2.0.x example war
file
http://repo2.maven.org/maven2/org/apache/myfaces/commons/myfaces-commons-examples20/1.0.1/myfaces-commons-examples20-1.0.1.war
The error spits out from myface seems to give some hint
21:06:14,178 | WARN | raf-2.2.0/deploy | /mfe
| .eclipse.jetty.util.log.Slf4jLog 50 | 193 -
org.eclipse.jetty.util - 7.2.2.v20101205 | unavailable
java.lang.IllegalStateException: No Factories configured for this
Application. This happens if the faces-initialization does not work at
all - make sure that you properly include all configuration settings
necessary for a basic faces application and that all the necessary
libs are included. Also che
ck the logging output of your web application and your container for
any exceptions!
If you did that and find nothing, the mistake might be due to the fact
that you use some special web-containers which do not support
registering context-listeners via TLD files and a context listener is
not setup in your web.xml.
A typical config looks like this;
<listener>
<listener-class>org.apache.myfaces.webapp.StartupServletContextListener</listener-class>
</listener>
at
javax.faces.FactoryFinder.getFactory(FactoryFinder.java:172)[243:mfe:0.0.0]
at
javax.faces.webapp.FacesServlet.init(FacesServlet.java:112)[243:mfe:0.0.0]
Even if I add the listener to my web.xml, then I ran into jsf tag
loading problem.
I also attempt the debug the issue with both myfaces and mojarra, both
indicate a bunch of jsf factories are not inititialized and there for
javax.faces.webapp.FacesServlet bails out
Look like this is karaf/felix class loader problem
-D
