Ah -- I see. This DataSet is coming from a .NET service (probably
generated by ADO.NET), and then stuffed into the SOAP message as a
string. Unfortunately, because the string starts with the ?xml
declaration, you won't be able to get Axis to process it for you. You
are going to have to extract the
Thank you so very much.
I suspected something like this, especially after investigating a
well-formed SOAP service (from Melissa Data) and working through
the client code generated by WSDL2Java for it.
I'm pretty new to all of this so I have to keep looking up
everything. And it seems that
Hi Anne,
Could you provide an example how to
extract that?
Thanks,
A
--- Anne Thomas Manes [EMAIL PROTECTED] wrote:
Ah -- I see. This DataSet is coming from a .NET
service (probably
generated by ADO.NET), and then stuffed into the
SOAP message as a
string. Unfortunately, because the
Don't waste the effort!
Instead, fix it at the source. . .
-Original Message-
From: Airline Pedestal [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 01, 2005 6:29 PM
To: axis-user@ws.apache.org; Anne Thomas Manes
Subject: Re: Handmade WSDL?
Hi Anne,
Could you provide an example how
To: axis-user@ws.apache.org
Subject: Handmade WSDL?
Hope this is not stupid, but
Problem: the wsdl for our (supposedly) enterprise credit card
processing service shows well defined request parameters, but the
SOAP responses are all designated as string, as shown below.
I am thinking that the best
Message-
From: Elaine Nance [mailto:[EMAIL PROTECTED]
Sent: Monday, February 28, 2005 3:45 PM
To: axis-user@ws.apache.org
Subject: Handmade WSDL?
Hope this is not stupid, but
Problem: the wsdl for our (supposedly) enterprise credit card
processing service shows well defined request parameters
