[
https://issues.apache.org/activemq/browse/CAMEL-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61635#action_61635
]
Claus Ibsen commented on CAMEL-2791:
------------------------------------
Ashwin the idea is that you can *override* an existing property with a JVM
system property. For example if something is wrong, then you can quickly remedy
the issue by overriding the property from the JVM command line.
The other idea is to have it to fallback to a system property if no property
exists with the given key.
So I was looking for adding a switch to the PropertiesComponent to dictate this
behavior.
To have an system scheme in the properties component. Yeah why not. The bits
are already there as we got that in the simple language as well.
> Properties component - Add option to let it look first/last for JVM system
> property
> -----------------------------------------------------------------------------------
>
> Key: CAMEL-2791
> URL: https://issues.apache.org/activemq/browse/CAMEL-2791
> Project: Apache Camel
> Issue Type: New Feature
> Components: camel-core
> Affects Versions: 2.3.0
> Reporter: Claus Ibsen
> Assignee: Ashwin Karpe
> Priority: Minor
> Fix For: Future
>
>
> See nabble
> http://old.nabble.com/File-Consumer-directoryName-problem-ts28777347.html
> By default the properties component will only resolve properties from
> properties files.
> But sometimes you may want to be able to set a JVM system property with
> either *override* or is used as *fallback* in case of a key. Such as if a key
> is missing it can fallback to a JVM key. Or a JVM key can override an
> existing key in the properties file.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
