[jira] Commented: (CAMEL-3605) Switch to use slf4j as logger (instad of commons logging)

[ https://issues.apache.org/jira/browse/CAMEL-3605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12989080#comment-12989080 ] Claus Ibsen commented on CAMEL-3605: All components migrated in rev: 1065931. > Switc

[jira] Created: (CAMEL-3607) How to set receiveBufferSizePredictor option in Camel-netty udp consumer server?

How to set receiveBufferSizePredictor option in Camel-netty udp consumer server? - Key: CAMEL-3607 URL: https://issues.apache.org/jira/browse/CAMEL-3607 Project: Camel

[jira] Commented: (CAMEL-3606) Regression in stateful job support caused by duplicate job name check added in camel-quartz 2.6

[ https://issues.apache.org/jira/browse/CAMEL-3606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988960#comment-12988960 ] Bryan Keller commented on CAMEL-3606: - The patch that caused this can be found in issu

[jira] Created: (CAMEL-3606) Regression in stateful job support caused by duplicate job name check added in camel-quartz 2.6

Regression in stateful job support caused by duplicate job name check added in camel-quartz 2.6 --- Key: CAMEL-3606 URL: https://issues.apache.org/jira/browse/CAMEL-3606

[jira] Commented: (CAMEL-3239) camel-quartz should require unique timername

[ https://issues.apache.org/jira/browse/CAMEL-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988952#comment-12988952 ] Bryan Keller commented on CAMEL-3239: - This change caused a regression in my applicati

[jira] Commented: (CAMEL-3285) Create a new blackbox component which can encapsulate routes using a specialized ProtocolBuilder endpoint (similar to RouteBuilder)

[ https://issues.apache.org/jira/browse/CAMEL-3285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988939#comment-12988939 ] Ashwin Karpe commented on CAMEL-3285: - Hi Claus & Kristof, I have added a warning to

Re: [HEADS UP] - Migrating of slf4j in progress - please dont do major commits

Hi I have now committed the "grunt work" of the slf4j migration. Tomorrow I will migrate the remaining camel components, examples and the likes. You should now be able to commit major stuff to camel-core or the likes. You are welcome to run tests on your system to see if the migrated caused any

[jira] Commented: (CAMEL-3605) Switch to use slf4j as logger (instad of commons logging)

[ https://issues.apache.org/jira/browse/CAMEL-3605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988823#comment-12988823 ] Claus Ibsen commented on CAMEL-3605: other needed components migrated in rev: 1065694.

Re: [HEADS UP] - Migrating of slf4j in progress - please dont do major commits

Yeah: Karaf 2.1.x uses PAX logging 1.5.x and SLF4J 1.5.8. Karaf 2.2.x uses PAX logging 1.6.0 (that Guillaume and I have released last week), PAX logging 1.6.0 supports SLF4J 1.6.1. Regards JB On 01/31/2011 05:25 PM, Claus Ibsen wrote: On Mon, Jan 31, 2011 at 5:14 PM, Guillaume Nodet wrote:

[jira] Commented: (CAMEL-3605) Switch to use slf4j as logger (instad of commons logging)

[ https://issues.apache.org/jira/browse/CAMEL-3605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988805#comment-12988805 ] Claus Ibsen commented on CAMEL-3605: camel-core migrated in rev: 1065692. > Switch to

Re: [HEADS UP] - Migrating of slf4j in progress - please dont do major commits

On Mon, Jan 31, 2011 at 5:48 PM, Guillaume Nodet wrote: > Yes, it's the case. I've release pax-logging a few days ago, however, > ServiceMix is still using karaf 2.1.x which hasn't upgraded to > pax-logging 1.6.x, so I'd rather keep using 1.5.11 if possible for the > api. > Or use 1.6.x on the mav

Re: [HEADS UP] - Migrating of slf4j in progress - please dont do major commits

Yes, it's the case. I've release pax-logging a few days ago, however, ServiceMix is still using karaf 2.1.x which hasn't upgraded to pax-logging 1.6.x, so I'd rather keep using 1.5.11 if possible for the api. Or use 1.6.x on the maven side, but make sure that the osgi range is [1.5,2.0) On Mon, Ja

Re: [HEADS UP] - Migrating of slf4j in progress - please dont do major commits

On Mon, Jan 31, 2011 at 5:14 PM, Guillaume Nodet wrote: > Not sure what the issue is, but pax-logging 1.5.x only supports slf4j > <= 1.5.11, so you need to make sure the range of the package uses is > large enough to support existing versions.   I'd recommend using > 1.5.11 for the slfaj-api and n

Re: [HEADS UP] - Migrating of slf4j in progress - please dont do major commits

Not sure what the issue is, but pax-logging 1.5.x only supports slf4j <= 1.5.11, so you need to make sure the range of the package uses is large enough to support existing versions. I'd recommend using 1.5.11 for the slfaj-api and not 1.6.x, unless there are strong requirements to do so. On Mon,

Re: [HEADS UP] - Migrating of slf4j in progress - please dont do major commits

Hi Okay seems ready for one of the first commits for the migration. There is an issue with OSGi blueprint, which I will have to revisit. That OSGi stuff can as usual be a bit tricky to decipher wtf is wrong. On Mon, Jan 31, 2011 at 3:37 PM, Claus Ibsen wrote: > On Mon, Jan 31, 2011 at 3:10 PM,

Re: [HEADS UP] - Migrating of slf4j in progress - please dont do major commits

On Mon, Jan 31, 2011 at 3:10 PM, Hadrian Zbarcea wrote: > Claus, if you do it incrementally, and commit only one major component at a > time (the small ones could go together) it will be less painful for you and > others. > Many thanks for the heads up. > Yeah I will try that. Currently I have

Re: [HEADS UP] - Migrating of slf4j in progress - please dont do major commits

Claus, if you do it incrementally, and commit only one major component at a time (the small ones could go together) it will be less painful for you and others. Many thanks for the heads up. Hadrian On Jan 31, 2011, at 7:51 AM, Claus Ibsen wrote: > Hi > > I am migrating from commons-logging t

Re: Apache Camel 2.6.0 released

sebb, I also realized also I missed the [ANNOUNCE] in the subject line (and there is a non-exculpatory explanation for that :) ). I will make the additions and resend. The link was there though [1] and the project description is the first thing on the page. Thanks a bunch, Hadrian On Jan 31,

[jira] Assigned: (CAMEL-3586) Fix camel-mina tests to use dynamic port numbers to ensure tests don't fail when ports are already in use on the test machine.

[ https://issues.apache.org/jira/browse/CAMEL-3586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tracy Snell reassigned CAMEL-3586: -- Assignee: (was: Tracy Snell) > Fix camel-mina tests to use dynamic port numbers to ensure t

[HEADS UP] - Migrating of slf4j in progress - please dont do major commits

Hi I am migrating from commons-logging to slf4j which means alot of files will be touched by switching the logger. https://issues.apache.org/jira/browse/CAMEL-3605?focusedCommentId=12988746#comment-12988746 There is a migrating tool to do this, so that part is easy http://www.slf4j.org/migrator.h

[jira] Commented: (CAMEL-3605) Switch to use slf4j as logger (instad of commons logging)

[ https://issues.apache.org/jira/browse/CAMEL-3605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988746#comment-12988746 ] Claus Ibsen commented on CAMEL-3605: And assembly kit should include the slf4j instead

[jira] Commented: (CAMEL-3605) Switch to use slf4j as logger (instad of commons logging)

[ https://issues.apache.org/jira/browse/CAMEL-3605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988745#comment-12988745 ] Claus Ibsen commented on CAMEL-3605: Remember to check the archetypes, the pom.xml the

[jira] Commented: (CAMEL-3605) Switch to use slf4j as logger (instad of commons logging)

[ https://issues.apache.org/jira/browse/CAMEL-3605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988738#comment-12988738 ] Claus Ibsen commented on CAMEL-3605: Migration in progress. It would take a bit time t

[jira] Issue Comment Edited: (CAMEL-2624) support for async responses on single tcp connection

[ https://issues.apache.org/jira/browse/CAMEL-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988737#comment-12988737 ] Ashwin Karpe edited comment on CAMEL-2624 at 1/31/11 12:02 PM: -

[jira] Commented: (CAMEL-2624) support for async responses on single tcp connection

[ https://issues.apache.org/jira/browse/CAMEL-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988737#comment-12988737 ] Ashwin Karpe commented on CAMEL-2624: - Hi, Is this issue still open given that we hav

[jira] Work started: (CAMEL-3605) Switch to use slf4j as logger (instad of commons logging)

[ https://issues.apache.org/jira/browse/CAMEL-3605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-3605 started by Claus Ibsen. > Switch to use slf4j as logger (instad of commons logging) > - > >

[jira] Issue Comment Edited: (CAMEL-2624) support for async responses on single tcp connection

[ https://issues.apache.org/jira/browse/CAMEL-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988737#comment-12988737 ] Ashwin Karpe edited comment on CAMEL-2624 at 1/31/11 12:01 PM: -

[jira] Commented: (CAMEL-3268) Maven 3 to build source

[ https://issues.apache.org/jira/browse/CAMEL-3268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988733#comment-12988733 ] Christian Müller commented on CAMEL-3268: - features-maven-plugin 2.1.0 (actual use

[jira] Commented: (CAMEL-3604) Upgrade to Spring 3.0.x as minimum (eg drop support for Spring 2.x)

[ https://issues.apache.org/jira/browse/CAMEL-3604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988730#comment-12988730 ] Christian Müller commented on CAMEL-3604: - This task also incudes: - removing the

Re: [DISCUSS] Dropping support for java 1.5 from camel-2.7.0 onwards

On 1/30/11 1:16 PM, Hadrian Zbarcea wrote: Why create a branch now? The branch should be created off of the camel-2.6.0 tag. Hence it can be created at any time. It must not be created off of trunk. That time is the first time somebody wants to apply a fix on both the trunk and 2.6.x moving f

[jira] Commented: (CAMEL-3595) FTP rename fails

[ https://issues.apache.org/jira/browse/CAMEL-3595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988723#comment-12988723 ] Mikael Jørgensen commented on CAMEL-3595: - I made the following small test case:

Re: [DISCUSS] Dropping support for java 1.5 from camel-2.7.0 onwards

On Mon, Jan 31, 2011 at 11:25 AM, Christian Müller wrote: > Droping Spring 2.x also means: > - removing the features file for Spring 2? > - removing the camel-itest-spring-2.0 module? > > Should we put this to the issue? > Yeah please comment on the JIRA tickets. There is also code in camel-jms

Re: [DISCUSS] Dropping support for java 1.5 from camel-2.7.0 onwards

Droping Spring 2.x also means: - removing the features file for Spring 2? - removing the camel-itest-spring-2.0 module? Should we put this to the issue?

[jira] Updated: (CAMEL-3602) camel xslt component should set the ErrorHandler when it uses Transformer to transform the message

[ https://issues.apache.org/jira/browse/CAMEL-3602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang updated CAMEL-3602: Summary: camel xslt component should set the ErrorHandler when it uses Transformer to transform the

Re: [DISCUSS] Dropping support for java 1.5 from camel-2.7.0 onwards

Hi I have created some tickets for the roadmap https://issues.apache.org/jira/browse/CAMEL-3603 https://issues.apache.org/jira/browse/CAMEL-3604 https://issues.apache.org/jira/browse/CAMEL-3605 On Sun, Jan 30, 2011 at 9:30 AM, Claus Ibsen wrote: > Hi > > I have created a wiki page for the 2.

[jira] Created: (CAMEL-3605) Switch to use slf4j as logger (instad of commons logging)

Switch to use slf4j as logger (instad of commons logging) - Key: CAMEL-3605 URL: https://issues.apache.org/jira/browse/CAMEL-3605 Project: Camel Issue Type: Task Reporter: C

[jira] Commented: (CAMEL-3604) Upgrade to Spring 3.0.x as minimum (eg drop support for Spring 2.x)

[ https://issues.apache.org/jira/browse/CAMEL-3604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988714#comment-12988714 ] Claus Ibsen commented on CAMEL-3604: Richard K have implemented the Spring EL as a lan

[jira] Created: (CAMEL-3603) Upgrade to JDK 1.6 as minimum (eg drop support for JDK 1.5)

Upgrade to JDK 1.6 as minimum (eg drop support for JDK 1.5) --- Key: CAMEL-3603 URL: https://issues.apache.org/jira/browse/CAMEL-3603 Project: Camel Issue Type: Task Reporte

[jira] Created: (CAMEL-3604) Upgrade to Spring 3.0.x as minimum (eg drop support for Spring 2.x)

Upgrade to Spring 3.0.x as minimum (eg drop support for Spring 2.x) --- Key: CAMEL-3604 URL: https://issues.apache.org/jira/browse/CAMEL-3604 Project: Camel Issue Type: Task

Re: camel-http4 wiki page

On Sun, Jan 30, 2011 at 11:01 PM, Christian Müller wrote: > Hello Claus! > > I added the missed wiki page and updated camel-http4 to use the Apache > HttpClient 4.1. > I realized that camel-http made some progression but camel-http4 not > (camel-http4 was forked in Camel 2.2).  :-( > Do you reme

[jira] Created: (CAMEL-3602) camel xslt component should set the ErrorHandler when it use Transformer to transform the message

camel xslt component should set the ErrorHandler when it use Transformer to transform the message - Key: CAMEL-3602 URL: https://issues.apache.org/jira/browse/CAMEL-36

[jira] Resolved: (CAMEL-3577) DefaultProducerTemplate - Should lazy initialize thread pool for the async operations

[ https://issues.apache.org/jira/browse/CAMEL-3577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-3577. Resolution: Fixed trunk: 1065534. > DefaultProducerTemplate - Should lazy initialize thread pool f

[jira] Commented: (CAMEL-3580) Type converter for CXFPayload data type

[ https://issues.apache.org/jira/browse/CAMEL-3580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988684#comment-12988684 ] Willem Jiang commented on CAMEL-3580: - Applied patch with thanks Stephan, also fixed s

[jira] Resolved: (CAMEL-3580) Type converter for CXFPayload data type

[ https://issues.apache.org/jira/browse/CAMEL-3580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CAMEL-3580. - Resolution: Fixed Fix Version/s: 2.7.0 > Type converter for CXFPayload data type > ---