"scott.stark(a)jboss.org" wrote :
| "scott.stark(a)jboss.org" wrote :
| | If an operation is invoked on the KernelBusRuntimeComponentDispatcher and passed
down to its KernelBus implementation, and that operation corresponds to a component
lifecycle operation such as start/stop, is this being handled correctly in terms of
dependencies?
| So the answer is yes
|
If I understand the question right, the answer should be _no_.
As apart from invoking that property/attribute or method/operation,
we don't do anything extra wrt dependencies.
It might be an impl detail of the service you're invoking,
but we simply do reflection invocation or in case of mbeans "talk" to mbean
server.
But it shouldn't be too big of a problem to properly react to lifecycle methods/ops.
Since all the info we need is already in underlying Bean/ServiceMetaData,
we would only require additional abstraction on top of InvokeDispatchContext.
e.g. do start
KernelControllerContext --> BeanMetaData --> Start LifecycleMetadata
* if already past start == ignore
* else try to move to Start state, (optionally) fail if not being able to get there
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4232466#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...