[
https://issues.apache.org/jira/browse/TAP5-843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Kemnade closed TAP5-843.
-------------------------------
Resolution: Invalid
We assume this is no longer relevant and therefore close it.
If you still have this issue in a recent Tapestry version (such as 5.3.8 or the
latest 5.4 preview release), feel free to provide the necessary information and
reopen.
> Allow nested symbol definitions
> -------------------------------
>
> Key: TAP5-843
> URL: https://issues.apache.org/jira/browse/TAP5-843
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-ioc
> Affects Versions: 5.2
> Reporter: Howard M. Lewis Ship
> Labels: bulk-close-candidate
>
> It would be nice if a Symbol's definition could be nested, i.e.
> ${foo.${bar}}
> This would evaluate ${bar} forming a new symbol name prefixed by 'foo', which
> would then itself be evaluated.
> Boy this is going to complicate the circular logic detection code!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
