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 01:38:43 UTC
[jira] Created: (TAPESTRY-1918) Tapestrys' reload logic should be
able to see additions, not just deletions and changes
Tapestrys' 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
[jira] Updated: (TAPESTRY-1918) Tapestry's reload logic should be
able to see additions, not just deletions and changes
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ 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
[jira] Updated: (TAPESTRY-1918) Tapestry's' reload logic should be
able to see additions, not just deletions and changes
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ 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: Tapestrys' 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
[jira] Commented: (TAPESTRY-1918) Tapestry's' reload logic should
be able to see additions, not just deletions and changes
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ 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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
[jira] Closed: (TAPESTRY-1918) Tapestry's reload logic should be
able to see additions, not just deletions and changes
Posted by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org>.
[ https://issues.apache.org/jira/browse/TAPESTRY-1918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAPESTRY-1918.
------------------------------------------
Resolution: Fixed
Fix Version/s: 5.0.7
Again, this is a quick but not perfect fix but I'm satisfied that it will work for most people. The worst will be for message catalog files, as it is more common to go from 0 to 1 of those files (which may not be picked up) than to go from n to m of them (which is more generally what the fix detects).
> 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
> Fix For: 5.0.7
>
>
> 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