If you haven't already, catch the InvocationTargetException and call the getTargetException() method on it. That will tell you the actual exception that is thrown. InvocationTargetException just means an exception was thrown by a method invoked via reflection, the exception inside it is the one that counts. I haven't been tuning in on the thread, so that advice may have already been covered.
Korosh Afshar, wrote: > > I saw this posting about OpenEJB doing some funky things with > their class loader which resulted in the same problem for the > poster: > http://www.mail-archive.com/[email protected]. > org/msg01387.html > And to set the record straight on old thread above, OpenEJB's classloading definitely does not suck, far from it in fact. The real issue was discovered and the finger points directly at Sun. Anyone who implements the java.net.URLStreamHandler interface, as OpenEJB does, will soon realize that the implementation *must* be loaded into the system classloader or it won't be found. There is a full explanation here: http://www.mail-archive.com/[email protected]/msg00339. html OpenEJB's classloading is actually pretty nice. In 0.9 onward, it will load into pretty much any classloader you throw at it. If anyone tried to make an OpenEJB block for Avalon using OpenEJB 0.8.3 or lower, try again using 0.9.0 or up -- should be a breeze. -David --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
