Updated the ticket with some info. Basically by using the other signature for Class.forName, I was able to get around the problem I was having. It doesn't address the issue of needing to use a custom classloader but because of the module system in the platform, things work.
Gerrick On Sat, Dec 18, 2010 at 6:41 PM, Sandro Martini <[email protected]>wrote: > Hi to all, > some year ago I had the same problem inside a Java Enterprise webapp, > where in a custom bean factory I need to load classes in a different > layer of the EAR, so (when needed) passing the classloader instance of > the caller solved the problem. > > I'll put some info in the ticket. > > > Uh, of course this in a multi-layered app is a very good feature :-) , > and probably not only in the BXMLSerializer but in any place where a > dynamic loading of classes is done inside Pivot, .. maybe later, so > BXMLSerializer is without doubt a good start for it. > > Bye, > Sandro >
