Tapestry's ordered constraints need to be like this to allow distributed configuration. If two contributions specify "after:X", tapestry will make sure that they both occur after X. Since it's impossible to order both directly after X, tapestry will (pseudo randomly) decide an ordering which is not guaranteed.
Likewise, if two contributions (A and B) specify a constraint of "after:**", tapestry will guarantee that both A and B occur after the other contributions but the ordering of A and B is not guaranteed. If you need more specific ordering, you will need to be more specific ;) -- View this message in context: http://tapestry.1045711.n5.nabble.com/Ioc-Ordering-Contraints-tp5716154p5716159.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
