You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "Robert Lazarski (Jira)" <ji...@apache.org> on 2026/01/24 23:50:00 UTC
[jira] [Resolved] (AXIS2C-1687) Support multipart soap in Axis2C engine
[ https://issues.apache.org/jira/browse/AXIS2C-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Lazarski resolved AXIS2C-1687.
-------------------------------------
Resolution: Implemented
Axis2/C already supports multipart SOAP through:
- MTOM (enabled via enableMTOM parameter in axis2.xml)
- SwA attachments
- MIME multipart handling in HTTP transport
Why this is confusing:
1. Vague request: The description is a single sentence with no
specifics about:
- What exact functionality is missing
- What use case requires this
- What error or limitation they encountered
2. "Multipart SOAP" is ambiguous - Could refer to:
- MTOM (Message Transmission Optimization Mechanism) - Already
supported in Axis2/C
- SwA (SOAP with Attachments) - Already supported in Axis2/C
- MIME multipart HTTP - Already supported by HTTP transport
> Support multipart soap in Axis2C engine
> ---------------------------------------
>
> Key: AXIS2C-1687
> URL: https://issues.apache.org/jira/browse/AXIS2C-1687
> Project: Axis2-C
> Issue Type: Bug
> Components: core/engine
> Reporter: Rafael Bronzeri
> Priority: Major
>
> Support multipart soap in Axis2C engine.
> Make possible to generates a multipart SOAP envelop payload.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: c-dev-help@axis.apache.org