Issue Details (XML | Word | Printable)

Key: TAPESTRY-881
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Jesse Kuhnert
Reporter: Matt Raible
Votes: 1
Watchers: 3
Operations

If you were logged in you would be able to see more operations.
Tapestry

Allow global i18n bundle location to be customized

Created: 10/Mar/06 10:58 PM   Updated: 05/Mar/07 02:33 AM
Return to search
Component/s: Framework
Affects Version/s: 4.1.1
Fix Version/s: 4.1.2

Time Tracking:
Not Specified

Resolution Date: 05/Mar/07 02:33 AM


 Description  « Hide
The current mechanism for specifying a global i18n resource bundle is not very flexible.

http://jakarta.apache.org/tapestry/UsersGuide/localization.html#localization.namespace

It requires you to name your i18n bundles the same as your .application file. Furthermore, it requires that your bundles be places in the WEB-INF directory. Most other web frameworks (and Java applications in general) require you to have the ResourceBundle somewhere in your classpath (generally in the root - WEB-INF/classes).

1. I think the root of the classpath should be the default location - even if you're using the ".application name matches i18n name" mechanism.
2. It should be possible to customize the name of the file. Possibly something like the following in your .application file:

<property name="org.apache.tapestry.global-properties" value="ApplicationResources"/> -> points to WEB-INF/classes/ApplicationResources.properties (and others with _locale.properties
<property name="org.apache.tapestry.global-properties" value="com.myapplication.web.messages"/> - points to /WEB-INF/classes/com/myapplication/web/messages.properties

 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
No work has yet been logged on this issue.