You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2011/08/11 20:38:28 UTC
[jira] [Updated] (TAP5-1336) Components / pages don't reload
correctly under tomcat
[ https://issues.apache.org/jira/browse/TAP5-1336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-1336:
---------------------------------------
That patch is no longer valid due to the switch over to Plastic. Could you see if this problem still manifests under Tomcat?
> Components / pages don't reload correctly under tomcat
> ------------------------------------------------------
>
> Key: TAP5-1336
> URL: https://issues.apache.org/jira/browse/TAP5-1336
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-ioc
> Affects Versions: 5.2.2
> Reporter: Denis Delangle
> Attachments: patch_tomcat_reload.txt
>
>
> I am using eclipse, with maven plugin m2eclipse.
> When I launch tomcat with tomcat-maven-plugin (V 1.1), pages don't reload when I modify them. I have to restart my web server to see the changes.
> What I noticed when I modify a page :
> * Tapestry is notified of a modification of the class file
> * It flushes the old page instance and tries to reload the class file
> * It in fact reloads the old version of the file -> it seems that Tomcat classloader gives the old class file inputStream in getResourceAsStream methods
> I made a modification in ClassFactoryClassPool to get a clean new InputStream from the classFile, that fixed my issue, now pages are well reloaded when I modify them under Tomcat.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira