@Service @Management & JMX

[wolfc]

I'm looking at the following issues:
http://jira.jboss.com/jira/browse/EJBTHREE-323
http://jira.jboss.com/jira/browse/EJBTHREE-606
http://jira.jboss.com/jira/browse/EJBTHREE-631

I have created some unit tests and to my surprise the @Service and @Management are working except for lifecycle calls (606). It appears that these are normally called by the the ServiceController, but this is a MBean.
Currently I'm lost in the forest around MCKernelAbstraction & JMXKernelAbstraction, but @Management is dependant on JMX, right?
If so 631 is unsolvable.

Shall I resolve 323 as done?

[wolfc]

Got lifecycle working.

Are any of the lifecycle methods (create, start, stop, destroy) optional?

[starksm64]

All of the lifecycle calls are optional in the legacy jmx service contract as an mbean is wrapped in a proxy that only delegates the lifecycle calls if there is a mapping. The underlying bean may not have a corresponding lifecycle method, or it may map the method to another name (start mapped to go for example).

[wolfc]

Okay thanks.

For the moment I'll just implement it with the 4 basic methods being optional.