On Fri, 21 Nov 2014 12:13:51 -0200, akshay <akshayestat...@gmail.com>
wrote:
Dear all,
I have a strange scenario like below :-
I have a component A
{
@Parameter(required = true)
private boolean isXYZ;
}
On debug, i see two parameters associated to the above field
-----isXYZ and isXYZ_FieldConduit.
They're not parameters. They're fields. Please use the right vocabulary or
people won't understand what you're saying. :)
Somehow, the values of both the fields are loaded differently and are not
in sync.
the _FieldConduit thing is actually a PropertyConduit instance, not the
field type, so they're supposed to be different. You shouldn't worry about
the _FieldConduit thing at all.
Is production mode off? If yes, Tapestry should keep the field updated.
What exactly is the problem you're having?
May be its something which is just against the tapestry way. Not sure,
any suggestion will be helpful.
This is actually how Tapestry works on page, component and mixin fields:
by transforming them. ;) This field, which is a parameter, is only left on
class, but any access to it (setting a value or reading it) is done
through the PropertyConduit.
--
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
