Hello,

I wondered if there was a way to store a global object in camel/camel context, which is not a String. Normally I would use a header or property on the message exchange perfectly well.

However, I have found a situation where one of our routes has a processor which is writing files directly to another directory. This directory is then consumed by another route we have. This means headers/properties etc cannot be used unfortunately.

This is not ideal and the correct solution would be to change this so we use the file endpoint so we can continue passing the exchange/message around different routes. However, this is not trivial to change right at this moment so I wondered if there was another way to store a kind of global object somewhere so these two independent routes could exchange information?

So far I have only seen the globalOptions on the camel context but this only permits storing string values.

Thanks for any suggestions
Jonathan

Reply via email to