You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "David Peterson (Created) (JIRA)" <ji...@apache.org> on 2011/12/03 20:08:39 UTC
[jira] [Created] (TAP5-1766) New Message Catalogs are not Loaded
"Live"
New Message Catalogs are not Loaded "Live"
------------------------------------------
Key: TAP5-1766
URL: https://issues.apache.org/jira/browse/TAP5-1766
Project: Tapestry 5
Issue Type: Bug
Components: plastic, tapestry-core
Affects Versions: 5.3
Reporter: David Peterson
Priority: Minor
In development mode, if you add a brand new message catalog for a page, the catalog does not appear to be loaded "live" but requires the server to be restarted in order for the catalog to be picked up. After a restart, changes to the messages in the catalog are updated live, however.
I've marked this "minor" rather than "trivial" because it's easy to work around, but is confusing for someone trying to use Tapestry's message catalogs for the first time. It makes it seem like the feature doesn't work or the user has done something wrong.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-1766) New Message Catalogs are not Loaded
"Live"
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-1766:
---------------------------------------
Component/s: (was: plastic)
> New Message Catalogs are not Loaded "Live"
> ------------------------------------------
>
> Key: TAP5-1766
> URL: https://issues.apache.org/jira/browse/TAP5-1766
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.3
> Reporter: David Peterson
> Priority: Minor
>
> In development mode, if you add a brand new message catalog for a page, the catalog does not appear to be loaded "live" but requires the server to be restarted in order for the catalog to be picked up. After a restart, changes to the messages in the catalog are updated live, however.
> I've marked this "minor" rather than "trivial" because it's easy to work around, but is confusing for someone trying to use Tapestry's message catalogs for the first time. It makes it seem like the feature doesn't work or the user has done something wrong.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TAP5-1766) New Message Catalogs are not Loaded
"Live"
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-1766:
---------------------------------------
Component/s: (was: plastic)
> New Message Catalogs are not Loaded "Live"
> ------------------------------------------
>
> Key: TAP5-1766
> URL: https://issues.apache.org/jira/browse/TAP5-1766
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.3
> Reporter: David Peterson
> Priority: Minor
>
> In development mode, if you add a brand new message catalog for a page, the catalog does not appear to be loaded "live" but requires the server to be restarted in order for the catalog to be picked up. After a restart, changes to the messages in the catalog are updated live, however.
> I've marked this "minor" rather than "trivial" because it's easy to work around, but is confusing for someone trying to use Tapestry's message catalogs for the first time. It makes it seem like the feature doesn't work or the user has done something wrong.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira