It would be nice just to have some documented "markers". I usually just look at the TapestryModule class to figure out what to do, but having some documented phases would probably solve most issues. It would also solve the problem workers changing between releases. For example what if UnclaimedField goes away.
-- View this message in context: http://tapestry.1045711.n5.nabble.com/Ioc-Ordering-Contraints-tp5716154p5716174.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
