I think in know the answer so I will post this in case others try to find solution. I'll preface this with the fact that I still have not really found a solution posted anywhere. So this is just a conclusion that I am making based on bits and peices I have put together.
If ear1 (at least) is isolated and ear2 wants to call an ejb inside ear1, the interfaces of the ejb that are in ear1 must be made available to both ear1 and ear2 classloaders. This means that either... | 1 ear1 does not isolate itself | | 2 the interfaces of ejbs in ear1 are put into a jar and placed say in deploy directory to be made accessible to all deployments. | | | I was really looking for something that would allow both ears to remain isolated without making interfaces available to all ears. This is due to my shared environment. However, after spending some time thinking about it. I think option 1 is the way to go. After all, if my ejbs are secured, who cares what other ears can attempt to call them. | | later, cgriffith View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3943285#3943285 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3943285 ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
