Hi,
It was the point of this patch that the logic of the force shutdown was
also executed when you cancel the future.
Consider a product that uses camel in order to deal with all its data
inputs and outputs, it has multiple CamelContext defined.
You can provide to the administrator the ability to
Woohoo! the more the merrier! look forward to your contributions...
pick some JIRAs (or create some) and send some pull requests/patches.
On Tue, Feb 4, 2014 at 5:24 PM, Alvaro Rodriguez
wrote:
> Hello,
> I sent an ICLA to Apache, received confirmation from jcarman, and I
> can see my name in the
Hello,
I sent an ICLA to Apache, received confirmation from jcarman, and I
can see my name in the "Unlisted CLAs" page.
I'd like to contribute to the project. I was thinking about editing
the website first if that's ok. I'll also try to at least get the
tests running on my box so I can contribute
I dissabled the Jenkis build [1]
[1]
https://builds.apache.org/view/A-D/view/Camel/job/Camel.trunk.fulltest.spring3.1/
Best,
Christian
-
Software Integration Specialist
Apache Member
V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
Apache Incubator PMC Membe
Thank's for letting us know and saving some CPU cycles on my side... ;-)
Best,
Christian
-
Software Integration Specialist
Apache Member
V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
Apache Incubator PMC Member
https://www.linkedin.com/pub/christian-muell
I just upgraded my local workspace to CXF 2.7.9 which I would like to see
in the next Camel versions [1]. The test suite is still running...
Afterwards I would like to give Camel 2.12.3 a "dry run"...
At present, we have 8 outstanding issues for 2.12.3 [2] (my one included).
Only one is classifie
On Feb 4, 2014, at 12:33 PM, Christian Müller
wrote:
> I just upgraded my local workspace to CXF 2.7.9 which I would like to see
> in the next Camel versions [1]. The test suite is still running…
2.7.9 was built wrong. I’ll be doing a 2.7.10 build likely tomorrow. :-(
Dan
>
> Afterwards
I have a few issues assigned to me. Please don't move them, the
camel-kafka component in particular (but not only).
Thanks,
Hadrian
On 02/04/2014 12:33 PM, Christian Müller wrote:
I just upgraded my local workspace to CXF 2.7.9 which I would like to see
in the next Camel versions [1]. The tes
Polishing your patch as the timeout logic should only happen if a
timeout exception was thrown, as the original code.
Will commit the revised code in a bit. Is there a JIRA ticket?
On Mon, Feb 3, 2014 at 3:52 PM, Antoine DESSAIGNE
wrote:
> Hi,
>
> Do you have any concerns or suggestions about th
+1
FYI, about Spring, I'm working on the "new" Spring bundles (both for
3.2.7.RELEASE and 4.0.1.RELEASE).
Regards
JB
On 02/03/2014 03:01 PM, 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 f
+1
Christian
On Mon, Feb 3, 2014 at 3:01 PM, 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.
>
> One reason would be
Hi
Logged a ticket to track this
https://issues.apache.org/jira/browse/CAMEL-7165
On Mon, Feb 3, 2014 at 3:01 PM, 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 be
12 matches
Mail list logo
