Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
2.3.0
-
None
-
None
Description
When overriding the default pax-web configuration (in the feature file) by providing a custom org.ops4j.pax.web.cfg in the etc folder, it seems like the jetty.xml (as specified in the org.ops4j.pax.web.config.file property in org.ops4j.pax.web.cfg) is not read at all.
This has been discussed in the Karaf user mailing list:
http://karaf.922171.n3.nabble.com/Problems-with-jetty-xml-td4027066.html