> Hmm. Whoever coded the Axis code in the first place thought that it was > valid and tried to deal with it, That would be me I think.
Simon, the way I read [1] is that characters information items mean text. [1] http://www.w3.org/TR/2003/REC-soap12-part1-20030624/#faultdetailelement Did the spec-speak turn my brain to mush? -- Tom Jordahl Adobe ColdFusion Team > -----Original Message----- > From: Benson Margulies [mailto:[EMAIL PROTECTED] > Sent: Thursday, December 29, 2005 8:54 PM > To: axis-dev@ws.apache.org > Subject: RE: [jira] Updated: (AXIS-2356) Axis fails to deserialize faults > that involve text elements > > Hmm. Whoever coded the Axis code in the first place thought that it was > valid and tried to deal with it, and I've now encountered two completely > independent products that produce faults like this (Mindreef SoapScope > and gSoap). Maybe it was permitted in an earlier incarnation? > > -----Original Message----- > From: Simon Fell [mailto:[EMAIL PROTECTED] > Sent: Thursday, December 29, 2005 8:50 PM > To: axis-dev@ws.apache.org > Subject: RE: [jira] Updated: (AXIS-2356) Axis fails to deserialize > faults that involve text elements > > <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> > > Probably un-related, but that actually isn't a valid fault structure, > the detail can only contain namesapce qualified child elements, not text > directly. > > Cheers > Simon > > -----Original Message----- > From: benson margulies (JIRA) [mailto:[EMAIL PROTECTED] > Sent: Thursday, December 29, 2005 5:26 PM > To: axis-dev@ws.apache.org > Subject: [jira] Updated: (AXIS-2356) Axis fails to deserialize faults > that involve text elements > > [ http://issues.apache.org/jira/browse/AXIS-2356?page=all ] > > benson margulies updated AXIS-2356: > ----------------------------------- > > Attachment: SOAPFaultBuilder.java.patch > > Here is a patch that fixes this probem. > > > 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
