Ambiguous DispositionReport returned when invalid XML is sent in SOAP request.
------------------------------------------------------------------------------
Key: JUDDI-66
URL: http://issues.apache.org/jira/browse/JUDDI-66
Project: jUDDI
Type: Bug
Versions: 0.9rc1, 0.9rc2, 0.9rc3
Reporter: Steve Viens
Assigned to: Steve Viens
Priority: Minor
Fix For: 0.9
The error information returned in a DispositionReport is much too ambiguous
when invalid XML is sent in SOAP request. For example, the following
find_business API call (notice that the closing </find_business> element is
missing):
<?xml version="1.0" encoding="utf-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>
<soapenv:Body>
<find_business maxRows="100" generic="2.0" xmlns="urn:uddi-org:api_v2">
<name>%</name>
</soapenv:Body>
</soapenv:Envelope>
Will return a DispositionReport that looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server</faultcode>
<faultstring>org.xml.sax.SAXParseException: The element type "find_business"
must be terminated by the matching end-tag "</find_business>".</faultstring>
<detail>
<dispositionReport generic="2.0" operator="Viens.net"
xmlns="urn:uddi-org:api_v2">
<result errno="10500">
<errInfo errCode="E_fatalError" xsi:type="xsd:string">An internal UDDI
server error has occurred. Please report this error to the UDDI server
administrator.</errInfo>
</result>
</dispositionReport>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
The client is in error in this case (not the server) so the SOAP Fault
'faultcode' value should indicate it's a client error and the errInfo text
element should contain the same or similar text that's in the SOAP Fault
'faultstring' attribute.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
