[jboss-dev-forums] [Design of POJO Server] - MainDeployerImpl process managed deployment

alesj do-not-reply at jboss.com
Fri Oct 5 10:58:28 EDT 2007


Just something I noticed when looking how to get a hold of runtime component's name in true OO fashion. :-)

Is this done on purpose - that we are skipping process on 2nd level context.
Since we do do getChildren on top contexts, and then immediately getChildren on those child contexts:

  |    public ManagedDeployment getManagedDeployment(String name) throws DeploymentException
  |    {
  |       DeploymentContext context = getDeploymentContext(name);
  |       if (context == null)
  |          throw new IllegalArgumentException("Context not found: " + name);
  |       
  |       Map<String, ManagedObject> rootMOs = getManagedObjects(context);
  |       ManagedDeployment root = mgtDeploymentCreator.build(context.getDeploymentUnit(), rootMOs, null);
  |       for (DeploymentContext childContext : context.getChildren())
  |       {
  |          processManagedDeployment(childContext, root);
  |       }
  |       return root;
  |    }
  | 
  |    protected void processManagedDeployment(DeploymentContext context, ManagedDeployment parent)
  |       throws DeploymentException
  |    {
  |       for (DeploymentContext childContext : context.getChildren())
  |       {
  |          DeploymentUnit childUnit = childContext.getDeploymentUnit();
  |          Map<String, ManagedObject> childMOs = getManagedObjects(childContext);         
  |          ManagedDeployment childMD = mgtDeploymentCreator.build(childUnit, childMOs, parent);
  |          processManagedDeployment(childContext, childMD);
  |       }
  |    }
  | 

There is no lookup on processManagedDeployment context param.

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

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



More information about the jboss-dev-forums mailing list