wood burning stoves 2.0*
The moose likes EJB and other Java EE Technologies and the fly likes Sharing same EJB 3.1 project in two (or more) EAR projects. Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "Sharing same EJB 3.1 project in two (or more) EAR projects." Watch "Sharing same EJB 3.1 project in two (or more) EAR projects." New topic
Author

Sharing same EJB 3.1 project in two (or more) EAR projects.

Claude Moore
Ranch Hand

Joined: Jun 24, 2005
Posts: 450
    
    1

Good morning,

I have the following scenario:
- An EJB 3.1 project;
- A first EAR Project (AlfaEAR) which includes the EJB project
- A second EAR Project (BetaEAR) which includes the EJB project as well.

When deploying B and C on my appserver, I can see in the log / trace that each EJB contained in B is resolved and installed in EJBs container, with different JNDI names which, of course, have a "reference" to the EAR app which exposes them; for example I have ejblocal:AlfaEAR/AlfaEJB.jar/SameBean#test.view.SameBeanLocal and ejblocal:BetaEAR/AlfaEJB.jar/SameBean#test.view.SameBeanLocal

Now I'm wondering what happens in EJB container: the same ejb SameBean is treated as two distinct entities ? What happens if I change SameBean and its interfaces and I update only one of the projects, lets say AlfaEAR ? What about if SampleBean is declared as singleton ?

Can anyone help me to understand ?
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Sharing same EJB 3.1 project in two (or more) EAR projects.