[jboss-dev] WARNING: Update to new deployers

[Adrian]

On Fri, 2007-06-29 at 15:39 +0200, Carlo de Wolf wrote:
> Done, the order looks pretty good now.

Thanks.

> Except maybe the Ejb3ClientDeployer it does run after the
> EJBStage2Deployer, but not by design. Hmm, it bypasses the meta data to
> look for beans and uses the internal registry. Ah, because it depends on
> meta data from other deployment units.
> How does this work now with ear deployments? Does an attachment fall all
> the way through the deployers first or does each deployer go through
> every available attachment first?

If I understand your question correctly.

It is width first at the deployment stage level
i.e. all classloaders get constructed before it moves onto
the aop/real deployer stages.

But depth first within a stage. i.e. all deployers for that stage
are run per context then it moves onto the next context.
-- 
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx