tapestry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jochen Kemnade (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (TAP5-842) Add a conditional clause to IoC Symbol evaluation
Date Mon, 12 Jan 2015 08:10:58 GMT

     [ https://issues.apache.org/jira/browse/TAP5-842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jochen Kemnade closed TAP5-842.
-------------------------------
    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.

> Add a conditional clause to IoC Symbol evaluation
> -------------------------------------------------
>
>                 Key: TAP5-842
>                 URL: https://issues.apache.org/jira/browse/TAP5-842
>             Project: Tapestry 5
>          Issue Type: New Feature
>          Components: tapestry-ioc
>    Affects Versions: 5.2
>            Reporter: Howard M. Lewis Ship
>              Labels: bulk-close-candidate
>
> It's very common to want to do some extra, extra late binding of symbols ... generally,
to configure things one way for production mode and another way for development mode.
> A symbol syntax such as
> ${foo ? bar  : baz }
> (whitespace optional and ignored)
> could be used for this (common) situation.  First symbol foo is evaluated and coerced
to Boolean, this selects either 'bar' or 'baz' which are then evaluated as symbols.  Thus:
> foo.delay.production=1 h
> foo.delay.development=1 s
> foo.delay = ${tapestry.production-mode ? foo.delay.production : foo.delay.development}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message