Apache Camel trunk on JDK 7

Hi Just wondering if anybody have tried to compile and test the Camel trunk source on a JDK 7 ? It would be nice to know if there is a few minor issues which we may be able to correct before the next 2.8.1 / 2.9.0 release so we at least can compile on JDK 7. -- Claus Ibsen -

FTP component enhancement suggestion

Hi All, when storing a file the ftp component checks if the file exists in the endpoint, this is done by listing the content of the destination folder and looping through all files listed. the list operation takes a long time when the destination folder contains hundreds of files. instead of

Re: FTP component enhancement suggestion

Hi, In my test method channel.ls(name) for SFTP server takes more less the same time like channel.ls() The quickest way is to do this in less elegant i think. I f you want to know if file exist just try to make directory with the same name and look for results. It require to have write permission

Re: Apache Camel trunk on JDK 7

On Friday, August 12, 2011 8:23:00 AM Claus Ibsen wrote: Hi Just wondering if anybody have tried to compile and test the Camel trunk source on a JDK 7 ? I tried and it didn't get very far. The antcalls off to the schemagen stuff all failed. It's the same stuff that fails with the IBM

Re: FTP component enhancement suggestion

Marco Crivellaro wrote: ... in the end the list of files needs to be sent over TCP the more files you have the longer it will take. Transferring big file list can be an issue for slow networks. In theory I agree with you but just try. 5000 files in folder is enough to observe SFTP server

[HEADS UP] - Adjustments to ExecutorServiceManager on trunk

Hi Recently the ExecutorServiceStrategy had a bigger refactor (https://issues.apache.org/jira/browse/CAMEL-4244) Such as renaming the class to a better name ExecutorServiceManager. Also introducing a ThreadPoolFactory, ThreadFactory among others. The ThreadPoolFactory is a great addition, which

[jira] [Commented] (CAMEL-4298) Add back ExecutorServiceStrategy and mark it as @deprecated

[ https://issues.apache.org/jira/browse/CAMEL-4298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13084190#comment-13084190 ] Claus Ibsen commented on CAMEL-4298: See post on dev forum

[jira] [Resolved] (CAMEL-4328) CAMEL-4244 broke EIP configuration of thread pools

[ https://issues.apache.org/jira/browse/CAMEL-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-4328. Resolution: Fixed Fixed part of rev 1157157. CAMEL-4244 broke EIP configuration of thread pools

[jira] [Resolved] (CAMEL-4298) Add back ExecutorServiceStrategy and mark it as @deprecated

[ https://issues.apache.org/jira/browse/CAMEL-4298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-4298. Resolution: Fixed Added back the ExecutorServiceStrategy interface, and a delegate implementation

Re: [DISCUSS] Supporting our users to be more involved with our project

The easy to resolve issues have the Novices annotation. Dan created and shared the new JIRA view which is called Camel-Novice [1]. I have linked this page from our contribution page [2]. I hope our users/contributors will like it and are more easily involved. [1]

Re: [DISCUSS] remove the commons-dbcp dependency from the Camel feature file

My comments inline. Best, Christian Installing the commons-dbcp in karaf would be as easy as just doing a osgi:install right? Yes. I would prefer if Karaf / SMX had some sort of jdbc features you could install and leverage out of the box. A bit similar to what you see in JEE servers

Re: [DISCUSS] remove the commons-dbcp dependency from the Camel feature file

Commons dbcp would need a few hacks to provide monitoring, there was talk on their devlists about it a while back http://nicoulaj.github.com/commons-dbcp-jmx/ And https://issues.apache.org/jira/browse/DBCP-292 On Aug 12, 2011, at 3:59 PM, Christian Müller wrote: My comments inline.