Yeap, working on it, just figured it should be safe to use the shadow. With the current interface, discarding changes (of conversations) might yield unexpected results though; I'll see what becomes out of it once I get a little further along with the implementation.
Kalle On Thu, Jan 15, 2009 at 8:38 AM, Richard Kirby <r...@capdm.com> wrote: > 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 > >
