We have an object passing on the exchange. We take it aside using wireTap, in order to add persist logic on it, logging, and more. (that's why we don't use 'log' processor). We do it with an in-memory queue (seda), with a bean in its other end.
*Problem*: As the object is passed by its pointer, it is the same object on the original exchange and on the wireTapped exchange. This causes a situation in which until the exchange is processed by the bean at the other side of the wireTap, a property on our object is changed, and we persist a different state of the object than we expected. Is there a way to do a deep copy while wireTapping, so that our object is copied and its state is snapshot? Is there a better way of achieving what is described above? thanks ShlomiJ -- View this message in context: http://camel.465427.n5.nabble.com/Concurrent-problem-with-message-Body-using-WireTap-tp5502505p5502505.html Sent from the Camel - Users mailing list archive at Nabble.com.
