You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Hiranya Jayathilaka (JIRA)" <ji...@apache.org> on 2010/05/24 15:28:40 UTC
[jira] Updated: (AXIS2-4723) Make it Possible to Configure the TCP
Transport at Service Level
[ https://issues.apache.org/jira/browse/AXIS2-4723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiranya Jayathilaka updated AXIS2-4723:
---------------------------------------
Attachment: AXIS2-4723.patch
First cut version of the patch. Feedback is much appreciated.
Summary:
* Introduced the TCPTransportListener extending AbstractTransportListenerEx
* Introduced TCPEndpoint
* Introduced TCPOutTransportInfo to handle request-response scenarios
* More configuration options to the tcp listener (backlog and content type are now configurable)
> Make it Possible to Configure the TCP Transport at Service Level
> ----------------------------------------------------------------
>
> Key: AXIS2-4723
> URL: https://issues.apache.org/jira/browse/AXIS2-4723
> Project: Axis2
> Issue Type: Improvement
> Components: transports
> Affects Versions: 1.5
> Reporter: Hiranya Jayathilaka
> Fix For: 1.6
>
> Attachments: AXIS2-4723.patch
>
>
> Currently the TCP transport can only be configured in the axis2.xml (globally). It would be nice to be able to configure the transport at service level. We can do this by using the Axis2TransportListenerEx API. (I will soon attach a patch)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org