Do you refer to the WebSphere-specific deployment descriptor?
The rude answer would be that it would'nt work unless you do so. The whole purpose of that file is to resolve the developer-defined java:comp/env jndi name into the real jndi reference of the application server into which you intend to deploy the bound ear file. If the developer has hard-coded the external jndi-name into the source code, rather than using java:comp/env-based jndi names, then there is nothing to bind in the binding file. This works for EJB references. For resource manager references, coding to external jndi name would make your code be incompliant with the J2EE specification. The way the app server would manage your transactional resources (JDBC connections, JMS sessions, JCA connections etc) would be "un- defined". History has shown that the behaviour has changed between versions of a specific app server. You are on your own, if you use external JNDI names in your code for looking up resource manager factories (jdbc DataSource, jms QueueConnectionFactory, JCA connection factories etc). /Johan On 10 aug 2005, at 17.43, SUBSCRIBE EJB-INTEREST Test wrote:
Hi, What is the advantage in using fully qualified jndi name (global jndi name) in ejb-jar binding file? Thanks in advance. ====================================================================== ===== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
=========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
