You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2013/05/25 12:30:20 UTC
[jira] [Updated] (CAMEL-6326) BridgePropertyPlaceholderConfigurer
does not support nested Spring properties from System variables
[ https://issues.apache.org/jira/browse/CAMEL-6326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-6326:
-------------------------------
Priority: Minor (was: Major)
Fix Version/s: 2.12.0
2.11.1
> BridgePropertyPlaceholderConfigurer does not support nested Spring properties from System variables
> ---------------------------------------------------------------------------------------------------
>
> Key: CAMEL-6326
> URL: https://issues.apache.org/jira/browse/CAMEL-6326
> Project: Camel
> Issue Type: Bug
> Components: camel-spring
> Affects Versions: 2.11.0
> Environment: Windows 7
> Reporter: Henrik Filtenborg Sørensen
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 2.11.1, 2.12.0
>
> Attachments: BridgePropertyPlaceholderConfigurer-problem.zip
>
>
> Some work has been done in order to make BridgePropertyPlaceholderConfigurer work with nested spring-style properties (see CAMEL-6233).
> However, the fix does not allow using nested spring-style properties for system variables; here only camel-style is supported. For example:
> inCamelSystem=${${environment}.inCamelSystem} does not work when "environment" has been set as a system variable (e.g. set to "junit").
> inCamelSystem={{{{environment}}.inCamelSystem}} works, however.
> Camel test case is attached.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira