On Thu, Jun 1, 2017 at 4:12 AM, Andrias Sundskarð wrote:
> That might work, but I'm thinking that the type coercer solution is more
> like "code once, fix every page", right?
Right. Or you could create a new class wrapping a collection and contribute
a coercion for it to GridDataSource, avoidin
I had similar issue when Grid lost its custom settings (though it wasn’t
related to coercer).
I solved it by directly calling grid.reset() in my event handler.
On Wed, May 31, 2017 at 4:41 PM, Andrias Sundskarð wrote:
> Hi, guys.
>
> I'm using tapestry 5.3.8.
>
> I need a different grid sorting
at not possible?
-Original Message-
From: Thiago H. de Paula Figueiredo [mailto:thiag...@gmail.com]
Sent: 31. maj 2017 20:51
To: Tapestry users
Subject: Re: Replacing default type coercer
Hi!
Why don't you just pass a GridDataSource directly instead of relying on having
your collection coerced
Hi!
Why don't you just pass a GridDataSource directly instead of relying on
having your collection coerced to it?
On Wed, May 31, 2017 at 10:41 AM, Andrias Sundskarð wrote:
> Hi, guys.
>
> I'm using tapestry 5.3.8.
>
> I need a different grid sorting than the one provided in
> "CollectionGridDa
Hi, guys.
I'm using tapestry 5.3.8.
I need a different grid sorting than the one provided in
"CollectionGridDataSource".
I contribute a custom type coercer like this:
public static void contributeTypeCoercer(Configuration
configuration)
{
configuration.add(Coercio