David,
responseXML is null means the XML document is invalid.
Check getResponseText(). There'll likely be something in
the response that is getting inserted into the stream, and
then the really fun thing is going to be finding out why
Weblogic does it. Look especially at the beginning of
the document.
isPprResponse() just means that "it has the right headers
from the server", that is, "It's supposed to be a PPR response".
-- Adam
On 6/22/07, David Brunette <[EMAIL PROTECTED]> wrote:
Hello…
I took a 1.0.2 build from the trunk a couple of days ago to start
testing our app against the latest and greatest PPR functionality (using
AJAX). After deploying the demo WAR to Tomcat, everything on the PPR Demo
page worked great. But when I took the same demo WAR and deployed it to
Weblogic 9.2, I started getting "Invalid PPR Response" errors whenever I
tried anything on that page.
Digging into the JS with Firebug, I can see that the
_requestStatusChanged() function gets a statusCode of 200, but is failing
because requestEvent.getResponseXML() is null. (Side note:
requestEvent.isPprResponse() is returning 'true' even if
_isResponseValidXML() is 'false'. Not sure if that was intended…).
I've gone about as far as I can go debugging this on my own. I have no
idea what would cause the responseXML to be null… or if I'm even on the
right path. Any help would be much appreciated!
Dave
The information transmitted herewith is sensitive information of Chordiant
Software or its customers and is intended only for use to the individual or
entity to which it is addressed. If the reader of this message is not the
intended recipient, you are hereby notified that any review, retransmission,
dissemination, distribution, copying or other use of, or taking of any
action in reliance upon, this information is strictly prohibited. If you
have received this communication in error, please contact the sender and
delete the material from your computer.
