I did start looking at the error handling framework. Right now I have
something in the spirit below, but I still am not sure, what would be the
best replacement recipientList or for inOnly.
<route id="doCompose">
<filter>
<aggregate>
........
<inOnly uri="activemq:doPost"/>
</aggregate>
</filter>
</route>
<route id="doPost">
<from uri="activemq:doPost?concurrentConsumers=1"/>
<onException
<exception> java.net.ConnectException</exception>
<redeliveryPolicy maximumRedeliveries="-1"
delayPattern="1:1000;5:10000;10:30000"/>
<handled>
<constant>true</constant>
</handled>
<setHeader headerName="CamelExceptionCaught">
<simple>Headers: ${headers} - ${exception.message}</simple>
</setHeader>
<to uri="activemq:rdf-connection-fail"/>
<log message="Error connecting to RDF repo body:${out.body}
exception message: ${exception.message} body:${exception.responseBody}"/>
</onException>
<onException>
<exception>java.lang.Exception</exception>
....
</onException>
<setHeader headerName="CamelHttpMethod">
<constant>POST</constant>
</setHeader>
<recipientList>
<simple>http://sesameServer.com:7171/repositories/repoQA/statements</simple>
</recipientList>
</route>
--
View this message in context:
http://camel.465427.n5.nabble.com/customizing-recipientList-tp5768423p5768481.html
Sent from the Camel - Users mailing list archive at Nabble.com.