[jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-655) Refactor @Service beans
[ http://jira.jboss.com/jira/browse/EJBTHREE-655?page=comments#action_12343600 ]
Carlo de Wolf commented on EJBTHREE-655:
----------------------------------------
The @Management interface must be registrered into the controller for @Depends to work.
Else the dependency will never be satisfied from the controller's point of view.
That means that the controller will call create/start/stop/destroy on the @Management
interface, resulting in calls to the container which has already done that.
At that point the create/start/stop/destroy methods in both @Management and the bean
become a double edged sword because either it's the management interface getting
c/s/s/d-ed or it's the container getting c/s/s/d-ed.
Refactor @Service beans
-----------------------
Key: EJBTHREE-655
URL: http://jira.jboss.com/jira/browse/EJBTHREE-655
Project: EJB 3.0
Issue Type: Task
Reporter: Bill Burke
Assigned To: Carlo de Wolf
Fix For: EJB 3.0 RC10 - FD
Refactor @Service beans to fix a number of problems:
* magic methods for lifecycle methods:
- create/start/stop/destroy
* lifecycle methods are not required to be in @Management (MBean) interface.
* @Management interface is not registered with the ServiceController (Controller in MC
land). It *IS* registered as a regular MBean though.
* If lifecycle methods exist on @Management interface, they must be intercepted on the
container so that the appropriate Controler start/stop is done on the container. This
would mean that you have to specify a <bind> in the Service aspect domain in
ejb3-interceptors-aop.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira