Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Sat, 22 Mar 2014 12:12:44 +0000 (UTC)
From: "Daniel Kulp (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <JIRA.12702641.1395324968142.124617.1395490364526@arcas>
In-Reply-To: <JIRA.12702641.1395324968142@arcas>
References: <JIRA.12702641.1395324968142@arcas>
Subject: [jira] [Commented] (CXF-5630) In robust one-way fault the fault
 message should result in SOAPFaultException
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CXF-5630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13944036#comment-13944036 ] 

Daniel Kulp commented on CXF-5630:
----------------------------------

Certainly not supportable at all with JMS.  We could try it with the Local trasnport since we could pass the "robust" flag right along from the client side so the server would know to send something back either way.  

> In robust one-way fault the fault message should result in SOAPFaultException
> -----------------------------------------------------------------------------
>
>                 Key: CXF-5630
>                 URL: https://issues.apache.org/jira/browse/CXF-5630
>             Project: CXF
>          Issue Type: Bug
>            Reporter: Grzegorz Grzybek
>            Assignee: Daniel Kulp
>             Fix For: 3.0.0, 2.7.11
>
>
> Now in {{org.apache.cxf.transport.http.HTTPConduit.WrappedOutputStream.handleResponseInternal()}} there's just one check if the exchange is one-way without checking the "robust" status and if exchange is one way, any soap fault is consumed.
> I'm not sure how this should be handled, as _robustnes_ is not defined per SOAP 1.1


--
This message was sent by Atlassian JIRA
(v6.2#6252)