The java:comp/env name space is reserved for a J2EE components environment values. The values will be different in each J2EE component. You add bean references in this environment using ejb-ref elements in the deployment descriptor.
A client program or another EJB would not be able to access another bean using the java:comp/env name space except as noted above. I'm not familiar with the RI server, but it must implicitly or explicitly bind your beans JNDI names somewhere in the JNDI name space available to all contexts. Most servers bind beans implicitly based on the ejb-name element in your deployment descriptor. --Victor Kenny Macleod wrote: > > I can't see anything wrong in your attempt, as long as you > > use the global > > namespace to which you have deployed your EJB and that you have the > > com.sun.jndi.cosnaming.CNCtxFactory class on your classpath, > > What do you mean by "global namespace", exactly? Are you referring to the > "java:comp/env" namespace? Does the client have to use that name > explicitly, or is it implicit? > > cheers > kenny =========================================================================== 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".
