The previous PPR strategy wrote out complete HTML documents
into an IFRAME. The new PPR strategy is pure XMLHttp,
and therefore there is no BODY or HEAD. This is 100%
intentional.
We'd need to talk to someone who knows the DefaultAddResource
code to describe how that code should work during AJAX
requests.
-- Adam
On 9/25/07, Renzo Tomaselli <[EMAIL PROTECTED]> wrote:
>
> Adam, indeed the warning comes from Myfaces
> (org.apache.myfaces.renderkit.html.util.DefaultAddResource
> writeWithFullHeader).
> Sorry, I lost this line while pasting.
> I see it on the Eclipse console at any node click.
> From some net browsing, I noticed that this is a known topic due to
> MyFaces/Tomahawk filters: they might need to insert resources into the page
> and they cannot find its head/body.
> I'm referring to Trinidad since this issue appeared just after upgrading to
> 1.02, never seen it before. I guess previous versions emitted well-formed
> PPR responses.
>
> -- Renzo
>
>
> Adam Winer wrote:
> I don't think that's a warning coming from Trinidad code. At
> least, I can't find that string anywhere in our codebase!
> Is that really a logged Java warning?
>
> -- Adam
>
>
> On 9/24/07, Renzo Tomaselli <[EMAIL PROTECTED]> wrote:
>
>
> Hi, since I had troubles while upgrading Trinidad from 1.01 to 1.02
> (tr:tree branches did not expand anymore), and my app. was a mixup with
> Trinidad-Tomahawk-Ajax4jsf, I removed all refs to Ajax4jsf/Richfaces.
> However, tree node expansion now raises a warning all the times I click
> on a node:
>
> WARNING: Response has no <head> or <body> tag:
> <?xml version="1.0" ?>
> <?Tr-XHR-Response-Type ?>
> <content action="/AxxBrowser/startPage.faces">
> <fragment><
