Belatedly replying to my own posting, for the sake of others having trouble
looking up env-entries:
Make sure all the ejb-refs in the same EJB declaration in your ejb-jar.xml
reference valid classes. I've noticed that Orion fails to explicitly
indicate that an ejb-ref is invalid. Everthing will appear to successfully
deploy, but the Environment Naming Context for the EJB with the invalid
ejb-ref will not contain any of the env-entries, and Home Interface lookups
(for all ejb-refs, not just the bad one) will fail the first time lookup()
is called - but not subsequently!?!
The problem only became evident when interating over the the results of a
listBindings() call on the ENC using hasMore() and next() - which throw
exceptions - rather than hasMoreElements() and nextElement() - which don't.
In short, if you're having trouble looking up env-entries, suspect a bad
ejb-ref as one of the possible culprits.
P. Pontbriand
Canlink Interactive Technologies, Inc.
----- Original Message -----
From: "Peter Pontbriand" <[EMAIL PROTECTED]>
To: "Orion-Interest" <[EMAIL PROTECTED]>
Sent: Wednesday, December 13, 2000 5:51 PM
Subject: <ENV-ENTRY> Broken in orion 1.4.4?
> Is there a problem with Orion 1.4.4's interpretation on the ejb-jar.xml
> <env-entry> tag? Nothing we put in such a tag is ever available in a
Context
> lookup() call whether we prefix with "java:comp/env" or not.
>
> P. Pontbriand
> Canlink Interactive Technologies Inc.
>
>
>
