Hi, I am working on developing a new component in Camel and this component will behave a lot like the SedaComponent. I am looking at how the SedaComponent was written and there is something I can't explain to myself. The SedaProducer creates a correlated copy before inserting the exchange in the blocking queue. Then the SedaConsumer picks up the exchange, and before sending it downstream, it does another copy, but this one is a copyExchangeAndSetCamelContext. Why do copies before and after the queue? Can someone explain this to me? (I am not questioning if this should be done or not. Just want to know if I should do the same in my component).
Thanks! -- View this message in context: http://camel.465427.n5.nabble.com/Developing-a-new-component-why-copy-exchanges-tp5730331.html Sent from the Camel - Users mailing list archive at Nabble.com.
