[jboss-dev] WARNING: Update to new deployers

[Carlo de Wolf]

Done, the order looks pretty good now.
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?

Carlo

On Fri, 2007-06-29 at 14:03 +0200, Adrian wrote:
> Ok, can you make those changes?
> You need to change the setInputs/Outputs for those deployers.
> 
> The deployers have a number of methods for adding
> inputs/outputs based on either class names or string names.
> http://anonsvn.jboss.org/repos/jbossas/projects/microcontainer/trunk/deployers-spi/src/main/org/jboss/deployers/spi/deployer/helpers/AbstractDeployer.java
> 
> NOTE: There is a difference between setInput and setInputs/addInput.
> The first is a requirement, i.e. the attachment must exist
> for the deployer to be invoked,
> the second only defines the ordering. i.e. they are optional.
> 
> Thanks,
> Adrian
> 
> On Fri, 2007-06-29 at 13:32 +0200, Carlo de Wolf wrote:
> > The logs shows how it's supposed to be. :-)
> > 
> > I'm missing the AppClientParsingDeployer. My guess is it will be run
> > before the AppClientScanningDeployer (as it is now, but not how it
> > ultimately should be).
> > 
> > The icky part is the EJBRegistrationDeployer telling the
> > SecurityDeployer to shut up (EJBRegistrationDeployer at line 167). This is
> > because we don't have a EjbScanningDeployer yet, so the SecurityDeployer
> > ignores annotations. Somewhere in the EJB 3 code it creates it's own
> > Jacc policy and stuff. For now this would mean the SecurityDeployer
> > should go after EJBRegistrationDeployer for icky reasons.
> > The output of EJBRegistrationDeployer is Ejb3Deployment +
> > "org.jboss.deployment.security.ignoreMe" and the input of
> > SecurityDeployer should be: WebMetaData | ApplicationMetaData |
> > BeanMetaData + "org.jboss.deployment.security.ignoreMe".
> > 
> > Carlo
> > 
> > On Fri, 2007-06-29 at 13:06 +0200, Adrian wrote:
> > > Carlo, can you validate that the deployment ordering
> > > shown in the DEBUG message here is correct for EJB3
> > > http://www.jboss.com/index.html?module=bb&op=viewtopic&t=112181&postdays=0&postorder=asc&start=11
> > > 
> > > I sort of guessed it from what attachments the deployers were
> > > getting/adding. :-)
> > > 
> > > On Fri, 2007-06-29 at 12:21 +0200, Adrian wrote:
> > > > On Fri, 2007-06-29 at 11:14 +0200, Carlo de Wolf wrote:
> > > > > You're welcome. :-)
> > > > > 
> > > > > Just out of curiosity, what did you test?
> > > > > (http://wolf.nerdnet.nl:8180/hudson/job/JBoss_EJB3_TRUNK/13/ )
> > > > > 
> > > > 
> > > > Just the basic stateless and entity standup tests.
> > > > 
> > > > > Meow,
> > > > > 
> > > > > Carlo
> > > > > 
> > > 
> > 
> > _______________________________________________
> > jboss-development mailing list
> > jboss-development at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/jboss-development