You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by Jerson John <je...@cprvision.com> on 2011/02/23 06:43:56 UTC
Session for User Class
Hi,
Can anyone suggest me a best practice for me to save the user object once user logined into my portal application...It seems that I am saving it in the actioncontext but not accessable to the other action classes...Pls help me
Many Thanks and Regards,
Jerson
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: Session for User Class
Posted by Dave Newton <da...@gmail.com>.
Put it in the session.
Dave
On Wednesday, February 23, 2011, Jerson John <je...@cprvision.com> wrote:
> U mean u use the sessionaware interface right....I am also following the same way but my scope it seems limited to Actioncontext which means only available in one actionclass and if I want to have my session user object available to all the action class for that particular session how can I achieve that....
>
> Many Thanks and regards
>
> Many Thanks and Regards,
>
> Jerson
>
>
> -----Original Message-----
> From: Brian Thompson [mailto:elephantium@gmail.com]
> Sent: Wednesday, February 23, 2011 3:33 PM
> To: Struts Users Mailing List
> Cc: Jerson John
> Subject: Re: Session for User Class
>
> Normally I use Spring Security for handling authentication. However, that's
> a fair bit of trouble to configure if your needs differ from the default
> config.
>
> For a "roll your own" approach, I'd put the user object into the session
> context.
>
> -Brian
>
>
> On Tue, Feb 22, 2011 at 11:43 PM, Jerson John <je...@cprvision.com> wrote:
>
>> Hi,
>> Can anyone suggest me a best practice for me to save the user object once
>> user logined into my portal application...It seems that I am saving it in
>> the actioncontext but not accessable to the other action classes...Pls help
>> me
>>
>> Many Thanks and Regards,
>>
>> Jerson
>>
>>
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
RE: Session for User Class
Posted by Jerson John <je...@cprvision.com>.
U mean u use the sessionaware interface right....I am also following the same way but my scope it seems limited to Actioncontext which means only available in one actionclass and if I want to have my session user object available to all the action class for that particular session how can I achieve that....
Many Thanks and regards
Many Thanks and Regards,
Jerson
-----Original Message-----
From: Brian Thompson [mailto:elephantium@gmail.com]
Sent: Wednesday, February 23, 2011 3:33 PM
To: Struts Users Mailing List
Cc: Jerson John
Subject: Re: Session for User Class
Normally I use Spring Security for handling authentication. However, that's
a fair bit of trouble to configure if your needs differ from the default
config.
For a "roll your own" approach, I'd put the user object into the session
context.
-Brian
On Tue, Feb 22, 2011 at 11:43 PM, Jerson John <je...@cprvision.com> wrote:
> Hi,
> Can anyone suggest me a best practice for me to save the user object once
> user logined into my portal application...It seems that I am saving it in
> the actioncontext but not accessable to the other action classes...Pls help
> me
>
> Many Thanks and Regards,
>
> Jerson
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: Session for User Class
Posted by Brian Thompson <el...@gmail.com>.
Normally I use Spring Security for handling authentication. However, that's
a fair bit of trouble to configure if your needs differ from the default
config.
For a "roll your own" approach, I'd put the user object into the session
context.
-Brian
On Tue, Feb 22, 2011 at 11:43 PM, Jerson John <je...@cprvision.com> wrote:
> Hi,
> Can anyone suggest me a best practice for me to save the user object once
> user logined into my portal application...It seems that I am saving it in
> the actioncontext but not accessable to the other action classes...Pls help
> me
>
> Many Thanks and Regards,
>
> Jerson
>
>
>
>