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 "Ralf Hauser (JIRA)" <ji...@apache.org> on 2018/09/11 14:42:00 UTC

[jira] [Created] (AXIS2-5931) AxisFault: A message with content type application/xop+xml can only appear in a MIME multipart message

Ralf Hauser created AXIS2-5931:
----------------------------------

             Summary: AxisFault: A message with content type application/xop+xml can only appear in a MIME multipart message
                 Key: AXIS2-5931
                 URL: https://issues.apache.org/jira/browse/AXIS2-5931
             Project: Axis2
          Issue Type: Improvement
          Components: transports
    Affects Versions: 1.7.8
            Reporter: Ralf Hauser


We are just about to upgrade our axis client from v1.6.2 to v1.7.8 ,but we get

 

<<org.apache.axis2.AxisFault: A message with content type application/xop+xml can only appear in a MIME multipart message
    at org.apache.axis2.builder.MTOMBuilder.processDocument(MTOMBuilder.java:40)
    at org.apache.axis2.transport.TransportUtils.createDocumentElement(TransportUtils.java:203)
    at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:144)
    at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:107)
    at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:66)
    at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:347)>>

 

The third party server side is unchanged.

MTOM is not globally activated on the client-side, but we use

 

            options.setProperty(
                    org.apache.axis2.Constants.Configuration.ENABLE_MTOM,
                    org.apache.axis2.Constants.VALUE_TRUE);

With 2-1.6.2. this was always set.

 

The server offers multiple stubs and even on stubs that do not need MTOM if omit setting ENABLE_MTOM, this happens.

 

Adding:

myConfigContext.getAxisConfiguration().addParameter(org.apache.axis2.Constants.Configuration.USE_DEFAULT_FALLBACK_BUILDER, "true");

 

doesn't help either.

 

Please document in

[MTOMBuilder|eclipse-javadoc:%E2%98%82=%20/%3C%7BMTOMBuilder.java%E2%98%83MTOMBuilder]{color:#000000}.processDocument({color}[InputStream|eclipse-javadoc:%E2%98%82=%20/%3C%7BMTOMBuilder.java%E2%98%83MTOMBuilder~processDocument~QInputStream;~QString;~QMessageContext;%E2%98%82InputStream]{color:#000000} inputStream, {color}[String|eclipse-javadoc:%E2%98%82=%20/%3C%7BMTOMBuilder.java%E2%98%83MTOMBuilder~processDocument~QInputStream;~QString;~QMessageContext;%E2%98%82String]{color:#000000}contentType, {color}[MessageContext|eclipse-javadoc:%E2%98%82=%20/%3C%7BMTOMBuilder.java%E2%98%83MTOMBuilder~processDocument~QInputStream;~QString;~QMessageContext;%E2%98%82MessageContext]{color:#000000} messageContext)  {color}

that always throws this exception, how this can be avoided to ensure backward compatibility

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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