This week's book giveaway is in the Server-Side JavaScript and NodeJS forum.
We're giving away four copies of Micro Frontends in Action and have Michael Geers on-line!
See this thread for details.
Win a copy of Micro Frontends in Action this week in the Server-Side JavaScript and NodeJS forum!

SU Lingam

Greenhorn
+ Follow
since Feb 09, 2005
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by SU Lingam

I'm looking for developing a prototype that would do the following.This service by default would go and fetch the local EJB if it exists by default else it woould go for a Remote access of the bean.The client is unaware whether he calling a Local or a Remote EJB.This prototype is like a decorator.

Is this do-able/worth a shot.

What do you think?

Thanks
I really appreciate, you taking your time explaining abt <ejb-ref> tag over JNDI tag.Sure did gain some perspective...

Thanks
Hi VT,

>>Please understand the difference. jndi names are not easy to manage and they might change over time much more often than the ejb-names (which shouldn�t change at all). If you�d like we can go through the versioning example in more detail and try to understand the issue from a maintenance point of view, when ejbs are accessed through references vs jndi names.

Yes..I would definitely would like to gain some perspective on this.Let's go thru an example.

Thanks for your insights.
Hi,

Thanks for the reply.

Well the value of the <ejb-ref> tag corresponds to the ejb-name of a Bean.Isn't?Well it's tightly coupled even then!!If the ejb-name of a bean
changes then you still have to change the ejb-ref??
The purpose of the ejb-ref tag shud have been I guess to be able to directly access the Home without going thru a lookup process.With the JNDI
Name we can go ahead directly accessing the Bean's Home,without having to
specify <ejb-ref> blocks.If the bean references 6-7 beans,the DD then becomes fairly complex and you still need to do the JNDI lookup for all the beans.That gives me the thinking why go for ejb-ref tags.

Thanks
Hi,

When a EJB wants to talk to an another bean,we always do a JNDI lookup to get the Bean's Home Interface,then the home's create to get the componenet interface.
In the deployment descriptor do we need to specify the <ejb-ref> tag inorder for a EJB to talk to another EJB.Is this required only when the two ejb's have seperate DD's.If the two EJB's are defined in the same ejb-jar.xml then we wouldn't need the <ejb-ref> tag?Am I right?

Why do we need this ejb-ref tag at all,when we always locate a Bean using the JNDI lookup?

Any insights is really appreciated.

Thanks