[
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-update5.patch
Fixed the problems in the transport sender:
* For messages sent to target EPRs, the output socket is stored in the message
context and closed in the cleanup method of the transport sender
* When processing responses, the message is no longer buffered in memory (the
input stream of the socket is directly handed to the parser)
> 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-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.
-
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]
