struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Taylor" <rtay...@mulework.com>
Subject RE: Best strategy for adding a user object to the session
Date Tue, 03 Sep 2002 11:54:48 GMT
Why not put it (the code/logic/delegate) in the Action class which supports
the login request?

Something like:

-submit request to login
-capture login credentials
-authenticate against the database
-retrieve user info
-place user info in session

robert



> -----Original Message-----
> From: Michael [mailto:michael@idtect.com]
> Sent: Tuesday, September 03, 2002 7:28 AM
> To: Struts Users Mailing List
> Subject: Best strategy for adding a user object to the session
>
>
> I want to add a user object (that I create with information from the
> database) to the session as soon as a user logs in.  I don't want to add
> code to each action subclass to do this, so my question is where is the
> best place to put it?  It sounds like subclassing the Struts
> RequestProcessor is the way to go.  Is this the best way?
>
> Michael
>
>
> --
> To unsubscribe, e-mail:
> <mailto:struts-user-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail:
> <mailto:struts-user-help@jakarta.apache.org>
>


--
To unsubscribe, e-mail:   <mailto:struts-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-user-help@jakarta.apache.org>


Mime
View raw message