Hi, We are trying to implement a couple of services in Apache Axis2 and Apache Synapse which must conform to the Dutch specifications ‘Digikoppeling’ and 'SuwiML Transactiestandaard’. This is basically ‘WS-I Basic Profile 1.1’ with a few additional requirements.
One of the requirements is the use of the WS-Addressing To header in the response. Although the services only have synchronous request-response operations we have to set the wsa:To header in the response to a custom value. The result is that Axis2 tries to send the response to the address specified in the wsa:To header, which we don’t want since this is a synchronous request-response operation. I noticed that this is the case for both the Axis2 Commons HTTP sender (CommonsHTTPTransportSender.java @ 221) and the Apache Synapse PassThrough (PassThroughHttpSender.java @ 258) and NIO sender (HttpCoreNIOSender.java @ 257). The 'Web Services Addressing 1.0 - SOAP Binding’ specification states that ‘any response message SHOULD be sent using a separate connection and using the address value specified by response endpoint’ when a value other than "http://www.w3.org/2005/08/addressing/anonymous"; is used, but this applies to 'response endpoint’, which ‘refers to the [reply endpoint] and [fault endpoint]’ (see https://www.w3.org/TR/ws-addr-soap/#addressesinsoap). It’s not clear to me if the ‘reply endpoint’ or ‘fault endpoint’ refers to the wsa:From header in the response or only the ReplyTo and FaultTo in the request. Is the implementation in Axis2 and Synapse too strict and should it allow any value for the wsa:To in the response, or does our requirement conflict with the WS-Addressing specification? Auke --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org For additional commands, e-mail: java-user-h...@axis.apache.org
