I like the idea of a flexible ClassLoaderResolverService, as long as can obtain the information about the bean class (if any) and interfaces. I'm not sure if just knowing the WebBeansContext is enough.
For the old javassist proxies, one trick was using the bean class as long as that classloader also had visibility to the necessary proxy infrastructure classes (javassist.proxy.ProxyFactory I think was the key one). Otherwise I think we would fall back on using the TCCL which was normally the module classloader. I'm not familiar with the new proxy code, but I wonder if we have a similar dependency. On Thu, Apr 4, 2013 at 7:09 AM, Romain Manni-Bucau <[email protected]>wrote: > Hi, > > just created https://issues.apache.org/jira/browse/OWB-812 > > the issue is: how to get the right classloader for a Bean<?> when creating > a proxy. > > ATM we use the bean class classloader but it will likely fail in a bunch of > JavaEE server and OSGi. > > I thought to add a ClassLoaderResolverService (or sthg like it) or > (probably better) link a ClassLoader to each WebBeansContext > > wdyt? > > *Romain Manni-Bucau* > *Twitter: @rmannibucau <https://twitter.com/rmannibucau>* > *Blog: **http://rmannibucau.wordpress.com/*< > http://rmannibucau.wordpress.com/> > *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* > *Github: https://github.com/rmannibucau* >
