Hi I am starting to work on this and will send a PR
On Wed, Jul 24, 2019 at 1:44 PM Claus Ibsen <[email protected]> wrote: > > Hi > > JIRA ticket: > https://issues.apache.org/jira/browse/CAMEL-13788 > > > So on the Camel Message API we have from Camel 1.0 an IN and OUT > message that was based on the JBI and SOAP-WS specs. > > > We have from time to time in the past debated about this API and what > to do for major new releases.What we have settled a bit on is to > favour using getMessage instead of getIn or getOut. So that is why you > have that today with > > getIn > getOut > > And recently introduced is > getMessage > > Which basically is a safe way to use that can deal with the IN vs OUT idiom. > > So I think its time to take the next step and deprecate OUT so we give > Camel end users and component developers and Camel itself amble time > to adjust our code and move to use getMessage instead. > > The getIn vs getOut has also caused a bit confusion what to use, and > despite having both javadoc and a FAQ it stills stumbles on Camel end > users > http://camel.apache.org/using-getin-or-getout-methods-on-exchange.html > > Any thoughts? > > -- > Claus Ibsen > ----------------- > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
