Re: [jira] Resolved: (CAMEL-3643) camel-cxf should not copy the attachments between the CXF and Camel message if the endpoint is working POJO DataFormat

2014-02-03 Thread yirco
Hi, this change breaks the backward compatibility of the CXF component as published on the camel site: Attachment Support POJO Mode: *Attachments are propagated to Camel message's attachments since 2.1. So, it is possible to retreive attachments by Camel Message API DataHandler Message.getAtta

Re: Aggregator completionSize = 1

2014-02-03 Thread Stephan Burkard
Sorry, the message was sent too early... The question to the Camel gurus is: what is more preferable: 1) On completionSize = 1 Camel throws an exception on context startup since this is treated as "invalid configuration" 2) The aggregator should just check for the very special case of completion

Aggregator completionSize = 1

2014-02-03 Thread Stephan Burkard
Hi Motivated by Claus' nice words :-) and to take a whiff of the Camel code, I analyzed my own Jira issue CAMEL-7146. In the method "doAggregation" the aggregator evaluates if the aggregation is complete. With completionSize = 1 this is the case on every Exchange. Therefore the aggregator does no

Re: [DISCUSS] - Drop Spring 3.1 support in Camel 2.13 onwards

2014-02-03 Thread Daniel Kulp
On Feb 3, 2014, at 9:01 AM, Claus Ibsen wrote: > Hi > > In Camel 2.12 we dropped support for Spring 3.0. But shipped and > tested with Spring 3.1. > > For Camel 2.13 we could drop support for Spring 3.1. And being shipped > and tested with Spring 3.2. This makes sense. CXF is also flipping

Re: camel pull request: Provide access to the shutdown task Future in order to ...

2014-02-03 Thread Antoine DESSAIGNE
Hi, Do you have any concerns or suggestions about these changes ? Right now, I've copy/pasted the DefaultShutdownStrategy and added those changes on order to make it work (and it's working nicely). Also, if you don't like this public getter, we can also make it protected. Thanks for the feedback

Re: [DISCUSS] - Drop Spring 3.1 support in Camel 2.13 onwards

2014-02-03 Thread David Karlsen
Sounds good to me. And also if one take into consideration moving onto spring 4.x as well: https://issues.apache.org/jira/browse/CAMEL-7074 2014-02-03 Claus Ibsen : > Hi > > In Camel 2.12 we dropped support for Spring 3.0. But shipped and > tested with Spring 3.1. > > For Camel 2.13 we could dr

[DISCUSS] - Drop Spring 3.1 support in Camel 2.13 onwards

2014-02-03 Thread Claus Ibsen
Hi In Camel 2.12 we dropped support for Spring 3.0. But shipped and tested with Spring 3.1. For Camel 2.13 we could drop support for Spring 3.1. And being shipped and tested with Spring 3.2. One reason would be that if we have spring 3.2 as minimum then we can use some of the new APIs it has for