"scott.stark(a)jboss.org" wrote :
| 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.
|
This could be achieved.
OK, it would still depend on exactly what you wanted to do - no cyclic/fork states.
You can do this atm.
Add these two new states (DESCRIBE_CLUSTERED, DESCRIBE_SINGLETON) to Controller.
Then when you install a bean that would use any of those two states, you need to push him
your own ControllerContextActions impl.
e.g. our alias handling
| Map<ControllerState, ControllerContextAction> map =
Collections.<ControllerState,
ControllerContextAction>singletonMap(ControllerState.INSTALLED, new
AliasControllerContextAction());
| ControllerContextActions actions = new AbstractControllerContextActions(map);
| install(new AliasControllerContext(alias, original, actions));
|
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4154547#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...