Current strategy works (it's separated in 2 steps inside a common-chain of operation), but it makes wuite a few lines to try to detect user login, and if tomcat was already providing such event that could be handled by a context listener, that would have been, perhaps, cleaner.
En l'instant précis du 20/08/07 17:41, Christopher Schultz s'exprimait en ces termes: > David, > > David Delbecq wrote: > > For now, the layout is Filter that check userPrincipal. If user > > principal is not null for the first time, issues that check, mark > > that user got checked for next times, in session, and continue query. > > However, if i could mark the session as "need upgrade" upon login, > > this would make things, i think, easier to manage as filter would > > only need to look for that "need upgrade" flag. > > I think you'll find that you're just breaking your filter into two > separate filters: you'd have one that check to see if the session "needs > an upgrade", and then another one to "upgrade" it. Since the > functionality is all related, I'm not sure if there's a good reason not > to keep it all together. > > Do you have any particular complaints about your existing strategy? > > -chris > --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- David Delbecq Institut Royal Météorologique Ext:518 -- http://www.noooxml.org/ --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
