One thing I have considered in the past is to be able to define "phases" for an ordered configuration, and place contributions within a phase, but also ordered relative to other contributions in that phase. Thus the service author would define (and document) a few phases, and contributions would go into those phases. The phases themselves would be ordered. So in your case, there might be a "FinalValidation" phase that, by default, just contained "UnclaimedField" and you could add your HasOnActivate contribution inside that phase.
Even without code changes, we could create a few null contributions (that is allowed) that exist just as placeholders. So we could contribute a "FinalValidation" element, order most things "before:FinalValidation" an dorder UnclaimedField "after:FinalValidation". Another alternative I've considered is new API that would allow you to modify existing contribution's constraints. Yes, this is complicated, because the basic concept is complicated in certain edge cases. The complexity is just an outgrown of the design requirements: handling the addition of any number of modules at runtime, and the growth of the framework over time. On Mon, Sep 10, 2012 at 9:03 AM, trsvax <trs...@gmail.com> wrote: > I'd try creating a dummy worker called beforeUnclaimedField and make it > > before:UnclaimedField > > then change yours to > > after:beforeUnclaimedField > > > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/Ioc-Ordering-Contraints-tp5716154p5716171.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
