Pete, Alex -
Can you elaborate on the consequences of running through the update
model phase during Ajax validation? Is the concern that this is just
unnecessary overhead (ie. is this a performance issue)? Or are there
other functional issues that come up?
FWIW, we haven't added such a facility for skipping update model in
Trinidad/ADF Faces Ajax. Perhaps we haven't needed this because we
primarily rely on client-side validation for quick feedback (though of
course there are cases that client-side validation does not cover.)
Ted -
Just curious - does ICEfaces provide a mechanism for skipping update
model during Ajax validation?
Andy
Pete Muir wrote:
Hi all,
I was chatting with Alex Smirnov this week, and he pointed out that an
essential feature needed for Ajax validation is missing from the Ajax
support in JSF 2.0.
When you are doing Ajax validation, you need an option to not update
the backing beans (in other words, skip the update model phase), so
that *if the value is valid*, then aren't saved to the model. I think
this is sufficiently important enough to go into the JSF maintenance
release. The RichFaces syntax is like:
<f:ajax updateModel="false" />
BTW, Ed, any updates on the MR?
Pete