[
https://issues.apache.org/jira/browse/CXF-5309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13801945#comment-13801945
]
Sergey Beryozkin commented on CXF-5309:
---------------------------------------
Hi Andriy,
you have a good point though about the fact that the custom
ConstraintValidationException mappers may find it simpler to check for the
specific exception type as opposed to going a more low-level check involving
the current message. And yes, we have a case for JAX-RS 2.1 enhancement
request, i.e, no portable way at the moment to figure in the custom mapper
whether it was a in or out validation issue.
I'd then drop CXF ServerConstraintValidationException for now and default
ConstraintValidationException to signal in validation issues, and keep
ClientConstraintValidationException, but rename it to
ResponseConstraintValidationException; when we do a CXF specific client proxy
validation support we can reuse ResponseConstraintValidationException as well.
I can take care of this updates next week
Cheers, Sergey
> Support Bean Validation API for JAX-RS
> --------------------------------------
>
> Key: CXF-5309
> URL: https://issues.apache.org/jira/browse/CXF-5309
> Project: CXF
> Issue Type: Sub-task
> Components: JAX-RS, JAX-WS Runtime
> Reporter: Sergey Beryozkin
> Attachments: patch-validation-poc.txt
>
>
--
This message was sent by Atlassian JIRA
(v6.1#6144)
