Thanks.
By the way, I wonder if the fix in CXF will need to be different after
all. See the JAXRS out interceptor validates the JAX-RS *method
response*, and if the validation fails and the custom Response is
created and the out chain is run again, the out validating interceptor
now still attempts to validate (via the extension) the *method
response*, which a custom entity which was created by your mapper does
not represent, rather it is a custom representation of the violations data.
I think, by default, JAXRSBeanValidationOutInterceptor should ignore the
data coming after the optional 2nd run, though the property will be
there to do the 2nd validation
Cheers, Sergey
On 17/10/16 22:28, tomstark wrote:
Slight mod to what you have:
JAXRSUtils.getCurrentMessage().setContent(List.class, new
MessageContentsList(resp));
Using the "put" method did not work but the above code works just fine and I
was able to see the original outbound violations in an error response.
Thanks.
--
View this message in context:
http://cxf.547215.n5.nabble.com/Using-JAXRSBeanValidationOutInterceptor-causes-Fault-when-validation-of-an-object-fails-tp5773878p5773971.html
Sent from the cxf-user mailing list archive at Nabble.com.
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
