[jboss-dev-forums] [Design of POJO Server] - Re: Controlling deployments via a barrier bean

[scott.stark@jboss.org]

I don't think a dependency is the way this should be handled as its not an optional dependency. Your using a dependency to try to identify the singleton bean in the cluster. Really we don't want the unelected singleton beans to be exposed as available for installation as runtime components.

To properly handle this we would need the ability to expand the states for the component in question to allow for alternate DESCRIBE, DESCRIBE_CLUSTERED, DESCRIBE_SINGLETON states depending on the cluster metadata associated with the bean. Currently the mc state machine does not allow for this choice type of state transition. I have not worked much with the lower level state manipulation so I could also be talking out of my ass, but I think this is the proper way to do it.

Given I don't believe there is proper mc support for this, how to do it? I'm not sure. Any idea I have would mix deployer and kernel bean state management behavior. Need some feedback from Adrian/Ales.


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

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