Help Desk Ticket Reference: https://access.redhat.com/issue-tracker/?module=issues&action=view&tid=1148953&gid=1354 Workaround Description: There is no known workaround. project_key: SOA 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.
Link: Added: This issue depends JBESB-3456
Link: Added: This issue is related to SOA-2171
Link: Added: This issue is incorporated by SOA-2210
It is nor possible to set any property starting with 'http.method.' in HttpMethodParams without writing explicit code to do so. This task will modify AbstractHttpMethodFactory to correctly extract the parameter and instantiate the handler.
(not possible)
The retry handler is configured by specifying the org.jboss.soa.esb.actions.routing.http.routingHandler parameter on the action. The value of this parameter must be the name of a class which - implements HttpMethodRetryHandler - has a public, no-arg constructor - *may* implement Configurable
RemoteWsdlLoader is now fixed.
Reopening to fix SOAPProxy propagation
Link: Added: This issue depends JBESB-3467
Temporarily reopening to update release note info.
Release Notes Docs Status: Added: Documented as Resolved Issue Release Notes Text: Added: https://issues.jboss.org/browse/SOA-2224 If the configuration was set in certain ways, the custom retry handler was not picked up. This was due to a bug in both POSTHttpMethodFactory and GETHttpMethodFactory, whereby the setConfiguration(ConfigTree):void method was not set in the HttpMethod's HttpMethodParams. A task has been added to AbstractHttpMethodFactory to correctly extract the parameter and instantiate the handler.
Release Notes Text: Removed: https://issues.jboss.org/browse/SOA-2224 If the configuration was set in certain ways, the custom retry handler was not picked up. This was due to a bug in both POSTHttpMethodFactory and GETHttpMethodFactory, whereby the setConfiguration(ConfigTree):void method was not set in the HttpMethod's HttpMethodParams. A task has been added to AbstractHttpMethodFactory to correctly extract the parameter and instantiate the handler. Added: https://issues.jboss.org/browse/SOA-2224 If the configuration was set in certain ways, the custom retry handler was not picked up. This was due to a bug in both POSTHttpMethodFactory and GETHttpMethodFactory, whereby the setConfiguration(ConfigTree):void method was not set in the HttpMethod's HttpMethodParams. A task has been added to AbstractHttpMethodFactory to correctly extract the parameter and instantiate the handler. Note that the retry handler is configured by specifying the org.jboss.soa.esb.actions.routing.http.routingHandler parameter on the action. The value of this parameter must be the name of a class which implements HttpMethodRetryHandler and has a public, no-arg constructor.
Writer: Added: dlesage