× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Yeah, maybe. I don't know yet if it's a bug or me doing something wrong.

I was hoping to get some experienced (with this issue) feedback first.

Thanks for the suggestion!

Shannon O'Donnell

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
Behalf Of Michael Ryan
Sent: Friday, February 29, 2008 1:21 PM
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Web Service from WDSC

Shouldn't you open a PMR about this?

On Fri, Feb 29, 2008 at 1:58 PM, Shannon ODonnell
<sodonnell@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
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



--
This is the Websphere Development Studio Client for iSeries (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.