axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sagara Gunathunga (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AXIS2-5373) Provide an option to switch between HTTPClient3 and HTTPClient4
Date Mon, 23 Jul 2012 06:53:34 GMT

    [ https://issues.apache.org/jira/browse/AXIS2-5373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13420470#comment-13420470
] 

Sagara Gunathunga  commented on AXIS2-5373:
-------------------------------------------

Please note that this won't break any default behaviors, if you continue to use HTTPClient3
this improvement is not related to you. Also In case If you want to use HTTPClient4 in a multi-tenant
server environment you could use axis2.xml to set  HTTPClient4 based HTTPSender which work
for both Axis2 server and clients. This is just to provide a simple option to enable HTTPClient4
 to use with simple use cases not target all possible use cases. 

Also this is an improvement only specific to HTTP transport and no means for other transports
hence I don't thin introduce a new API is not wise thing to do here.    
                
> 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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


Mime
View raw message