This is completely false. The java:comp/env context is local to J2EE components and can be used to isolate code from deployment specific names. The global JNDI can be used as it is on the client in the server. Read about the enterprise naming context and ejb-ref in any standard EJB book for an explanation.
xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Eric Kaplan" <[EMAIL PROTECTED]> To: "Mike Kenyon" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Wednesday, March 06, 2002 2:57 PM Subject: RE: [JBoss-user] Newbie JNDI Question > I remember way back originally reading in the documentation that there was a > difference > in jboss in the way ejbs were looked up on the server versus a client. On > the server, you > had to use "java:comp/env/ejbname" whereas on the client it was simply > "ejbname". At the > time, I remember thinking this was at odds with every example I had seen > (normally there > is no differentiation between naming on the client and the server. My fear > is that we'll have > to port to a server other than jboss and I'll have the opposite problem from > you. What worked > on jboss won't work on other servers. All my client code (luckily its all > in one place) that > tries to find ejbs without the comp/env will fail... > > Can someone please confirm or deny this difference? > > Thanks > > Eric > _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
