[
https://issues.apache.org/jira/browse/CXF-5401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13827697#comment-13827697
]
Sergey Beryozkin commented on CXF-5401:
---------------------------------------
Hi,
> validation provider might raise a violation if object (instance) <-> method
> doesn't match (we may rely on Hibernate Validator implementation as well in
> this case)
Single-argument validateResponseValue will use a non-executors base Validator
to validate the value as a bean, so I think we are safe here; keeping this
option (not utilized by default) will let user to avoid issues when future
Hibernate or ApacheBVal will enforce the type-safety of the return value, we
may still end up defaulting to a single-argument validateResponseValue in the
end :-) or find some other solution
Cheers, Sergey
> Better support for validating the entities wrapped in JAX-RS Response
> ---------------------------------------------------------------------
>
> Key: CXF-5401
> URL: https://issues.apache.org/jira/browse/CXF-5401
> Project: CXF
> Issue Type: Improvement
> Reporter: Sergey Beryozkin
> Assignee: Sergey Beryozkin
> Fix For: 3.0.0-milestone1
>
> Attachments: patch-response-validation.txt
>
>
> At the moment Response entities can only be validated against the rules
> attached to the entity properties. Method-level constraints (ex, NotNull) can
> not be applied yet.
> We need to either offer a support for few well-known constraints (NotNull,
> Null, etc) or come up with some generic code to get all the available
> constraints validated
--
This message was sent by Atlassian JIRA
(v6.1#6144)
