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 44BA418933 for ; Mon, 18 Jan 2016 13:45:41 +0000 (UTC) Received: (qmail 5721 invoked by uid 500); 18 Jan 2016 13:45:40 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 5675 invoked by uid 500); 18 Jan 2016 13:45:40 -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 5655 invoked by uid 99); 18 Jan 2016 13:45:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Jan 2016 13:45:40 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id CDAA42C1F57 for ; Mon, 18 Jan 2016 13:45:39 +0000 (UTC) Date: Mon, 18 Jan 2016 13:45:39 +0000 (UTC) From: "Sabiya Kazi (JIRA)" To: issues@cxf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CXF-6605) WS-Addressing 07/05 not working 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-6605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sabiya Kazi updated CXF-6605: ----------------------------- Attachment: ordermanagement.zip Hi Akitoshi, Please find attached maven project for scenario mentioned above. I get an error while invoking a service from SOAP-UI. Please let me know if you have any further queries. Regards, -Sabiya > WS-Addressing 07/05 not working > ------------------------------- > > Key: CXF-6605 > URL: https://issues.apache.org/jira/browse/CXF-6605 > Project: CXF > Issue Type: Bug > Components: WS-* Components > Affects Versions: 3.1.2 > Environment: Win 8, current Spring Boot, Embedded Tomcat > Reporter: Stefan Kuhn > Labels: easyfix > Attachments: AddressingMetadataNamespace.patch, ErrorMessageAtClient.bmp, ExceptionTrace.txt, ordermanagement.zip > > Original Estimate: 2h > Remaining Estimate: 2h > > using > xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata" instead of > xmlns:wsam="http://www.w3.org/2007/02/addressing/metadata" > invalidates valid WS requests. > e.g. in my usecase, the WSDL uses > > > > > > and > > > > Springs CXF configuration uses the policy interceptor with > > > > > > > and > publish="true" > implementor="#outbound" > address="/OrderManagementServiceOutbound" > serviceName="s:OrderManagementServiceOutbound" > endpointName="s:OrderManagementResponsePort" > wsdlLocation="/wsdl/OrderManagementServiceOutbound.wsdl" > xmlns:s="urn:OrderManagementServiceOutbound"> > > > > > > > > > > > > > I've used CXF and SOAP-UI as a client for the server application, both successful for 2007/02, both unsuccessful for 2007/05. > CXF replies to the same request with > > ns1:MessageAddressingHeaderRequired > A required header representing a Message Addressing Property is not present > > It seems to me, that the qualified name of ADDRESSING_ASSERTION_QNAME_0705 is not added to the QName[] types in org.apache.cxf.ws.addressing.impl.MAPAggregatorImpl.assertAddressing(Message, EndpointReferenceType, EndpointReferenceType), Line 334. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)