HTTP4 retrying with I/O exception in fuse 6.3

2017-06-12 Thread Kevin-Void
Hi All, I have used Http4 component in fuse 6.2.1 and it works fine as expected. In new version of fuse 6.3, the response is not as expected. It is as follows: 2017-06-12 18:34:54,886 | INFO | mer[SAMPLE.ROUTE] | RetryExec | 219 - org.apache.httpcomponents.httpclient -

Re: Configuring Quartz in cfg file (Property placeholder)

2017-05-23 Thread Kevin-Void
Thanks Claus. So we need to code as below manner. Kindly correct me if i am wrong. Kind Regards, Kevin -- View this message in context: http://camel.465427.n5.nabble.com/Configuring-Quartz-in-cfg-file-Property-placeholder-tp5799160p5800081.html

Re: Configuring Quartz in cfg file (Property placeholder)

2017-05-10 Thread Kevin-Void
Yes Claus.. Is there a way to use quartz.properties file externally like cfg file or properties file outside the jar :( Regards, Kevin -- View this message in context: http://camel.465427.n5.nabble.com/Configuring-Quartz-in-cfg-file-Property-placeholder-tp5799160p5799232.html Sent from the

Re: Configuring Quartz in cfg file (Property placeholder)

2017-05-09 Thread Kevin-Void
Thanks for the response Claus.. Actually the module is deployed in fabric environment(Clustered). The module is deployed in 3 nodes with same jar and config file. Kind Regards, Kevin -- View this message in context:

Configuring Quartz in cfg file (Property placeholder)

2017-05-09 Thread Kevin-Void
Hello All, I want to configure my quartz properties in cfg file or in an individual property file in etc directory of the container, so that i can make changes easily in that file instead of making change in code and rebuilding the jar again. Please find my code below: my route:

Dynamic URI based on file name/cfg file/property value

2016-05-13 Thread Kevin-Void
Hi Folks, I am trying to pass a *to URI value dynamically* with a property value. That property value will be configured already in the cfg file. When the file name is extracted using *CamelFileNameOnly* header, it has to get passed to the to Uri endpoint. So that the same name is referred in