OK... so everything in the responseText looks fine... but the
contentType in the header shows "text/html" instead of "text/xml". I
can see that XmlHttpServletResponse specifically sets "text/xml", but
I'm guessing that something further along on the filter chain or
something is changing it to "text/html".
Am I correct in my understanding that we need "text/xml" here...
and if the contentType is incorrect, then we would get a null
responseXML, even if the responseText was valid XML?
Dave
-----Original Message-----
From: Adam Winer [mailto:[EMAIL PROTECTED]
Sent: Friday, June 22, 2007 1:46 PM
To: MyFaces Development
Subject: Re: [Trinidad] AJAX PPR - Invalid PPR Response error
There's gotta be some other difference, as what you've
identified wouldn't result in an invalid XML document.
-- Adam
On 6/22/07, David Brunette <[EMAIL PROTECTED]> wrote:
>
> Thanks Adam.
>
> I had a look at that method and the value of xmlhttp.responseText
> between Tomcat & Weblogic looked pretty close. The only differences
> were in the content node of the response text: 1) different tokens for
> the STATE (which is, of course, expected), and 2) the Tomcat response
> text had an additional fragment that had " <span id=\"rbTarget\"
> class=\"x0\">selectBoolean set, item 1</span>". The beginning of each
> response text was exactly the same:
>
> <?xml version=\"1.0\" ?>
> <?Tr-XHR-Response-Type ?>
>
> So I'm guessing that the missing bit of the Weblogic responseText
> is the thing to track down... though I don't know whether it is a
cause
> or result the error. I'll keep digging, but any other thoughts are
> welcomed...
>
> Dave
>
> -----Original Message-----
> From: Adam Winer [mailto:[EMAIL PROTECTED]
> Sent: Friday, June 22, 2007 11:28 AM
> To: MyFaces Development
> Subject: Re: [Trinidad] AJAX PPR - Invalid PPR Response error
>
> 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.
> 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.
>
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.
