[jira] [Assigned] (CAMEL-4485) Exceptions are not propagated to the parent route when they are thrown from the RecipientList EIP

[ https://issues.apache.org/jira/browse/CAMEL-4485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-4485: -- Assignee: Claus Ibsen Exceptions are not propagated to the parent route when they are thrown

[jira] [Resolved] (CAMEL-4485) Exceptions are not propagated to the parent route when they are thrown from the RecipientList EIP

[ https://issues.apache.org/jira/browse/CAMEL-4485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-4485. Resolution: Duplicate Fix Version/s: 2.9.0 2.8.2 Duplicate of CAMEL-4484

[jira] [Assigned] (CAMEL-4486) Exceptions are not propagated to the parent route when endpoint cannot be resolved in the RoutingSlip EIP

[ https://issues.apache.org/jira/browse/CAMEL-4486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-4486: -- Assignee: Claus Ibsen Exceptions are not propagated to the parent route when endpoint cannot

[jira] [Updated] (CAMEL-4487) MockEndpoint should reset defaultProcessor

[ https://issues.apache.org/jira/browse/CAMEL-4487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-4487: --- Description: Thanks for the patch. I added unit test as well. Priority: Minor (was:

[jira] [Resolved] (CAMEL-4487) MockEndpoint should reset defaultProcessor

[ https://issues.apache.org/jira/browse/CAMEL-4487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-4487. Resolution: Fixed Thanks for the patch. I added an unit test as well. MockEndpoint should reset

Re: [DISCUSS] - Trunk as Camel 3.0

On 9/25/11 9:14 AM, Hadrian Zbarcea wrote: Ioannis, what you suggest is similar to what Christian was suggesting except instead of a 2.9 and maybe a 2.10 who knows, you would be ok with calling these versions 3.0, 3.1, with the intention, probably, to accommodate Claus' proposal. Now, to answer

[jira] [Commented] (CAMEL-3941) Camel-cxf dependencies problem as: jetty-7.3.1 is servlet-2.5 and cxf-2.4.0 is servlet-3.0 dependent

[ https://issues.apache.org/jira/browse/CAMEL-3941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13114257#comment-13114257 ] Willem Jiang commented on CAMEL-3941: - Another workaround is adding the synchronous

Re: Camel 2.8.2 - Reason for the many backports?

On Sat, Sep 24, 2011 at 7:34 PM, Christian Müller christian.muel...@gmail.com wrote: Hello Claus! Thank you for your work updating the WIKI page. I didn't know them... Yeah there is some good to know wiki pages for Camel team members here http://camel.apache.org/developers.html But I have

Re: Camel 2.8.2 - Reason for the many backports?

On Sat, Sep 24, 2011 at 8:32 PM, Hadrian Zbarcea hzbar...@gmail.com wrote: Excellent points Christian. My take on this inline. Hadrian On 09/24/2011 01:34 PM, Christian Müller wrote: Hello Claus! Thank you for your work updating the WIKI page. I didn't know them... But I have to stress

Re: Camel 2.8.2 - Reason for the many backports?

On Fri, Sep 23, 2011 at 3:09 PM, Willem Jiang willem.ji...@gmail.com wrote: Hi Claus, I just found your svnmerge.py doesn't has the detail log message like this, it may be cause by your old copy of svnmerge.py. Author: davsclaus Date: Fri Sep 23 07:51:41 2011 New Revision: 1174573 URL:

[jira] [Commented] (CAMEL-4256) Adding a EndpointConfiguration interface

[ https://issues.apache.org/jira/browse/CAMEL-4256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13114285#comment-13114285 ] Claus Ibsen commented on CAMEL-4256: Why introduce an interface? You could use those

[jira] [Resolved] (CAMEL-4486) Exceptions are not propagated to the parent route when endpoint cannot be resolved in the RoutingSlip EIP

[ https://issues.apache.org/jira/browse/CAMEL-4486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-4486. Resolution: Fixed Fix Version/s: 2.9.0 2.8.2 Thanks for reporting and

Re: [DISCUSS] - Trunk as Camel 3.0

Willem, it sounds to me like you agree on most of the issues, correct? Comments inline. Hadrian I think already stated my +1 for a new API module to break the cycle dependency of camel-core which was proposed by Christian. Excellent. But I don't think we should ship the camel-api module

[jira] [Updated] (CAMEL-3824) Allow cometd component to send message headers with the message

[ https://issues.apache.org/jira/browse/CAMEL-3824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Watkins updated CAMEL-3824: -- Attachment: cometd_header_support_patch.txt Patch contains fixes for adding in header support

[jira] [Updated] (CAMEL-3824) Allow cometd component to send message headers with the message

[ https://issues.apache.org/jira/browse/CAMEL-3824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua Watkins updated CAMEL-3824: -- Patch Info: [Patch Available] Fix Version/s: 2.9.0 Allow cometd component to send

Re: Camel 2.8.2 - Reason for the many backports?

Hi Claus, I just ran the svnmerge.py merge -r1175323 to merge the patch by hand, but after checking the commit mail, I found I forget to update the svnmerge-commit-message.txt with the original commit log :( On 9/25/11 11:29 PM, Claus Ibsen wrote: On Fri, Sep 23, 2011 at 3:09 PM, Willem

Camel - Build # 1340 - Failure

The Apache Jenkins build system has built Camel (build #1340) Status: Failure Check console output at https://builds.apache.org/job/Camel/1340/ to view the results.