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" ??
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.
