Hi,
The following is excerpted from a message I sent to Integration-Support at
TeleCheck, the ACH-intermediary. I'm trying to invoke their new Web Service
for online-check processing. I'm using Axis 1.1, since they've said they've
had "good experiences" with it, though they do not claim their Service is
certified to be called by Axis. It's certified to be called by GLUE
(enterprise edition) and .NET. They do claim their Service is "SOAP 1.2
compliant".
Note in the raw response, below, the "href"-attribute within the
"reasonCode"-element. Once I'd fixed the errors that had caused that
response to be returned (the dashes in the two phone-numbers), there were no
more such "href"s used in the response, and Axis had no problem handling
that new (successful) response.
So, my question is this:
Is there a particular version of Xerces, or what not, that one needs to use
with Apache Axis, to get it to properly parse XML documents that include
ID/IDREFs ?
Also, this next item, from the error-response below, seems peculiar to me:
<xsd:string xsi:type="xsd:string" id="ID_6">910</xsd:string>
It's the very last element in the body of the response cited below.
Does such mark-up indicate that that element's name is "string"? It's
peculiar that the name of the element seems to be appropriate only for the
value of a type-attribute.
Is that a bug in TeleCheck's Service? They claim to not be able to
replicate this issue -- though I suspect that's because they're testing with
GLUE, not with Axis.
Any advice would be much appreciated.
Larry LeFever
org.xml.sax.SAXException: Invalid element in
webservices.achex.com.ResponseDetail - ResponseDetail
at org.apache.axis.AxisFault.makeFault(AxisFault.java:129)
at org.apache.axis.client.Call.invoke(Call.java:2275)
at org.apache.axis.client.Call.invoke(Call.java:2171)
at org.apache.axis.client.Call.invoke(Call.java:1691)
at
com.achex.CheckAuthorizationServicePortSoapBindingStub.createCheckAut
horization(CheckAuthorizationServicePortSoapBindingStub.java:222)
at test.Test.main(Test.java:47)
Caused by: org.xml.sax.SAXException: Invalid element in
webservices.achex.com.ResponseDetail - ResponseDetail
at
org.apache.axis.encoding.ser.BeanDeserializer.onStartChild(BeanDeserializer.
java:260)
at
org.apache.axis.encoding.DeserializationContextImpl.startElement(Dese
rializationContextImpl.java:963)
at
org.apache.axis.message.SAX2EventRecorder.replay(SAX2EventRecorder.java:198)
at
org.apache.axis.message.MessageElement.publishToHandler(MessageElement.java:
722)
at
org.apache.axis.message.RPCElement.deserialize(RPCElement.java:233)
at org.apache.axis.message.RPCElement.getParams(RPCElement.java:347)
at org.apache.axis.client.Call.invoke(Call.java:2272)
HTTP/1.1 200 OK
Date: Tue, 22 Jul 2003 01:12:49 GMT
Server: Apache
Content-Length: 1691
Connection: close
Content-Type: text/xml
<env:Envelope
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/";
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
<env:Header></env:Header>
<env:Body>
<m:createCheckAuthorizationResponse
xmlns:m="http://achex.com";
env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";>
<result xsi:type="ns100:AuthorizationResponse"
xmlns:ns100="java:com.achex.webservices">
<statusDisplayDescription xsi:nil="true"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";></statusDisplayDescrip
tion>
<details xmlns:ns101="java:com.achex.webservices"
soapenc:arrayType="ns101:ResponseDetail[2]">
<ns101:ResponseDetail xsi:type="ns101:ResponseDetail">
<key
xsi:type="xsd:string">DDAAccount.Address.phone1</key>
<description xsi:nil="true"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";></description>
<value xsi:type="xsd:string">123-123-1234</value>
<reasonCode href="#ID_6"></reasonCode>
</ns101:ResponseDetail>
<ns101:ResponseDetail xsi:type="ns101:ResponseDetail">
<key
xsi:type="xsd:string">AuthorizationDetails.Address.phone1</key>
<description xsi:nil="true"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";></description>
<value xsi:type="xsd:string">123-123-1234</value>
<reasonCode href="#ID_6"></reasonCode>
</ns101:ResponseDetail>
</details>
<statusCode xsi:type="xsd:string">100</statusCode>
<clearerID xsi:type="xsd:string">{omitted by me}</clearerID>
<merchantID xsi:type="xsd:string">{omitted by me}</merchantID>
<trackingID xsi:type="xsd:string">1058837212440</trackingID>
</result>
</m:createCheckAuthorizationResponse>
<xsd:string xsi:type="xsd:string" id="ID_6">910</xsd:string>
</env:Body>
</env:Envelope>
