changing WS-Addressing version for proxies to submission

Ok, I've found the cause of the issue. We are using WS-Addressing submission from 2004/03, but Axis/Synapse recognizes 2004/08. When I've change NS to the one below, everything is working fine. http://schemas.xmlsoap.org/ws/2004/08/addressing Is there a way to change to the older version of submission? Michal Stochmialek R&D Leader, eurobank

Hi Michal, I am sorry there is no direct means of doing this, unless you go through an another proxy layer to switch the addressing version. If you could elaborate on your exact requirements, I could help you to get that working with the ESB. Thanks, Ruwan Linton

By having a look at the query once again, I don't think you need to switch to the new addressing version within ESB. ESB can understand the submission version of the addressing headers as well. Please elaborate on your requirement, I will try my best to help you get through this. If you cannot send this information in public please use my email [ruwan AT wso2 DOT com] Thanks, Ruwan Linton

Ruwan, There are at least two submission versions of ws-addressing. ESB is understanding "http://schemas.xmlsoap.org/ws/2004/08/addressing", but we are using an older version ("http://schemas.xmlsoap.org/ws/2004/03/addressing"). See the difference in the month number? What our requirement? We need to create a proxy that translates from SOAP 1.1/WS-Addressing Submission/2004/03 (a client side) to a SOAP 1.1 (a server side). There also will be a change in payload (which is not a big issue). inSequence is simple. Just remove WS-Addressing headers. outSequence is the biggest problem. We are not able to set ws-addressing headers in response. I've tried: 1. header mediator - but it only supports flat values. We cannot set <wsa:From><wsa:Address>http://example.com</wsa:From></wsa:Address> using it. 2. xslt mediator - but they don't work for headers: <xslt key="wsa-response.xsl" source="soapenv:Header" /> <xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/03/addressing"> <xsl:output method="xml" omit-xml-declaration="yes" /> <xsl:template match="/"> <xsl:apply-templates select="soapenv:Header"/> </xsl:template> <xsl:template match="soapenv:Header"> <soapenv:Header> <wsa:MessageID soapenv:mustUnderstand="0"><xsl:value-of select="wsa:MessageID"/>-RESPONSE</wsa:MessageID> <wsa:To soapenv:mustUnderstand="0"><xsl:value-of select="wsa:From/wsa:Address"/></wsa:To> <wsa:From soapenv:mustUnderstand="0"> <wsa:Address><xsl:value-of select="wsa:To"/></wsa:Address> </wsa:From> <wsa:RelatesTo soapenv:mustUnderstand="0" wsa:RelationshipType="wsa:Reply"><xsl:value-of select="wsa:MessageID"/></wsa:RelatesTo> </soapenv:Header> </xsl:template> </xsl:stylesheet> 3. xquery mediator - but they also don't work for headers: <xquery key="wsa-response.xq" target="soapenv:Header"> <variable name="header" type="ELEMENT" expression="soapenv:Header"/> </xquery> <x><![CDATA[ declare namespace soapenv="http://schemas.xmlsoap.org/soap/envelope/" ; declare namespace wsa="http://schemas.xmlsoap.org/ws/2004/03/addressing"; declare variable $header as document-node() external; <soapenv:Header xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/03/addressing"> <wsa:MessageID soapenv:mustUnderstand="0">{$header//wsa:MessageID/child::text()}-RESPONSE</wsa:MessageID> <wsa:To soapenv:mustUnderstand="0">{$header//wsa:From/wsa:Address/child::text()}</wsa:To> <wsa:From soapenv:mustUnderstand="0"> <wsa:Address>{$header//wsa:To/child::text()}</wsa:Address> </wsa:From> <wsa:RelatesTo soapenv:mustUnderstand="0" wsa:RelationshipType="wsa:Reply">{$header//wsa:MessageID/child::text()}</wsa:RelatesTo> </soapenv:Header> ]]></x> Both XQuery and XSLT removes whole Header element. I've tried on the message in the first post. Any suggestions? Michal Stochmialek R&D Leader, eurobank

Hi Michael There are two possible fixes.. add support into the WS-Addressing, if the Submission version is used by other SOAP stacks - this is the proper solution, and should not be that difficult either. >Both XQuery and XSLT removes whole Header element. I've tried on the message in the first post This could be due to WS-A getting engaged on the proxy from the axis2.xml.. after an XSLT/XQ on the out message, try a full Log mediator, and check the output. If you see the correct message, next step will not be that difficult cheers asankha http://adroitlogic.org

> There are two possible fixes.. add support into the WS-Addressing, if the Submission > version is used by other SOAP stacks - this is the proper solution, and should not be > that difficult either. I would be happy to see this solution implemented. What chances are this will be fixed in a near future? > This could be due to WS-A getting engaged on the proxy from the axis2.xml.. after an > XSLT/XQ on the out message, try a full Log mediator, and check the output. If you see > the correct message, next step will not be that difficult I've checked it already. I'm logging the full message just after transformation. The message in the output doesn't contain headers. Michal Stochmialek R&D Leader, eurobank

Hi Michal >I would be happy to see this solution implemented. What chances are this will be fixed in a near future? You could raise a JIRA for this on Axis2 (if one does not exist already) >I've checked it already. I'm logging the full message just after transformation. The message in the output doesn't contain headers. This should work!.. let me try your example and get back to you. My suggestion is to use this right now (I am quite sure this could be made to work) and raise the JIRA so that eventually the issue would be handled better for other users as well.. cheers asankha http://adroitlogic.org

I've create a issue: https://issues.apache.org/jira/browse/AXIS2-4211 Michal Stochmialek R&D, eurobank