Chris is right, if you include an onPassivate() with your policy/policyId there is no need to pass it in the ajax event as it tapestry will implicitly populate the value for you.
You might also want to consider the @PageActivationContext annotation which takes care of onActivate() and onPassivate(). 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 - 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
