Yes, that's the correct way to do it. I think you could also do
t:context="foo,bar" if both foo and bar are properties (e.g. a getter for
each).
On Sep 17, 2016 3:24 PM, "Adam X" <vbgnm3c...@gmail.com> wrote:

> I'm not sure if I did this right but I introduced a getter in my page
> class returning object array like this:
>
> public Object[] getFoo() {
>  return new Object[] { tx.id, true };
> }
>
> So this allows me to have a context that is partially dynamic
> (transaction id) and partially static (literal):
>
> public void onAjax(String txId, String fmt) {
> }
>
> This works.
>
> Adam
>
> On Sat, Sep 17, 2016 at 3:18 PM, Adam X <vbgnm3c...@gmail.com> wrote:
> > Hi,
> >
> > I have the following event link which works (with single context
> parameter)
> >
> > <t:eventlink event="doAjax" t:context="literal:true"
> > zone="payloadZone">raw</t:eventlink>
> >
> > In my page class I have the associated handler:
> >
> >     public void onDoAjax(boolean format) {
> >         log.debug("{}", format);
> >     }
> >
> > Now, I'd like to add a second (dynamic) context parameter. By dynamic
> > I mean a property from the Page class. What's the best way to do this?
> >
> > Adam
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>

Reply via email to