ResolveEndpointFailedException with a file endpoint

true, delay=1000}] at org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:351) //... /U -- View this message in context: http://old.nabble.com/ResolveEndpointFailedException-with-a-file-endpoint-tp27024218p27024218.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: ResolveEndpointFailedException with a file endpoint

ured with a valid starting directory: C:\ftp\data\in.txt This is likely a different problem - but I would appreciate any hints! Thanx! /U Claus Ibsen-2 wrote: > > On Tue, Jan 5, 2010 at 7:21 AM, /U wrote: >> >> I have a simple route transferring contents of files >>

2.1.0 Manual?

Is the manual for 2.1.0 available? The link http://camel.apache.org/manual/camel-manual-2.1-SNAPSHOT.pdf is broken. Regards, /U -- View this message in context: http://old.nabble.com/2.1.0-Manual--tp27066471p27066471.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: 2.1.0 Manual?

Thanks Hadrian. Is there a chance you could upload it today? Is there a significant delta between 2.0.0PDF and the one for 2.1.0? Regards, /U hzbarcea wrote: > > Yes, there was a problem with the generation of the pdf. I will > upload it manually. > Thanks > Hadrian > &g

Re: Groovy support stable in 1.3.0?

jars for jsr223 groovy support. /U Seon Lee wrote: > > I'm having trouble getting groovy support working in release 1.3.0 stable. > > Here is the stack trace: > java.lang.IllegalArgumentException: No script engine could be created for: &

Re: Groovy support stable in 1.3.0?

org.codehaus.groovy > groovy-all > 1.7.0 > > > Willem > /U wrote: >> the same issue is seen on 2.1.0 as well. With the dependency >> camel.script ver 2.1.0 added, a route with groovy filter fails >> to instantiate with

Re: Groovy support stable in 1.3.0?

({ it > 50 }) //... Dependencies: org.apache.camel camel-script 2.1 com.sun.script groovy-engine 20080611 org.codehaus.groovy groovy-all 1.7.0 am i missing s.th? can you plz point me to camel unit test cases using groov

onException()

7;t onException() method invoked? - is there a way to pass an arbitrary data to a bean which is used as an endpoint. Eg: to("bean:myBean?method=processError&arg="+fromUri) regardds, /U -- View this message in context: http://old.nabble.com/onException%28%29-tp28008233p2800

Re: onException()

thnaks for the help - it works. Only problem: if connection to toUri fails, MyErrorhandler is invoked; but if connection to fromUri fails, MyErrorHandler not invoked! for example, from("file://a.log").onException(Exception.class).process(MyErrHandler).to("ftp://u...@server?.

Re: onException()

cess to the route that failed in myerrHandler's rollback() method so I could remove the route from the context. how i can do that? many thanx for any help! /U Claus Ibsen-2 wrote: > > On Wed, Mar 24, 2010 at 11:30 PM, /U wrote: >> >> thnaks for the help - it w

Re: onException()

melcontext for each such route so the entire context can be destroyed after workflow is complete? much thanks! /U Claus Ibsen-2 wrote: > > Hi > > Why do you need to remove it? Can you just stop it instead? > The Camel in Action book, chapter 13, contains details how to s