You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwebbeans.apache.org by "Mark Struberg (JIRA)" <ji...@apache.org> on 2011/03/24 23:28:05 UTC

[jira] [Resolved] (OWB-417) BaseEjbBean.destroyComponentInstance() should call direct container remove API, not call an @Remove annotated method

     [ https://issues.apache.org/jira/browse/OWB-417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Struberg resolved OWB-417.
-------------------------------

    Resolution: Fixed

seems like this got resolved.

> BaseEjbBean.destroyComponentInstance() should call direct container remove API, not call an @Remove annotated method
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: OWB-417
>                 URL: https://issues.apache.org/jira/browse/OWB-417
>             Project: OpenWebBeans
>          Issue Type: Bug
>          Components: Java EE Integration
>            Reporter: Eric Covener
>            Assignee: Gurkan Erdogdu
>             Fix For: 1.1.0
>
>   Original Estimate: 16h
>  Remaining Estimate: 16h
>
> BaseEjbBean.destroyComponentInstance() should call direct container remove API, not call an @Remove annotated method. 
> "When the destroy() method is called, and if the underlying EJB was not already removed by direct invocation of a remove method by the application, the container removes the stateful session bean. The @PreDestroy callback must be invoked by the container."
> Calling business methods with a side effect of the container removing the EJB does not seem to be what is intended.   
> Completing this ticket requires an API in OpenEJB to remove a SFSB given just the reference the container gave us earlier.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira