FYI one bonus of using @PageActivationContext is that you automatically
have onPassivate() generated for you. If you declare onActivate() you'll
need to do this yourself
On 20 Sep 2016 5:56 p.m., "Thiago H de Paula Figueiredo"
wrote:
> On Tue, 20 Sep 2016 13:24:08 -0300, Nathan Quirynen <
> nat.
On Tue, 20 Sep 2016 13:46:27 -0300, Adam X wrote:
How do I create links? Can I do this:
yo
bam
I'd go with a separate method:
yo
Object[] getPageContext() {
// whatever logic you want or need.
}
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
On Tue, 20 Sep 2016 13:24:08 -0300, Nathan Quirynen
wrote:
|You can do something like the following: void onActivate(EventContext
eventContext) { |
||if(eventContext.getCount() == 1) { ... }
if(eventContext.getCount() == 2) { ... }
if(eventContext.getCount() == 3) { ... } ...
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" wrote:
> You don't need explicit nulls, it'll work with or without
You don't need explicit nulls, it'll work with or without them.
On 20 Sep 2016 5:46 p.m., "Adam X" 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
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;
@PageActi
Correction: This feature was added in 5.4 (not 5.3)
On 20 Sep 2016 5:29 p.m., "Lance Java" 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 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;
|You can do something like the following: void onActivate(EventContext
eventContext) { |
||if(eventContext.getCount() == 1) { ... } if(eventContext.getCount() == 2)
{ ... } if(eventContext.getCount() == 3) { ... } ... |
} |
On 20/09/16 18:04, Adam X wrote:
I would like to have mul
Try this:
http://jumpstart.doublenegative.com.au/jumpstart7/examples/navigation/variableparameters1
Geoff
> On 21 Sep 2016, at 12:04 AM, Adam X wrote:
>
> I would like to have multiple (overloaded) onActivate methods in my
> page but seems like Tapestry is always picking a method with
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) {
}
11 matches
Mail list logo
