AKostylev wrote:
>That's a pity but exception is stile the same when using Properties.
>
OK, thanks for trying that out. The fact that the behavior was
the same helps isolate the problem. This is looking like a bug in
a piece of our code that does its own internal lookup during
the EJB 3.0 reference processing on the client-side. It should be
using a context that matches the one on which the original lookup
was performed but instead it's internally creating its own
no-arg InitialContext(). Since Resin has overridden the default
naming provider for the JVM, the resulting internal lookup is not
successful.
I've filed an issue to track this bug :
https://glassfish.dev.java.net/issues/show_bug.cgi?id=920
We'll fix this in the trunk and backport it for the 9.0 UR1 release.
Note that it's possible there will be some other conflict with the
Resin environment even after this is fixed but we'll handle that
as necessary. One interim solution is to expose an adapted
2.x Home interface from your EJB and look that up instead.
The lookup for the 2.x Home involves a different path that will
not encounter the same bug.
Thanks for your patience.
--ken
>
>
>>
>>