[jboss-dev-forums] [Deployers on JBoss (Deployers/JBoss)] - Re: Deployer order solely based on inputs/outputs now?

[adrian@jboss.org]

"bill.burke at jboss.com" wrote : Ok, after talking to Ales I think i get it.
  | 
  | There would be:
  | 
  | EJBParserDeployer
  | EJBDescribeDeployer
  | EJBComponentDeployer
  | 
  | So, if my EJBDescribeDeployer is part of the DESCRIBE stage, it should happen after EVERY DeploymentUnit has gone through Parsing, right?

This can only work if you add the dependencies to the deployment rather than
the ejb instance. The same way OSGi dependencies work.

It has to be real dependencies, no "flow" or ordering of deployers is going to
solve the problem where deployments are deployed piecemeal, i.e. not at
the same time, or even worse  (more complicated)

* redeployed
* one of the transient dependencies is missing and deployed later

The real solution is to create your own DependencyItem implementation 
like I've been telling you to over a year now.

The JNDI plugin to the MC registry is stupidly inefficient, it's ok as an
early hack to try out the idea.

A DependencyItem that does the same thing, but only for those you expect to
be JNDI dependencies is much more efficient. 

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

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