I think that we need to decide whether we want to introduce the
UpdateModelException and if so, we want to introduce special handling
for the case where it wraps a ValidatorException. If we do introduce
special behavior for ValidatorExceptions, should this behavior be
identical to the handling of ValidatorExceptions earlier in the lifecycle?
-- Blake Sullivan
Min Lu said the following On 2/16/2009 10:33 AM PT:
The patch below is for message reformat. We need a solution to skip reporting
message.
Since other than ValiatorException, the end users cannot fix other types of exception, we can change the updateModel() logic to only report error messages for ValidatorException type.
If error messages are reported by the model layer already, model layer can throw a RuntimeException to indicate failure to updateModel but let updateModel skip reporting errors.
Thanks,
Min
-----Original Message-----
From: Matthias Wessendorf [mailto:[email protected]]
Sent: Monday, February 16, 2009 12:21 AM
To: MyFaces Development
Subject: Re: [Trinidad] Introduce UpdateModelSkipMessageException
Hi Min,
Looks like the JSF 2.0 spec will contain an UpdateModelException, see
the gobal exception_handling item in their bug-system:
https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=248
and the proposed patch:
https://javaserverfaces-spec-public.dev.java.net/nonav/issues/showattachment.cgi/186/changebundle.txt
Greetings,
Matthias
On Sun, Feb 15, 2009 at 10:19 PM, Matthias Wessendorf
<[email protected]> wrote:
Hi,
IMO this makes sense. I think I saw an item for JSF 2 that does this too. If
possible we should take a look at it so that our solution is not to
different from the standard.
Sent from my iPod.
On 15.02.2009, at 19:48, Min Lu <[email protected]> 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
