-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: 5.0.0 GA
-
Fix Version/s: 5.1.0 GA
-
Component/s: JBossESB
-
Labels:
-
Workaround Description:
-
Release Notes Text:
-
Release Notes Docs Status:Documented as Resolved Issue
If you set your config like this:
<action ... class="org.jboss.soa.esb.actions.soap.proxy.SOAPProxy">
...
<property name="http-client-properties">
<http-client-property name="http.method.retry-handler" value="com.foobar.MyRetryHandler"/>
</property>
or like this:
<action ... class="org.jboss.soa.esb.actions.soap.proxy.SOAPProxy">
...
<property name="file" value="http-client.properties"/>
http-client.properties:
http.method.retry-handler=com.foobar.MyRetryHandler
, your custom retry handler is not picked up. This is NOT a bug in SOAPProxy.
The bug is in both POSTHttpMethodFactory and GETHttpMethodFactory, where in the setConfiguration(ConfigTree):void method, the http-client-properties that are available in the passed-in ConfigTree are not set into the HttpMethod's HttpMethodParams.
What should happen is that ANY property that starts with "http.method." should be set into the HttpMethodParams.
- is blocked by
-
JBESB-3456 AbstractHttpMethodFactory should extract retry handler parameter in setConfiguration method
-
- Closed
-
-
JBESB-3467 Propagate http-client-property configuration to SOAPProxyWsdlLoader.newLoader
-
- Closed
-
- is related to
-
SOA-2171 http-client-properties not propagated to HttpMethodParams
-
- Closed
-