[jbossts-issues] [JBoss JIRA] (JBTM-3031) Error messages for XTS registration is unprecise and hardly tracable
Ondra Chaloupka (JIRA)
issues at jboss.org
Fri Jun 8 05:42:00 EDT 2018
Ondra Chaloupka created JBTM-3031:
-------------------------------------
Summary: Error messages for XTS registration is unprecise and hardly tracable
Key: JBTM-3031
URL: https://issues.jboss.org/browse/JBTM-3031
Project: JBoss Transaction Manager
Issue Type: Bug
Components: XTS
Affects Versions: 5.8.2.Final
Reporter: Ondra Chaloupka
Assignee: Ondra Chaloupka
Based on the changes made for JBTM-2928 : Provide WS-AT Integration with .NET we discussed with [~f_marchioni] there are gaps in understandability of error messages and it's hard to be traced.
The point is to report the XTS WS-AT register errors in better way.
Here is some of the points
{quote}
Francesco Marchioni: In the test testAlreadyRegisteredProtocolIdentifierException
Francesco Marchioni: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Header>
<Action xmlns="http://www.w3.org/2005/08/addressing">http://docs.oasis-open.org/ws-tx/wscoor/2006/06/Register<...>
<MessageID xmlns="http://www.w3.org/2005/08/addressing">testAlreadyRegisteredProtocolIdentifierException</Messag...>
<To xmlns="http://www.w3.org/2005/08/addressing">http://localhost:8080/ws-c11/RegistrationService</To>
<ReplyTo xmlns="http://www.w3.org/2005/08/addressing">
<Address>http://localhost:8080/ws-c11/RegistrationResponseService</Address>
</ReplyTo>
<FaultTo xmlns="http://www.w3.org/2005/08/addressing">
<Address>http://localhost:8080/ws-c11/CoordinationFaultService</Address>
</FaultTo>
<wsarj:InstanceIdentifier xmlns:wsarj="http://schemas.arjuna.com/ws/2005/10/wsarj" xmlns="http://www.w3.org/2005/08/addressing" xmlns:wsa="http://www.w3.org/2005/08/addressing" wsa:IsReferenceParameter="1">identifier</wsarj:InstanceIdentifier>
</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://wsc.example.org/already-registered-protocol-identifier</ProtocolIdentifier>
<ParticipantProtocolService>
<ns2:Address>http://wsc.example.org/protocol-participant-service</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">participant</wsarj:InstanceIdentifier>
</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:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:wsc="http://wsc.example.org/" EndpointName="ProtocolParticipantEndpoint">wsc:ProtocolParticipantService</wsam:ServiceName>
</ns2:Metadata>
</ParticipantProtocolService>
</Register>
</soap:Body>
</soap:Envelope><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Header>
<Action xmlns="http://www.w3.org/2005/08/addressing">http://schemas.xmlsoap.org/wsdl/soap/envelope/fault</Act...>
<MessageID xmlns="http://www.w3.org/2005/08/addressing">urn:uuid:e4953fa1-0dc2-41cb-a565-0f446fa0e86c</MessageID>
<To xmlns="http://www.w3.org/2005/08/addressing">http://localhost:8080/ws-c11/CoordinationFaultService</T...>
<RelatesTo xmlns="http://www.w3.org/2005/08/addressing">testAlreadyRegisteredProtocolIdentifierException</Relate...>
</soap:Header>
<soap:Body>
<soap:Fault>
<faultcode xmlns:wscoor="http://docs.oasis-open.org/ws-tx/wscoor/2006/06">wscoor:CannotRegister</faultcode>
<faultstring>Sender</faultstring>
<detail>
<wscoor:CannotRegister xmlns:wscoor="http://docs.oasis-open.org/ws-tx/wscoor/2006/06">ARJUNA042081: Participant already registered</wscoor:CannotRegister>
</detail>
</soap:Fault>
</soap:Body>
</soap:Envelope>
Francesco Marchioni: The Exception message seem not correct: It's "Participant already registered"
{quote}
{quote}
Francesco Marchioni: RegistrationServiceTest there's one similar
Francesco Marchioni: <soap:Header>
<Action xmlns="http://www.w3.org/2005/08/addressing">http://schemas.xmlsoap.org/wsdl/soap/envelope/fault</Act...>
<MessageID xmlns="http://www.w3.org/2005/08/addressing">urn:uuid:ff6387eb-df3a-4e97-9349-d39c042ac584</MessageID>
<To xmlns="http://www.w3.org/2005/08/addressing">http://localhost:8080/ws-c11/CoordinationFaultService</T...>
<RelatesTo xmlns="http://www.w3.org/2005/08/addressing">testUnknownCoordinationType</RelatesTo>
</soap:Header>
<soap:Body>
<soap:Fault>
<faultcode xmlns:wscoor="http://docs.oasis-open.org/ws-tx/wscoor/2006/06">wscoor:InvalidProtocol</faultcode>
<faultstring>Sender</faultstring>
<detail>
<wscoor:InvalidParameters xmlns:wscoor="http://docs.oasis-open.org/ws-tx/wscoor/2006/06">ARJUNA042082: Invalid protocol identifier</wscoor:InvalidParameters>
</detail>
</soap:Fault>
</soap:Body>
</soap:Envelope>
Francesco Marchioni: It says "invalid protocol identifier" for a test of unknownCoordinationType
{quote}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
More information about the jbossts-issues
mailing list