Generally an interoperability issue / problem.
As I do not yet know much about MTOM / SwA I know that a
.Net
WCF binding is a set of binding elements
binding elements have to be added to the binding in a given
order
One of the binding elements defines the required encoder
The encoder can be either of type
a) TextMessageEncodingBindingElement
b) BinaryMessageEncodingBindingElement
c) MtomMessageEncodingBindingElement
So there is no encoder for SwA.
To be 100% correct informed, I woulk suggest to ask
this question in the Microsoft MSDN WCF forum under
http://social.msdn.microsoft.com/Forums/en-US/wcf/
Josef
Von: Yashwanth Rajaram -X (yrajaram - ZENSAR TECHNOLOGIES INC at Cisco)
[mailto:yraja...@cisco.com]
Gesendet: Freitag, 13. Januar 2012 20:00
An: axis-u...@ws.apache.org
Betreff: MIMEBoundary after enabling MTOM
Hi All,
I have two questions on attachments in Axis2 - would appreciate any
thoughts/pointers/answers.
1. Until recently our Axis based service implementation was not
supporting attachments. We now enabled attachments support by enabling
MTOM/SwA in our service.xml. After this we see that whether our clients
send attachments or not they always get the response along with a new
MIME boundary header like the one below which seems to break their code
that was build earlier when we were not supporting attachments:
MIMEBoundaryurn_uuid_26DB12B4E6FE9133A11318962816779
Content-Type: text/xml; charset=UTF-8
Content-Transfer-Encoding: 8bit
Content-ID: <0.urn:uuid:26db12b4e6fe9133a11318962816...@apache.org>
How to support attachments without affecting our end clients?
2. We also gathered that Microsoft .Net clients cannot
communicate using SwA; so we were told that the only way attachments can
be supported by us is by using MTOM. Is this true?
thanks,
--
Yashwanth
