Re: General debugging query

2010-09-02 Thread Thiago H. de Paula Figueiredo
On Thu, 02 Sep 2010 12:58:09 -0300, Jim O'Callaghan  
 wrote:


Thanks Thiago.  This may be the cause of it - will have to keep an eye  
on whether this just happens to annotated fields or not.


In 5.2+, which I could play with yet, I guess all fields are removed, as  
there's no page pool anymore. In 5.1- the fields remain.


--
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



RE: General debugging query

2010-09-02 Thread Jim O'Callaghan
Thanks Thiago.  This may be the cause of it - will have to keep an eye on 
whether this just happens to annotated fields or not.

Regards,
Jim.

-Original Message-
From: Thiago H. de Paula Figueiredo [mailto:thiag...@gmail.com] 
Sent: 02 September 2010 16:29
To: Tapestry users
Subject: Re: General debugging query

On Thu, 02 Sep 2010 11:53:53 -0300, Jim O'Callaghan  
 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



-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org



Re: General debugging query

2010-09-02 Thread Thiago H. de Paula Figueiredo
On Thu, 02 Sep 2010 11:53:53 -0300, Jim O'Callaghan  
 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