tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (TAP5-1957) setupRender methods are not always invoked
Date Tue, 19 Jun 2012 18:31:42 GMT

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

Howard M. Lewis Ship updated TAP5-1957:

     Labels:   (was: setupRender)
    Summary: setupRender methods are not always invoked  (was: The setupRender is not always
trigger after upgrade to 5.3.2)

This will likely be closed as "not reproducable" unless you can provide a test case, or at
least, sample code on which the problem has been observed. Although the code for class transformation
was rewritten in 5.3, that code is backed up by hundreds of tests, and I personally have done
upgrades from Tapestry 5.2 to 5.3 on some massive sites without encountering the problem you
describe.  That doesn't rule it out, but given that I can't think of scenario that would allow
the behavior you are seeing, my first expectation is that something outside of Tapestry is
causing the problem, and that raises the bar for proving there's a problem, and not some coding
error in your own code.
> setupRender methods are not always invoked
> ------------------------------------------
>                 Key: TAP5-1957
>                 URL: https://issues.apache.org/jira/browse/TAP5-1957
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.3.2
>            Reporter: virgil hong
> When  after upgrade to 5.3.2, my project some pages not alwarys trigger the SetupRender
method, but after restart the Jetty, then it's OK, it's not stable, or sometime unlucky restart
the server repeat, it's also exists the problem, I have to change the setupRender method to
> the strange thing is some pages ok, some pages bad....

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message