tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAP5-843) Allow nested symbol definitions
Date Sat, 16 Apr 2011 00:01:06 GMT

    [ https://issues.apache.org/jira/browse/TAP5-843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13020493#comment-13020493
] 

Hudson commented on TAP5-843:
-----------------------------

Integrated in tapestry-5.2-freestyle #317 (See [https://hudson.apache.org/hudson/job/tapestry-5.2-freestyle/317/])
    

> 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.0
>            Reporter: Howard M. Lewis Ship
>
> 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message