Return-Path: 
 <dev-return-8419-apmail-synapse-dev-archive=synapse.apache.org@synapse.apache.org>
Delivered-To: apmail-synapse-dev-archive@www.apache.org
Received: (qmail 46757 invoked from network); 13 Jan 2009 18:26:35 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 13 Jan 2009 18:26:35 -0000
Received: (qmail 85471 invoked by uid 500); 13 Jan 2009 18:26:35 -0000
Delivered-To: apmail-synapse-dev-archive@synapse.apache.org
Received: (qmail 85281 invoked by uid 500); 13 Jan 2009 18:26:34 -0000
Mailing-List: contact dev-help@synapse.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@synapse.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@synapse.apache.org>
List-Post: <mailto:dev@synapse.apache.org>
List-Id: <dev.synapse.apache.org>
Reply-To: dev@synapse.apache.org
Delivered-To: mailing list dev@synapse.apache.org
Received: (qmail 85272 invoked by uid 99); 13 Jan 2009 18:26:34 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Jan 2009 10:26:34 -0800
X-ASF-Spam-Status: No, hits=-2000.0 required=10.0
	tests=ALL_TRUSTED
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; Tue, 13 Jan 2009 18:26:24 +0000
Received: from brutus (localhost [127.0.0.1])
	by brutus.apache.org (Postfix) with ESMTP id D8FEE234C48B
	for <dev@synapse.apache.org>; Tue, 13 Jan 2009 10:26:02 -0800 (PST)
Message-ID: <2096670723.1231871162887.JavaMail.jira@brutus>
Date: Tue, 13 Jan 2009 10:26:02 -0800 (PST)
From: "Asankha C. Perera (JIRA)" <jira@apache.org>
To: dev@synapse.apache.org
Subject: [jira] Resolved: (SYNAPSE-498) Make it easier to detect fault
 messages when mediating them
In-Reply-To: <895857313.1231323164261.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/SYNAPSE-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Asankha C. Perera resolved SYNAPSE-498.
---------------------------------------

    Resolution: Fixed

The XPath extension function get-property() is now extended to indicate if the message (ie the transport, message formatter, or message payload) indicates a fault message

To detect SOAP 1.1 / 1.2, POX, and other (e.g. Hessian) faults etc, one can just write:

                <filter xpath="get-property('FAULT')">
                    <!-- fault logic here -->
                    <log level="custom">
                        <property name="MSG" value="SOAP Fault"/>
                    </log>
                </filter>

This also eliminates the need to write a long XPath expression to detect SOAP 1.1/1.2 faults:

<filter xpath="/soap11:Envelope/soap11:Body/soap11:Fault or /soap12:Envelope/soap12:Body/soap12:Fault" 
                    xmlns:soap11="http://schemas.xmlsoap.org/soap/envelope/" 
                    xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
                

> Make it easier to detect fault messages when mediating them
> -----------------------------------------------------------
>
>                 Key: SYNAPSE-498
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-498
>             Project: Synapse
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.2
>            Reporter: Asankha C. Perera
>            Assignee: Asankha C. Perera
>            Priority: Minor
>             Fix For: 1.3
>
>
> It should be easy to find if a message being mediated upon is an error or a fault. Currently for SOAP interactions, one may have to write a filter as shown below to detect a SOAP 1.1 and/or 1.2 fault
> <filter xpath="/soap11:Envelope/soap11:Body/soap11:Fault or /soap12:Envelope/soap12:Body/soap12:Fault"
>                     xmlns:soap11="http://schemas.xmlsoap.org/soap/envelope/"
>                     xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
> It should also be possible for someone to check for POX and other types of faults, which maybe indicated by the transport and/or other (possibly within the payload of a binary message) information as well. e.g. HTTP response code for POX, custom binary indication for Hessian
> One possible way of implementing this is using the get-property() function, and allowing someone to detect any known fault messages with say a "get-property('FAULT')" call - which could check for SOAP 1.1/1.2, HTTP non-2xx, and Hessian faults etc. For HTTP one could also check the status code via the already available HTTP_SC property on the Axis2 message context level.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org