[
https://issues.apache.org/struts/browse/TILES-221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antonio Petrelli moved STR-1129 to TILES-221:
---------------------------------------------
Component/s: (was: Tiles 1 Plugin)
tiles-jsp (jsp support)
tiles-core
Affects Version/s: (was: Nightly Build)
2.0.4
Workflow: Struts - editable closed status (was: jira)
Issue Type: New Feature (was: Improvement)
Key: TILES-221 (was: STR-1129)
Project: Tiles (was: Struts 1)
> Add ability to import tile attributes into a java.util.Map
> ----------------------------------------------------------
>
> Key: TILES-221
> URL: https://issues.apache.org/struts/browse/TILES-221
> Project: Tiles
> Issue Type: New Feature
> Components: tiles-core, tiles-jsp (jsp support)
> Affects Versions: 2.0.4
> Environment: Operating System: other
> Platform: Other
> Reporter: Graham Carlyle
> Priority: Minor
>
> It would be useful to be able to access a tiles attributes via a java.util.Map
> object.
> This would make it more obvious where the tile attributes (rather than an
> ordinary page scope attribute) are being used in the tile.
> When used with JSTL it would make tile attribute access more consistent with
> the
> other JSTL scoped attributes (pageScope, requestScope, sessionScope,
> applicationScope, param etc.)
> This could be achieved by adding an optional "id" attribute to the
> importAttribute tag which, when no "name" attribute is specified, would
> introduce an appropriately scoped java.util.Map of the tile attributes.
> For example:
> <importAttribute id="args"/>
> <c:out value="${args.message}"/>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
