tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Heston (JIRA)" <j...@apache.org>
Subject [jira] Updated: (TAP5-1077) Merge symbol values into property values from a bean definition
Date Thu, 22 Apr 2010 16:31:49 GMT

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

Brian Heston updated TAP5-1077:
-------------------------------

    Attachment: TapestrySpringFilter working.txt
                TapestrySpringFilter broken.txt
                ContextLoaderListener.txt

> Merge symbol values into property values from a bean definition
> ---------------------------------------------------------------
>
>                 Key: TAP5-1077
>                 URL: https://issues.apache.org/jira/browse/TAP5-1077
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-spring
>    Affects Versions: 5.1.0.5
>            Reporter: Igor Drobiazko
>            Assignee: Igor Drobiazko
>            Priority: Minor
>             Fix For: 5.2.0
>
>         Attachments: ContextLoaderListener.txt, TapestrySpringFilter broken.txt, TapestrySpringFilter
working.txt
>
>
> Springs allows you to externalize property values from a bean definition into a property
file. It would be nice if the values of the property placeholders could be read from symbol
values. An example:
> <bean id="serviceStrategy" class="${custom.strategy.class}"/>
> public static void contributeApplicationDefaults(MappedConfiguration<String, String>
configuration) {
>     configuration.add("custom.strategy.class", "com.foo.DefaultStrategy");
> }

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message