I think that you are seeing the expected behavior of OrderedConfiguration. By specifying a constraint of "after:CheckForUpdates", you are not guaranteed that your filter will occur directly after CheckForUpdates. You are only guaranteed that it will occur at some stage after CheckForUpdates (possibly last).
I *think* that you want to add one (or more) "before:X" constraints to guarantee that your filter occurs before some other filter(s). The diagram on this page might help http://tapestry.apache.org/request-processing.html -- View this message in context: http://tapestry.1045711.n5.nabble.com/Request-Filter-not-called-if-declared-with-addInstance-vs-add-tp5715859p5715903.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
