[ 
https://issues.apache.org/jira/browse/KARAF-499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006257#comment-13006257
 ] 

Achim Nierbeck commented on KARAF-499:
--------------------------------------

I did some research on this. 

After some refactoring in ops4j pax-web jsp bundle using the same jsp/jsf jars 
as used within jetty I end up with the exact same issue with a test environment 
I used. 
It seems to be a "race"-condition for the myfaces servlets. These Servlets need 
to be configured before they are started. 
I'm still researching how this can be done with pax-web, there is a issue for 
that at pax-web (http://issues.ops4j.org/browse/PAXWEB-255)

> Unable to load simple standalone JSF 2.0 webapp - JSF's implementation's 
> META-INF/*.tld files are not scanned at startup
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: KARAF-499
>                 URL: https://issues.apache.org/jira/browse/KARAF-499
>             Project: Karaf
>          Issue Type: Bug
>          Components: runtime
>    Affects Versions: 2.2.0
>         Environment: windows, linux, java 6
>            Reporter: Dan Tran
>            Priority: Blocker
>
> A testable war file is at 
> http://repo2.maven.org/maven2/org/apache/myfaces/commons/myfaces-commons-examples20/1.0.1/myfaces-commons-examples20-1.0.1.war
> Discussion is at 
> http://karaf.922171.n3.nabble.com/Unable-to-load-a-JSF-2-0-Spring-JPA-2-0-standalone-webapp-war-onto-Karaf-2-2-with-war-feature-instald-td2622522.html

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to