I have something like this implemented in our app for component events only, a field with the special annotation will add its value as a request parameter to all links inside rendering phase and on incoming event the special filter will send restore event to restore field's previous value.
Works great with deep component hierarchy, otherwise you need to preserve that state using context in all events, which is very ugly. Denis On 24.10.2011, at 20:39, trsvax wrote: > In my case the page does not know about the parameter. I have a grid like > component that is managing what rows in the grid to display. I don't really > want to make the page care one way or another what part of the grid is > displaying (or even that is is a grid). > > Since the value is available in the Request it's easy to get in the > component which makes it seem a bit arbitrary I can use this annotation in a > page and not a component. > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/ActivationRequestParameter-only-works-in-a-page-tp4932370p4933666.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
