-
1. Re: ClassLoader 3.0 vs 2.0
mingardia Dec 28, 2002 8:27 PM (in response to mingardia)An Update,
Was able to get past the first exception of not finding the EJB class in JNDI context by adding a ejb-ref and a jboss-web.xml file. Still however can not load the interface class. In our business deligate we do a class.forName, and I suspect that perhaps we need to use the thread context to load the delegate implimentation. Not sure but will try this next. End result however is we are still getting a class not found exception, when looking for the interface class. Any one know the "right" way to dynamically load a class, such that it is loaded by the right classloader and has visibility into deployed ejb jar files?
mike... -
2. Re: ClassLoader 3.0 vs 2.0
mingardia Dec 29, 2002 10:00 AM (in response to mingardia)Having our business delegate loaded via the thread context loader worked... Although from time to time we still get the class not found error on the first load of an EAR. Restarting the server clears it up, and from that point on we seem to be fine which is very strange. Perhaps its some packaging problem. In the end we are now on our way to 3.x compatability