[
https://issues.apache.org/jira/browse/SLING-5584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15182127#comment-15182127
]
Konrad Windszus commented on SLING-5584:
----------------------------------------
I agree with [~cziegeler]. I don't see much advantage of using
{{javax.validation.ValidationException}} over our own class, especially since
we don't use any other part of JSR 303 yet
(http://beanvalidation.org/1.0/spec/).
Whether the exception should live in its own package or not is not that
relevant to me. The only thing relevant here is semantic versioning, so if we
increase the package version of the {{org.apache.sling.validation.exceptions}}
this might break less consumers than increasing the version of
{{org.apache.sling.validation}}. But I am not sure whether that is enough for
requiring a dedicated package.
> replace SlingValidationException by ValidationException (javax.validation)
> --------------------------------------------------------------------------
>
> Key: SLING-5584
> URL: https://issues.apache.org/jira/browse/SLING-5584
> Project: Sling
> Issue Type: Improvement
> Components: Validation
> Reporter: Oliver Lietz
> Fix For: Validation 1.0.0
>
>
> The current Validation API contains a single exception
> {{SlingValidationException}} in package
> {{org.apache.sling.validation.exceptions}}. I don't see any added value in
> {{SlingValidationException}} and think we should remove the package and use
> {{javax.validation.ValidationException}} instead.
> [~cziegeler], [~kwin]: WDYT? (see _e)_ in SLING-4027)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
