[ https://issues.jboss.org/browse/JBTM-2928?page=com.atlassian.jira.plugin.... ] Ricardo Martin Camarero commented on JBTM-2928: ----------------------------------------------- When the WS-TX is initiated in the windows side, a windows client creates a context with the windows coordinator service and later it calls to a wildfly WS, the process fails at Registration operation. The JBOSS/Wildfly side tries to execute the Registration operation as a client and windows just responds 202 (no content, no XML is returned) which throws a NPE. The XML sent in the request is the following: {code:xml} <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Header> <Action xmlns="http://www.w3.org/2005/08/addressing">http://docs.oas... <MessageID xmlns="http://www.w3.org/2005/08/addressing">urn:a632e947aaf... <To xmlns="http://www.w3.org/2005/08/addressing">https://windows... <ReplyTo xmlns="http://www.w3.org/2005/08/addressing"> <Address>http://www.w3.org/2005/08/addressing/anonymous</Address> </ReplyTo> <mstx:RegisterInfo xmlns="http://www.w3.org/2005/08/addressing" xmlns:mstx="http://schemas.microsoft.com/ws/2006/02/transactions" xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsa="http://www.w3.org/2005/08/addressing" wsa:IsReferenceParameter="1"> <mstx:LocalTransactionId>edd12908-c2f4-427a-86d6-4fab6dde3d32</mstx:LocalTransactionId> </mstx:RegisterInfo> </soap:Header> <soap:Body> <Register xmlns="http://docs.oasis-open.org/ws-tx/wscoor/2006/06" xmlns:ns2="http://www.w3.org/2005/08/addressing"> <ProtocolIdentifier>http://docs.oasis-open.org/ws-tx/wsat/2006/06/Durab... <ParticipantProtocolService> <ns2:Address>https://jboss.sample.com:8443/ws-t11-participant/ParticipantService</ns2:Address> <ns2:ReferenceParameters> <wsarj:InstanceIdentifier xmlns:wsarj="http://schemas.arjuna.com/ws/2005/10/wsarj" xmlns:wsa="http://www.w3.org/2005/08/addressing">restaurantS... </ns2:ReferenceParameters> <ns2:Metadata> <wsam:ServiceName xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata" xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:wsat="http://docs.oasis-open.org/ws-tx/wsat/2006/06" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" EndpointName="ParticipantPortType">wsat:ParticipantService</wsam:ServiceName> </ns2:Metadata> </ParticipantProtocolService> </Register> </soap:Body> </soap:Envelope> {code} After some tests it seems that windows implementation does not understand the _"http://www.w3.org/2005/08/addressing/anonymous"_ as *ReplyTo*. The request should send a *ReplyTo* with a valid URL and the Microsoft implementation calls back to that URL with the RegisterResponse type. We think that "anonymous" behavior is covered by the standard (it means synchronous execution) and that the windows implementation is an extreme interpretation of the specification (with that idea any partner, even an standalone application that calls to two web services with WS-TX support, needs to have endpoints and be a web server too). References of the ws-addressing spec about anonymous in [current|https://www.w3.org/TR/2006/REC-ws-addr-core-20060509/#eprinfomodel] and [previous spec|https://www.w3.org/Submission/ws-addressing/#_Toc77464322]. -- This message was sent by Atlassian JIRA (v7.5.0#75005)