Well, our app is using Facelets... so now that I've got a version of the
JARs that works with that, I can get back to validating the app that I've got
against the latest PPR stuff.
But you're right, this is sounding more like a BEA forum topic now.
That's my next stop.
Thanks for the guidance...
Dave________________________________ From: Adam Winer [mailto:[EMAIL PROTECTED] Sent: Mon 6/25/2007 7:26 PM To: MyFaces Development Subject: Re: [Trinidad] AJAX PPR - Invalid PPR Response error On 6/25/07, David Brunette <[EMAIL PROTECTED]> wrote: Sorry... it seems as though it was a bit premature to say that it was not working with Facelets. After trying a bunch of different things, I forgot one very important thing to try... get the latest code! I was about to ask! :) Yeah, the XMLHttp-PPR was broken with Facelets. The ResponseWriter construction in Facelets is really tortuous, took awhile to come up with a solid solution. After getting a newly built set of JARs this afternoon and trying it again with Facelets, the PPR works just fine in both Tomcat and Weblogic. Woops. But we're still stuck on having the wrong response contentType with JSP & Weblogic. Well, that's a better defined problem at least! One possibility - instead of using the directive, maybe use a JSP scriptlet along the lines of: FacesContext fc = FacesContext.getCurrentInstance(); RequestContext rc = RequestContext.getCurrentInstance(); if (!rc.isPartialRequest(fc)) pageContext.getResponse().setContentType("text/html; charset=iso-8859-1") ... though, of course, you'd want to wrap this workaround up in a tag. I'm mostly just guessing here, though. You could bring the general issue to a BEA forum: why do WebLogic 8.1 JSPs set the content type out directly, instead of going through the ServletResponse API - blowing off any wrappers added by filters? -- Adam 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.
<<winmail.dat>>
