[jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-992) The javax.ejb.SessionContext.SessionContext.getEJBLocalObject and javax.ejb.SessionContext.SessionContext.getEJBObject implementations returns always new proxies for EJB3

Tue Jun 12 16:46:11 EDT 2007

     [ http://jira.jboss.com/jira/browse/EJBTHREE-992?page=all ]

William DeCoste closed EJBTHREE-992.
------------------------------------

    Fix Version/s: Branch_4_2
       Resolution: Duplicate Issue
         Assignee: William DeCoste

> The javax.ejb.SessionContext.SessionContext.getEJBLocalObject and javax.ejb.SessionContext.SessionContext.getEJBObject  implementations returns always new proxies for EJB3
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-992
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-992
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - Patch 1
>            Reporter: Roland Räz
>         Assigned To: William DeCoste
>             Fix For: Branch_4_2
>
>
> The javax.ejb.SessionContext.SessionContext.getEJBLocalObject and javax.ejb.SessionContext.SessionContext.getEJBObject  implementations returns always new proxies. The api states "Obtain a reference to the EJB object that is currently associated with the instance". My interpretation is that this api should always return a proxy to the current instance. At least for stateful session beans a proxy for the actual session bean should be returned else the bean instance has no mean to return a reference to itself (except when the stateful session bean is passed as parameter).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira