[jboss-dev-forums] [Design of OSGi Integration] - Re: Facade Questions

[johnbailey]

"alesj" wrote : When mapping Controller states to bundle states, you should consider DeploymentStages, since those are probably the one's we're after.
  | Those mentioned before are POJO centric.
  | 
  | I would do something like this:
  | ERROR --> UNINSTALLED
  | NOT_INSTALLED --> INSTALLED (this one looks funny, but it's technically ok :-)
  | CLASSLOADING --> RESOLVED
  | REAL --> STARTING / STOPPING
  | INSTALLED --> ACTIVE

It seems like the DeploymentStage isn't available through the DeploymentUnit or Controller context.   I checked all the references of the DeploymentStage and didn't see it attached.   It looks like the DeployersImpl translates the ControllerState into a DeploymentStage, which determines the Deployer to use. 



  | DeploymentControllerContext deploymentControllerContext = (DeploymentControllerContext) context;
  |       String stageName = toState.getStateString();
  |       
  |       DeploymentContext deploymentContext = deploymentControllerContext.getDeploymentContext();
  |       try
  |       {
  |          List<Deployer> theDeployers = getDeployersList(stageName);
  | ...

Am I missing something?  I will use the corrisponding ControllerStates for now, and we can move to the DeploymentStage if there is a way to get it.  The only thing I don't see is the ControllerStates is the CLASSLOADING stage.
 


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

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