On Tue, Jul 8, 2008 at 12:22 AM, Stuart McCulloch <[EMAIL PROTECTED]> wrote:
> again, this wouldn't solve the Pax-Logging issue because > then the application will have all it's logging calls bound to > the original Log4J jar, which lacks the OSGi support that > Pax-Logging provides (various other things will then fail) Correct. I suspect that the Log4J classes from the WebAppClassloader is "leaking" and what causes the problems. So, either it is in Craig's configuration "somewhere" that the Framework should expose those packages from the parent CL, or we are touching on a bug in Felix. > I believe Niclas has some ideas on how to proceed... I have received the whole project from Craig, and will try to look at it later when I am back "home"... Stay tuned. Cheers Niclas
