axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Veithen (JIRA)" <>
Subject [jira] [Updated] (AXIS2-5373) Provide an option to switch between HTTPClient3 and HTTPClient4
Date Sun, 24 Jan 2016 15:34:41 GMT


Andreas Veithen updated AXIS2-5373:
    Fix Version/s:     (was: 1.7.0)

> Provide an option to switch between HTTPClient3 and HTTPClient4
> ---------------------------------------------------------------
>                 Key: AXIS2-5373
>                 URL:
>             Project: Axis2
>          Issue Type: Improvement
>          Components: kernel, transports
>            Reporter: Sagara Gunathunga 
>            Assignee: Sagara Gunathunga 
>            Priority: Critical
>             Fix For: 1.7.1
> 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 was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message