Re: Using PropertiesComponent

[Preben.Asmussen]

year - that's a weak point. I end up using a mix of Spring and Camel
properties whenever the properties file contains a dynamic reference e.g.
environment variable reference.

At the moment I define <Endpoint> elements in the camel context to be able
to use Spring property placeholders, but it's not the nicest solution to
have this kind of mix.

Example:
<camelContext id="GallupFTPContext"
xmlns="http://camel.apache.org/schema/spring";>
                <endpoint id="ftpTempDirEP" uri="file:${ftptempdir}"/>
                <endpoint id="cleanUpEP"
uri="file:${targetdirectory}?delete=true&amp;delay=24h&amp;filter=#oldFilesFilter"/>
                
                <route id="gallupFTPRoute">
                        <from
uri="ftp://{{ftpuser}}:{{ftppw}}@ftp.server/Rawdata?binary=true&amp;disconnect=true&amp;stepwise=false&amp;delay={{ftppolldelay}}&amp;filter=#ftpFilter";
/>
                        <log message="Copying ${file:name} to the ftp 
directory" 
logName="com.log.name" loggingLevel="TRACE" />
                        <to ref="ftpTempDirEP" />
                </route>
.........

--
View this message in context: 
http://camel.465427.n5.nabble.com/Using-PropertiesComponent-tp4299191p4806381.html
Sent from the Camel - Users mailing list archive at Nabble.com.