Hi, Currently akka-camel's CamelMessage only allows access to the Exchange's body and headers. As a workaround for CAMEL-8674, I would like to access the Exchange's properties as well. I can currently do this by adding setHeader() nodes for specific properties to the RouteDefinition, but this seems cumbersome.
Do you think it would be a bad idea to extend CamelMessage to provide access to properties as well? If so, why? -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
