[ https://issues.jboss.org/browse/CDI-275?page=com.atlassian.jira.plugin.sy... ] Mark Struberg commented on CDI-275: ----------------------------------- guess that 3.2.1. "EJB remove methods of session beans" answers this {quote} If a session bean is a stateful session bean: • If the scope is @Dependent, the application may call any EJB remove method of a contextual instance of the session bean. • Otherwise, the application may not directly call any EJB remove method of any contextual instance of the session bean. If the application directly calls an EJB remove method of a contextual instance of a session bean that is a stateful session bean and declares any scope other than @Dependent, an UnsupportedOperationException is thrown. If the application directly calls an EJB remove method of a contextual instance of a session bean that is a stateful session bean and has scope @Dependent then no parameters are passed to the method by the container. Furthermore, the container ignores the instance instead of destroying it when Contextual.destroy() is called, as defined in Section 7.3.2, “Lifecycle of stateful session beans”. {quote} -- 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

[ https://issues.jboss.org/browse/CDI-275?page=com.atlassian.jira.plugin.sy... ] 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? -- 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

[ https://issues.jboss.org/browse/CDI-275?page=com.atlassian.jira.plugin.sy... ] Pete Muir updated CDI-275: -------------------------- Fix Version/s: 1.1 (Proposed) -- 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

[ https://issues.jboss.org/browse/CDI-275?page=com.atlassian.jira.plugin.sy... ] Pete Muir resolved CDI-275. --------------------------- Resolution: Done -- 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