I'm having a very similar problem since upgrading to 4.0. I have a significant amount of development work working under 3.2.4/6, and I thought it was time to upgrade. Now, none of my archives seem to be part of the classpath. The only applicable note I've found so far was on the Wiki which says something like, "the classloader scheme has changed in 4.0, try running the 'standard' server implementation for something closer to 3.2.x." I deployed my stuff to standard and ran it, and, sure enough, everything worked fine.
I've tried several different solutions, including the manifest classpaths that you mentioned, but with no luck. If nothing else, I think the 4.0 administrators guide is supposed to be released soon. Wish I could be more help, Brett View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3853882#3853882 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3853882 ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
