On Fri, Jan 23, 2009 at 12:55 AM, Claus Ibsen <claus.ib...@gmail.com> wrote: > Hi > > The OUT message really starts to irritate me. > > We have various components that set data on the OUT body and then the > Pipeline will use this result as IN for then next node. > What happens is then whatever headers etc from IN is lost. Then you > cant really route and have your headers preserve during the entire > route.
I don't know t much about pipeline, but it sounds like pipeline should do the copying if it is going to use one output message as input to the next processor. That it, the pipeline should copy both the body and header (?) The component does not know if the in header should be copied to the out header. Those in header may not be relevant to the out body. My intuition is that out header the header information associated with the out message. It (out header) does not have to include everything in the in header. > > We might wanna give this a thought in Camel 2.0? > - Pipeline to always add headers from IN to OUT, so headers is preserved +1 > - Components to enforce MEP and only set data on OUT if its InOut +1. > - Components to add headers from IN to OUT if it set OUT as result > and what not Not sure. > > Currently the SQL component has this flaw. In the past it was > Velocity. And I guess there are some other components as well. > > Just starting a thread to not forget. I only had one cup of coffee > this morning. Going to boil water now..... > > > -- > Claus Ibsen > Apache Camel Committer > > Open Source Integration: http://fusesource.com > Blog: http://davsclaus.blogspot.com/ >
