Sorry... I spoke to soon. You want index=1 to be a string sometimes and a long others? If you want to use @PageActivationContext you'll need to declare as a string and parse to long yourself
On 20 Sep 2016 5:51 p.m., "Lance Java" <lance.j...@googlemail.com> wrote: > You don't need explicit nulls, it'll work with or without them. > > On 20 Sep 2016 5:46 p.m., "Adam X" <vbgnm3c...@gmail.com> wrote: > >> Wow, you guys rock and support is great. I like >> onActivate(EventContext eventContext). I like even better >> @PageActivationContext annotation (I'm doing a new project on 5.4.1 so >> I can use it). >> >> So in my earlier example, if I define this: >> >> @PageActivationContext(index=0) private String foo; >> @PageActivationContext(index=1) private String bar; >> @PageActivationContext(index=2) private Long id1; >> @PageActivationContext(index=3) private Long id2; >> >> How do I create links? Can I do this: >> >> <t:pagelink context="['abc','def']">yo</t:pagelink> >> <t:pagelink context=['xyz',10,20]>bam</t:pagelink> >> >> ? Or do I have to explicitly pass null to keep indexes straight? >> >> <t:pagelink context="['abc','def']">yo</t:pagelink> >> <t:pagelink context=['xyz','null'10,20]>bam</t:pagelink> >> >> Adam >> >> On Tue, Sep 20, 2016 at 6:34 PM, Lance Java <lance.j...@googlemail.com> >> wrote: >> > Correction: This feature was added in 5.4 (not 5.3) >> > >> > On 20 Sep 2016 5:29 p.m., "Lance Java" <lance.j...@googlemail.com> >> wrote: >> > >> >> @PageActivationContext supports multiple values thanks to the new index >> >> property added in 5.3. Missing values will simply be null >> >> >> >> Eg: >> >> @PageActivationContext(index=0) private String value0; >> >> @PageActivationContext(index=1) private String value1; >> >> @PageActivationContext(index=2) private String value2; >> >> >> >> More info: https://issues.apache.org/jira/browse/TAP5-2138 >> >> >> >> On 20 Sep 2016 5:04 p.m., "Adam X" <vbgnm3c...@gmail.com> wrote: >> >> >> >>> I would like to have multiple (overloaded) onActivate methods in my >> >>> page but seems like Tapestry is always picking a method with fewest >> >>> arguments. >> >>> >> >>> How can I achieve something like this? >> >>> >> >>> TargetPage { >> >>> >> >>> void onActivate(String foo, String bar) { >> >>> } >> >>> >> >>> void onActivate(String foo, Long id1, Long id2) { >> >>> } >> >>> } >> >>> >> >>> <t:pagelink context="['abc','def']">yo</t:pagelink> >> >>> <t:pagelink context=['xyz',10,20]>bam</t:pagelink> >> >>> >> >>> Adam >> >>> >> >>> --------------------------------------------------------------------- >> >>> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >> >>> For additional commands, e-mail: users-h...@tapestry.apache.org >> >>> >> >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: users-h...@tapestry.apache.org >> >>
