Author: dan.j.allen Date: 2009-11-03 16:57:11 -0500 (Tue, 03 Nov 2009) New Revision: 4638 Modified: doc/trunk/reference/en-US/gettingstarted.xml Log: more notes about remove method Modified: doc/trunk/reference/en-US/gettingstarted.xml =================================================================== --- doc/trunk/reference/en-US/gettingstarted.xml 2009-11-03 21:47:49 UTC (rev 4637) +++ doc/trunk/reference/en-US/gettingstarted.xml 2009-11-03 21:57:11 UTC (rev 4638) @@ -1844,10 +1844,11 @@ }]]></programlisting> <para> - <!-- 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). + Since this is a stateful session bean, you can include an optional <literal>@Remove</literal> method, which the + container will call 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 forbidden to invoke the remove method). Since + CDI is integrated into the container, it does not need this method to operate correctly. If the method's empty, + just get rid of it. </para> <para>