Sean Schofield wrote:
I would recommend storing the user information in the session (I use POJO's) as you have suggested. Then you can access it from the session to preopulate the form. Your approach sounds correct.
We're storing user information in the session on our project because its constantly being used for almost every single action.
+1. The user information is accessed in every request so it makes sence to have it available as a javabean/POJO in the session. Two things you need to remember is
* make sure you have the latest screenshot of the user in each request (an admin may be changing his/her rights for example)
* avoid storing large object graphs in the session (e.g. in the case of hibernate POJOs, make sure your collections are lazy).
Cheers,
Manos
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
