10:12 a.m.
http-client-properties not propagated to HttpMethodParams
---------------------------------------------------------
Key: JBESB-3378
URL: https://jira.jboss.org/browse/JBESB-3378
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Configuration, Rosetta, Transports
Affects Versions: 4.8
Reporter: David Ward
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:16 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-3378) http-client-properties not propagated to HttpMethodParams
[
https://jira.jboss.org/browse/JBESB-3378?page=com.atlassian.jira.plugin.s...
]
Kevin Conner updated JBESB-3378:
--------------------------------
Fix Version/s: 4.9 CP1
http-client-properties not propagated to HttpMethodParams
---------------------------------------------------------
Key: JBESB-3378
URL: https://jira.jboss.org/browse/JBESB-3378
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Configuration, Rosetta, Transports
Affects Versions: 4.8
Reporter: David Ward
Fix For: 4.9 CP1
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:18 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-3378) http-client-properties not propagated to HttpMethodParams
[
https://jira.jboss.org/browse/JBESB-3378?page=com.atlassian.jira.plugin.s...
]
Kevin Conner commented on JBESB-3378:
-------------------------------------
This needs to have a SOA issue created
http-client-properties not propagated to HttpMethodParams
---------------------------------------------------------
Key: JBESB-3378
URL: https://jira.jboss.org/browse/JBESB-3378
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Configuration, Rosetta, Transports
Affects Versions: 4.8
Reporter: David Ward
Fix For: 4.9 CP1
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:54 a.m.
New subject: [JBoss JIRA] Assigned: (JBESB-3378) http-client-properties not propagated to HttpMethodParams
[
https://jira.jboss.org/browse/JBESB-3378?page=com.atlassian.jira.plugin.s...
]
David Ward reassigned JBESB-3378:
---------------------------------
Assignee: David Ward
http-client-properties not propagated to HttpMethodParams
---------------------------------------------------------
Key: JBESB-3378
URL: https://jira.jboss.org/browse/JBESB-3378
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Configuration, Rosetta, Transports
Affects Versions: 4.8
Reporter: David Ward
Assignee: David Ward
Fix For: 4.9 CP1
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:58 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-3378) http-client-properties not propagated to HttpMethodParams
[
https://jira.jboss.org/browse/JBESB-3378?page=com.atlassian.jira.plugin.s...
]
Kevin Conner updated JBESB-3378:
--------------------------------
Issue Type: Feature Request (was: Bug)
Marking as a feature request for now
http-client-properties not propagated to HttpMethodParams
---------------------------------------------------------
Key: JBESB-3378
URL: https://jira.jboss.org/browse/JBESB-3378
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Configuration, Rosetta, Transports
Affects Versions: 4.8
Reporter: David Ward
Assignee: David Ward
Fix For: 4.9 CP1
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:58 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-3378) http-client-properties not propagated to HttpMethodParams
[
https://jira.jboss.org/browse/JBESB-3378?page=com.atlassian.jira.plugin.s...
]
Kevin Conner commented on JBESB-3378:
-------------------------------------
I don't believe this functionality has existed prior to now, why is this marked as a
bug?
The configuration for HttpClient has been done through 'Configurator' classes and
we do not have any which automatically pull properties across.
http-client-properties not propagated to HttpMethodParams
---------------------------------------------------------
Key: JBESB-3378
URL: https://jira.jboss.org/browse/JBESB-3378
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Configuration, Rosetta, Transports
Affects Versions: 4.8
Reporter: David Ward
Assignee: David Ward
Fix For: 4.9 CP1
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:13 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-3378) http-client-properties not propagated to HttpMethodParams
[
https://jira.jboss.org/browse/JBESB-3378?page=com.atlassian.jira.plugin.s...
]
Kevin Conner commented on JBESB-3378:
-------------------------------------
It looks like the AbstractHttpMethodFactory.java added the ability to set the retry
handler through the wrapRetryHandler method but did not add any mechanism by which
alternative can be configured.
The code does look at the parameters in the method but, as there has never been a
mechanism to propagate these, it could never have worked. It would always use the
default.
We need to introduce a new mechanism, similar to the Configurator for HttpClient.
http-client-properties not propagated to HttpMethodParams
---------------------------------------------------------
Key: JBESB-3378
URL: https://jira.jboss.org/browse/JBESB-3378
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Configuration, Rosetta, Transports
Affects Versions: 4.8
Reporter: David Ward
Assignee: David Ward
Fix For: 4.9 CP1
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:20 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-3378) http-client-properties not propagated to HttpMethodParams
[
https://jira.jboss.org/browse/JBESB-3378?page=com.atlassian.jira.plugin.s...
]
Kevin Conner commented on JBESB-3378:
-------------------------------------
Alternatively, the simpler solution is to fix the setConfiguration so that it pulls out
the property and then the wrapRetryHandler can use that rather than existing method
parameters.
http-client-properties not propagated to HttpMethodParams
---------------------------------------------------------
Key: JBESB-3378
URL: https://jira.jboss.org/browse/JBESB-3378
Project: JBoss ESB
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Configuration, Rosetta, Transports
Affects Versions: 4.8
Reporter: David Ward
Assignee: David Ward
Fix For: 4.9 CP1
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:22 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-3378) http-client-properties not propagated to HttpMethodParams
[
https://jira.jboss.org/browse/JBESB-3378?page=com.atlassian.jira.plugin.s...
]
Kevin Conner updated JBESB-3378:
--------------------------------
Issue Type: Bug (was: Feature Request)
The bug is that setConfiguration should exist in the AbstractHttpMethodFactory (it is
currently called setconfiguration) and that the retry handler property should be extracted
and used within wrapRetryHandler. This method will also need to be invoked by the
subclasses.
Adding further configuration is not appropriate at this time.
http-client-properties not propagated to HttpMethodParams
---------------------------------------------------------
Key: JBESB-3378
URL: https://jira.jboss.org/browse/JBESB-3378
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Configuration, Rosetta, Transports
Affects Versions: 4.8
Reporter: David Ward
Assignee: David Ward
Fix For: 4.9 CP1
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:26 a.m.
New subject: [JBoss JIRA] Updated: (JBESB-3378) AbstractHttpMethodFactory should extract retry handler parameter in setConfiguration method
[
https://jira.jboss.org/browse/JBESB-3378?page=com.atlassian.jira.plugin.s...
]
Kevin Conner updated JBESB-3378:
--------------------------------
Summary: AbstractHttpMethodFactory should extract retry handler parameter in
setConfiguration method (was: http-client-properties not propagated to HttpMethodParams)
AbstractHttpMethodFactory should extract retry handler parameter in
setConfiguration method
-------------------------------------------------------------------------------------------
Key: JBESB-3378
URL: https://jira.jboss.org/browse/JBESB-3378
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Configuration, Rosetta, Transports
Affects Versions: 4.8
Reporter: David Ward
Assignee: David Ward
Fix For: 4.9 CP1
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:28 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBESB-3378) AbstractHttpMethodFactory should extract retry handler parameter in setConfiguration method
[
https://jira.jboss.org/browse/JBESB-3378?page=com.atlassian.jira.plugin.s...
]
Kevin Conner edited comment on JBESB-3378 at 8/3/10 7:27 AM:
-------------------------------------------------------------
The bug is that the retry handler property should be extracted within setConfiguration and
used within wrapRetryHandler. This method will also need to be invoked by the
subclasses.
Adding further configuration is not appropriate at this time.
was (Author: kevin.conner(a)jboss.com):
The bug is that setConfiguration should exist in the AbstractHttpMethodFactory (it is
currently called setconfiguration) and that the retry handler property should be extracted
and used within wrapRetryHandler. This method will also need to be invoked by the
subclasses.
Adding further configuration is not appropriate at this time.
AbstractHttpMethodFactory should extract retry handler parameter in
setConfiguration method
-------------------------------------------------------------------------------------------
Key: JBESB-3378
URL: https://jira.jboss.org/browse/JBESB-3378
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Configuration, Rosetta, Transports
Affects Versions: 4.8
Reporter: David Ward
Assignee: David Ward
Fix For: 4.9 CP1
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:28 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-3378) AbstractHttpMethodFactory should extract retry handler parameter in setConfiguration method
[
https://jira.jboss.org/browse/JBESB-3378?page=com.atlassian.jira.plugin.s...
]
Kevin Conner commented on JBESB-3378:
-------------------------------------
Sorry, it appears that eclipse is playing games with me as setConfiguration does exist.
Presumably I hit some magic key combination to change the method name to lower case while
investigating. My bad.
AbstractHttpMethodFactory should extract retry handler parameter in
setConfiguration method
-------------------------------------------------------------------------------------------
Key: JBESB-3378
URL: https://jira.jboss.org/browse/JBESB-3378
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Configuration, Rosetta, Transports
Affects Versions: 4.8
Reporter: David Ward
Assignee: David Ward
Fix For: 4.9 CP1
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:48 a.m.
New subject: [JBoss JIRA] Commented: (JBESB-3378) AbstractHttpMethodFactory should extract retry handler parameter in setConfiguration method
[
https://jira.jboss.org/browse/JBESB-3378?page=com.atlassian.jira.plugin.s...
]
Kevin Conner commented on JBESB-3378:
-------------------------------------
Reading further into this would suggest that the ability to configure the retry handler
was never intended in the first place. The code in AbstractHttpMethodFactory just wraps
the class created in DefaultHttpParamsFactory.
AbstractHttpMethodFactory should extract retry handler parameter in
setConfiguration method
-------------------------------------------------------------------------------------------
Key: JBESB-3378
URL: https://jira.jboss.org/browse/JBESB-3378
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Configuration, Rosetta, Transports
Affects Versions: 4.8
Reporter: David Ward
Assignee: David Ward
Fix For: 4.9 CP1
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:11 a.m.
New subject: [JBoss JIRA] Assigned: (JBESB-3378) AbstractHttpMethodFactory should extract retry handler parameter in setConfiguration method
[
https://jira.jboss.org/browse/JBESB-3378?page=com.atlassian.jira.plugin.s...
]
Kevin Conner reassigned JBESB-3378:
-----------------------------------
Assignee: Kevin Conner (was: David Ward)
AbstractHttpMethodFactory should extract retry handler parameter in
setConfiguration method
-------------------------------------------------------------------------------------------
Key: JBESB-3378
URL: https://jira.jboss.org/browse/JBESB-3378
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Configuration, Rosetta, Transports
Affects Versions: 4.8
Reporter: David Ward
Assignee: Kevin Conner
Fix For: 4.9 CP1
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:44 a.m.
New subject: [JBoss JIRA] Closed: (JBESB-3378) AbstractHttpMethodFactory should extract retry handler parameter in setConfiguration method
[
https://jira.jboss.org/browse/JBESB-3378?page=com.atlassian.jira.plugin.s...
]
Kevin Conner closed JBESB-3378.
-------------------------------
Resolution: Done
Updated in revision 34813.
AbstractHttpMethodFactory should extract retry handler parameter in
setConfiguration method
-------------------------------------------------------------------------------------------
Key: JBESB-3378
URL: https://jira.jboss.org/browse/JBESB-3378
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Configuration, Rosetta, Transports
Affects Versions: 4.8
Reporter: David Ward
Assignee: Kevin Conner
Fix For: 4.9 CP1
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5714
days inactive
5742
days old
14 comments
2 participants
participants (2)
-
David Ward (JIRA) -
Kevin Conner (JIRA)