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

Andreas Veithen moved TRANSPORTS-8 to AXIS2-5530:
-------------------------------------------------

      Component/s:     (was: TCP)
                   TCP
    Fix Version/s:     (was: 1.7.0)
                   1.7.0
              Key: AXIS2-5530  (was: TRANSPORTS-8)
          Project: Axis2  (was: Axis2 Transports)
    
> Use MessageFormatter Interface in the TCPTransportSender
> --------------------------------------------------------
>
>                 Key: AXIS2-5530
>                 URL: https://issues.apache.org/jira/browse/AXIS2-5530
>             Project: Axis2
>          Issue Type: Improvement
>          Components: TCP
>            Reporter: Hiranya Jayathilaka
>             Fix For: 1.7.0
>
>         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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org

Reply via email to