"jajansen" wrote : Bill, I understand your point on the scoping being spec mandated. But the spec is not final yet, I believe, so do you think that this should be repared in the final spec? Or do you see benifits of scoping to the JAR instead of the EAR level?
Well, EJB-JAR classes may be isolated. Also, EJB-JARs may be developed separately and maybe contain the same persistence unit names. Same goes with pu's deployed within a WAR. A WAR is *definately* isolated from all other EJBs and WARs. In JBoss, EJB jars are not deployed in an isolated classloader, so this point is moot, but this may not be the same in other app servers. | Your suggestion on repacking sound a lot like what I've done in my project (a core.jar that contains the EJBs and a domain.jar that contains the PersistenceUnit and the entity beans. The PU is scoped to the domain.jar so in the domain.jar I'm fine. But the EJB package also needs to reference the PU and then I need to scope it to the domain.jar, right? Or am I missing something? | | Best regards, | Jan Arend Jansen View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3920967#3920967 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3920967 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
