You are viewing a plain text version of this content. The canonical link for it is here.

Posted to java-dev@axis.apache.org by "Deepal Jayasinghe (JIRA)" <ji...@apache.org> on 2009/06/13 02:09:08 UTC

[jira] Resolved: (AXIS2-2813) [Performance] set enableMTOM flag for RPCMessageReceivers.

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

Deepal Jayasinghe resolved AXIS2-2813.
--------------------------------------

    Resolution: Fixed

> [Performance] set enableMTOM flag for RPCMessageReceivers.
> ----------------------------------------------------------
>
>                 Key: AXIS2-2813
>                 URL: https://issues.apache.org/jira/browse/AXIS2-2813
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Improvement
>            Reporter: Davanum Srinivas
>            Assignee: Deepal Jayasinghe
>
> Please see AXIS2-2743 for additional information, Suppose enableMTOM is switched on the repo's axis2.xml but the actual service itself does not do any MTOM, we still take a penalty hit of serializing twice once into a string and then the actual stream. Not sure how to handle this situation. Should RPCMessageReceiver somehow signal the transport sender that this service does not do MTOM/Swa?
> thanks,
> dims 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.