You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Thiago H. de Paula Figueiredo (JIRA)" <ji...@apache.org> on 2008/10/28 01:01:44 UTC
[jira] Created: (TAP5-315) Make Tapetry pick page and template
classes created after the application was started
Make Tapetry pick page and template classes created after the application was started
-------------------------------------------------------------------------------------
Key: TAP5-315
URL: https://issues.apache.org/jira/browse/TAP5-315
Project: Tapestry 5
Issue Type: Improvement
Components: tapestry-core
Affects Versions: 5.0.15
Reporter: Thiago H. de Paula Figueiredo
Tapestry does not pick new pages, components, mixins and templates after it is started. If this fact is reversed, we could develop an entire web interface without reloading the application.
In addition, there is one other reason to implement this new feature: applications with static content. Every time I add a new page to my website, I have to restart the application, as it's written on T5. This is not an issue to my site, but can be to high traffic ones.
--
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: (TAP5-315) Make Tapetry pick page and template
classes created after the application was started
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12643107#action_12643107 ]
Howard M. Lewis Ship commented on TAP5-315:
-------------------------------------------
Workaround: touch a file that has been loading by Tapestry (such as Index.class or Index.tml) and Tapestry will pick up all changes. It's caching is very simple.
> Make Tapetry pick page and template classes created after the application was started
> -------------------------------------------------------------------------------------
>
> Key: TAP5-315
> URL: https://issues.apache.org/jira/browse/TAP5-315
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0.15
> Reporter: Thiago H. de Paula Figueiredo
>
> Tapestry does not pick new pages, components, mixins and templates after it is started. If this fact is reversed, we could develop an entire web interface without reloading the application.
> In addition, there is one other reason to implement this new feature: applications with static content. Every time I add a new page to my website, I have to restart the application, as it's written on T5. This is not an issue to my site, but can be to high traffic ones.
--
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: (TAP5-315) Tapestry should be able to "notice" the
creation of new templates or classes, rather than just updates to existing
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-315:
--------------------------------------
Summary: Tapestry should be able to "notice" the creation of new templates or classes, rather than just updates to existing (was: Make Tapetry pick page and template classes created after the application was started)
As a note; when Tapestry monitors a file, it also monitors the folder containing the file, so often loading a file from a directory then adding a new file to that directory will properly force a cache refresh (the first step in picking up new and changed files).
> Tapestry should be able to "notice" the creation of new templates or classes, rather than just updates to existing
> ------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-315
> URL: https://issues.apache.org/jira/browse/TAP5-315
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0.15
> Reporter: Thiago H. de Paula Figueiredo
> Priority: Minor
>
> Tapestry does not pick new pages, components, mixins and templates after it is started. If this fact is reversed, we could develop an entire web interface without reloading the application.
> In addition, there is one other reason to implement this new feature: applications with static content. Every time I add a new page to my website, I have to restart the application, as it's written on T5. This is not an issue to my site, but can be to high traffic ones.
--
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: (TAP5-315) Make Tapetry pick page and template
classes created after the application was started
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-315:
--------------------------------------
Priority: Minor (was: Major)
> Make Tapetry pick page and template classes created after the application was started
> -------------------------------------------------------------------------------------
>
> Key: TAP5-315
> URL: https://issues.apache.org/jira/browse/TAP5-315
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0.15
> Reporter: Thiago H. de Paula Figueiredo
> Priority: Minor
>
> Tapestry does not pick new pages, components, mixins and templates after it is started. If this fact is reversed, we could develop an entire web interface without reloading the application.
> In addition, there is one other reason to implement this new feature: applications with static content. Every time I add a new page to my website, I have to restart the application, as it's written on T5. This is not an issue to my site, but can be to high traffic ones.
--
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