[
https://issues.apache.org/jira/browse/TRINIDAD-2058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13005256#comment-13005256
]
Pavitra Subramaniam commented on TRINIDAD-2058:
-----------------------------------------------
Can you upload a simple testcase that reproduces the bug, because I am unable
to reproduce it? I am using a simple testcase where multiple components on the
page get partially refreshed when a command button is clicked. I seeing
multiple <update> elements in the partial response but they all end up updating
the UI correctly.
For e.g.,
<tr:panelGroupLayout layout="horizontal">
<tr:inputText id="foo1" value="#{bean.value1}" columns="6"/>
<tr:outputText id="out1" value="#{bean.value1}"/>
<tr:commandButton text="Duplicate" id="bar1" partialSubmit="true"
actionListener="#{bean.duplicate}">
<f:ajax event="action" execute="foo1" render="foo1 out1"/>
</tr:commandButton>
</tr:panelGroupLayout>
Thanks
Pavitra
> PPR request doesn't update components
> -------------------------------------
>
> Key: TRINIDAD-2058
> URL: https://issues.apache.org/jira/browse/TRINIDAD-2058
> Project: MyFaces Trinidad
> Issue Type: Bug
> Components: Components
> Affects Versions: 2.0.0-beta-2
> Environment: WinXP, IE 8, Firefox 3.6, Tomcat 5.5
> Reporter: Volker Malzahn
> Priority: Blocker
>
> A PPR request which contains one or more "update" elements doesn't updates
> these components in the browser.
> Reason: same as in issue TRINIDAD-1837, but with 2.0.0-beta-2 this doesn't
> happen for some rare cases but for all PPR requests (in my environment)
> because the new format of the PPR response always has an HTML comment as
> first child node of an "update" element.
> Solution is easy: just merge the changes of TRINIDAD-1837 to the 2.0.0 branch.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
