Re: Cannot use ${file:xx} in blueprint route / properties

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

Re: Cannot use ${file:xx} in blueprint route / properties

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

Re: Cannot use ${file:xx} in blueprint route / properties

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

Re: Cannot use ${file:xx} in blueprint route / properties

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

camel:netty udpConnectionlessSending option and "Too many open files"

I'm using Camel 2.15.2 and the *camel-netty* component and I have a Camel route that mirrors UDP datagrams to a remote server via *netty:udp*. I saw that *camel-netty *supports the *udpConnectionlessSending *option, and I thought it would be a good idea as it will not result in failures when the

Re: Cannot use ${file:xx} in blueprint route / properties

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

Cannot use ${file:xx} in blueprint route / properties

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

Re: Want to keep original file but want to delete done file.

There is no support for deleting only the done file. You would need to delete it manually, you can add a step in the route that does this at the end. On Thu, Aug 13, 2015 at 9:01 PM, Manish wrote: > Hi, > > I am new to camel.. > My requirement is: I want to consume file using file endpoint, but

Re: polling enricher on split exchanges?

Hi all, I found a way to use enricher to aggregate from the external rest endpoint and generate an exchange property before splitting to the batch-level aggregators. Thanks, Patrick -- View this message in context: http://camel.465427.n5.nabble.com/polling-enricher-on-split-exchanges-tp5770

Camel - CXF javax.xml.ws.Holder parts issue in POJO mode

Hi everyone, Working with Camel-CXF Client endpoint I identified an issue which I cannot bypass without building custom CXF interceptor. Camel / Camel-Cxf version: 2.15.1.redhat-620133 CXF version: 3.0.4.redhat-620133 Scenario: 1. Camel-CXF endpoint: dataFormat=POJO 2. WS SEI method in Java: