Re: [jsr-314-open] Ajax validation
Thanks Pete -
Pete Muir wrote:
The issue is that it isn't always (normally IMO) the case that
you
want the model update on an ajax request to do validation, you only
want the model updated when you actually hit submit... This is a
problem if you are applying values directly to the managed JPA
entities which get flushed to the database at the end of the TX.
What are the consequences of applying a validated value to a managed
entity early - ie. during Ajax validation, as opposed to waiting until
the full submit? Is there some overhead here that you want to avoid?
Presumably the value is not being flushed to the database immediately
(as you said, this won't happen until the end of the TX), but perhaps
there are cases where some action is taken in response to model update
that needs be avoided?
BTW - I am not trying to argue against the proposal. I just want to
make sure I understand the issue. :-)
Andy