> 1. How can I implement the state saving and reconstructing using memento in
> a generic way without serialization?
If you can probably narrow the generic requirements of your messages
to structure similar to the one below:
class MessageState(correlationId String, metaDataCsv: String)
Storing f
ries cached in
memcache expires before app comes up. It makes me store state in DB. I am
thinking of couchbase at this point.
Thanks,
Rakesh
--
View this message in context:
http://camel.465427.n5.nabble.com/Event-Driven-Use-Case-tp5726809p5726927.html
Sent from the Camel - Users mailing list arc
Hi,
> I would as you describe use the claimcheck
Pontus answer is a fair solution. A bit of elaboration from my side.
First of all I must mention however that I would strongly prefer to
create POJO-based memento [1] instead of serializing the exchanges.
In order to avoid the need to clean up ex
to many factors outside of my control.
>
> Thanks,
> Rakesh
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Event-Driven-Use-Case-tp5726809.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
vy traffic applications and I am not sure if I am doing it
in right way. Any suggestion will be highly appreciated. Using messaging
system is not an option due to many factors outside of my control.
Thanks,
Rakesh
--
View this message in context:
http://camel.465427.n5.nabble.com/Event-Drive
