As long as we can still hook in when a session is invalidated (something like a destroy method?)
Maurice On 2/25/06, SourceForge.net <[EMAIL PROTECTED]> wrote: > Bugs item #1438486, was opened at 2006-02-24 22:14 > Message generated for change (Tracker Item Submitted) made by Item Submitter > You can respond by visiting: > https://sourceforge.net/tracker/?func=detail&atid=684975&aid=1438486&group_id=119783 > > Please note that this message will contain a full copy of the comment thread, > including the initial issue submission, for this request, > not just the latest update. > Category: core > Group: 1.2 > Status: Open > Resolution: None > Priority: 7 > Submitted By: Jonathan Locke (jonathanlocke) > Assigned to: Nobody/Anonymous (nobody) > Summary: lifecycle methods > > Initial Comment: > > I searched for a bug or RFE on this and couldn't find > one. Although we are essentially feature-frozen for > 1.2 at this point, it seems to me that the various > lifecycle methods we have ought to be reviewed and > tweaked now rather than later. There are at least a > couple which are misleading. In retrospect, I wish I > had not created any of these, but rather worked to > solve the related problems instead. For example, > instead of using onEndRequest() to solve the problem of > logging someone out through session invalidation, it > would have been more intuitive to have a > Session.setInvalidate() boolean property that would do > this internally at the end of the request. More > readable, safer, doesn't rely on "lore" to get the job > done, etc. I suspect in thinking about this now that > there are actually NO really legitimate uses for these > methods that are not also shortcomings in the framework > that ought to be fixed anyway. It may be too late at > this point, but in case it's not I just wanted to put a > little brain-dump in this bug because i'd prefer to see > these methods disappear from the public API if at all > possible... > > > > ---------------------------------------------------------------------- > > You can respond by visiting: > https://sourceforge.net/tracker/?func=detail&atid=684975&aid=1438486&group_id=119783 > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting language > that extends applications into web and mobile media. Attend the live webcast > and join the prime developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 > _______________________________________________ > Wicket-develop mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wicket-develop > ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
