This content has been marked as final.
Show 2 replies
-
1. Re: What the JSF lifecycle should have been
jazir1979 Nov 28, 2008 1:34 AM (in response to deanhiller2000)Does that mean you'd need a
revert model back to original state
if your validations fail? It seems a bit troublesome to me. -
2. Re: What the JSF lifecycle should have been
deanhiller2000 Nov 28, 2008 5:10 PM (in response to deanhiller2000)why would I need that when hibernate supports it just find. Here is how hibernate does it
1. end the conversation 2. create the new entity manager 3. entity manager grabs the unwritten values from the db
note that the commit to database above is optional depending on if you are doing a long running conversation. Instead, it seems there are
tricks
to get around this problem like immediate=true which seemed to break using FacesMessages AND moves the validation up a level too. we have had all sorts of problems that I think this change would solve. Though it is not likely to change, it kind of sounds nice in theory....sometimes reality works out a bit differently and new problems creep up.