[
https://jira.jboss.org/jira/browse/JBAS-5302?page=com.atlassian.jira.plug...
]
Galder Zamarreno commented on JBAS-5302:
----------------------------------------
As indicated via the support portal, the JNDI method is still a valid solution but with
limitations.
It works when the client is located in the same network or same machine and both are
accessing
via the same place.
What we need to do though is fix the invoker method so that it works properly, so the aim
of this
JIRA will be precisely that, make the legacy invoker method work again.
StatefulHandleImpl is not portable from client A to client B
------------------------------------------------------------
Key: JBAS-5302
URL:
https://jira.jboss.org/jira/browse/JBAS-5302
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: EJB2
Affects Versions: JBossAS-4.2.3.GA, JBossAS-5.0.0.GA
Reporter: Bernd Zeitler
Assignee: Alexey Loubyansky
Fix For: JBossAS-5.1.0.Beta1
The StatefulHandleImpl holds the jndiEnv after creation and uses these properties in
getEJBObject.
Since jndiEnv is not transient, the properties used on client A are passed within the
handle to Client B. This can lead to problems when these two clients use different
properties (e.g. different host names for the same physical machine or a different
implementation of the NamingContextFactory).
Example: client A resides on the JBoss server and realizes remote access to the server
using localhost within his URL. A handle, created on this client and passed to client B,
which resides on another machine, can not be used to get the EBJ object, since even this
clients tries to connect to the server using a lookup on localhost.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira