On Fri, 21 Nov 2014 15:17:11 -0200, Akshay
wrote:
Hi
Hi!
Infact, the idea to intialize it in the way given below is taken from
the Grid component of tapestry,as I am trying to build a customized grid
over the tapestry default grid. The value transferred from Component A
to B doesn't
On Fri, 21 Nov 2014 13:06:25 -0200, akshay
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 Componen
7
To: "Tapestry users"
Subject: Re: Property Values to be modified
don't initialize the property where you declare it. Use onActivate
setupRender or similar to set det default value
On Fri, Nov 21, 2014 at 4:06 PM, akshay wrote:
> Hi Thiago,
>
> Yes it should be field, ju
don't initialize the property where you declare it. Use onActivate
setupRender or similar to set det default value
On Fri, Nov 21, 2014 at 4:06 PM, akshay wrote:
> Hi Thiago,
>
> Yes it should be field, just a typo :). But anyways, below is the
> scneario:-
>
>
> I have a component A and Compone
Hi Thiago,
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;
}
Com
On Fri, 21 Nov 2014 12:13:51 -0200, akshay
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
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.
Somehow, the values of both the fields are loaded differently and
