On Wed, 26 May 2010 12:40:34 -0300, Dmitry Gusev
wrote:
No, because there's no field to be set.
Not true. If there was no field eclipse wouldn't show it in debugger.
I stand corrected. Please file a JIRA about it if you haven't done it yet.
It seems like a nice addition to me.
--
Thiag
On Wed, May 26, 2010 at 16:10, Thiago H. de Paula Figueiredo <
thiag...@gmail.com> wrote:
> On Wed, 26 May 2010 02:31:34 -0300, Dmitry Gusev
> wrote:
>
> May be during transformation in non-production mode T5 should assign value
>> to corresponding field also, not just to conduit?
>>
>
> No, bec
On Wed, 26 May 2010 02:31:34 -0300, Dmitry Gusev
wrote:
May be during transformation in non-production mode T5 should assign
value to corresponding field also, not just to conduit?
No, because there's no field to be set.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5
I noticed that also, thats make debugging a hard process.
May be during transformation in non-production mode T5 should assign value
to corresponding field also, not just to conduit?
Its not good to declare realXXX fields in a class while original field not
used.
On Wed, May 26, 2010 at 06:08, Th
On Tue, 25 May 2010 20:28:44 -0300, Dariusz Majewski
wrote:
Hi All,
Hi!
@Parameter(value="120")
private int maxWidth;
Now my problem is that when I debug onMyCustomEvent method I can't see
the real value of maxWidth parameter.
That's Tapestry doing it heavy wizardry: when it
