[
https://issues.apache.org/jira/browse/TAPESTRY-1918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543444
]
Howard M. Lewis Ship commented on TAPESTRY-1918:
------------------------------------------------
A partial fix for this is to add the directory containing each file checked via
URLChangeTracker. This isn't perfect: a file needs to be loaded from the
directory before the directory is "checked" for changes, but this covers the
majority of cases pretty well, I think. A perfect solution will require some
significant juggling of the framework.
> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
