[jboss-jira] [JBoss JIRA] Updated: (JBAS-5302) StatefulHandleImpl should be able to use legacy invoker method to retrieve EJBObject

[Galder Zamarreno (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBAS-5302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Galder Zamarreno updated JBAS-5302:
-----------------------------------

              Summary: StatefulHandleImpl should be able to use legacy invoker method to retrieve EJBObject  (was: StatefulHandleImpl is not portable from client A to client B)
        Fix Version/s: JBossAS-5.1.0.Beta1
    Affects Version/s: JBossAS-5.0.0.GA


> StatefulHandleImpl should be able to use legacy invoker method to retrieve EJBObject
> ------------------------------------------------------------------------------------
>
>                 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: Galder Zamarreno
>             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