gt; An: java-user@axis.apache.org
> Betreff: AW: Axis2 Service: No MTOM+XOP in response
>
> Hello Andreas,
>
> Thank you very much! This solved my problem.
>
> Best regards,
> Arndt
>
> Arndt F. Bonitz
> Department Safety & Security
>
> AIT Austri
xis2 Service: No MTOM+XOP in response
The response is actually not an MTOM message but a SwA message.
Probably you have enabled both. In that case SwA takes precedence over
MTOM because MTOM is simply an alternative serialization of an XML
message while SwA is a different type of message. In addi
The response is actually not an MTOM message but a SwA message.
Probably you have enabled both. In that case SwA takes precedence over
MTOM because MTOM is simply an alternative serialization of an XML
message while SwA is a different type of message. In addition, SwA
doesn't allow the SOAP stack t
nitz Arndt [mailto:arndt.bon...@ait.ac.at]
Sent: Thursday, November 17, 2011 7:47 AM
To: java-user@axis.apache.org
Subject: Axis2 Service: No MTOM+XOP in response
Dear all,
I am experiencing the following problem with an Axis2 service: Upon a
service request, my service should return a SOAP messa
Dear all,
I am experiencing the following problem with an Axis2 service: Upon a service
request, my service should return a SOAP message with an MTOM attachment. I
enabled XOP in the Axis2 configuaration. All messages are returned as
XOP+MTOM responses, but the attachment is encoded as Base64
