yeah - it's a custom component and I figured it out.
Somehow I had the impression that I had to set the consumer properties
manually calling setConsumerProperties ->
protected Endpoint createEndpoint(String uri, String remaining,
Map<String,
Object> parameters) throws Exception {
SplunkConfiguration configuration =
connFactory.parseMap(parameters);
setProperties(configuration, parameters);
Endpoint endpoint = new SplunkEndpoint(uri, this,
configuration);
((ScheduledPollEndpoint)endpoint).setConsumerProperties(parameters);
return endpoint;
}
Removing call to setConsumerProperties solved it on trunk and it also works
on 2.11.x.
The odd thing is that 2.11.x seems to handle it anyway
--
View this message in context:
http://camel.465427.n5.nabble.com/consumer-bridgeErrorHandler-true-on-2-12-SNAPSHOT-tp5736355p5736363.html
Sent from the Camel - Users mailing list archive at Nabble.com.
