[jboss-dev-forums] [Design of JBoss Remoting, Unified Invokers] - Re: Duplicate mbean removal

[scott.stark@jboss.org]

Service lifecycle is independent of existence as an mbean. There still is not enough code here for me to understand what the invoker/connector relationship is. It looks like registration and the jboss service lifecycle are being mixed up here. The question is, what is actually creating the invoker mbean, the Connector?

You can cycle an mbean service through start, stop, start and this should have no impact on whether the service exists as an mbean. The only time a service should be registering an mbean is if its acting as a container that fully owns the mbean; meaning its not exposed to the jboss service deployment layer.


View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4098563#4098563

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4098563