Hey Zeron, I've been there & done that. I spent a whole day on this one and related errors, and found the best solution was to tidy up my development environment so that the class path available when I compile is exactly the same or more restricted than the class path used by JBoss's class loader.
It meant taking my project apart and putting it back together as 3 seperate ones, but now I'm confident where the classes are going to be and I don't have to wing it anymore. Plus of course after spending so long hunting down the exception's cause, I will now for evermore associate 'class not found' with this problem.... :) <a href="http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3827069#3827069";>View the original post</a> <a href="http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3827069>Reply to the post</a> ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
