On Exception and OnRedeliver behavior

Hi ! I would like to have a single bean to process every errors and be able to choose inside this bean if the error is recoverable or not, and then if the message shall be redelivered or not. What i've done : http://camel.apache.org/schema/spring";> example.UnrecoverableE

Camel CXF and CXF.XML

Hi ! There is something i don't understand about camel and cxf. While trying to secure my camel cxf endpoints, I found and example using It need its attribute "bus" to be set, and if i make no mistake it have to be defined with that kind of bean usually found in a cxf.xml. But i don't under

One processor for multiple camelContext

Hi ! In my project there is a lot of communication by mail with attached zipped xml files. So i made two processor to zip the file, or unzip from a mail. My problem is that i have three differents bundles (three jar, three camelContext), all of them using those two processors. How can i make t

Re: recursion with Camel ?

Why don't you just make your processor call a recursive function ? A processor isn't made to be able to invoke another processor, you need to make it recursive with your route http://camel.apache.org/schema/spring";> $in.header.continue = 't

Re: One processor for multiple camelContext

Hi : Willem.Jiang wrote >> But how i can make this works : >> >> File2 : >> / > >> > >> > >> > > / >> > You need to make sure Camel can find out the bean test from the Spring > application context. Ok. But how is it possible ? -- View this message in context: http://camel.4654

Logging make my body empty...

Hi ! I'm trying to make a WS proxy with cxf, and there is somethings i do not understand. This route is ok, and i can see my soap message with wireshark, everythings is fine. http://10.67.119.44:9090/metierTest?throwExceptionOnFailure=false"/>

Re: How do I avoid using the dead letter queue using Camel?

Hi ! First : what's wrong with the DLQ ? I don't really understand what is your goal. Put it's maximumRedeliveries to -1 and it will always redeliver the message. Next, to prevent your message to go to the DLQ, you can catch your timeout exception and handle it. See http://camel.apache.org/exce

Re: How do I avoid using the dead letter queue using Camel?

Maybe you can configure your endpoints behavior. kiwi.mec wrote > What should happen is the producer thread should cleanly give up waiting > and hand the waiting game over to a janitor thread to process when the > message finally arrives If your producer just send the message and does not listen

How to use a cxf consumer in camel

Hi ! I'm currently unable to win against this error : /The PayLoad elements cannot fit with the message parts of the BindingOperation. Please check the BindingOperation and PayLoadMessage/ which come with this warning : / Cannot set right payload parameters. Please check the BindingOperation and P

Re: How to use a cxf consumer in camel

It's ok with the operationName, it works with this route : CreerOuModifierCargaisons and this message http://webservices.basemetier/";> a <...> ... f Thanks

Creating new processor components

Hi ! I'm trying to make a component from one of my processor. I followed this tutorial which does not includes informations about installation and use. Now my jar is here, i don't know where i have to put it, i tri

Re: Creating new processor components

Hi ! Claus Ibsen-2 wrote > For the component name, then make sure the > META-INF/services/org/apache/camel/component/helloworld file is > included in the JAR. And that it refers to the component class name. > > For example here is an example from camel-mybatis component: > https://svn.apache.org

Camel Properties override

Hi ! Just a quick question about properties. If I define two property files like this : classpath:test1.properties file:${karaf.home}/etc/test2.properties And test1 and test2 both define the /foo/property, am

Re: Calling WebService with Camel

What kind of problem ? And where ? I'm currently using cxf for ws consumer and producer, so i may be able to help you, but i can't post my whole project here. -- View this message in context: http://camel.465427.n5.nabble.com/Calling-WebService-with-Camel-tp5731026p5731027.html Sent from th

Re: Calling WebService with Camel

What about this ? http://camel.465427.n5.nabble.com/How-can-I-call-a-web-service-with-no-parameters-via-a-producerTemplate-td4806257.html -- View this message in context: http://camel.465427.n5.nabble.com/Calling-WebService-with-Camel-tp5731026p5731063.html Sent from the Camel - Users mailing

Re: How to set a custom ExceptionHandler to a consumer

from("netty:tcp:...").onException(MyEx).dosomethings.end().transform(constant("hello")); http://camel.apache.org/exception-clause.html -- View this message in context: http://camel.465427.n5.nabble.com/How-to-set-a-custom-ExceptionHandler-to-a-consumer-tp5731097p5731098.html Sent from the Cam

Re: 'fire and forge' from InOut exchange

Hi ! I'm not sure to understand what you mean brnzn1 wrote > and send the response message to the replyTo queue without waiting for > nonBlocking to complete. If 'nonBlocking' is not over, how can you have it's response ? Anyway I think you can do this : from("activemq:queue1").setExchang

Exchange and memory use

Hi ! I'm trying to find what is the best solution to manage temporary unavailable systems with my bus. A few exceptions I catch mean "try again later", so I used a dead letter queue with no representation limit. My question is : if I have a lots of messages waiting for the next representation, a

Exception list ?

Hi ! I'm trying to make my bus more robust, mostly against bad configuration / unavailable service. I use lots of http, cxf, file and mail (smtp) endpoints, but I'm not able to find any doc listings exceptions they can throw, and when. Does that kind of documentation exist ? and where ? Regard

TransactionnalDeadLetterChannel ?

Hi, My route read a file, parse the xml stuff inside, valid and transform it to finally write it somewhere else. My goal is : on any unhandled error, rollback and redeliver up to X times, every Y seconds and finally send the original file on another queue. Right now, i've defined a deadLetterCh