"mutpup" wrote : The problem is that I am basically carrying on the object
that I logged in with.
|
| I want to retain information from my users login, but I also need only
users who have logged to have the ability to create users.....so does the
create need to be a seperate conversation off the first?
Probably the nicest approach for you is to try out the new @Roles feature that
I just committed to CVS. Other approaches include using an indirection between
the scoped seam component and the actual User object. So instead of getting the
User directly bound to a context variable, you do stuff like
#{currentLogin.user} and #{userEditor.user}.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3919555#3919555
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3919555
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
