Hello,
Forwarding to mailing list as it contains the definite answer.
Thanks Daniel.
Didn't have time yet, will try to update wiki.
Pegards
Philippe
-- Forwarded message --
From: *Daniel Kulp*
Date: Wednesday, May 8, 2013
Subject: What is the proper way of setting client Timeout
of setting client Timeout per
Webservice method ?
To: Philippe Mouawad pmoua...@apache.org
On May 8, 2013, at 1:40 AM, Philippe Mouawad pmoua...@apache.org wrote:
Hello Daniel,
Thanks for this.
Regarding mu question on timeout I wanted to know if I was issing something
in your proposed solution
Hello,
Any update on this ?
If we want to contribute some docs patches, what is the way for it ? I
don't see docs in source code of project. I've read this
http://cxf.apache.org/getting-involved.html.
Thanks
Regards
Philippe
On Mon, May 6, 2013 at 6:53 PM, Philippe Mouawad
I think the only way to do it right now is to create a specific
HTTPClientPolicy object for your operation and do something like;
((BindingProvider)proxy).getRequestContext().put(HTTPClientPolicy.class.getName(),
policy);
The conduit should pick that up and intersect it with anything
Hello Daniel
Many thanks for clarifications but what I don't understand is how this one
would not impact other methods of Webservice.
- ((BindingProvider)proxy)
getRequestContext().put(HTTPClientPolicy.class.getName(), policy);
I made a little test and it seems the second operation
On May 6, 2013, at 10:48 AM, Philippe Mouawad pmoua...@apache.org wrote:
Hello Daniel
Many thanks for clarifications but what I don't understand is how this one
would not impact other methods of Webservice.
- ((BindingProvider)proxy)
Thanks Daniel,
That fixes the concurrent access but In my understanding and tests it does
not allow setting a different timeout depending on method, right ?
Maybe I am not clear enought, here is the call sequence I have where I want
a timeout of 3 secondes for getCustomersByName and default one
Thanks Jason,
But my requirement is to have a different client timeout per operation, so
setting it with A wildcard on conduit won't do it.
Regards
Philippe
On Saturday, May 4, 2013, Jason Pell wrote:
You should define a http conduit and you can use a wild card in the id of
the conduit to
ok well yea not sure what you can do other than your interceptor idea then.
On Sat, May 4, 2013 at 4:58 PM, Philippe Mouawad pmoua...@apache.orgwrote:
Thanks Jason,
But my requirement is to have a different client timeout per operation, so
setting it with A wildcard on conduit won't do it.
Hello,
I am working on the right way to configure Client Timeout on client side
and I am kind of confused by what I read:
-
http://cxf.547215.n5.nabble.com/Setting-Http-conduit-using-spring-configuration-file-td2644363.html
- https://issues.apache.org/jira/browse/CXF-3011
-
You should define a http conduit and you can use a wild card in the id of
the conduit to make sure it applies to your service.
To ensure it applies to every service you can set a name *.http-conduit
Because the config of the conduit will be applied at init time its ok no
issues with thread
11 matches
Mail list logo
