RegisterResponse interop issue with .NET 3.5
gllambi Jan 25, 2010 11:48 AMHi!!! while doing some interop test between .NET 3.5 and jboss using ws-at 1.1 and I'm having some problems during the registration phase. In particular, when JBoss creates the RegisterResponse message.
Here's a register message made by the XTS
<env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'> <env:Header xmlns:wsa='http://www.w3.org/2005/08/addressing'> <wsa:To>http://vmxp.localdomain:8080/ws-c11/RegistrationService</wsa:To> <wsa:Action>http://docs.oasis-open.org/ws-tx/wscoor/2006/06/Register</wsa:Action> <wsa:MessageID>urn:3dbed0d84e3d4aab:-56340795:1266668751d:-7ca8</wsa:MessageID> <wsarj:InstanceIdentifier wsa:IsReferenceParameter='true' xmlns:wsarj='http://schemas.arjuna.com/ws/2005/10/wsarj'>-3f570b7e:d22:4b5dcd91:12a</wsarj:InstanceIdentifier> </env:Header> <env: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/Durable2PC</ProtocolIdentifier> <ParticipantProtocolService> <ns2:Address>http://vmxp.localdomain:8080/ws-t11/ParticipantService</ns2:Address> <ns2:ReferenceParameters> <wsarj:InstanceIdentifier xmlns:wsarj='http://schemas.arjuna.com/ws/2005/10/wsarj'>BridgeParticipantAT_-3f570b7e:d22:4b5dcd91:12d</wsarj:InstanceIdentifier> </ns2:ReferenceParameters> <ns2:Metadata> <Metadata wsdlLocation='https://192.168.244.130:8443/ws-c11/RegistrationService?wsdl' xmlns='' xmlns:ns3='http://docs.oasis-open.org/ws-tx/wscoor/2006/06'> <InterfaceName>RegistrationService</InterfaceName> </Metadata> </ns2:Metadata> </ParticipantProtocolService> </Register> </env:Body> </env:Envelope>
and here's the registerResponse message also made by the XTS:
<env:Envelope xmlns:env='http://schemas.xmlsoap.org/soap/envelope/'> <env:Header xmlns:wsa='http://www.w3.org/2005/08/addressing'> <wsa:To>http://www.w3.org/2005/08/addressing/anonymous</wsa:To> <wsa:Action>http://docs.oasis-open.org/ws-tx/wscoor/2006/06/RegistrationPortType/RegisterOperationResponse</wsa:Action> <wsa:RelatesTo>urn:3dbed0d84e3d4aab:-56340795:1266668751d:-7ca8</wsa:RelatesTo> </env:Header> <env:Body> <RegisterResponse xmlns='http://docs.oasis-open.org/ws-tx/wscoor/2006/06' xmlns:ns2='http://www.w3.org/2005/08/addressing'> <CoordinatorProtocolService> <ns2:Address>http://vmxp.localdomain:8080/ws-t11/CoordinatorService</ns2:Address> <ns2:ReferenceParameters> <wsarj:InstanceIdentifier xmlns:wsarj='http://schemas.arjuna.com/ws/2005/10/wsarj'>D-3f570b7e:d22:4b5dcd91:136</wsarj:InstanceIdentifier> </ns2:ReferenceParameters> <ns2:Metadata/> </CoordinatorProtocolService> </RegisterResponse> </env:Body> </env:Envelope>
As you can see the WS-Addressing action in the response is http://docs.oasis-open.org/ws-tx/wscoor/2006/06/RegistrationPortType/RegisterOperationResponse. Is this action right? as far as I now it's http://docs.oasis-open.org/ws-tx/wscoor/2006/06/RegisterResponse.
I'm having an interop issue and I suppose the reason is this. If someone could answer this, I would appreciatte it a lot
Thanks
Guzman