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 9164B1147B for ; Sun, 13 Jul 2014 01:25:06 +0000 (UTC) Received: (qmail 92552 invoked by uid 500); 13 Jul 2014 01:25:04 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 92511 invoked by uid 500); 13 Jul 2014 01:25: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 92444 invoked by uid 99); 13 Jul 2014 01:25:04 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 13 Jul 2014 01:25:04 +0000 Date: Sun, 13 Jul 2014 01:25:04 +0000 (UTC) From: "Roberto (JIRA)" To: issues@cxf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CXF-5875) Problems in WS-Addressing with anonymous replyTo or faultTo Address MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Roberto created CXF-5875: ---------------------------- Summary: Problems in WS-Addressing with anonymous replyTo or faultTo Address Key: CXF-5875 URL: https://issues.apache.org/jira/browse/CXF-5875 Project: CXF Issue Type: Bug Components: WS-* Components Affects Versions: 3.0.0 Environment: Windows 7 64-bits JDK 1.7.0_51 64-bits Reporter: Roberto Priority: Minor In WS-Addressing, setting the fault-to WSA_ANONYMOUS_ADDRESS does not work if reply-to is set to a different server. Example: EndpointReferenceType replyTo = EndpointReferenceUtils.getEndpointReference("http://localhost:9092/callback"); EndpointReferenceType faultTo = EndpointReferenceUtils.getEndpointReference(Names.WSA_ANONYMOUS_ADDRESS) AddressingProperties maps = new AddressingProperties(); maps.setReplyTo(replyTo); maps.setFaultTo(faultTo); requestContext.put(CLIENT_ADDRESSING_PROPERTIES, maps); In this case, I expect successful replys sent to "http://localhost:9092/callback", and exceptions sent back to client. Instead of that, both answers are sent to "http://localhost:9092/callback". I made some tests for the following cases: Case 1 (No problems found): replyTo=endpoint 1 -> result: reply sent to endpoint 1 (OK) faultTo=endpoint 2 -> result: fault sent to endpoint 2 (OK) Case 2 (No problems found): replyTo=WSA_ANONYMOUS_ADDRESS -> result: reply sent back to client (OK) faultTo=WSA_ANONYMOUS_ADDRESS -> result: fault sent back to client (OK) Case 3 (Unexpected message received in client) replyTo=WSA_ANONYMOUS_ADDRESS -> result: reply sent back to client (OK) faultTo=endpoint 2 -> result: fault sent to endpoint 2 (OK), but client recieves an extra empty message which raises an exception (WRONG): "org.apache.cxf.binding.soap.SoapFault: Error reading XMLStreamReader: Unexpected EOF in prolog" Case 4 (Exception sent to replyTo instead of faultTo) replyTo=endpoint 1 -> result: reply sent to endpoint 1 (OK) faultTo=WSA_ANONYMOUS_ADDRESS -> result: reply sent to endpoint 1 (WRONG) -- This message was sent by Atlassian JIRA (v6.2#6252)