Hi Harald,
wow great, could you push your changes to git.
I'm really thankful for you seeing into this. It already did cost me
quite a lot of time.
Now I can focus on fixing bugs again :)
Thanks a lot, Achim
Am 07.11.2011 22:53, schrieb Harald Wellmann:
Am 07.11.2011 22:12, schrieb Harald Wellmann:
5) Same problem with WarJSFIntegrationTest, this time also when running
under Equinox. The web app does not get published and the HTTP clients
receive a 404.
A possible cause for the different behaviour of the Native Container vs
the Pax Runner Container might be classloader issues - some classes from
the application class loader might be leaking into the bundle class
loaders, and if any class in Pax Web or Jetty tries to access the System
classloader directly, there's no way that Pax Exam can avoid that, but
this is bound to cause trouble...
Found it - exactly as suspected...
Stepping through DOMWebXmlParser, I had an exception in
ServiceLoader<ServletContainerInitializer>
serviceLoader = ServiceLoader.load(ServletContainerInitializer.class,
bundle.getClass().getClassLoader());
which for some reason did not get logged. Stepping into this call, I
could see a MyFaces class being loaded via the AppClassLoader, causing
a ClassCastException.
itest/pom.xml has two MyFaces dependendencies with test scope, that's
why the MyFaces initializer is visible via the system classloader, but
you only need it via the bundle classloader.
After removing the myfaces dependencies from the POM, the test passes,
both under Equinox and Felix.
Best regards,
Harald
_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general
--
--
*Achim Nierbeck*
Apache Karaf<http://karaf.apache.org/> Committer& PMC
OPS4J Pax Web<http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer&
Project Lead
blog<http://notizblog.nierbeck.de/>
_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general
