On Thu, Oct 16, 2008 at 5:31 PM, Stuart McCulloch <[EMAIL PROTECTED]> wrote:
> when CGLIB dynamically creates a proxy class > it must be loaded by a classloader before it can be used. If it loads it in > the classloader of the type/interface being proxied (default) then it can > see all the types needed by that interface, but _not_ any CGLIB types > (unless that bundle also imports CGLIB... see later) > > If on the other hand, it loads the proxy class in the classloader of the > Qi4j > runtime bundle then it can't see all of the types needed by the interface > (unless the Qi4j runtime bundle has a dynamic import of *) Ok, so the solution is straight forward the "bridging classloader" to be handled internally by the Qi4j Runtime. Doesn't sound like rocket science, but I guess Guice have forced the devil out of the details by now. Cheers Niclas _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
