You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2014/05/13 15:23:25 UTC

[jira] [Closed] (TAP5-854) add a package-level localization feature

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

Jochen Kemnade closed TAP5-854.
-------------------------------

    Resolution: Not a Problem

Another year has passed since the last comment. Therefore, we assume this issue has either been resolved in the meantime or it is no longer relevant to you.
If recent versions of Tapestry (i.e. 5.4 betas and 5.3.7) are still affected, please reopen the issue and adjust the "Affected Version/s" property.

> add a package-level localization feature
> ----------------------------------------
>
>                 Key: TAP5-854
>                 URL: https://issues.apache.org/jira/browse/TAP5-854
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-core
>    Affects Versions: 5.1.0.5
>            Reporter: cleverpig
>              Labels: bulk-close-candidate
>
> just like struts2 had done in Localization:http://struts.apache.org/2.1.6/docs/localization.html
> I mean when i develope some page class in the same package,i always meet some same resource message defines for CRUD pages of one POJO..
> so i think it's effectual under this dev habit:create a package level property file for this package(pages)..



--
This message was sent by Atlassian JIRA
(v6.2#6252)