RE: [DISCUSS] - Fix 2 pain issues with camel-bindy for Camel 2.9

+1 for both. 2) Makes Bindy a lot more pleasant to use. Cheers, Mathieu > Date: Wed, 16 Nov 2011 12:40:06 -0800 > Subject: Re: [DISCUSS] - Fix 2 pain issues with camel-bindy for Camel 2.9 > From: christian.muel...@gmail.com > To: dev@camel.apache.org > >

Re: [DISCUSS] Rules for backports

Hello Dan! Thanks for your contribution. I like it... Best, Christian Sent from a mobile device

Re: Unit test failure on trunk in camel-saxon

On Mon, Nov 21, 2011 at 3:23 PM, Willem Jiang wrote: > Current camel-xslt endpoint will not try to load the xslt file until the > endpoint is processing the first exchange. > I think we need to let the camel-xslt endpoint load the xslt file when it is > created to let the user know what is wrong a

Re: [DISCUSS] Rules for backports

I just fixed a few minor grammatical things and added more into the "who" section. Dan On Sunday, November 20, 2011 9:25:03 PM Christian Müller wrote: > Today, I had some time to work on it and update [1]. > Please review this change and feel free to update/ask/discuss the changes > you do no

Re: [VOTE] Release Camel 2.8.3 (the second try)

+1 Dan On Friday, November 18, 2011 9:51:48 AM Willem Jiang wrote: > This is a vote to release Camel 2.8.3. 2.8.3 contains fixes about 60+ > JIRA issues that would be good to get into the hands of Camel users. > > Please find the staging repo here: > https://repository.apache.org/content/repo

Re: [VOTE] Release Camel 2.8.3 (the second try)

+1 Hadrian On 11/17/2011 08:51 PM, Willem Jiang wrote: This is a vote to release Camel 2.8.3. 2.8.3 contains fixes about 60+ JIRA issues that would be good to get into the hands of Camel users. Please find the staging repo here: https://repository.apache.org/content/repositories/orgapachecamel-

Re: Unit test failure on trunk in camel-saxon

So that by [1] I simply mimicked the same changes done on unit-tests by [2] [1] https://issues.apache.org/jira/browse/CAMEL-4700 [2] https://issues.apache.org/jira/browse/CAMEL-4689 Babak -- View this message in context: http://camel.465427.n5.nabble.com/Unit-test-failure-on-trunk-in-camel-sax

Re: Unit test failure on trunk in camel-saxon

Hi Willem, completely agree on your proposal, and looking at the changes on the existing unit-tests by [1], that's [2] & [3] that "fail-fast" behaviour seems to be gone away. [1] http://svn.apache.org/viewvc?rev=1202819&view=rev [2] http://svn.apache.org/viewvc/camel/trunk/camel-core/src/test/jav

Re: Unit test failure on trunk in camel-saxon

Hi, https://issues.apache.org/jira/browse/CAMEL-4700 Babak -- View this message in context: http://camel.465427.n5.nabble.com/Unit-test-failure-on-trunk-in-camel-saxon-tp5009713p5010536.html Sent from the Camel Development mailing list archive at Nabble.com.

Re: Unit test failure on trunk in camel-saxon

Current camel-xslt endpoint will not try to load the xslt file until the endpoint is processing the first exchange. I think we need to let the camel-xslt endpoint load the xslt file when it is created to let the user know what is wrong about the endpoint configuration. It could save lots of trou

Re: [VOTE] Release Camel 2.8.3 (the second try)

+1 On Fri, Nov 18, 2011 at 02:51, Willem Jiang wrote: > This is a vote to release Camel 2.8.3. 2.8.3 contains fixes about 60+ > JIRA issues that would be good to get into the hands of Camel users. > > Please find the staging repo here: > https://repository.apache.org/**content/repositories/**or

Re: [VOTE] Release Camel 2.8.3 (the second try)

Get chance to run more examples in Servicemix, they're camel-example-cafe camel-example-cxf camel-example-cxf-osgi camel-example-cxf-proxy camel-example-osgi camel-example-osgi-rmi camel-example-pojo-messaging camel-example-spring-xquery camel-example-spring all good for me. Though found some mi