-
30. Re: Facade Questions
"adrian@jboss.org" wrote:
We can add a
DeploymentStage DeployerClient::getDeployerStage(String deploymentName);
which will probably give you what you want?
By the way, we'll probably have to revisit this, since probably what is really
required is notifications of the stage/state changes.
You'll then be able to manage the OSGi state from that. -
31. Re: Facade Questions
"adrian@jboss.org" wrote:
By the way, we'll probably have to revisit this, since probably what is really
required is notifications of the stage/state changes.
I think we need to introduce some more event propagation through core MC code.
We currently only do it when pojo gets (un)registered.
Plus making event emmiter more pluggable.
Not just having single instance for all our controller contexts.
Or we still could have just a single instance, but then the filter should be automatically added to filter our kernel contexts from jmx or deployment or aliases or ... -
32. Re: Facade Questions
For this case, we should just make DeployersImpl an emitter
of some DeploymentStage event.
That way it can include information related to the deployment
which a generic event can't do (the listener would have to filter for
relevant events and then do lookups to get information).