tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Massimo Lusetti (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (TAP5-315) Tapestry should be able to "notice" the creation of new templates or classes, rather than just updates to existing
Date Fri, 12 Aug 2011 10:18:27 GMT

     [ https://issues.apache.org/jira/browse/TAP5-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Massimo Lusetti closed TAP5-315.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 5.2.6

Tested against a clean webapp based on 5.2.6 and it has noticed the newly created and compiled
class/page so I guess this is a leftover and maybe is due to the changes related to the pagepool
mechanism

> 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
>             Fix For: 5.2.6
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message