Sagara Gunathunga created AXIS2-5373:
-----------------------------------------
Summary: Provide an option to switch between HTTPClient3 and
HTTPClient4
Key: AXIS2-5373
URL: https://issues.apache.org/jira/browse/AXIS2-5373
Project: Axis2
Issue Type: Improvement
Components: kernel, transports
Reporter: Sagara Gunathunga
Priority: Critical
Fix For: 1.7.0
HTTPClient4 based transport implementation is more or less completed now. At
the moment it's required to use axis2.xml to register
HTTPClient4TransportSender this seems acceptable solution in server side but in
client side this is not the ideal solution. It should possible to enable
HTTPClient4TransportSender programticlly without using axis2.xml file. Set
TransportSender as a property to the Option object is the ideal solution but
unfortunately default TransportSenders already have initialized when time of
Option object's properties processing.
Specify HTTPClient4TransportSender as a System property ( e.g-
HTTPTransportSenderClass ) and look that property value within the
AxisConfigBuilder can be a valid solution. Further this setting can be used in
server side too.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
