This week's book giveaway is in the Design forum.
We're giving away four copies of Building Microservices and have Sam Newman on-line!
See this thread for details.
The moose likes EJB Certification (SCBCD/OCPJBCD) and the fly likes Deployment Descriptors Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Building Microservices this week in the Design forum!
JavaRanch » Java Forums » Certification » EJB Certification (SCBCD/OCPJBCD)
Bookmark "Deployment Descriptors" Watch "Deployment Descriptors" New topic

Deployment Descriptors

Ranganathan Kaliyur Mannar

Joined: Oct 16, 2003
Posts: 1101

Hello All,
I have quite a few doubts about deployment descriptors in EJB. I assume that the ejb-jar.xml is a standard one as it is dealt in the spec.

1.Why hasn't Sun standardised the other xmls - like the one we use to give the jndi-names. It differs from vendor to vendor.

2.When I just package a jar with only ejb-jar.xml, and do a lookup with the name of the EJB, how does it work? does the vendor himself give the bean a jndi-name? if so, is there a standard to this?

3.can the jndi-name be the same for local and remote lookup?

Thank You,

Raja Sagar Panamgipalli
Ranch Hand

Joined: Aug 13, 2003
Posts: 109
The container vendor may implement naming service using LDAP,RMI,COS or any other way.

Each naming service has its own characteristics with respect to what kind of objects it is capable of storing, whether it is persistent or transient, etc. JNDI itself does not dictate those characteristics. It merely provides an abstraction for accessing the naming service in a way that protects your code from the gory details of the specific naming service implementation as much as possible.

JNDI is not the naming service itself. It's just an API you use to access a naming service. Just like JDBC is not a database. It's just an API you use to access a database. Someone needs to make a conscious decision to expose a particular naming service, LDAP, CosNaming, etc. via JNDI.

This decision would typically be made by the implementors of the naming service, but could be done by a 3rd party as well.

So basically its for vendors usage and their comfort.

Expect corrections.


SCJP 1.4<br />SCBCD 1.3
Ranganathan Kaliyur Mannar

Joined: Oct 16, 2003
Posts: 1101

Thanks very much for your reply.

Its a lot more clearer now.

Thank You,
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link:
subject: Deployment Descriptors
It's not a secret anymore!