Re: catch error in producer endpoint

2009-10-10 Thread Claus Ibsen
On Fri, Oct 9, 2009 at 11:20 PM, parasmk para...@gmail.com wrote: Claus Ibsen-2 wrote: See the pollStrategy option on this page: http://camel.apache.org/polling-consumer.html You can then configure your own poll strategy on the ftp consumer and decide what to do in case of FTP server

Re: File component blocked by existing files

2009-10-10 Thread Vladimir Okhotnikov
Got it! The bitness (and probably OS flavor) is not relevant - the problem is because the service account does not have Modify permission on the existing file. I strongly suspect that it cannot rename the offending file to satisfy readLock=rename and hangs forever. When I manually gave the Modify

Re: human friendliness of camel

2009-10-10 Thread Willem Jiang
camelContext also supports to find the router within the package. Here is an example: camelContext xmlns=http://camel.apache.org/schema/spring; packageScan packageorg.apache.camel.spring.config.scan/package excludes**/*Excluded*/excludes

Re: Example previously running with IONA FUSE Camel 1.6, breaks with Apache Came 2.0.0

2009-10-10 Thread Willem Jiang
Just one comments, if you are trying to run the camel on a nonOSGi environment, you need to remove the camel-osgi from the class path. Or, you will get the complain about can find OSGi related class. Willem Claus Ibsen wrote: Its called routeBuilderRef now in 2.0 And it looks like you need

Re: Newbie looking for feedback on generating events from a database insert

2009-10-10 Thread Willem Jiang
Hi, You can also try the camel-jpa component[1], This unit test[2] may be helpful for you. [1]http://camel.apache.org/jpa.html [2]https://svn.apache.org/repos/asf/camel/trunk/components/camel-jpa/src/test/java/org/apache/camel/processor/jpa/JpaBatchConsumerTest.java Willem Pitre, Russell

Bean endpoint in a route is holding reference to the last used methodName and does not invoke Camel's Bean binding

2009-10-10 Thread sasidharm
I am trying to upgrade to Camel 2.0 and running into a weird issue. Say i have the following route: route from uri=jms:jms/queue/ process ref=someProcessor / to uri=bean1 / /route Here i am not specifying any method name explicitly for bean1 and I am depending on

Re: modify message before delivering to Dead Letter Queue

2009-10-10 Thread tide08
I would assume that uri would be available in header as per Camel-Http Documentation: HttpProducer.HTTP_URI - for v1.6.x Exchange.HTTP_URI - for v2.x or else as other approach you can just set header to distinguish between uri's avoiding custom processor for errorHandler itself. Something like