You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org> on 2007/11/19 02:27:43 UTC
[jira] Updated: (TAPESTRY-1918) Tapestry's reload logic should be
able to see additions, not just deletions and changes
[ https://issues.apache.org/jira/browse/TAPESTRY-1918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAPESTRY-1918:
-------------------------------------------
Summary: Tapestry's reload logic should be able to see additions, not just deletions and changes (was: Tapestry's' reload logic should be able to see additions, not just deletions and changes)
> Tapestry's reload logic should be able to see additions, not just deletions and changes
> ---------------------------------------------------------------------------------------
>
> Key: TAPESTRY-1918
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1918
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0.6
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
>
> Tapestry has change monitoring logic for templates, classes and properties files. However, that change logic is only aware of changes to loaded files, and of deletion of loaded files. It would be nice if Tapestry was aware of the folders containing tracked files, and was capable of identifying when files were added as well. This shows up in development, when creating a new page class in a running application still gives a "page not found" exception, because Tapestry is not aware of the new class.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org