Found the problem - the class loader failed to find the *interface* that the class was 
implementing and reported merely that the class could not be loaded. Didn't say 
anything about the interface that was the real root of the problem. I'll figure out 
how to beef up the error reporting so it is less confusing...

View the original post : 
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3834507#3834507

Reply to the post : 
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3834507


-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to 
deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to