Hi The @user mailing list is the best place to ask questions about Camel. There are many more subscribers who can help and follow the discussions.
The @dev is about the development of the Apache Camel project. Exchange is not serializable because Camel cannot guarantee that content in the exchange is serializable. End users of Camel can put any kind of non serializable data in it. There is a DefaultExchangeHolder which Camel uses for some of its EIPs and components to serialize the Exchange using it. http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/impl/DefaultExchangeHolder.html On Sat, Jul 30, 2011 at 11:07 AM, E.Gherardini <e.gherard...@hotmail.com> wrote: > Hi claus, > in fact my question was stupid, and is related to component development. > > I need to have messages serializable, passing over the wire. So I was > wondering why DefaultMessage isn't serializable, it would make things > easier. > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Why-Exchange-is-not-serializable-tp4647549p4649365.html > Sent from the Camel Development mailing list archive at Nabble.com. > -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
