[jboss-user] [Microcontainer] - Re: Ordering a deployer which needs multiple inputs

jaikiran do-not-reply at jboss.com
Sat Mar 14 03:26:48 EDT 2009


"alesj" wrote : "jaikiran" wrote : 
  |   | I believe the ordering of the deploying... 
  |   | 
  | The order of _deployers_ is done based on inputs/outputs.
  | This is not dynamic, it's resolved when a deployer is added per deployment stage.
  | 
Yep. 

"alesj" wrote : 
  | "jaikiran" wrote : 
  |   | But, i still think MC should have handled this differently (not complaining ;-) ). The FinalDeployer was expecting 2 inputs and until the 2 inputs were available, it shouldn't have been invoked.
  | This can be achieved, but then you need to make this as a true dependency item.
  | Which is not a common use case as attachments normally don't come on the fly,
  | but are generated via some deployment flow,
  | which needs to be predictable / consistent.
  | Hence the 'static' natural order via inputs/outputs is perfect.


I agree with the 'static' natural order via inputs/outputs is the correct way. No issues :) However what i meant in my earlier post was something along the following lines:


1) The static ordering (mentioned above) decides the order when the deployer is checked for relevance for deploying a unit - This works currently in MC

2) When the deployer gets picked up in this order, check the "required inputs" for this deployer and also check the "attachments in the unit" being deployed, to see if *all* the required inputs are available. If yes, then the deployer is invoked. If not, then just ignore this deployer for deploying the current unit. Note that this #2 is currently what is missing in MC.


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

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



More information about the jboss-user mailing list