This feature is in place for release 2.4. If your page (or component) implements one of the three listener interfaces, it is automatically registerred for it.
----- Original Message ----- From: "Christian Sell" <[EMAIL PROTECTED]> To: "Tapestry-Developer" <[EMAIL PROTECTED]> Sent: Friday, January 10, 2003 10:40 AM Subject: [Tapestry-developer] pageDetached implementation > Hello, > > I am just looking into tapestrys component state management technique. > In doing that, I implemented the PageDetachedListener interface, > resetting all component variables to default values, as the > documentation describes. > > However, the method did not get called. It seems the docs fail to > mention that I also have to implement the method finishLoad() and call > > getPage().addPageDetachListener(this); > > therein to have my method called. In addition to the omission in the > docs, I wonder why the page does not automatically register all > components that implement the PageDetachListener interface. IMO that > would simplify the state management without apparent drawbacks. > > regards, > Christian > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > _______________________________________________ > Tapestry-developer mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/tapestry-developer > ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
