Camel 1.6 and Spring 3
Spring's ServerSessionFactory has been removed in Spring 3. There's a related issue that made it in to 2.0. http://issues.apache.org/activemq/browse/CAMEL-502 It seems that the changes to JmsConfiguration and JmsComponent from that issue should be (almost) enough to get this working correctly. However, the commit message says Do NOT backport this to Camel 1.x branch. It builds fine but one test fails: Running org.apache.camel.converter.IOConverterTest Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.14 sec FAILURE! Why was it specified to not backport this to 1.x? Thanks. -- View this message in context: http://old.nabble.com/Camel-1.6-and-Spring-3-tp27152604p27152604.html Sent from the Camel - Users mailing list archive at Nabble.com.
1.6 equivalent of interceptFrom/interceptSendToEndpoint
I think this would be the correct syntax to intercept all exchanges on ContentManagerClearCacheTopic, converting beans to JSON on the way in, and JSON back to beans on the way out. dataFormats json id=json/ /dataFormats interceptFrom uri=activeMq:topic:ContentManagerClearCacheTopic unmarshal ref=json/ /interceptFrom interceptSendToEndpoint uri=activeMq:topic:ContentManagerClearCacheTopic marshal ref=json/ /interceptSendToEndpoint Can anyone convert that to 1.6 syntax for me or point me in the right direction? The old docs seem to disappear when new versions are released. I don't have the time to do a 2.0 upgrade right now. Thanks. -- View this message in context: http://www.nabble.com/1.6-equivalent-of-interceptFrom-interceptSendToEndpoint-tp25791665p25791665.html Sent from the Camel - Users mailing list archive at Nabble.com.
Redeliver to end of Endpoint/Queue?
Is it possible to have an exchange/message that threw an exception during processing be redelivered to the end of the queue instead of staying at the front of the queue and holding up all messages that are behind it? Some sort of interceptor or callback or customization to DeadLetterChannel? I'm sure there are ways to do this, but what might be considered best practice? Thanks. Eric -- View this message in context: http://www.nabble.com/Redeliver-to-end-of-Endpoint-Queue--tp22060777s22882p22060777.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Redeliver to end of Endpoint/Queue?
After thinking about this some more, what I'd really like is to be able to consume a message at some time in the future. If an exception occurs during processing, instead of the processing thread sleeping for the delay period, the message should be re-delivered with something like a consume_time header. Then the message consumer will change its selector every time it polls, something like consume_time System.currentTimeInMillis() Thoughts anyone? -- View this message in context: http://www.nabble.com/Redeliver-to-end-of-Endpoint-Queue--tp22060777s22882p22071417.html Sent from the Camel - Users mailing list archive at Nabble.com.
