[
https://issues.apache.org/jira/browse/AXIS2-4723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12873262#action_12873262
]
Hiranya Jayathilaka commented on AXIS2-4723:
--------------------------------------------
This bit of code was written in this manner to ensure that by the time the
socket is closed the response is fully read by the transport sender. Otherwise
the parser would throw exceptions when the socket is closed. If there is a way
to ensure this without buffering the response in memory, that would be great.
That will basically fix both aforementioned limitations.
> 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-update1.patch, AXIS2-4723-update2.patch,
> AXIS2-4723-update3.patch, AXIS2-4723-update4.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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
