faultactor element disappears when detail element is present in SOAP Fault
--------------------------------------------------------------------------
Key: XFIRE-1056
URL: http://jira.codehaus.org/browse/XFIRE-1056
Project: XFire
Issue Type: Bug
Affects Versions: 1.2.6
Environment: Xfire 1.2.6, SOAP 1.1 (other environment factors are
irrelevant. see description)
Reporter: Allard Buijze
Assignee: Dan Diephouse
Fix For: 1.2.7
When the XFire client receives a SOAP Fault, it is parsed into an XFireFault
(exception). However, if this SOAP Fault contains a "detail" element, the
faultactor element is no longer parsed.
I have debugged the parsers and found the exact cause and location of the error:
When de details element is parsed, there is one call too many on r.next (r =
XMLStreamReader) in StaxBuilder.java on line 446. This causes the pointer to be
on the start element of the "faultactor" tag. After returning to the file
Soap11FaultSerializer.java on line 68 and returning back to the loop, on line
40, there is another call to r.next (r = same XMLStreamReader instance as
above).
The result is that the element following the "details" element in the SOAP
Fault (in my case that is "faultactor") is never parsed.
--
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
