empts did
not work.
--
View this message in context:
http://camel.465427.n5.nabble.com/Conditional-route-scoped-onException-tp5731725p5731789.html
Sent from the Camel - Users mailing list archive at Nabble.com.
ignore error
b) if (exception) AND (batch_size=1) : use the error handler specified on
the route level (in my case a DeadLetterChannel with a redeliveryPolicy) ?
In my solution, a) is working fine, but not b)
--
View this message in context:
http://camel.465427.n5.nabble.com/Conditional-route-
lse
But this is not conform to xml schema :-(
--
View this message in context:
http://camel.465427.n5.nabble.com/Conditional-route-scoped-onException-tp5731725p5731728.html
Sent from the Camel - Users mailing list archive at Nabble.com.
irectly follow a element ?
Thx,
Bernard.
--
View this message in context:
http://camel.465427.n5.nabble.com/Conditional-route-scoped-onException-tp5731725.html
Sent from the Camel - Users mailing list archive at Nabble.com.
lieve this second route should be innocuous and
> never get exercised.
>
Ah well spotted. Its in fact a bug, when you are using the same class
type in onException on route scope.
I will get this fixed
https://issues.apache.org/jira/browse/CAMEL-3448
> Thanks again for all of your help,
http://camel.465427.n5.nabble.com/route-scoped-onException-tp3300994p3312060.html
Sent from the Camel - Users mailing list archive at Nabble.com.
ill have to put that logic *inside* the Processor because that
being invoked again on redelivery attempts.
See the following unit tests added
http://svn.apache.org/viewvc?rev=1050690&view=rev
http://svn.apache.org/viewvc?rev=1050691&view=rev
> --
> View this message in context:
>
rows Exception
> {
> System.out.println(" throw
> ConnectException");
> throw new java.net.ConnectException();
> }
> })
> .otherwise()
> .log("--- sending it on
System.out.println(" throw
ConnectException");
throw new java.net.ConnectException();
}
})
.otherwise()
.log("--- sending it on")
.to(postingAcceptWsEndpoint
ption before the
aggregation in the route causes issues with "groupExchanges".
If I'm allowed to use the route that Ashwin suggested, the DSL errors go
away.
Thanks,
-john
--
View this message in context:
http://camel.465427.n5.nabble.com/route-scoped-onException-tp3300994p330310
s route?
>
Is the aggregate part of the onException or not?
Add .end() where you want the onException to end.
> Thanks,
>
> -john
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/route-scoped-onException-tp3300994p3300994.html
> Sent from the Came
sed to be
in the start of the route.
In Camel 3.0 we will tighten this up so the DSL don't allow this.
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/route-scoped-onException-tp3300994p3301973.html
> Sent from the Camel - Users mailing list arch
Thanks Ashwin. I'll give that a shot. I thought I had read where onException
had to be at the start of the route, so I didn't realize I could place it
there.
--
View this message in context:
http://camel.465427.n5.nabble.com/route-scoped-onException-tp3300994p3301973.html
Sent from
nsourceknowledge.blogspot.com
http://opensourceknowledge.blogspot.com
-
--
View this message in context:
http://camel.465427.n5.nabble.com/route-scoped-onException-tp3300994p3301524.html
Sent from the Camel - Users mailing list archive at Nabble.com.
pExchanges().batchTimeout(5000)
.beanRef("processAggregationBean")
.to("http://some_web_service";);
How can I use onException in this route?
Thanks,
-john
--
View this message in context:
http://camel.465427.n5.nabble.com/route-scoped-onException-tp330099
15 matches
Mail list logo