[jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-655) Refactor @Service beans

[Andrew Lee Rubinger (JIRA)]

     [ https://jira.jboss.org/jira/browse/EJBTHREE-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Lee Rubinger updated EJBTHREE-655:
-----------------------------------------

    Fix Version/s: 1.0.0-Beta12
                       (was: AS 4.2.0 GA)
      Description: 
Refactor @Service beans to fix a number of problems:

* magic methods for lifecycle methods:
  - create/start/stop/destroy
* @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

  was:
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






Updated to reflect current state of affairs

> Refactor @Service beans
> -----------------------
>
>                 Key: EJBTHREE-655
>                 URL: https://jira.jboss.org/jira/browse/EJBTHREE-655
>             Project: EJB 3.0
>          Issue Type: Task
>            Reporter: Bill Burke
>            Assignee: Andrew Lee Rubinger
>             Fix For: 1.0.0-Beta12
>
>
> Refactor @Service beans to fix a number of problems:
> * magic methods for lifecycle methods:
>   - create/start/stop/destroy
> * @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: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira