On Thu, 02 Sep 2010 11:53:53 -0300, Jim O'Callaghan
<j...@peritussolutions.com> wrote:
Does this debugging issue ring a bell with anyone? Any workarounds? Is
it down to using T5 annotations on methods and them being instrumented?
Access to annotated fields in Tapestry 5 are silently replaced by method
calls. In Tapestry 5.2+, the fields don't even exist, as they're removed
from the transformed classes completely.
--
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
