[
https://issues.apache.org/jira/browse/TAP5-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12859874#action_12859874
]
Brian Heston commented on TAP5-1077:
------------------------------------
The change made for this feature has broken existing Spring functionality
regarding properties. I have a single project with Spring for the services and
Tapestry for the presentation. The Spring beans that used to load properties
from the properties files can no longer get their values. I have attached log
output from the version before the update and the version with this update to
illustrate the lack of Spring loading the properties files. I've also attached
the config files used to reproduce the problem.
> 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: applicationContext.xml, ContextLoaderListener.txt,
> database.properties, TapestrySpringFilter broken.txt, TapestrySpringFilter
> working.txt, web.xml
>
>
> 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.
