You missed one.
Paul Benedict wrote:
Most people who have this problem do so because of four things: (1)
they are
switching protocols from HTTP/HTTPS (2) they are switching contexts
(3) they
are switching domains (4) they are invalidating the session.
(5) Or trying to access the session in the Action constructor.
I am not sure if this was my mistake. I would like to hear form some one.
By the way, can I save models on the ValueStack rather than the session ?
-- Paul
On 5/26/07, Dave Newton <[EMAIL PROTECTED]> wrote:
--- Mansour <[EMAIL PROTECTED]> wrote:
> Thank you Dave for replying. I think I need a lot of
> help on this. The problem is even if I implement
> SessionAware, using chaining doesn't work as the
> setSession method is never called.
Are you talking about the *second* action's
setSession()?
Are you running a basicStack or stack that includes
the servletConfig interceptor on the action whose
setSession is *not* being called?
At what point in the action object's lifecycle are you
attempting to access the session?
d.
____________________________________________________________________________________Got
a little couch potato?
Check out fun summer activities for kids.
http://search.yahoo.com/search?fr=oni_on_mail&p=summer+activities+for+kids&cs=bz
---------------------------------------------------------------------
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]
