Or try JAXRSBeanValidationInvoker (register it with jaxrs:invoker)
Sergey
On 14/10/16 22:17, Sergey Beryozkin wrote:
Hi
See
https://issues.apache.org/jira/browse/CXF-7091
We are voting for a 3.1.8 release right now, so I can only guess at this
stage that 3.1.9 will be out by the end of Dec or
Hi
See
https://issues.apache.org/jira/browse/CXF-7091
We are voting for a 3.1.8 release right now, so I can only guess at this
stage that 3.1.9 will be out by the end of Dec or early January.
Please try CXF interceptors in meantime
Cheers, Sergey
On 14/10/16 21:59, tomstark wrote:
Hi
Hi Sergey,
Thanks for the info. I'll try your suggestion.
Do you have a time frame for when 3.1.9 would be released? Also, can you
reply with the bug number so I can track it? Depending on timing, I may
have to wait to pick up the fix until our next release.
Thanks.
--
View this message
Hi
Yes, the response filters are expected to be run again after an
exception has been mapped. The fact that the abstract CXF filter sees
the original value on the 2nd run is a bug, in most case the default
mapper which only creates an HTTP error is sufficient. So I guess this
is why this
I'm trying to use the JAXRSBeanValidationOutInterceptor with a customized
ValidationExceptionMapper but it throws a Fault when processing instead of
returning a response with the violations.
Here is the scenario:
When a Response is built with an entity object that has violations, the
interceptor
Hi
thanks, well, I guess there is some specific code sequence there, when
ReplaceOutInterceptor2 is run, which exposes a bug. As far as I know
CachedOutputStream was created to support some typical request/response
situations and I'm not sure it was ever meant to be used publicly - it
is
Hi!
Please see
https://github.com/slavb18/cachedstreamtest
There is 2 interceptors
My first variant based on AbstractPhaseInterceptor
https://github.com/slavb18/cachedstreamtest/blob/master/src/main/java/ru/ilb/common/jaxrs/interceptors/ReplaceOutInterceptor2.java
is not working with large
