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 C97B99C1B for ; Sun, 30 Sep 2012 14:19:07 +0000 (UTC) Received: (qmail 94231 invoked by uid 500); 30 Sep 2012 14:19:07 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 94208 invoked by uid 500); 30 Sep 2012 14:19:07 -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 94198 invoked by uid 99); 30 Sep 2012 14:19:07 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 30 Sep 2012 14:19:07 +0000 Date: Mon, 1 Oct 2012 01:19:07 +1100 (NCT) From: "Benson Margulies (JIRA)" To: issues@cxf.apache.org Message-ID: <1230859511.145527.1349014747705.JavaMail.jiratomcat@arcas> In-Reply-To: <562007385.145430.1349012707709.JavaMail.jiratomcat@arcas> Subject: [jira] [Resolved] (CXF-4528) WebApplicationExceptionMapper is too shy 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-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies resolved CXF-4528. ----------------------------------- Resolution: Fixed fixed in trunk in 1392027. > WebApplicationExceptionMapper is too shy > ---------------------------------------- > > Key: CXF-4528 > URL: https://issues.apache.org/jira/browse/CXF-4528 > Project: CXF > Issue Type: Bug > Components: JAX-RS > Affects Versions: 2.6.2 > Reporter: Benson Margulies > Assignee: Benson Margulies > Fix For: 2.6.3, 2.7.0 > > > When an application installs a FaultListener, and the FaultListener requests logging, the logging should be INFO or WARN, not DEBUG. Further, the 'printStackTrace' feature should apply only to the non-Listener case, as the listener can perfectly well log stack traces if it likes. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira