I'm using SecurityFilter and use the Principal to store the user ID. The
actions use the J2EE compliant request.getUserPrincipal(). Having
userId, they can call business objects.
Nico.
Günther Wieser a écrit :
i for one put the user object into the session, as i have a lot of method
calls agains
i for one put the user object into the session, as i have a lot of method
calls against this use object on each page. if you don't use the user object
often, put some identifier in the session to mark that the user has logged
in, eg. key="user", value=. if you need to access the user data
later on,
wo_shi_ni_ba_ba wrote:
do struts developers usually store user as an object
in session?
Yes, that is typical.
or does struts have additional framework
for handling user management.
No. But there is container managed security, which has its own concept
of a "user" (typically represented by a ja
3 matches
Mail list logo