Mailing-List: contact commits-help@tapestry.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@tapestry.apache.org
Date: Fri, 1 Apr 2011 00:06:05 +0000 (UTC)
From: "Howard M. Lewis Ship (JIRA)" <jira@apache.org>
To: commits@tapestry.apache.org
Message-ID: 
 <830517539.26295.1301616365734.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Closed] (TAP5-738) Component's body is sometimes not
 rendered
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/TAP5-738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship closed TAP5-738.
-------------------------------------

    Resolution: Cannot Reproduce
      Assignee: Howard M. Lewis Ship

I believe this was fixed separately; there was a scenario where a  page was created to handle an Ajax request before it was rendered the first time and it was partially uninitialized.  In any case, between that fix and the removal of page pooling, I suspect your difficult to reproduce but no longer exists.

> Component's body is sometimes not rendered
> ------------------------------------------
>
>                 Key: TAP5-738
>                 URL: https://issues.apache.org/jira/browse/TAP5-738
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.1.0.5
>            Reporter: Michal Buczko
>            Assignee: Howard M. Lewis Ship
>
> component's body is not rendered after few frequent AJAX updates. this is not reproducible in a simple way. sometimes happens after first update sometimes after 50th. refreshing the page always helps but after next few updates the same situation occurs.
> this has been confirmed by few other people. please take a look at: http://www.nabble.com/T5.1.0.5-Component%27s-body-not-rendered-td23837971s302.html for more information.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira