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 running on windows and the access will be done using the user the camel process is running as. This might lead to problems when running the application as a service as oppose to when you run it as your self during development. Perhaps you should take a look at the camel-jcifs component in the camel-extra project. https://camel.apache.org/jcifs.html Best regards Pontus On Mon, 17 Aug 2015 at 16:06 rwijngaa <rino.van.wijngaar...@gmail.com> wrote: > On a related note (an maybe blueprint related) > > example.endpoint = file:\\\\example.host.com > > <from uri="{{example.endpoint}}" /> > => Does not work: creates folder in root of c:\ named example.host.com > and > reads from that > > <from uri="file:\\\\example.host.com" /> > => Works / reads from windows share example.host.com > > > Any ideas on this? Should i try spring based routes here or is this sort of > property usage > not supported? > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Cannot-use-file-xx-in-blueprint-route-properties-tp5770764p5770770.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
