Hi Yeah sure we love contributions, and you are welcome to provide a PR with improved javadoc http://camel.apache.org/contributing
Github PR is the easiest https://github.com/apache/camel/ On Wed, Apr 12, 2017 at 1:34 PM, Jonathan Schoreels <[email protected]> wrote: > Is it allowed to open pull request just to add java doc, or would you prefer > to do it yourself ? > > > On 2017-04-12 13:31, Claus Ibsen wrote: >> >> Yes only body + headers is stored that is by design >> >> On Wed, Apr 12, 2017 at 1:19 PM, Jonathan Schoreels >> <[email protected]> wrote: >>> >>> Hello, >>> >>> I've been using JdbcAggregationRepository recently and discovered that it >>> won't save the property in the table and thus, losing them at each >>> aggregation step. >>> >>> I know property are meant to be inner-route variable, and headers >>> metadata >>> for protocol/outer-scope, and that by definition, a >>> JdbcAggregationRepository is an outer service. However, at the same time, >>> it's an abstraction inside the route, and it's still very unsetting to >>> have >>> property that dissapear in the same camel route. >>> >>> Do you see it as a Bug or a Feature ? >>> >>> PS : I'm still asking myself why there is no user guide to use >>> JdbcAggregationRepository in the book (Hawt example) or a "pretty-doc" in >>> http://camel.apache.org/aggregator.html. Or maybe there is other more >>> standard way to aggregate in a persistent repository that I don't know >>> yet ? >>> >>> Thank you, >>> >>> Jonathan Schoreels >> >> >> > -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
