portlet decorator actions displaying alt text from the wrong locale
-------------------------------------------------------------------

                 Key: JS2-1249
                 URL: https://issues.apache.org/jira/browse/JS2-1249
             Project: Jetspeed 2
          Issue Type: Bug
          Components: Decorations/Themes
    Affects Versions: 2.2.0
         Environment: Windows XP SP3
Sun Java 1.5
Jetspeed 2.2.0

Observed in Firefox 3.6.x, Firefox 4 and Chrome 10.x
            Reporter: Daniel DeGroff
            Priority: Minor


When switching the locale in the browser configuration between Japanese and 
English, the alt text for the portlet decorator actions are not consistently in 
the correct locale.

While using the ja locale, the alt text will remain in English for 'Maximize', 
'Minimize' etc, and vice versa, while using en locale, the Japanese characters 
may display for the alt text.

While stepping through AbstractDecoratorActionsFactory.createAction, one line 
169

  169  HashMap resourcesMap = (HashMap)actionResourcesMap.get();

If this returns a reference, the values in the resourceMap are not cleared and 
initialized with the values from the localized bundle.
The resourceMap contains the localized bundle, it seems that even if a valid 
reference is returned, the locale of the bundle in the resourceMap should be 
compared with locale in the jetspeedRequestContext to see if it needs to be 
updated.

Because the resourceMap is not cleared when the locale changes, the 
localizedName string used to create the new DecoratorAction is in the wrong 
locale.

I initially posted this on the jetspeed forum, and then opened this issue.
http://mail-archives.apache.org/mod_mbox/portals-jetspeed-user/201104.mbox/%[email protected]%3E

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to