[
https://issues.apache.org/activemq/browse/CAMEL-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61637#action_61637
]
Ashwin Karpe commented on CAMEL-2791:
-------------------------------------
Hi Claus,
Sure, No worries... I was reviewing the component code and wanted my approach
to be clear as to whether we were doing a load of system properties using a
location "system:..." or whether it as a default fallback to do a lookup and
adjust.
I will implement the solution as an override and provide fallback as a check
before giving up.
Do you think there is any merit to adding a "system:..." as an addtional way of
injecting properties inderpendently like "file:..."?
Please let me know.
Cheers,
Ashwin...
> 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.