[
https://issues.apache.org/jira/browse/CXF-5775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14016488#comment-14016488
]
Sergey Beryozkin commented on CXF-5775:
---------------------------------------
Hi
I've updated JAXRSBeanValidationInInterceptor to get the default chain-level
logging ignored given that either the default or custom Exception mapper will
deal with it. We can't do it at the core BeanValidationInInterceptor level
though as it can be used by JAX-WS endpoints too
Cheers, Sergey
> Constraint Validation Exceptions Logging at Warn logging.LogUtils
> -----------------------------------------------------------------
>
> Key: CXF-5775
> URL: https://issues.apache.org/jira/browse/CXF-5775
> Project: CXF
> Issue Type: Improvement
> Components: JAX-RS
> Affects Versions: 3.0.0
> Reporter: Peter Davidson
>
> When a ConstraintValidationExceptions are thrown they are bubbled up to the
> PhaseInterceptorChain before being logged. This causes exceptions to be
> logged at logging.LogUtils as a WARN message. This is not ideal because cxf
> validation failures will end up being logged or true cxf WARN messages will
> not be logged. Would be nice if these were logged at a different level, or
> were not logged using the default logger, but instead a custom FaultListener.
> h4. Note
> This is being logged by PhaseInterceptorChain, not the
> ValidationExceptionMapper
> h4. Example Log
> bq. Interceptor for
> {http://profile.services.profile.bodybuilding.com/}ProfileService has thrown
> exception, unwinding now javax.validation.ConstraintViolationException
--
This message was sent by Atlassian JIRA
(v6.2#6252)
