Thanks guys - no luck tho - trying two EAR deployments sounded hopeful (with one EAR just being a skin for the WAR) - surely that would give classloader isolation!?!? However even with settings for Pass-by-Value everywhere, using isolated loader-repositories in the jboss-app.xml's, trying java2ParentDelegation=false , ensuring Serializable and serialVersionUID set, etc. all it would give when I tried to cast the remote object retrieved via JNDI back into the original interface was the ClassCastException that I have now seen more times than I've had hot breakfasts. JBoss simply will not marshall/unmarshall the object as its passes between archives as it is supposed to.
So I have had to relent and just package the WAR inside the original EAR, where the code instantly works (of course). JBoss classloader is hereby victorious over me... if I try tangling with that evil [EMAIL PROTECTED] classloader again I will involve a priest and copious amounts of holy water. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985325#3985325 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3985325 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
