myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Max Starets (JIRA)" <>
Subject [jira] Resolved: (TRINIDAD-1671) Trinidad 2: ppr error when interacting with programatically added component
Date Tue, 12 Jan 2010 21:02:54 GMT


Max Starets resolved TRINIDAD-1671.

       Resolution: Fixed
    Fix Version/s: 2.0.1-plugins

The offending code has been in PPRResponseWriter forever:
super.write("<?Tr-XHR-Response-Type ?>\n"); should have been:
_xml.write("<?Tr-XHR-Response-Type ?>\n");

This was putting PPRResponseWriter into the 'forceInsideTarget' mode, so all output was sent
to the client. The problem used to be masked by Trinidad's ResponseWriterDecorator overriding
all write() methods. It got exposed once we started relying on JSF's ResponseWriterWrapper

Note: we need to reevaluate whether the  'forceInsideTarget' mode is even necessary with the
current version of Facelets.

> Trinidad 2: ppr error when interacting with programatically added component
> ---------------------------------------------------------------------------
>                 Key: TRINIDAD-1671
>                 URL:
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>            Reporter: Gabrielle Crawford
>            Assignee: Max Starets
>             Fix For: 2.0.1-plugins
> wait for the fix for, or move "_parent
= parent;" to the top of UIXComponentBase.setParent, which is a workaround for 1670.
> Now run stateSaving/partialAddComponent.jspx. You don't need to set up partial state
saving or change web.xml, just try adding the component, and then opening the showDetail,
when it asks you to reload the page hit cancel and look at the js error.
> The js error starts with: ["Invalid PPR response. The response-headers were:

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message