On Fri, 31 Jan 2014 17:40:47 -0200, Richard Frovarp <rfrov...@apache.org>
wrote:
I have not tried to use that service before now (didn't know it
existed?). It is exactly what I needed to use though. Thanks for the
help.
:)
It might be useful to reference that service on the class reloading page:
http://tapestry.apache.org/class-reloading.html
Actually, the most recommended approach is to write a
ComponentClassTransformWorker and check the annotation there, as they're
called everytime a component (and page) class changes. You'll probably use
MutableComponentModel.setMeta(String, String) to store the annotation
information and later use MetaDataLocator to retrive it in a service. See,
for example, the source of SecureWorker and RequestSecurityManagedImpl.
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
