I would reduce your problem to a simple class that does nothing but access only the HttpSession and see if the problem still exists, then build up around that until something blows up.
I would also consider using Spring's DI/IoC to inject a user service object (generally not the same class as a user itself) into the action rather than accessing Spring's application context directly. d. --- Mark Rollins <[EMAIL PROTECTED]> wrote: > > I'm actually using two different browsers, IE and > Firefox, as I thought this > would guarantee me two separate sessions. > > > How are you starting a new browser from this *same* > machine? If you are > pressing Ctrl-N New Window, this is your problem! > This will appear to be > two browsers, when actually it is two browser > "windows" over the same > session! You must start a second (3rd, 4th, ...) > browser the way you > started the first if you truly want unique session > ids. > > Scott > > > -- > View this message in context: > http://www.nabble.com/Session-problem-tf4324658.html#a12354179 > Sent from the Struts - User mailing list archive at > Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
