On Fri, 21 Nov 2014 13:06:25 -0200, akshay <akshayestat...@gmail.com>
wrote:
Hi Thiago,
Hi!
Yes it should be field, just a typo :). But anyways, below is the
scneario:-
I have a component A and Component B
Component A{
@Component(id = "B", parameters = { "sortAscending=sortAscending"})
private ComponentB b;
@Property
private boolean sortAscending=true;
Never, never, never ever initialize a Tapestry page, component or mixin
field in its declaration. I cannot repeat this enough.
For identifying the reason, I checked that my property conduit value is
always true in component B.
How? A PropertyConduit doesn't have a value. It provides access to it.
--
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
