UpdateModel also sets valid to false when it sees an exception, although
I'm not sure Min needs that. If she has access to the component she
could also set valid to false I guess.
Thanks,
Gab
Andrew Robinson wrote:
I'm missing something, why not just call
FacesContext.getCurrentInstance().renderResponse()? This is the "JSF
way" to skip any following phases and also what happens when UIInput
catches validation exceptions. I see no need for a new exception, no
to mention Exceptions are not cheap to throw, relatively speaking.
-Andrew
On Sun, Feb 15, 2009 at 11:48 AM, Min Lu <MIN.LU
<http://MIN.LU>@oracle.com <http://oracle.com>> wrote:
I would like to propose that we introduce a new exception class
UpdateModelSkipMessageException extends RuntimeException, which
indicates failure in UpdateModel phase, however the error message
has been added in the model layer for reporting, so UpdateModel
can skip adding the message for this type of exception (done at
the end of UIXEditableValue.updateModel() ).
Thanks,
Min Lu
