Author: dan.j.allen Date: 2009-11-02 15:44:34 -0500 (Mon, 02 Nov 2009) New Revision: 4561 Modified: doc/trunk/reference/en-US/gettingstarted.xml doc/trunk/reference/en-US/intro.xml Log: clarify remove method Modified: doc/trunk/reference/en-US/gettingstarted.xml =================================================================== --- doc/trunk/reference/en-US/gettingstarted.xml 2009-11-02 20:37:51 UTC (rev 4560) +++ doc/trunk/reference/en-US/gettingstarted.xml 2009-11-02 20:44:34 UTC (rev 4561) @@ -1848,9 +1848,10 @@ }]]></programlisting> <para> - [CHECK is this still accurate?] Since this is a stateful session bean, we have to have a remove method. The - bean manager will call the remove method for you when the bean is destroyed; in this case at the end of the - request. + <!-- QUESTION is this still a requirement in EJB 3.1? --> + Since this is a stateful session bean, we have to have a remove method. The container will call the remove + method for you when the bean is destroyed; in this case at the end of the request. (Keep in mind that since + this bean is not dependent-scoped, the application is not allowed to invoke the remove method). </para> <para> Modified: doc/trunk/reference/en-US/intro.xml =================================================================== --- doc/trunk/reference/en-US/intro.xml 2009-11-02 20:37:51 UTC (rev 4560) +++ doc/trunk/reference/en-US/intro.xml 2009-11-02 20:44:34 UTC (rev 4561) @@ -707,7 +707,7 @@ Stateful session beans can define a no arguments remove method, annotated <literal>@Remove</literal>, that is used by the application to indicate the instance should be destroyed. However, in a CDI environment, this method can only be executed by the application if the bean is dependent-scoped. Otherwise, it's illegal for - the application to invoke this method. + the application to invoke this method because the container is controlling its lifecycle. </para> <para>