You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Lukasz Lenart (JIRA)" <ji...@apache.org> on 2016/09/06 19:33:20 UTC
[jira] [Commented] (WW-4685) Allow directly accessing I18N keys
from Tiles defintions
[ https://issues.apache.org/jira/browse/WW-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15468310#comment-15468310 ]
Lukasz Lenart commented on WW-4685:
-----------------------------------
Docs https://cwiki.apache.org/confluence/display/WW/Tiles+Plugin#TilesPlugin-AccessingStrutsattributes
> Allow directly accessing I18N keys from Tiles defintions
> --------------------------------------------------------
>
> Key: WW-4685
> URL: https://issues.apache.org/jira/browse/WW-4685
> Project: Struts 2
> Issue Type: Improvement
> Components: Plugin - Tiles
> Reporter: Lukasz Lenart
> Assignee: Lukasz Lenart
> Priority: Minor
> Fix For: 2.5.3
>
>
> It'd be better to allow directly fetching I18N keys from Struts properties instead of using multiple {{tiles.xml}} definitions. The latest version of Tiles supports expression languages so it can be possible to add support for Struts' internals.
> {code:xml}
> <definition name="home" extends="logged-in">
> <put-attribute name="title" expression="S2:home.title"/>
> <put-attribute name="body" value="/WEB-INF/tiles/home.jsp"/>
> </definition>
> {code}
> and {{home.title}} should be first evaluated as a key in resource bundle and then as a value from ValueStack.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)