[
https://issues.apache.org/jira/browse/TRANSPORTS-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen moved AXIS2-4723 to TRANSPORTS-38:
--------------------------------------------------
Fix Version/s: (was: 1.6.0)
1.6.0
Component/s: (was: transports)
TCP
Affects Version/s: (was: 1.5)
1.0.0
Key: TRANSPORTS-38 (was: AXIS2-4723)
Project: Axis2 Transports (was: Axis2)
> Make it Possible to Configure the TCP Transport at Service Level
> ----------------------------------------------------------------
>
> Key: TRANSPORTS-38
> URL: https://issues.apache.org/jira/browse/TRANSPORTS-38
> Project: Axis2 Transports
> Issue Type: Improvement
> Components: TCP
> Affects Versions: 1.0.0
> Reporter: Hiranya Jayathilaka
> Assignee: Andreas Veithen
> Fix For: 1.6.0
>
> Attachments: AXIS2-4723-docs.patch, AXIS2-4723-update1.patch,
> AXIS2-4723-update2.patch, AXIS2-4723-update3.patch, AXIS2-4723-update4.patch,
> AXIS2-4723-update5.patch, 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.
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]
