"andber" wrote : I now see that all other jars than the app1-ejb.jar is shown in the loader-repository for app2.ear.. Why is this?
Is EAR isolation turned on or off via the EAR deployer? java2Parent delegation effects if a JAR is first seen (cached) in the UCL, not whether EARs are isolated - that's part of your ear-service.xml in the deploy directory. If its turned on then everything in app1 will not be seen via app2. If you are trying to share some interface across EARs, you should package those specific interfaces as a JAR, drop it in the deploy directory so now it has global scope across EARs. If EAR isolation is turned off, than app1-ejb.jar should be visible to app2 (at least my understanding of JBoss classloading). Please take a look at the following WIKIs if you haven't already: http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossClassLoadingUseCases http://wiki.jboss.org/wiki/Wiki.jsp?page=ClassLoadingOverview And Chapter 8 of the J2EE spec. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3938556#3938556 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3938556 ------------------------------------------------------- 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 JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
