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 8A393D7C6 for ; Tue, 16 Oct 2012 21:57:04 +0000 (UTC) Received: (qmail 63901 invoked by uid 500); 16 Oct 2012 21:57:04 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 63846 invoked by uid 500); 16 Oct 2012 21:57:04 -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 63597 invoked by uid 99); 16 Oct 2012 21:57:04 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Oct 2012 21:57:04 +0000 Date: Tue, 16 Oct 2012 21:57:04 +0000 (UTC) From: "Alessio Soldano (JIRA)" To: issues@cxf.apache.org Message-ID: <1217468340.54016.1350424624177.JavaMail.jiratomcat@arcas> In-Reply-To: <1828417251.54000.1350424383486.JavaMail.jiratomcat@arcas> Subject: [jira] [Resolved] (CXF-4576) Provide logs on policy attachment parsing errors 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-4576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alessio Soldano resolved CXF-4576. ---------------------------------- Resolution: Fixed > Provide logs on policy attachment parsing errors > ------------------------------------------------ > > Key: CXF-4576 > URL: https://issues.apache.org/jira/browse/CXF-4576 > Project: CXF > Issue Type: Improvement > Components: WS-* Components > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: 2.7.1 > > > PolicyAnnotationListener is completely silent when failing parsing a policy from an external policy file. User has no clue of what might be wrong in the policy and might have caused the policy attachment to be silently ignored. > We should output at least a minimal warning with the exception message. -- 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