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

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

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

JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/AXIS2-5931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16627372#comment-16627372 ]

Ralf Hauser edited comment on AXIS2-5931 at 9/25/18 1:37 PM:
-------------------------------------------------------------

seems that the server is not compliant with

[https://wiki.apache.org/ws/FrontPage/Axis2/MTOM]

adding

serviceClient.getAxisConfiguration().addMessageBuilder("application/xop+xml", new SOAPBuilder());

seems to solve the problem (probably quite quick&dirty, but somehow as Axis2-1.6.2 did it before)

 


was (Author: [hidden email]):
seems that the server is not compliant with

[https://wiki.apache.org/ws/FrontPage/Axis2/MTOM]

adding

serviceClient.getAxisConfiguration().addMessageBuilder("application/xop+xml", new SOAPBuilder());

seems to solve the problem (probably quite quick&dirty, but somehow as Axis2-1.6.2 did it

 

> 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
>            Priority: Major
>
> 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.processDocument(InputStream inputStream, String contentType, MessageContext messageContext) throws AxisFault
> 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: [hidden email]
For additional commands, e-mail: [hidden email]