[jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1846) CLONE -Injected SessionContext became invalid after passivation

[Carlo de Wolf (JIRA)]

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

Carlo de Wolf resolved EJBTHREE-1846.
-------------------------------------

    Resolution: Cannot Reproduce Bug


StatefulSessionContextImpl is the implementation of SessionContext that is injected into the bean. When getBusinessObject is called after activation it'll reinstantiate a delegate in getDelegate referencing the container.

BaseSessionContext is a class from AS 4 and no longer in use. If you need help on AS 4 post in the forums or file a support case.

> CLONE -Injected SessionContext became invalid after passivation
> ---------------------------------------------------------------
>
>                 Key: EJBTHREE-1846
>                 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1846
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: AS 5.0.0.CR1
>         Environment: JBoss AS 5.1.0DR
>            Reporter: Krashan Brahmanjara
>            Assignee: Carlo de Wolf
>
> I have SFSB with SessionContext injected as:
> @Resource
> private SessionContext ctx;
> Some of my SFSB's methods use ctx.getBusinessObject(). After passivation and activation of bean ctx.getBusinessObject() produces NPE.
> While debugging I discover that ctx is instance of org.jboss.ejb3.BaseSessionContext. In it's writeExternal() / readExternal() it loose baseContext, which is needed for getBusinessObject() invocation.

-- 
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