To the IBM WDSC team..
I've noticed something peculiar when creating a webservice using the WDSC
wizards.
Within the wizard, I can select which Method(s) to include with my web
service, either an XML-output version or a non-XML output version. So I
select both or just the XML-output.
Anyway.now when I test the web service using anything other than the WAS
Test Environment.for example, if I load the service on to my iSeries and use
SoapUI to test it with.
The XML-Output webservice method ALWAYS sends all of the response data back
in a <! [CDATA [ error block.
This happens on any web service I create (they all use an iSeries Java Bean
to pull the data through) I create and any data set I bring back. Also,
tried this on two different iSeries, one at V5R3 and the other at V5R4 and
get the same results.
The error makes me think I'm sending an invalid character back somewhere,
but that's really strange too because I can do this over many different
backend programs that the java bean points too and it always gives me the
same results. And studying the result set, I see no invalid characters at
all.
Now I'm wondering if this is an undocumented "feature" of WAS 6.0? I can
upgrade to WAS 6.1, and probably will eventually, but I'd like to figure out
why this always happens first.
Here's an example:
<soapenv:Envelope xmlns:soapenv="
http://schemas.xmlsoap.org/soap/envelope/"
xmlns:soapenc="
http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="
http://www.w3.org/2001/XMLSchema"
xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header/>
<soapenv:Body>
<p653:wsgetitem_XMLResponse xmlns:p653="
http://wsGetItem">
<wsgetitem_XMLReturn>
<![CDATA[<?xml version="1.0" encoding="UTF-8"?>
<WSGETITEM>
<INITEMNO>2008TR000039</INITEMNO>
<INLOT>000072543</INLOT>
Etc.
Shannon O'Donnell
As an Amazon Associate we earn from qualifying purchases.