Hi
Did you find a solution to this?
I would take a look at the spring ws documentation to find details
about timeout support.
Then its often a matter of having the camel-spring-ws component
configure that timeout option.
And if something is missing in camel-spring-ws, we can add that to the
component.
On Sat, Mar 30, 2013 at 2:50 PM, Smith-John <mich...@gmail.com> wrote:
> Hi,
>
> I wanted to create a camel route with which it is possible to invoke various
> SOAP-WebServices.
> I ended up with following:
>
> from("direct:Invoke").recipientList(this.header("WSAddress"));
>
> and
>
> Document response = template.requestBodyAndHeader("direct:Invoke", request,
> "WSAddress", "spring-ws:" + address.toString(), Document.class);
>
> For testing purpose I created a WS that needs about 5 minutes to response.
> Calling it directly with SoapUI I'm getting of course a
> /ERROR:java.net.SocketTimeoutException: Read timed out/.
> But with posted camel route there isn't a timeout.
>
> Now my question is how spring-ws component handles long running Web Services
> concerning timeouts for example? What's the mechanism? Async or sync?
> Callback? Or has spring-ws just a higher default timeout?
> It would be nice if someone could explain it to me.
>
> With kind regards.
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/spring-ws-timeout-question-tp5730111.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cib...@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
