Re: Camel 2.0 Async Findings - Roadmap to a solution

Hi Claus, As per your blog request, I'd like to discuss the virtues of naming the async method "async" vs treating your 2.0 functionality as a new implementation of the existing "thread" method. When I think about concurrency I think about multiple threads of execution - not whether something is

[jira] Commented: (CAMEL-1466) Wsdl file not find by cxf or camel-cxf endpoint in OSGI server

[ https://issues.apache.org/activemq/browse/CAMEL-1466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51887#action_51887 ] Charles Moulliard commented on CAMEL-1466: -- >From my point of view, this ticket must

Re: Camel 2.0 Async Findings - Roadmap to a solution

On Mon, May 25, 2009 at 9:00 AM, huntc wrote: > > Hi Claus, > > As per your blog request, I'd like to discuss the virtues of naming the > async method "async" vs treating your 2.0 functionality as a new > implementation of the existing "thread" method. > > When I think about concurrency I think ab

Re: Camel 2.0-M2 release status

Hello Does this mean that CAMEL 2.0-M2 will be based on revision 777408? Thanks S. Ali Tokmen savas-ali.tok...@bull.net Office: +33 4 76 29 76 19 GSM:+33 66 43 00 555 Bull, Architect of an Open World TM http://www.bull.com Willem Jiang a écrit : Hi Hadrain, I just change the trunk co

Re: Camel 2.0-M2 release status

On Mon, May 25, 2009 at 9:32 AM, S. Ali Tokmen wrote: > Hello > > Does this mean that CAMEL 2.0-M2 will be based on revision 777408? I think Hadrian will do the 2.0m2 release at any day when he has time. And usually its based on the trunk revision at the time. So if he does it tomorrow then the c

[DISCUSS - CAMEL 2.0] - About Producers and thread safety

Hi A recent bug was reported in ticket CAMEL-1641 https://issues.apache.org/activemq/browse/CAMEL-1641 The issue is in Camel 2.0 the FTP producer is not thread safe, in the sense that you cannot concurrently send at the same time to the same FTP endpoint. I have digged into this issue and discov

[jira] Created: (CAMEL-1644) Producer - Add scope for singleton to allow using non singleton producers to address thread safety

Producer - Add scope for singleton to allow using non singleton producers to address thread safety -- Key: CAMEL-1644 URL: https://issues.apache.org/activemq/browse/CA

[jira] Updated: (CAMEL-1644) Producer - Add scope for singleton to allow using non singleton producers to address thread safety

[ https://issues.apache.org/activemq/browse/CAMEL-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-1644: --- Attachment: CAMEL-1644.patch First cut of a patch. Notice there are some changes in for the CAMEL

[jira] Updated: (CAMEL-1641) camel-ftp is not thread safe

[ https://issues.apache.org/activemq/browse/CAMEL-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-1641: --- Affects Version/s: (was: 1.6.1) Fix Version/s: (was: 1.6.2) trunk: 778354. When/

[jira] Work started: (CAMEL-1641) camel-ftp is not thread safe

[ https://issues.apache.org/activemq/browse/CAMEL-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-1641 started by Claus Ibsen. > camel-ftp is not thread safe > > > Key: CAMEL-1641 > URL: ht

[jira] Created: (CAMEL-1645) Can't set the outgoing mail's content-type and charset

Can't set the outgoing mail's content-type and charset -- Key: CAMEL-1645 URL: https://issues.apache.org/activemq/browse/CAMEL-1645 Project: Apache Camel Issue Type: Bug Component

[jira] Updated: (CAMEL-1644) Producer - Add scope for singleton to allow using non singleton producers to address thread safety

[ https://issues.apache.org/activemq/browse/CAMEL-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-1644: --- Attachment: (was: CAMEL-1644.patch) > Producer - Add scope for singleton to allow using non s

[jira] Updated: (CAMEL-1644) Producer - Add scope for singleton to allow using non singleton producers to address thread safety

[ https://issues.apache.org/activemq/browse/CAMEL-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-1644: --- Attachment: CAMEL-1644b.patch A patch without the file/ftp changes. > Producer - Add scope for

camel-restlet - Why is it not InOut by default

Hi I am looking into adding some more unit test for concurrency and got into an issue with camel-restlet. By default the exchange it creates are InOnly and I was wondering why its not InOut. I do think this is a flaw and that we should let it by InOut. If not then we have a bug in the DefaultRes

[jira] Created: (CAMEL-1646) camel-restlet - Should be InOut exchange pattern

camel-restlet - Should be InOut exchange pattern Key: CAMEL-1646 URL: https://issues.apache.org/activemq/browse/CAMEL-1646 Project: Apache Camel Issue Type: Bug Components: camel-res

[jira] Resolved: (CAMEL-1646) camel-restlet - Should be InOut exchange pattern

[ https://issues.apache.org/activemq/browse/CAMEL-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-1646. Resolution: Fixed trunk: 778399 1.x: 778401 > camel-restlet - Should be InOut exchange pattern

[jira] Commented: (CAMEL-1075) mina tcp: support for asyncronous InOut endpoint.

[ https://issues.apache.org/activemq/browse/CAMEL-1075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51893#action_51893 ] Claus Ibsen commented on CAMEL-1075: Yannick, thanks for reporting your experience and th

Re: [DISCUSS - CAMEL 2.0] - About Producers and thread safety

Hi I have looked into this a bit more. With this we can support correlation for concurrent request/response with mina as well. A feature that was generelly lacking there. So this is definitely a great step in a good direction for Camel. This feature has been tracked here: http://fusesource.com/

[jira] Created: (CAMEL-1647) Producer Pool - Add a producer pool for connection pooling capabilities

Producer Pool - Add a producer pool for connection pooling capabilities --- Key: CAMEL-1647 URL: https://issues.apache.org/activemq/browse/CAMEL-1647 Project: Apache Camel I

[jira] Resolved: (CAMEL-1644) Producer - Add scope for singleton to allow using non singleton producers to address thread safety

[ https://issues.apache.org/activemq/browse/CAMEL-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-1644. Resolution: Fixed trunk: 778418. > Producer - Add scope for singleton to allow using non singl

[jira] Resolved: (CAMEL-1641) camel-ftp is not thread safe

[ https://issues.apache.org/activemq/browse/CAMEL-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-1641. Resolution: Fixed trunk: 778419 And fixed by CAMEL-1644. > camel-ftp is not thread safe > ---

[jira] Updated: (CAMEL-1599) Add the proxy options to camel-http so you can set it easily from the URI

[ https://issues.apache.org/activemq/browse/CAMEL-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Cook updated CAMEL-1599: - Attachment: httpProxyPatch.txt Patch attached. I haven't included my unit test as it was te

CAMEL-1599 - Add the proxy options to camel-http so you can set it easily from the URI

I attached the patch. However I could not see the the patch attached button as per the instructions on the wiki.. http://camel.apache.org/contributing.html Jonathan -- View this message in context: http://www.nabble.com/CAMEL-1599---Add-the-proxy-options-to-camel-http-so-you-can-set-it-easily-f

Re: CAMEL-1599 - Add the proxy options to camel-http so you can set it easily from the URI

Hi Jonathan Thanks for the patch. Its attached to the JIRA so cool. On Mon, May 25, 2009 at 4:12 PM, jpcook wrote: > > I attached the patch. However I could not see the the patch attached button > as per the instructions on the wiki.. > http://camel.apache.org/contributing.html > > Jonathan > --

[jira] Created: (CAMEL-1648) Bespin editor mangles route XML

Bespin editor mangles route XML --- Key: CAMEL-1648 URL: https://issues.apache.org/activemq/browse/CAMEL-1648 Project: Apache Camel Issue Type: Sub-task Reporter: Jonathan Anstey -- This message i

[jira] Updated: (CAMEL-1648) Bespin editor mangles route XML

[ https://issues.apache.org/activemq/browse/CAMEL-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Anstey updated CAMEL-1648: --- Description: The Bespin editor in the web console takes nice route XML like {code} http

[jira] Commented: (CAMEL-1648) Bespin editor mangles route XML

[ https://issues.apache.org/activemq/browse/CAMEL-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51898#action_51898 ] Jonathan Anstey commented on CAMEL-1648: Just disabled the Bespin editor in revision

[jira] Reopened: (CAMEL-825) async endpoints like SEDA and VM do not work with InOut and Spring Remoting - as the caller does not wait for the exchange to be completed

[ https://issues.apache.org/activemq/browse/CAMEL-825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Hunt reopened CAMEL-825: I see the seda queue as being very similar to a jms queue in Camel with the main difference