[
https://issues.apache.org/jira/browse/EXTVAL-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12890202#action_12890202
]
Rudy De Busscher commented on EXTVAL-107:
-----------------------------------------
For the moment, you can create an implementation of
ValidationExceptionInterceptor that calls the facesContext.validaitonFailed
method. That way you can already start using the isValidationFailed check
method.
The interceptor can be registered by a call to
ExtValContext.getContext().addValidationExceptionInterceptor() in a
ExtValStartupListener.
> ExtVal should call FacesContext.validationFailed() in case of validation
> failure
> --------------------------------------------------------------------------------
>
> Key: EXTVAL-107
> URL: https://issues.apache.org/jira/browse/EXTVAL-107
> Project: MyFaces Extensions Validator
> Issue Type: Improvement
> Components: Bean Validation, Property Validation
> Affects Versions: 1.1.1
> Reporter: Tom M.
> Priority: Minor
>
> In JSF 2.0 a new method was introduced -->
> javax.faces.context.FacesContext.validationFailed(): "Sets a flag which
> indicates that a conversion or validation error occurred while processing the
> inputs. Inputs consist of either page parameters or form bindings. This flag
> can be read using {...@link #isValidationFailed}."
> It seems to me that ExtVal 2.0 r4m3 does not make use of this leaving me to
> check if messages are available.
> Could you add this behaviour?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
