<div class="gmail_quote">On Tue, Jun 23, 2009 at 11:40 AM, Ted Goddard <span dir="ltr"><<a href="mailto:ted.goddard@icesoft.com">ted.goddard@icesoft.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
ICEfaces doesn't alter the lifecycle from the point of view of<br>
validation -- our purpose there was to make Ajax development and<br>
non-Ajax development as similar as possible. The submit action is<br>
where we typically recommend putting the database commit.</blockquote><div><br>Just the clarify (not countering your statement), with JPA you often don't get to choose when the database is updated. That's something that JPA decides based on the flush mode. In standard JPA, this happens at least when the transaction commits (FlushMode.COMMIT) or sooner (FlushMode.AUTO). So it's more that the developer has to be conscious of whether a commit will happen, even in the absense of an explicit commit in the code.<br>
<br>The technical details of this problem could be debated for days. If we want to avoid going down that slippery path, we should discuss whether it is worth introducing the concept of "skip update model".<br><br>
-Dan<br></div></div><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br><br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br>
<a href="http://in.relation.to/Bloggers/Dan">http://in.relation.to/Bloggers/Dan</a><br><br>NOTE: While I make a strong effort to keep up with my email on a daily<br>basis, personal or other work matters can sometimes keep me away<br>
from my email. If you contact me, but don't hear back for more than a week,<br>it is very likely that I am excessively backlogged or the message was<br>caught in the spam filters. Please don't hesitate to resend a message if<br>
you feel that it did not reach my attention.<br>