Hi Simon,
Your approach seems reasonable. In the app I'm developing my LoginAction
class creates a User object and stores it in the session.
If you plan to deploy your app in a clustered environment, session size
becomes a real issue. So only store what you really need to in the session.
Jon.
-----Original Message-----
From: Simon Liang [mailto:[EMAIL PROTECTED]]
Sent: 15 June 2001 21:39
To: [EMAIL PROTECTED]
Subject: The right way in Struts
Hi guys:
I consider myself fairly new to Strut. I have done a login flow that allows
user to edit his/her profile.
The login workflow is simple using the Struts framework:
Map the login screen form to a form bean, then the action bean login the
user and forward to the useredit.jsp upon a successful login.
But once I forward to the useredit.jsp, i am out of the Struts workflow.
The useredit.jsp would need to display the current user info for editing.
How best is to do this within the Struts framework? The idea I have is to
retrieve the user profile object and save in the session(to be done within
the login action class). Then in the useredit.jsp, i can get the object back
to display. Is this the right way in Struts or am I violating the Struts
framework?
Please advice!
Thanks for any help in advance.
Cy
============================================================================
This message is intended only for the use of the Addressee(s) and may
contain information that is PRIVILEGED and CONFIDENTIAL. If you are not
the intended recipient, dissemination of this communication is prohibited.
If you have received this communication in error, please erase all copies
of the message and its attachments and notify [EMAIL PROTECTED]
immediately.
============================================================================
============================================================================
This message is intended only for the use of the Addressee(s) and may
contain information that is PRIVILEGED and CONFIDENTIAL. If you are not
the intended recipient, dissemination of this communication is prohibited.
If you have received this communication in error, please erase all copies
of the message and its attachments and notify [EMAIL PROTECTED]
immediately.
============================================================================
