If you can build the soap request by yourself, you can just use camel-http
component to send a request without using a client.
Otherwise you can wsdl2java (from CXF) to generate a client for you.
You can find some example here[1]
[1]http://camel.apache.org/cxf.html
--
Willem Jiang
Red Hat,
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
Thanks Kraythe! It worked.
On Tue, Dec 24, 2013 at 3:20 AM, kraythe . wrote:
> Ewww... I hate spring xml DSL (fluent Java or Scala is much better) ..
> anyway after my eyes are done bleeding ... it seems like you are wrapping
> the "possible failure" calls in a doTry/catch. Since you are handli
I fixed CAMEL-5958 in my own repo on GitHub
(https://github.com/lburgazzoli/camel)
I would greatly appreciate any feedback before to open a pull request.
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-bindy-bindy-ignore-bean-class-type-tp5725275p5745206.html
Sent from
We are seeing a transient exception while deserializing date objects. The
exception doesn't present itself if the tracer is on. The messages that hit
the DLC are able to be pushed back through with no issue. I know the mapper
is supposed to be thread safe but I'm not entirely sure it is. The proble