On the other hand, I guess you can use Tapestry-IoC service advice to
implement this.
I should have been more specific: you can add an advice to be applied for
all services. Your advice would need to advise all methods and check
whether it's the first time a method was invoked on it. You can also use
service decoration. In this case, the method that creates a decorator will
be invoked for every service instance created by Tapestry-IoC.
Regarding annotations, Tapestry-IoC 5.3.2, as far as I know, doesn't copy
annotations from service implementations classes nor methods to their
proxies (Tapestry-IoC creates proxies for all interface-defined services)
anymore. This would be another JIRA and it'll have my vote. :)
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
