Hi, Thanks for the "recycle" classloader answer.... :-) Though my problem is not of that kind. Actually the interceptor will undeployed and re-deployed correctly (with the modifications).
The problem is that everything the interceptor uses are included in the same package ejb-aop.aop. I'm not sure of this but It seems that the re-deployed (new) interceptor uses the old interfaces (from the un-deployed ejb-aop.aop) and the test program uses the newly compiled ones. But really... I don't get it why it should even complain since I haven't altered the interface and all serializable classes have serialVersionUID attached to them. Anyway it is the interface that do not match. Is there something here I don't understand. (A interface do not have a identity such as serialVersionUID or?) Clearly the serialization mechanism do not complain about serialVersionUID conflicts. And when completely de-serialized the container deployed classes shall be used and thus this should not be of an issiue??? Many Regards, Mario View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3840260#3840260 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3840260 ------------------------------------------------------- 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
