Hi,
Have you checked out: http://tapestry.apache.org/page-navigation.html
To see if "onPassivate" or providing an explicit activation context can help you
--
Chris
On Mon, Nov 12, 2012 at 4:20 PM, nquirynen <nat...@pensionarchitects.be> wrote:
> Hi
>
> I have a page with an activation context:
>
> void onActivate(int policyId) {
> policy = policyRepository.get(policyId);
> }
>
> Now I have a component on this page which does AJAX requests. At this point
> the policy variable set in the activation context is null.
> Now I can 'solve' this by using the @Persist annotation, but I don't think
> @Persist is meant for this use? Also it brings other problems like
> forgetting to reset persisted values when needed etc.
>
> So I was just wondering what do you people do when you need properties that
> are set while rendering the page also 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-later-ajax-calls-tp5717936.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> 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
