EJB folks, The following is a section from the final revision public draft of the EJB 1.1 specification document (Section 16.5): EJB 1.1 Specification (Final public draft: Section 16.5) <!-- The ejb-name element specifies an enterprise beans name. This name is assigned by the ejb-jar file producer to name the enterprise bean in the ejb-jar files deployment descriptor. The name must be unique among the names of the enterprise beans in the same ejb-jar file. The enterprise bean code does not depend on the name; therefore the name can be changed during the application-assembly process without breaking the enterprise beans function. There is no architected relationship between the ejb-name in the deployment descriptor and the JNDI name that the Deployer will assign to the enterprise beans home. The name must conform to the lexical rules for an NMTOKEN. Used in: entity, method, and session Example: <ejb-name>EmployeeService</ejb-name> --> <!ELEMENT ejb-name (#PCDATA)> This seems to imply the the Vendor (or runtime) EJB deployment descriptor MUST support identification of the JNDI name or the requirement in the foregoing specification can not be satisified (that IS if the JNDI name, say <jndi-name/> XML element, is not supportted by the vendor then the vendor has "architected a (sic) relationship between the ejb-name and the JNDI name". A particuliar vendor specific XML DD mapping does not support the JNDI name element except in the <ejb-ref/> DD. Thus since each session or entity EJB does not support an absolute JNDI name for the bean, how does a RMI-IIOP client of the bean access the home interface of the EJB via the look-up of the initial context. In other words, there is no way for the vendor in question to support a name change during the assembly process, since the vendor does not support the absolute JNDI name (outside of the <ejb-ref/> DD). I currently think this is a lack of coherence to the EJB 1.1 XML DD specification, and would like any comments you may have on this area. For the reference implementation of the J2EE (from Javasoft) the vendor (j2ee RI) XML DD specification requires the specification of the absolute JNDI name using the <jndi-name/> element. This is then accessed by performing a lookup of the "java:/comp/env/ejb" subcontext in the JDNI. As always, I could be misreading the specification along the "world-view" of the J2EE RI vendor; so I could be wrong. Again, any comments would be most helpful. Regards, Rick Landon =========================================================================== 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".
