[
https://issues.apache.org/jira/browse/WICKET-959?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Frank Bille Jensen updated WICKET-959:
--------------------------------------
Fix Version/s: (was: 1.3.0-rc1)
1.3.0-rc2
> I18n and resource bundles prioritization
> -----------------------------------------
>
> Key: WICKET-959
> URL: https://issues.apache.org/jira/browse/WICKET-959
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.0-beta3
> Reporter: Alexandru Objelean
> Assignee: Juergen Donnerstag
> Priority: Minor
> Fix For: 1.3.0-rc2
>
>
> The wicket wiki page
> [http://cwiki.apache.org/confluence/display/WICKET/I18n+and+resource+bundles]
> states that "you can use MyApplication.properties for site wide messages and
> override these in any of the other properties files.".
> But there is a case where this is not true:
> I have a BaseApplicationPage.properties file with the following resource
> message:
> <code>
> nullValid=All
> </code>
> And another, component specific file: NewBookingPeriod.properties with the
> same resource message:
> <code>
> nullValid=Empty Prices
> </code>
> I would expect that the latest resource message (Empty Prices) would override
> the generic nullValid resource message. But it doesn't work this way.
> My workaround is to change (prepend to nullValid the component id) the
> resource message from NewBookingPeriod.properties to:
> <code>
> bookingPeriods.nullValid=Empty Prices
> </code>
> This way it works. Shouldn't it work also when the
> NewBookingPeriod.properties defines nullValid the same way as
> BaseApplicationPage.properties does?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
