A bit of further reading shows that you can specify an ordering using the Order annotation. Perhaps this is why tapestry is not allowing the sercond advice?
http://tapestry.apache.org/service-advisors.html Matching And Ordering Each service advice method gets a unique id, obtained by stripping the "advise" prefix from the method name. Advice ids must be unique across all modules. If the @Match annotation is omitted, the advice will match against a service with the same id. In many cases, the order in which the advice is given is very important; for example, you may want logging first, then transaction management, then security checks. The @Order annotation allows you to explicitly set the order. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Several-Advices-on-same-service-tp5716615p5716623.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
