Hi, as I'm still puzzled by what your are trying to achieve. Are you trying to have a Servlet-Bridge? In that case we still have a wip-branch[1] for that. It could need some love, but maybe that part will already help you?
regards, Achim [1] - https://github.com/ops4j/org.ops4j.pax.web/tree/PAXWEB-606-Servlet-Bridge 2016-11-04 12:11 GMT+01:00 Benson Margulies <[email protected]>: > On Thu, Nov 3, 2016 at 10:12 PM, Niclas Hedhman <[email protected]> > wrote: > > Hi, > > > > from my experience with "inside"/"outside" set ups, I can feel your pain. > > Have you considered to package all the "outside" into a single large > bundle > > and deploy that "inside" ?? > > In this particular case, the problem is all caused by wanting a web > server that the code in the container can talk to for testing. I guess > I could stuff that in, but I don't like it. > > My non-testing 'outside' is very skinny: really just SLF4J and a tiny > interface of mine. > > I debugged this at some length, and found that pax-web creates thread > pools and does not set the context class loader to the current class > loader. Various specific classes set the TCCL, but when this explosion > happens, the tccl is the outer application class loader. I cannot > begin to guess how the presence of a copy of CXF and Jetty in the > outside class loader cause this, so we've decided to retire this test > for now. > > > > > > Niclas > > > > On Fri, Nov 4, 2016 at 5:41 AM, Benson Margulies <[email protected]> > > wrote: > >> > >> In the failing case, > >> > >> Thread[paxweb-config-1-thread-1,5,main] > >> > >> has a context class loader that is not an OSGi bundle class loader at > >> all. Jetty uses the context class loader, and things go badly. > >> > >> I can make this problem appear and disappear by changing what is in > >> the classpath _outside_ the container -- if I put CXF both inside and > >> outside, I get this. > >> > >> -- > >> -- > >> ------------------ > >> OPS4J - http://www.ops4j.org - [email protected] > >> > >> --- > >> You received this message because you are subscribed to the Google > Groups > >> "OPS4J" group. > >> To unsubscribe from this group and stop receiving emails from it, send > an > >> email to [email protected]. > >> For more options, visit https://groups.google.com/d/optout. > > > > > > > > > > -- > > Niclas Hedhman, Software Developer > > http://zest.apache.org - New Energy for Java > > > > -- > > -- > > ------------------ > > OPS4J - http://www.ops4j.org - [email protected] > > > > --- > > You received this message because you are subscribed to the Google Groups > > "OPS4J" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [email protected]. > > For more options, visit https://groups.google.com/d/optout. > > -- > -- > ------------------ > OPS4J - http://www.ops4j.org - [email protected] > > --- > You received this message because you are subscribed to the Google Groups > "OPS4J" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Apache Member 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/> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS> Software Architect / Project Manager / Scrum Master -- -- ------------------ OPS4J - http://www.ops4j.org - [email protected] --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
