I'm guessing that you render the "recalculate" zone by submitting another
form... correct?
If so, you could include the values from the first calculate as in the second form.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Best-practice-activation-context
calculated values from the
initial calculation. Now I don't see another way than to @Persist these
values to use them, or is there a better/other way?
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Best-practice-activation-context-and-later-ajax-calls-tp5717936p5717966
(). Assuming you have a
ValueEncoder configured, you can do the following:
@PageActivationContext
private Policy policy;
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Best-practice-activation-context-and-later-ajax-calls-tp5717936p5717941.html
Sent from the Tapestry
;
}
[1]
http://tapestry.apache.org/current/apidocs/org/apache/tapestry5/ValueEncoder.html
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Best-practice-activation-context-and-later-ajax-calls-tp5717936p5717939.html
Sent from the Tapestry - User mailing list archive at
lso in your AJAX calls?
> Do you use @Persist, or maybe just write getter methods and retrieve them
> again every request?
>
>
>
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/Best-practice-activation-context-and-l
your AJAX calls?
Do you use @Persist, or maybe just write getter methods and retrieve them
again every request?
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Best-practice-activation-context-and-later-ajax-calls-tp5717936.html
Sent from the Tapestry - User mailing
