[WW-4295] provide better documentation and / or functionality for localization of struts2 tag elements (select, radio, etc.)

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.3.16
• Fix Version/s: 2.3.20
• Assignee: Lukasz Lenart
• Reporter: adam brin
• Created: 03/Mar/14 21:09
• Updated: 13/Nov/16 10:44
• Resolved: 30/Jul/14 07:16

Description

The <@s.text> macro is very useful for localization of text values. The <@s.textfield tag also takes a "key" > but, the select, radio, and checkbox options don't have good options for localization. One option raised on the list and identified in a few places is to construct a separate map of variables that have been localized in Freemarker and use that for localization (https://stackoverflow.com/questions/5548104/struts-select-tag-localization-implementation/17258640#17258640)... this does not seem sustainable or maintainable. Two possible methods for addressing this might be:

1. update the documentation to better identify how to localize these values in the "approved" way
2. implement a listKey parameter that like the textfield implementation or other implementations might call getText() on the key prior to rendering

Example Implementation for Radiobutton

    <#if parameters.listKey??>
        <#assign itemValue><@s.text name="${stack.findString(parameters.listKey)}" /><#rt></#assign>    
    <#elseif parameters.listValue??>
        <#assign itemValue = stack.findString(parameters.listValue)/>
    <#else>
        <#assign itemValue = stack.findString('top')/>
    </#if>

Issue Links

• is duplicated by: WW-3441 support list ui tag bind data by listValue beside by listKey