Due to the magic of tapestry IOC, just inject the Request object into
your implementation of PersistentFieldStrategy and you have access - no
need to change/extend the PersistentFieldStrategy interface!
Richard.
Kalle Korhonen wrote:
I'd like to implement a custom PersistentFieldStrategy for conversations
within the same page, but a PersistentFieldStrategy only knows the page
name. Currently my conversation id is part of the activation context and I'd
somehow need to pass the id on to my custom strategy. Is there a way to do
this? If I could obtain the page instance, the request or a filter I could
probably work it out. Also, PersistentFieldStrategy only has
discardChanges(String pageName) (and Page has
discardPersistentFieldChanges() ) which discards all changes, but I'd need
it to discard changes for specific conversations only. Should I perhaps open
an enhancement request for it? Howard, care to comment?
Kalle
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
