I'd start by sniffing the connection to see what (if anything) the browser
is receiving from the HTTP server.

If you're receiving valid data, you know that the problem is on the browserside (likely the JavaScript code) and if you're not, you know that the problem is on the server (CGI) side.

Personally, I prefer to test the server side independently, make sure it works exactly as you expect, then write the AJAX code to use it. It just makes it easier to track down problems.

---
Scott Klement  http://www.scottklement.com

On Tue, 20 Jun 2006, Bruce Guetzkow wrote:

All:

I'm giving Ajax a try and after a bit of effort, everything is working,
except that I'm not getting either the responseText or responseXML back from
the server.  My CGI program is executing (I can walk through it using debug)
and I can see the XML document being created and written to the browser via
QtmhWrStout.  My call-back function is being called, but both the
responseText and responseXML are null.

The CGI program is created using RSP (RPG Server Pages) and it calls CGIDEV2
procedures to build the XML file (since CGIDEV2 has such nice features for
this purpose).  I've even tried simply using a test RSP program to create
the XML.  If I simply execute the test program outside of the Ajax Request,
the XML document displays in the browser.  If I then call it via the Ajax
Request, the test program executes, but neither responseText nor responseXML
is returned.

I know an XML document is being created because if we use WrtHtmlToStmf, we
can get a file on the IFS and it looks just the way we want.  If we change
to WrtSection('*fini'), nothing is returned.

I'm wondering:
- is there an Apache directive that needs to be set/changed?
- is there a possibility of authority issues?

Has anyone else run into this?  Any thoughts?

Thanks in advance,
--Bruce Guetzkow



--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.