Apparently, the trick is to specify multiple constraints. Constraints are
very loose; after means 'somewhere after' rather than 'immediately after',
so just specify as many as are important to you.
Someone more informed can weigh in whether you can mix specific constraints
with wildcards. In the meantime, give it a shot!
Michael
On 9 September 2012 22:02, Steve Eynon <steve.ey...@alienfactory.co.uk>wrote:
> Hi,
>
> I have a transform worker which I want to run after everything else (it
> checks for the existence of an onActive() method) so I have the following
> Module method, note the "after:*"
>
> @Contribute(**ComponentClassTransformWorker2**.class)
> @Primary
> public static void provideTransformWorkers(
> OrderedConfiguration<**ComponentClassTransformWorker2**> configuration)
> {
>
> configuration.addInstance(
> "ContextNotRequiredWorker",
> NotRequiredWorker.class,
> "after:*");
> }
>
> But then I get the following warning:
>
> WARN : ConentClassTransformWorker - Unable to add 'UnclaimedField' as a
> dependency of 'ContextNotRequiredWorker', as that forms a dependency cycle
> ('ContextNotRequiredWorker' depends on itself via 'UnclaimedField'). The
> dependency has been ignored.
>
> because T5 defines UnclaimedField to also be "after:*". How can I define
> my config to be "after:* except UnclaimedField", or "before:UnclaimedField
> but after:everthing else"?
>
> Or does anyone know how else may I resolve my ordering problem?
>
> Cheers,
>
> Steve.
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail:
> users-unsubscribe@tapestry.**apache.org<users-unsubscr...@tapestry.apache.org>
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
