if you read the wiki page, then if i have A.jar deployed, and A.ear and B.ear depend upon A.jar, if i redeploy A.jar, the class loader is going to have stale references to those classes and give me ClassCastExceptions.
in order to get around that, you "touch" A.ear and B.ear so they are given new class loaders that will re-search for the required classes when a method is invoked. if you only have one or two packages deployed, this works ok, but if you end up having lots of things deployed and you modify A.jar, you're better off just restarting the whole server. if you're changing interceptor code, your only option may be to restart the server. your best bet would be to split up the packaging as described in the wiki page (place all the interceptors into the jar, in addition to the ejb home/remote classes and any dependent helper classes) and then try hot-deploying an ear and see if you get issues. if that works, then try redeploying the jar file and then "touch" the ear so it gets reloaded and see what happens. as a rule of thumb for myself, any time i change interceptor code, i always restart the server to be on the safe side. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3839892#3839892 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3839892 ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
