You are viewing a plain text version of this content. The canonical link for it is here.
Posted to kandula-dev@ws.apache.org by "Andreas Veithen (JIRA)" <ji...@apache.org> on 2010/08/25 12:58:15 UTC
[jira] Moved: (TRANSPORTS-8) Use MessageFormatter Interface in the
TCPTransportSender
[ https://issues.apache.org/jira/browse/TRANSPORTS-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen moved AXIS2-4789 to TRANSPORTS-8:
-------------------------------------------------
Project: Axis2 Transports (was: Axis2)
Key: TRANSPORTS-8 (was: AXIS2-4789)
Component/s: TCP
(was: transports)
> Use MessageFormatter Interface in the TCPTransportSender
> --------------------------------------------------------
>
> Key: TRANSPORTS-8
> URL: https://issues.apache.org/jira/browse/TRANSPORTS-8
> Project: Axis2 Transports
> Issue Type: Improvement
> Components: TCP
> Reporter: Hiranya Jayathilaka
> Attachments: AXIS2-4789.patch
>
>
> AXIS2-4723 added the concept of content-types to the TCP transport. While the TCPTransportListener uses the message builder API when receiving messages, the sender does NOT use the message formatter API when writing messages out. This should be added to the transport sender. Other transport senders like UDP and JMS already use the message formatter API when serializing messages.
> I will send in a patch which implements this feature.
--
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