Why would such closely coupled functionality operate on PUs from separate modules? It seems some thing is being attempted that could be better organised. It would be better to have the same PU used from the second module. Given the scoping definitions in the specification the spec suggests this could be by placing the shared PU at the EAR level either as a JAR in the root of the EAR or in the lib directory of the EAR. Alternatively the PU of the first module could be referenced through the '[i]#[/i]' syntax in the second module. The benefit of accessing the same PU is propagation. It would be the same Persistence Context injected into the second SLSB. By having access to the same Persistence Context the amount of work need by the EntityManagers to manage the entities would be reduced, there would be no scoping confusions and the application would run more efficiently.
--Gordon
[Message sent by forum member 'gyorke' (gyorke)]
http://forums.java.net/jive/thread.jspa?messageID=226627