Thanks for the answer. Is there something that I am doing wrong in my package to cause this issue? This is happening upon the re-deploy of the EAR, so I am wondering why the re-deploy is using a destroyed class loader instead of a "new one". Any suggestions on how I might fix it or is the JBoss restart the only way to go?
Thanks. Thomas View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3861533#3861533 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3861533 ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
