Hi Geoff,
another way to handle this situation (a workaround?) is by using
@ActivationRequestParameter("paramName") attribute on page properties.
This is what I do for my projects and what's working for me.
On Mon, Feb 24, 2014 at 4:20 PM, Geoff Callender <
geoff.callender.jumpst...@gmail.com> wrote:
> To participate in nested components in an AJAX page we can utilise Form's,
> EventLink's, and ActionLink's context parameter. It can be used to pass the
> parameters of the enclosing component. The containing component's event
> handlers can receive the context and set its parameters from them before
> making any decisions. This works well.
>
> However, Grid doesn't have a context parameter. Consequently, when the
> user chooses a new page in a GridPager, or a new sort order in a Grid
> column, the containing component doesn't know the context and consequently
> might not be able to render the Grid correctly.
>
> I've produced an example, in which I've created a GridWithContext to wrap
> a Grid, and modified GridPager to include the context in its links and
> bubble up a new event with the context. It's in JumpStart 7.0 preview-6:
>
> http://jumpstart.doublenegative.com.au/jumpstart7/
>
> Without this, I would lose the selectedPersonId when I a GridPager link.
>
> So I think Grid needs a context. Or is there another existing way to
> handle this problem?
>
> There's an existing JIRA for this.
> https://issues.apache.org/jira/browse/TAP5-1162
>
> Cheers,
>
> Geoff
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: dev-h...@tapestry.apache.org
>
>
--
Dmitry Gusev
AnjLab Team
http://anjlab.com
