You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Sergey Beryozkin (JIRA)" <ji...@apache.org> on 2014/06/03 15:22:01 UTC

[jira] [Resolved] (CXF-5775) Constraint Validation Exceptions Logging at Warn logging.LogUtils

     [ https://issues.apache.org/jira/browse/CXF-5775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sergey Beryozkin resolved CXF-5775.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 3.0.1
         Assignee: Sergey Beryozkin

> 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
>            Assignee: Sergey Beryozkin
>             Fix For: 3.0.1
>
>
> 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)