axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Veithen (JIRA)" <>
Subject [jira] [Reopened] (AXIS2-4602) JAX-WS MTOM issue
Date Sat, 23 Jun 2012 12:16:43 GMT


Andreas Veithen reopened AXIS2-4602:

This issue is not fixed. Note that AXIOM-420 provides a mechanism that could eventually be
used to solve this problem, but it can't be applied yet because JAXB2 produces XOP encoded
> JAX-WS MTOM issue
> -----------------
>                 Key: AXIS2-4602
>                 URL:
>             Project: Axis2
>          Issue Type: Bug
>          Components: jaxws
>            Reporter: Isuru Eranga Suriarachchi
>             Fix For: 1.7.0
>         Attachments: jaxws-mtom-fix.txt
> In Axis2 JAX-WS implementation, org.apache.axis2.jaxws.message.Block is extending OMDataSourceExt.
In the response messages of normal invocations, this object is kept inside the body of the
SOAPEnvelope and directly serialized without building the OMElement. In order to handle MTOM,
it uses the JAXBAttachmentMarshaller which writes data handler objects into the MTOMXMLStreamWriter.
> MTOM works fine as far as the return OMElement is not built and directly serialized using
the OMDataSource. But if the OMElement is built by some handler on the return path, JAXB Block
is written to a ByteArrayOutputStream and read as a ByteArray (through the getReader() method
of BlockImpl). Therefore, the OMElement which is built using this ByteArray, doesn't know
about MTOM. So, the response is given as base64 (inline).
> So even though the service is MTOM enabled, if some handler (Ex: Security) builds the
body element, the binary response data is transmitted as base64-encoded inline, instead of
as a separate binary attachment (see below - I remove most of the returned data due to its
> --MIMEBoundaryurn_uuid_6A41A9AB6F9E3EEAB71262792774662
> Content-Type: application/xop+xml; charset=UTF-8; type="text/xml"
> Content-Transfer-Encoding: binary
> Content-ID: <>
> <?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope xmlns:soapenv=""><soapenv:Body><dlwmin:getBinaryTestDataResponse
> --MIMEBoundaryurn_uuid_6A41A9AB6F9E3EEAB71262792774662-- 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message