Hi, I find out the root cause thanks to your idea Lance.
Actually when you use the @Advise twice, matching the same Interface... then you MUST use the id parameter in the @Advice Annotation. If not Tapestry try to create Advice ids based on the Interface name... in that case you end up with 2 Advices with the same Ids which is not working well :) Thanks for the help ! Martin -- View this message in context: http://tapestry.1045711.n5.nabble.com/Several-Advices-on-same-service-tp5716615p5716627.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
