Yes, each Deployer implementation calls setStage(...) to indicate which stage of deployment it should be considered a candidate. There's a variety of base deployers you can build from, which imply the stage. For instance, there's AbstractParsingDeployer which sets the stage to PARSE. Then there's AbstractParsingDeployerWithOutput which designates it'll produce some object (MetaData or other attachments) as the result of the parse.
Based upon available inputs (files, directories, resources or MetaData) it may fire its deploy() and produce more MetaData or alter existing MetaData (or just take an action and produce no meta-data at all). Within each stage, your deployers are ordered, so you can wedge things before or after existing deployers to change how things ultimately get processed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4177184#4177184 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4177184 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
