This issue had been risen before, but was never fixed.
The problem is, *HandleImpl classes, such as
StatefulHandleImpl, in their getEJBObject() contain
such a code:
...
ContainerRemote container = (ContainerRemote) new
InitialContext().lookup("invokers/"+name);
...
But wait!
Enterprise JavaBeans™ Specification, v1.1,
chapter 5.5 says:
"A session object handle can be held beyond the life
of a client process by serializing the handle to
per-sistent
store. When the handle is later deserialized, the
session object it returns will work as long as the
session object still exists on the server."
In my understanding it means client process is able
to getEJBObject() no matter what system properties for
InitialContext it uses, EJB object is a function of
handle, not of both handle and client process.
Right?
But in current implementation of *HandleImpl different
client process will get different EJB objects
from the same handle
(or most probably will fail to get any),
if they have different system properties for
InitialContext.
Is JBoss truly EJB1.1 compliant?
Hope this didn't sound like a blame :)
Thank you all for your time,
Andris Birkmanis
__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
