Gave it a shot. That is pretty nice. I was actually able to set the entire user object in my ModifyUserBean vs individual properties of that object as the wiki has for it's example. Not too shabby. Thanks for the tip.
GreggOn 6/9/06, Gregg Bolinger <[EMAIL PROTECTED]> wrote:
Thanks for the link.
Thanks for the link. That looks interesting. I might try that and see if it clean up my code any. Although, it would appear that it is doing the same thing I am doing now, but in the JSP rather than me doing it in my java code.
Thanks again.On 6/9/06, Matthias Wessendorf <[EMAIL PROTECTED]> wrot
Gregg,
have you tried to use the "updateActionListener" for some master/detail stuff?
It works pretty good!
http://wiki.apache.org/myfaces/ExecutingMethodsFromLinkButtonParameters
-Matthias
On 6/9/06, Gregg Bolinger <[EMAIL PROTECTED]> wrote:
What I've discovered is that if in the constructo
What I've discovered is that if in the constructor I do setCurrentUser(new User()), then when the values are being repopulated on a validation errror, there is an object to apply those values to.I guess what is sort of confusing me is the fact that, realizing how request scope works, everytime the
I am currently trying something that I haven't seen anyone else do (doesn't mean someone else isn't doing it). In UserAdminBean I have a dataTable with a list of users. When I click on one of the users in the dataTable I am taken to
ModifyUser.jsp which uses ModifyUserBean.In the action method i
5 matches
Mail list logo