Return-Path: X-Original-To: apmail-cxf-issues-archive@www.apache.org Delivered-To: apmail-cxf-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D991310612 for ; Wed, 28 May 2014 15:14:01 +0000 (UTC) Received: (qmail 38528 invoked by uid 500); 28 May 2014 15:14:01 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 38496 invoked by uid 500); 28 May 2014 15:14:01 -0000 Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list issues@cxf.apache.org Received: (qmail 38488 invoked by uid 99); 28 May 2014 15:14:01 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 May 2014 15:14:01 +0000 Date: Wed, 28 May 2014 15:14:01 +0000 (UTC) From: "Peter Davidson (JIRA)" To: issues@cxf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CXF-5775) Constraint Validation Exceptions Logging at Warn logging.LogUtils MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CXF-5775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Davidson updated CXF-5775: -------------------------------- Description: 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 was: 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. Example Log bq. Interceptor for {http://profile.services.profile.bodybuilding.com/}ProfileService has thrown exception, unwinding now javax.validation.ConstraintViolationException > 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)