Title: SV: Problems with JNDI lookups of ejb-ref-name defined in application-client.xml from a client application...
Did you try looking up java:comp/env/ejb/id ?
WR
-Ursprungligt meddelande-
Från: Alex Paransky [mailto:[EMAIL PROTECTED]]
Skickat: den 15 mars 2001 14:11
Till:
try: new InitialContext().lookup("java:comp/env/ejb/id");
- Original Message -
From: "Alex Paransky" [EMAIL PROTECTED]
To: "Orion-Interest" [EMAIL PROTECTED]
Sent: Thursday, March 15, 2001 10:10 PM
Subject: Problems with JNDI lookups of ejb-ref-name defined in
application-client.xml
Hia guys,
Here is a bit of my experience with this stuff - I found out that if I
have a regular Java client it's the ejb-jar.xml's ejb-name that is
being used to lookup the bean name without the comp/env. The comp/env is
only to be used by J2ee clients i.e. servlets or JSPs. For the J2EE
Just a sidenote, maybe it's your problem. From page 377 of Enterprise
JavaBeans, 2nd Edition (Oreilly):
"The ejb-link value must match one of the ejb-name values declared in the same
deployment descriptor."
That is, it's only valid if you're using an ejb-jar.xml to define multiple
beans.
Jeff
I
tried that before, and got the following exception:
Exception in thread "main" javax.naming.NamingException: java:comp/env
namespace is only available from within a J2EE
component at
com.sun.enterprise.naming.java.javaURLContext.getComponentContext(javaURLContext.java:392)
at
I have a client application which has META-INF with the following
application-client.xml definition:
application-client
ejb-ref
ejb-ref-nameejb/id/ejb-ref-name
ejb-ref-typeSession/ejb-ref-type
homecom.indnet.model.id.IdSessionHome/home
remotecom.indnet.model.id.IdSession/remote
