Thanks Claus, that worked!
--
View this message in context:
http://camel.465427.n5.nabble.com/Cannot-use-file-xx-in-blueprint-route-properties-tp5770764p5770785.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Thanks,
it took 8 backslashes to make it work. This looks ridiculous ;-)
file:{{example.host}}
--
View this message in context:
http://camel.465427.n5.nabble.com/Cannot-use-file-xx-in-blueprint-route-properties-tp5770764p5770782.html
Sent from the Camel - Users mailing list arch
Probably due to how escaping the backslash is handled when using property
placeholder.
Try adding additional backslash to escape the backslashes in the config
file.
So
example.endpoint = file:\\example.host.com
Also note that using the file component to access windows shares only work
when run
On a related note (an maybe blueprint related)
example.endpoint = file:example.host.com
=> Does not work: creates folder in root of c:\ named example.host.com and
reads from that
=> Works / reads from windows share example.host.com
Any ideas on this? Should i try spring based routes he
See the alternative syntax at
http://camel.apache.org/simple
On Mon, Aug 17, 2015 at 10:51 AM, rwijngaa
wrote:
> Hi,
>
> I noticed that i cannot use things like ${file:name} or ${date:now} in my
> blueprint route that uses a OSGI config file (the value stays empty)
>
> E.g.
>
>
> I got this in th
More specific:
This works:
When you include tempFileName=tempTransfer/${file:name} in the
cfs.defaultWriteOptions property, than this does not work:
--
View this message in context:
http://camel.465427.n5.nabble.com/Cannot-use-file-xx-in-blueprint-route-properties-tp5770764p5770765.html
S
Hi,
I noticed that i cannot use things like ${file:name} or ${date:now} in my
blueprint route that uses a OSGI config file (the value stays empty)
E.g.
I got this in the /etc/com.example.myconfig.cfg
The {{ }} works ok, how can i make the ${file:xx} work ?
I'm using Camel 2.15.
--
View t
