[
https://issues.apache.org/jira/browse/WW-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15468781#comment-15468781
]
Hudson commented on WW-4685:
----------------------------
SUCCESS: Integrated in Jenkins build Struts-JDK7-master #518 (See
[https://builds.apache.org/job/Struts-JDK7-master/518/])
WW-4685 Supports evaluating expressions from tiles definitions as a
(lukaszlenart: rev 1bed00d3d7269bbe11cd3ec1711400e050ef57b4)
* (add)
plugins/tiles/src/main/java/org/apache/struts2/tiles/StrutsAttributeEvaluator.java
* (edit)
plugins/tiles/src/main/java/org/apache/struts2/tiles/StrutsTilesContainerFactory.java
> 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)
