[jboss-dev-forums] [Design of POJO Server] - Re: EJB/War deployer ordering problem

[adrian@jboss.org]

"alesj" wrote : "scott.stark at jboss.org" wrote : I don't think we should have to do that? The deployment context state should not reach DeploymentState.DEPLOYED unless all its components are installed, right?
  |   | 
  | Hmm, I don't think we currently introduce any dependencies between deployment context and its components.
  | I'll have a look, but I don't remember seeing any dependency items being put on DeploymentControllerContext.
  | 

If any sub deployment "fails" then the whole deployment (top level
and subdeployments) is unravelled.

But that is different from a dependency being missing.
That is just something that can be satisifed by deploying the missing dependency.

It the ServiceMetaData that represents the war that should have the depends
not the deployment context.

You're going to get into all sorts of cirucular reference problems if you want
the war to add dependencies to the deployment context that is a reference
to an ejb in the same ear.

The DeploymentControllerContext is per top level deployment,
you can't move individual subdeployments to different deployment stages,
the whole thing moves together (including uninstalling to the ERROR stage
if one of the subdeployments produces an error).

e.g. war -> depends -> ejb1

my.ear -> myejbs.jar -> ejb1
my.ear -> my.war -> servlet1 -> ejb-ref -> ejb1

There is only one DeploymentControllerContext for my.ear
so making my.ear depend on ejb1 is a cirucular reference that will
never be satisied.

i.e. my.ear won't reach the REAL stage until ejb1 is installed
ejb1 won't be installed because my.ear never reaches the REAL stage

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

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