aspose file tools*
The moose likes EJB and other Java EE Technologies and the fly likes Why do we need ejb-references ?? 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 "Why do we need ejb-references ??" Watch "Why do we need ejb-references ??" New topic
Author

Why do we need ejb-references ??

Karol Oslowski
Ranch Hand

Joined: Jul 22, 2005
Posts: 51
Dear all,

I read everywhere that if I want to get access to a local interface from a bean I must declare a reference.

The problem is that I haven't found anywhere the explanation why I need to do this. Why a bean can't just get access to other beans by JNDI lookups ?

kind regards

k.
Jeanne Boyarsky
author & internet detective
Marshal

Joined: May 26, 2003
Posts: 30947
    
158

Karol,
Welcome to JavaRanch!

To some extent, we need the references because the spec says so. As a result, the EJB containers require you to use references.

The reason that the spec says so is to provide a level of indirection between the JNDI and the actual resource. This is true for DataSources and other resources as well.


[Blog] [JavaRanch FAQ] [How To Ask Questions The Smart Way] [Book Promos]
Blogging on Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, OCAJP, OCPJP beta, TOGAF part 1 and part 2
Valentin Tanase
Ranch Hand

Joined: Feb 17, 2005
Posts: 704
Hi Karol,

EJB references are good practice because they help to achieve location transparency. In a nutshel your bean's jndi name could change and as an example consider versioning: a new version of the bean could be deployed with another jndi name. If you use ejb references than your configuration don't need to change at all. If your app would look up the bean based on its jndi name, than your configuration must change accordingly. However they are not mandatory and you can lokup your remote as well as local ejb home objects if you like.
Regards.


I think, therefore I exist -- Rene Descartes
Karol Oslowski
Ranch Hand

Joined: Jul 22, 2005
Posts: 51
Thank you very much!

Your answers have clarified this issue to me.

kind regards
Valentin Tanase
Ranch Hand

Joined: Feb 17, 2005
Posts: 704
you're very welcome Karol, I'm glad I could help
Roger Chung-Wee
Ranch Hand

Joined: Sep 29, 2002
Posts: 1683
The reason that the spec says so is to provide a level of indirection between the JNDI and the actual resource. This is true for DataSources and other resources as well.

Let's understand the reason for this. The Bean Provider writes reusable components which can be deployed anywhere and by anyone. When he needs to do a JNDI lookup on a DataSource, he does not know the real JNDI name of the database let alone the real name of the database. So, he invents a JNDI name to use in his code.

However, he also declares the same fake JNDI name in the DD.

The Application Deployer will then map the fake JNDI name to the real JNDI name (let's call it CustDatabse) under which the DataSource is registered using a vendor-supplied tool. The System Administrator will then configure the database (let's say its real name is CustomerData) into the server and gives it a JNDI name.

So, the use of fake JNDI names and subsequent mapping to real names is fundamentally important to the objective of WODA (write once deploy anywhere).


SCJP 1.4, SCWCD 1.3, SCBCD 1.3
 
Consider Paul's rocket mass heater.
 
subject: Why do we need ejb-references ??