axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "benson margulies (JIRA)" <axis-...@ws.apache.org>
Subject [jira] Commented: (AXIS-2356) Axis fails to deserialize faults that involve text elements
Date Wed, 26 Apr 2006 14:09:03 GMT
    [ http://issues.apache.org/jira/browse/AXIS-2356?page=comments#action_12376487 ] 

benson margulies commented on AXIS-2356:
----------------------------------------

You can pick up my patch and apply it to your copy of Axis 1.3. I've been running with the
patch for months now. This seems to be a clear case of 'be picky in what you generate, but
generous in what you accept' or whoever that protocol cliche works out.

On the one hand, the consensus of a discussion elsewhere is that the standard really doesn't
permit this. On the other hand, there are lots of servers out there that do it, the original
author was trying to support it, and the fix is small.

On the third hand, the caravan seems to have moved on to Axis 2.

> Axis fails to deserialize faults that involve text elements
> -----------------------------------------------------------
>
>          Key: AXIS-2356
>          URL: http://issues.apache.org/jira/browse/AXIS-2356
>      Project: Apache Axis
>         Type: Bug

>   Components: Serialization/Deserialization
>  Environment: Java 1.4 on WIndows, talking to a gSoap server. (axis 1.3.1).
>     Reporter: benson margulies
>  Attachments: SOAPFaultBuilder.java.patch
>
> SOAPFaultBuilder.onEndChild fails with a DomEx error in the case where the node is a
Text node. The complaint is that the node that is being added by XMLUtils.newDocument().createElement("text")
is in the wrong document.
> <SOAP-ENV:Envelope
>   xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
>    <SOAP-ENV:Body>
>        <SOAP-ENV:Fault>
>            <faultcode>SOAP-ENV:Server</faultcode>
>            <faultstring>502 Bad Gateway</faultstring>
>            <detail>Invalid response from upstream server localhost:8000</detail>
>        </SOAP-ENV:Fault>
>    </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>
> SOAPFaultBuilder.onEndChild(String, String, DeserializationContext) line: 305 DeserializationContext.endElement(String,
String, String) line: 1090
> Parser2.maybeElement(ElementValidator) line: 1712 Parser2.content(ElementDecl, boolean,
ElementValidator) line: 1963
> Parser2.maybeElement(ElementValidator) line: 1691 Parser2.content(ElementDecl, boolean,
ElementValidator) line: 1963
> Parser2.maybeElement(ElementValidator) line: 1691 Parser2.content(ElementDecl, boolean,
ElementValidator) line: 1963
> Parser2.maybeElement(ElementValidator) line: 1691
> Parser2.parseInternal(InputSource) line: 667
> Parser2.parse(InputSource) line: 337
> XMLReaderImpl.parse(InputSource) line: 448 SAXParserImpl(SAXParser).parse(InputSource,
DefaultHandler) line: 345
> DeserializationContext.parse() line: 227

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message