Explicit depends tag on the bean definitions for the deploye

[anil.saldhana]

Scott mentioned that there is no need to add explicit depends tag on the bean definitions for the deployers.

Eg:
The EJB2xDeployer has a depends tag on SecurityDeployer.
The WebServiceDeployerEJB has a depends tag on EJB2xDeployer and EJB3Deployer.


Should we be getting rid of these soon?

[alesj]

Ages ago :-) we added inputs/outputs which naturally order the deployers for a certain stage.

I think MarkN just added deployers user guide section in the docs:
- http://labs.jboss.com/files/jbossmc/docs/2.0.x/userGuide/index.html
Check those for more details.

Or see my MC presentation from Zurich JUG:
- http://anonsvn.jboss.org/repos/jbossas/projects/presentations/trunk/microcontainer/

So, if you ask me, drop it. :-)

[anil.saldhana]

I know about the setInputs and setOutputs methods added into the deployers. But where do these methods indicate that they will handle dependency? ;)

I was of the impression that these methods handled the metadata type passed to the deployer and the type of the attachment as output.

I will take a look at your MC presentation. :)

I will scan the files for depends tags next week and remove them. :)

[alesj]

But where do these methods indicate that they will handle dependency? ;)

In the initial deployers design forum post for sure. ;-)

If there is no such (simple) indication in the code/javadocs, then we should definitely add a note.

They don't handle generic dependency, but this is somehow equivalent to depends dependency. It's just that the info is much more natural + being already present also helps. :-)

I was of the impression that these methods handled the metadata type passed to the deployer and the type of the attachment as output.

That too. ;-)