[cdi-dev] [JBoss JIRA] (CDI-275) clarify behavior of stateful beans (EJB) and cdi scopes

[Romain Manni-Bucau (JIRA)]

    [ https://issues.jboss.org/browse/CDI-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724517#comment-12724517 ] 

Romain Manni-Bucau edited comment on CDI-275 at 10/6/12 10:33 AM:
------------------------------------------------------------------

yes this part explains it but something is still not very clear IMO: should a remove method be mandatory or does it work without any @Remove method?

there is nothing blocking to make it optional technically since it was needed only to be able to run the remove hook but since we manage the lifecycle now we can do it internally

so i think a sentence should be added to clarify it

wdyt?
                
      was (Author: rmannibucau):
    yes this part explains it but something is still not very clear IMO: is a remove method mandatory?

there is nothing blocking to make it optional technically since it was needed only to be able to run the remove hook but since we manage the lifecycle now we can do it internally

so i think a sentence should be added to clarify it

wdyt?
                  
> clarify behavior of stateful beans (EJB) and cdi scopes
> -------------------------------------------------------
>
>                 Key: CDI-275
>                 URL: https://issues.jboss.org/browse/CDI-275
>             Project: CDI Specification Issues
>          Issue Type: Clarification
>            Reporter: Romain Manni-Bucau
>
> EJB specification let think the Stateful beans should be user managed so what about the integration with CDI and in particular the @Remoe methods
> I think it is not so clear in the current specification and that @requestScoped (or session...) on a statful bean should be clarified

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira