----- Original Message -----
From: "Valentijn Scholten" <[EMAIL PROTECTED]>
To: "Peter Pontbriand" <[EMAIL PROTECTED]>
Sent: Thursday, March 08, 2001 3:51 AM
Subject: RE: Inconsistent EJB JNDI Locations
> what do you mean just the ejb-name?
>
> So use "MyBean" instead of "java:comp/env/MyBean" ???
>
> This doesn't work either for me!?
Yes, this is what works for us. Assuming that the Entity EJB is deployed
with <ejb-name>MyBean</ejb-name> and that the Session EJB's deployment
descriptor has an <ejb-ref-name>ejb/MyBean</ejb-ref-name>, the home
interface for MyBean is supposed to be found with
'lookup("java:comp/env/ejb/MyBean")'. Unfortunately, this doesn't work, but
rather MyBean is found with 'lookup("MyBean")'.
If the second lookup doesn't work for you, I would suspect your deployment
descriptor(s). Do you have an <ejb-ref> element for the Entity EJB in your
Session EJB's <session> element? Have you tried using the Orion console to
see if your EJBs are both successfully deployed?
> Do you have a complete example of a Session bean createing/looking op an
> entity bean,
> that works/should work on Orion?
Unfortunately, I don't have a handy example outside of our project code base
I could pass along without some major editing, which I simply don't have the
time to do. It sounds like you have the right idea already anyway. Keep at
it, its most likely a small ommission in your deployment descriptor as
mentioned above.
P. Pontbriand
Canlink Interactive Technologies Inc.
