hrm - i'm not really sure. you shouldn't be getting casting exceptions if both archives are being deployed as one unit. the classloader that deploys the ear should be the same one that is being used to look up class references.
i haven't experienced this problem when deploying everything in one ear. adding the loader repository isn't going to do you much good in this instance b/c you're not trying to prevent the classes inside the ear from being accessed outside of the ear. assuming you have a mbean in the sar, is it being shutdown and destroyed properly on the hot-deployment? the only other thing that comes to mind is that somehow it's not being completely destoryed and somehow as an incorrect reference. at this point, i'd recommend turing on classloader debugging and posting back the relevant portions here. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831938#3831938 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3831938 ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
