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

Hi Its just to use toD instead of to On Wed, Aug 29, 2018 at 3:39 PM Hemant Pekhale wrote: > > 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: >

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

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:52 PM Hemant Pekhale

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

Hi You can use toD and set ignoreInvalidEndpoint=true On Wed, Aug 29, 2018 at 2:52 PM Hemant Pekhale wrote: > > 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 thi

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

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 ignoreInv