Hi Thanks for reporting.
I did try to reproduce it here but it worked nicely. I added unit tests to Camel itself. You can check the commit here http://svn.apache.org/viewvc?view=rev&revision=801511 Also about the file thingy it worked fine here as well as the .camelLock files are removed after use. On Wed, Aug 5, 2009 at 2:07 PM, akuhtz<[email protected]> wrote: > > Hello, > > I use a direct endpoint to access a service that throws a RuntimeException > and on the calling side I get a UndeclaredThrowableException (with the > nested RuntimeException deep in the stack) instead of the expected > RuntimeException. > Maybe I missed something and this be changed by configuration somewhere ... > or is this standard behaviour if CamelProxyFactoryBean is used to create the > proxy? > > I've attached a sample project based on the camel-example-pojo-messaging > project that shows the problem. > > Another small > http://www.nabble.com/file/p24825646/camel-problem-pojo-messaging.zip > camel-problem-pojo-messaging.zip thing: > In the sample camel-example-pojo-messaging the @Consume(uri = > "file:src/data?noop=true") should be changed to @Consume(uri = > "file:src/data?noop=true&readLock=none") because otherwise the user has to > delete the lock files in the src/data directory after each run, otherwise > the files will not be read in subsequent runs. > > Cheers, > Andi > -- > View this message in context: > http://www.nabble.com/Camel-Spring-Remoting-throwing-RuntimeException-question-tp24825646p24825646.html > Sent from the Camel - Users mailing list archive at Nabble.com. > > -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
