[ http://jira.jboss.com/jira/browse/EJBTHREE-655?page=all ] Carlo de Wolf updated EJBTHREE-655: ----------------------------------- Fix Version/s: EJB 3.0 RC10 - FD (was: EJB 3.0 RC9 - FD) -- 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

[ http://jira.jboss.com/jira/browse/EJBTHREE-655?page=all ] Carlo de Wolf resolved EJBTHREE-655. ------------------------------------ Resolution: Rejected -- 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

[ https://jira.jboss.org/jira/browse/EJBTHREE-655?page=com.atlassian.jira.p... ] 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 -- 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

[ https://jira.jboss.org/jira/browse/EJBTHREE-655?page=com.atlassian.jira.p... ] Carlo de Wolf commented on EJBTHREE-655: ---------------------------------------- Note that only bullet #1 is implemented. The other bullets are not supported. -- 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