*@Michael* Constraints are very loose; after means 'somewhere after' rather than > 'immediately after'
If that was the case, why did cause an issue if it was so loose ? Is this one special case (i.e. after:***) ? What's the advantage of having this behavior over having it strict as being *immediately after* ? I haven't tried this before but if I had to chose, I'd chose it to act as *immediately after*. Thinks would be more clear and I only need to identify the injected transformers order to set mine up correctly. *@Steve* * * Does it fit your needs to specify *UnclaimedField* order as *after:** and then specify the other transformer with less priority to be before * UnclaimedField* as *before: UnclaimedField* ? On Mon, Sep 10, 2012 at 4:33 AM, Steve Eynon <steve.ey...@alienfactory.co.uk > wrote: > Hi Michael, > > > just specify as many as are important to you. > > I kinda want mine to run last, because I need make sure no other > workers (in T5 or other modules) add a onActivate() method. The issue > here is that both my 'ContextNotRequiredWorker' and T5's > 'UnclaimedField' want to run last - which isn't allowed. > > > the trick is to specify multiple constraints > > I could specify many "after" clauses for T5 workers as you mention, > but that then won't (be guaranteed to) work if some other another > module adds an onActivate() method. > > Stumpted, > > Steve. > -- > Steve Eynon > ------------------------------- > "If at first you don't succeed, > so much for skydiving!" > > > > On 10 September 2012 10:13, Michael Prescott > <michael.r.presc...@gmail.com> wrote: > > Michael > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
