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:[EMAIL PROTECTED]] > 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:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
