|
From: Rob H. <ro...@ca...> - 2005-03-31 20:17:03
|
I see no problem in implictly creating a session - although I am concerned about the impact of this on clustered applications. Can the session implementation be factored out so that users can implement their own session storage? Rob Erwin Vervaet wrote: > The Spring Web Flow (SWF) FlowController forces the "requireSession" > property it inherits from AbstractController to "true". This is > logical since the webflow system needs to store flow execution state > in the HTTP session. > > So far so good. However, since the controller now requires an existing > session, the user/developer is responsible for creating that session > before a flow is started. This is typically not a problem in real-life > applications since those carefully manage session creation and > invalidation. > > Still, we are wondering whether it is a good idea to implicitly create > sessions (usually using request.getSession()) in a controller, or > should this be left as a responsability of the application developer? > Note that AbstractWizardFormController and AbstractFormController > implicitly create sessions. > > Erwin Vervaet > erw...@er... > > > ------------------------------------------------------- > This SF.net email is sponsored by Demarc: > A global provider of Threat Management Solutions. > Download our HomeAdmin security software for free today! > http://www.demarc.com/info/Sentarus/hamr30 > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > |