Return-Path: Delivered-To: apmail-cxf-issues-archive@www.apache.org Received: (qmail 49975 invoked from network); 8 Oct 2008 12:18:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 8 Oct 2008 12:18:16 -0000 Received: (qmail 90862 invoked by uid 500); 8 Oct 2008 12:18:15 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 90818 invoked by uid 500); 8 Oct 2008 12:18:15 -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 90807 invoked by uid 99); 8 Oct 2008 12:18:15 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Oct 2008 05:18:15 -0700 X-ASF-Spam-Status: No, hits=-1999.9 required=10.0 tests=ALL_TRUSTED,DNS_FROM_SECURITYSAGE X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Oct 2008 12:17:08 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 52591234C210 for ; Wed, 8 Oct 2008 05:17:44 -0700 (PDT) Message-ID: <1531650636.1223468264336.JavaMail.jira@brutus> Date: Wed, 8 Oct 2008 05:17:44 -0700 (PDT) From: "Daniel Kulp (JIRA)" To: issues@cxf.apache.org Subject: [jira] Commented: (CXF-1849) PolicyVerificationOutInterceptor writes faults at wrong phase when processing response In-Reply-To: <1106633241.1223460704647.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/CXF-1849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637897#action_12637897 ] Daniel Kulp commented on CXF-1849: ---------------------------------- I think policy verification on the outgoing side needs to just log an error, not throw an exception. With streaming, there really isn't a way to "undo" what was written. Either that, or all the policies need two interceptors. One that runs very early to make sure the policy is assertable and then a second that really does the work. > PolicyVerificationOutInterceptor writes faults at wrong phase when processing response > -------------------------------------------------------------------------------------- > > Key: CXF-1849 > URL: https://issues.apache.org/jira/browse/CXF-1849 > Project: CXF > Issue Type: Bug > Components: WS-* Components > Affects Versions: 2.1.2 > Reporter: Fred Dushin > Fix For: 2.1.3, 2.2 > > > When a CXF response is processed on an endpoint that contains policy assertions (via spring, WSDL, etc), and the policy assertions are not marked as asserted, the PolicyVerificationOutInterceptor properly raises a SOAP fault. However, this interceptor is inserted into the "post-stream" phase, and it seems as though the fault gets written to the SOAP body after the business logic has been written. > So a response in this scenario will come out as follows: > > > > Bonjou > > > soap:Server > These policy alternatives can not be satisfied: [snip] > > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.