[
https://issues.apache.org/activemq/browse/CAMEL-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52015#action_52015
]
Jonathan Cook commented on CAMEL-1631:
--------------------------------------
I assume this would work for all endpoints? Is there a clever way to lookup the
right endpoint to delegate to?
> create a properties component so that endpoints can be created where the URI
> is looked up in a properties file at runtime
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-1631
> URL: https://issues.apache.org/activemq/browse/CAMEL-1631
> Project: Apache Camel
> Issue Type: New Feature
> Reporter: James Strachan
> Fix For: 2.0.0
>
>
> rather than this trick:
> http://camel.apache.org/how-do-i-use-spring-property-placeholder-with-camel-xml.html
> which is spring specific and a bit cludgy (requiring an <endpoint> in XML
> and an entry in a properties file) it would be good if we could define a
> PropertiesComponent which can be configured like this...
> {code}
> <bean id="properties"
> class="org.apache.camel.components.properties.PropertiesComponent">
> <property name="location" value="classpath:myfile.properties"/>
> </bean>
> {code}
> Then if the file *myfile.properties* on the classpath looks like this
> {code}
> foo = file://usr/local/cheese
> {code}
> Then sending to the endpoint *properties:foo* would in fact send to
> *file://usr/local/cheese* unless folks overrode the system property on the
> command line (say)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
