You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Gerhard Petracek (JIRA)" <de...@myfaces.apache.org> on 2009/05/29 03:22:45 UTC
[jira] Created: (EXTVAL-44) constraint severity for the validation
process
constraint severity for the validation process
----------------------------------------------
Key: EXTVAL-44
URL: https://issues.apache.org/jira/browse/EXTVAL-44
Project: MyFaces Extensions Validator
Issue Type: New Feature
Components: Core, Property Validation
Reporter: Gerhard Petracek
Assignee: Gerhard Petracek
via the parameter-type ViolationSeverity it is possible to switch the severity.
severity warn and info don't lead to a ValidatorException - in such a case just a faces-message is queued with the given severity.
@Required(parameters = ViolationSeverity.Warn.class)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (EXTVAL-44) constraint severity for the validation
process
Posted by "Gerhard Petracek (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/EXTVAL-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gerhard Petracek reopened EXTVAL-44:
------------------------------------
reason: adding customizable severity handling
> constraint severity for the validation process
> ----------------------------------------------
>
> Key: EXTVAL-44
> URL: https://issues.apache.org/jira/browse/EXTVAL-44
> Project: MyFaces Extensions Validator
> Issue Type: New Feature
> Components: Core, Property Validation
> Reporter: Gerhard Petracek
> Assignee: Gerhard Petracek
> Fix For: 1.2.3-SNAPSHOT, 1.1.3-SNAPSHOT
>
>
> via the parameter-type ViolationSeverity it is possible to switch the severity.
> severity warn and info don't lead to a ValidatorException - in such a case just a faces-message is queued with the given severity.
> @Required(parameters = ViolationSeverity.Warn.class)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (EXTVAL-44) constraint severity for the validation
process
Posted by "Gerhard Petracek (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/EXTVAL-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gerhard Petracek resolved EXTVAL-44.
------------------------------------
Resolution: Fixed
Fix Version/s: 1.1.3-SNAPSHOT
1.2.3-SNAPSHOT
> constraint severity for the validation process
> ----------------------------------------------
>
> Key: EXTVAL-44
> URL: https://issues.apache.org/jira/browse/EXTVAL-44
> Project: MyFaces Extensions Validator
> Issue Type: New Feature
> Components: Core, Property Validation
> Reporter: Gerhard Petracek
> Assignee: Gerhard Petracek
> Fix For: 1.2.3-SNAPSHOT, 1.1.3-SNAPSHOT
>
>
> via the parameter-type ViolationSeverity it is possible to switch the severity.
> severity warn and info don't lead to a ValidatorException - in such a case just a faces-message is queued with the given severity.
> @Required(parameters = ViolationSeverity.Warn.class)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (EXTVAL-44) customizable constraint severity for
the validation process
Posted by "Gerhard Petracek (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/EXTVAL-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gerhard Petracek resolved EXTVAL-44.
------------------------------------
Resolution: Fixed
> customizable constraint severity for the validation process
> -----------------------------------------------------------
>
> Key: EXTVAL-44
> URL: https://issues.apache.org/jira/browse/EXTVAL-44
> Project: MyFaces Extensions Validator
> Issue Type: New Feature
> Components: Core, Property Validation
> Reporter: Gerhard Petracek
> Assignee: Gerhard Petracek
> Fix For: 1.2.3-SNAPSHOT, 2.0.3-SNAPSHOT, 1.1.3-SNAPSHOT
>
>
> via the parameter-type ViolationSeverity it is possible to switch the severity.
> severity warn and info don't lead to a ValidatorException - in such a case just a faces-message is queued with the given severity.
> @Required(parameters = ViolationSeverity.Warn.class)
> default behaviour: warn and info messages don't interrupt the lifecycle
> it's possible to set a custom ViolationSeverityInterpreter which interprets the severities differently
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.