-
1. Re: Relative order of deployers to other deployers
bill.burke Nov 2, 2006 4:40 PM (in response to starksm64)Why can't you just create a dependency in the bean definition and ensure that the bean will comein the same relative order number but after any of that level.
-
2. Re: Relative order of deployers to other deployers
starksm64 Nov 2, 2006 5:39 PM (in response to starksm64)That does not help if I want to be ahead of another deployer. I still depend on the other deployer, but want to modify its input. Deployers can exist independent of the kernel anyway and need to be ordered in that case as well.
-
3. Re: Relative order of deployers to other deployers
kabirkhan Nov 2, 2006 7:14 PM (in response to starksm64)How about a precedence bean that is injected into the main deployer, and defines relative ordering between all the deployers that would otherwise be at the same level. Isn't the main deployer what maintains the order of all the deployers?
-
4. Re: Relative order of deployers to other deployers
starksm64 Nov 2, 2006 7:32 PM (in response to starksm64)"kabir.khan@jboss.com" wrote:
How about a precedence bean that is injected into the main deployer, and defines relative ordering between all the deployers that would otherwise be at the same level. Isn't the main deployer what maintains the order of all the deployers?
Yes, its the MainDeployerImpl that uses standard collections and the Deployer.COMPARATOR to order deployers based on the relativeOrder value currently. Allowing for the injection of the comparator would allow for alternate ordering mechanisms. -
5. Re: Relative order of deployers to other deployers
adrian.brock Nov 4, 2006 9:33 AM (in response to starksm64)Like I said on a different thread, my preference is for each deployer to
define its input/output metadata. This will lead to a natural (relative) ordering.
The relative order is still required however to define when each step is taken
(relative to other deployers that are not in the same chains).
e.g. We always classloaders to be created together even if they are
different implementations for different deployer chains.