Wicket
  1. Wicket
  2. WICKET-1361

Localizer doesn't honor style when caching property lookups

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.3.1
    • Fix Version/s: 1.3.2
    • Component/s: wicket
    • Labels:
      None

      Description

      In Wicket 1.2.6, we created some properties files like:

      Foo.properties
      Foo_style1.properties
      Foo_style2.properties

      and used StringResourceModel to look up property values. This worked correctly as in 1.2.6, Localizer didn't cache the property lookups and respected the style. However, in 1.3, Localizer now caches the lookups but doesn't respect the style when creating the cache key (though it does append the locale to the end of the cache key).

      The side-effects of this are that whatever style is in use when a property is first looked up, that property value will be returned for all subsequent lookups regardless of style.

        Activity

          People

          • Assignee:
            Igor Vaynberg
            Reporter:
            Meetesh Karia
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development