XFireFault serialization is not compliant w/ SOAP 1.2, and fails XML validation
-------------------------------------------------------------------------------
Key: XFIRE-995
URL: http://jira.codehaus.org/browse/XFIRE-995
Project: XFire
Issue Type: Bug
Components: Core
Affects Versions: 1.2.5
Reporter: Reshat Sabiq
Assignee: Dan Diephouse
Attachments: soap-fault-w3-schema-compliance-and-validatability.patch
Attached patch ensures that it is valid by changing SubCode to subcode, and
adding xml:lang to Text. The patch also provides for re-use of
Soap12FaultSerializer for custom XFireFault type, given that XFireFault is not
currently serialized into soap:Fault when it is a descendant of a child of
soap:Body. Patch also includes updates to junit tests to make sure they pass.
E.g., the following is a valid example, which is produced after applying the
patch attached:
<soap:Fault>
<soap:Code>
<soap:Value>soap:Receiver</soap:Value>
<soap:Subcode>
<soap:Value
xmlns:error="urn:some.urn">error:MainframeConnectionFailed</soap:Value>
</soap:Subcode>
</soap:Code>
<soap:Reason>
<soap:Text xml:lang="en">Mainframe Connection
Failed</soap:Text>
</soap:Reason>
<soap:Detail>
<error:detail code="2001"
xmlns:error="urn:some.urn">Failed to retrieve a security context from the
mainframe.</error:detail>
</soap:Detail>
</soap:Fault>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
