Re: CXF endpoint getting resolved at the time of initialization of the route

2018-08-29 Thread Hemant Pekhale
Hi Calus, thanks for your reply. can you show a sample code here. I am using java DSLProcessor. So wanted to have a look at the sample. On Wed, Aug 29, 2018 at 6:33 PM Claus Ibsen wrote: > Hi > > You can use toD and set ignoreInvalidEndpoint=true > On Wed, Aug 29, 2018 at 2:

CXF endpoint getting resolved at the time of initialization of the route

2018-08-29 Thread Hemant Pekhale
Hi All, I've a route which has CXF in middle of it. But when I start the route it throws error "Could not resolve endpoint" that endpoint is indeed not accessible but I want this to happen when a message is actually reach to the cxf. Is there any way to prevent this. I red somewhere that

Re: Camel lock gets acquired on files but not picked sometime

2018-08-06 Thread Hemant Pekhale
o only pickup files with a certain file > > > pattern, or to exclude names with temporary names, etc. > > > There is a number of different filter options, see its doc. > > > > > > On Mon, Aug 6, 2018 at 3:52 PM, Hemant Pekhale < > hemant.pekh...@gmail.com> >

Re: Camel lock gets acquired on files but not picked sometime

2018-08-06 Thread Hemant Pekhale
documentation about these. > > > On Mon, Aug 6, 2018 at 3:19 PM, Hemant Pekhale > wrote: > > Hi All, > > > > I have a route which picks files from a folder and do some processing on > it > > and store it in other folder. I have used parameter "de

Camel lock gets acquired on files but not picked sometime

2018-08-06 Thread Hemant Pekhale
Hi All, I have a route which picks files from a folder and do some processing on it and store it in other folder. I have used parameter "delete=true" for deleting file from source folder. Sometime it happens that files are stuck in the source folder and camel lock files are also created for all

Re: Consuming 1 file at a time in camel route

2018-04-09 Thread Hemant Pekhale
Hi Claus, Thanks for the solution. It worked perfectly as expected. Thanks! On Mon, Apr 9, 2018 at 7:21 PM, Claus Ibsen <claus.ib...@gmail.com> wrote: > Set synchronous=true on the cxf endpoint > > On Mon, Apr 9, 2018 at 3:43 PM, Hemant Pekhale <hemant.pekh...@gmail.com>

Re: Consuming 1 file at a time in camel route

2018-04-09 Thread Hemant Pekhale
FYI : I am using cxf to post on webservice On Mon, Apr 9, 2018 at 7:12 PM, Hemant Pekhale <hemant.pekh...@gmail.com> wrote: > Hi Claus, > > Thanks for the quick response. My route is picking a file and and posting > on a web service. What is happening is webservice tak

Re: Consuming 1 file at a time in camel route

2018-04-09 Thread Hemant Pekhale
, Apr 9, 2018 at 2:42 PM, Hemant Pekhale <hemant.pekh...@gmail.com> > wrote: > > Hi, > > > > I want to consume file one by one from a directory. Second file must not > be > > picked until the route completes the processing of first file. &

Consuming 1 file at a time in camel route

2018-04-09 Thread Hemant Pekhale
Hi, I want to consume file one by one from a directory. Second file must not be picked until the route completes the processing of first file. Which approach I can use?

Re: Retrying a message from a specific point of the route

2018-02-09 Thread Hemant Pekhale
e possible with a home made custom Talend component. Or, rethink > the case globally to avoid tweaking the TOS way. > > Regards, > Alex > > On Thu, Feb 8, 2018 at 11:58 AM, Hemant Pekhale <hemant.pekh...@gmail.com> > wrote: > >> Hi Alex, >

RE: Retrying a message from a specific point of the route

2018-02-08 Thread Hemant Pekhale
ack-or-an-entire-route.html> of interest in order to influence the redelivery. Enjoy, Alex On Mon, Feb 5, 2018 at 7:40 AM, Hemant Pekhale <hemant.pekh...@gmail.com> wrote: > Hi, > > How to retry a message from a specific point of the route when exception > occurs. > I am

Retrying a message from a specific point of the route

2018-02-04 Thread Hemant Pekhale
Hi, How to retry a message from a specific point of the route when exception occurs. I am using camel 2.15 and Spring configuration. Some example is most appreciated. Thanks!