>  Hmm.. I've always handled session data by creating an application base action
> that implements a "getUserData()" and a "setUserData() method. All my actions
> extend this base action. I then use an interceptor to grab the session data
> build whatever object I decide to use to hold the data and inject it into the
> base action. In this way, all my actions can simply "getUserData()" without
> having to care where the data comes from. Is this bad practice or just a
> matter of personal preference?
>
I hope it's not a bad idea, I do the exact same thing with my User
=8^)  But there are commonly other things stored in the session that
you might need access to and, depending on the app, writing an
Interceptor for each of them might be a bit much.
  (*Chris*)

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to