axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiranya Jayathilaka (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AXIS2-4789) Use MessageFormatter Interface in the TCPTransportSender
Date Wed, 04 Aug 2010 04:50:15 GMT

     [ https://issues.apache.org/jira/browse/AXIS2-4789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Hiranya Jayathilaka updated AXIS2-4789:
---------------------------------------

    Attachment: AXIS2-4789.patch

Patch for the aforementioned improvement. I did not encounter any regressions when running
the tests.

> Use MessageFormatter Interface in the TCPTransportSender
> --------------------------------------------------------
>
>                 Key: AXIS2-4789
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4789
>             Project: Axis2
>          Issue Type: Improvement
>          Components: transports
>            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


Mime
View raw message