On Tue, 21 Nov 2000 16:14:37 -0800, Richard Landon <[EMAIL PROTECTED]> wrote: >The following is a section from the final revision public draft of the EJB >1.1 specification document (Section 16.5): <snip> >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". Note that there is no requirement in the EJB specification for a JNDI namespace at all. It is common to have one, but not mandatory. >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). This is a perfectly ok vendor decision. Not very flexible, but definitely ok from a spec compliance point of view. >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. How can this be a lack of coherence? Again, note that the very notion of binding the beans in a global namespace is proprietary in the first place. And again, just because most (all?) vendors support it does not mean that it is mandatory. It would be perfectly legal to not do it, and I can see scenarios where it would even be a requirement that a global JNDI namespace is not available (for example in an embedded application). >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. This is more counter-spec I think. Are you saying that the RI binds *all* beans into java:comp/env based on their JNDI name? That is wrong: it should only bind those that have been explicitly referenced to in ejb-ref's in the XML. BTW, when you say "lookup of java:/comp/env", is this by an application client or a bean? /Rickard -- Rickard �berg Email: [EMAIL PROTECTED] http://www.telkel.com http://www.jboss.org http://www.dreambean.com =========================================================================== 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".
