WCF / Netweaver PI MTOM bug

Question

I believe we have found a bug in the sap soap adapter.  The bug occurs when we send a message with an attachment using MTOM encoding from a Microsoft WCF web service client.  The WCF client uses a URL Encoded href cid for xopInclude.  The problem is the content id for the attachment is not URL encoded.  When the mapping program runs and it attempts to map the attachment over to the inbound message it gives an exception because it thinks the attachment is null.  It doesn't seem to recognize that http%3A%2F%2Ftempuri.org%2F1%2F634505586330493745 and
http://tempuri.org/1/634505586330493745 are the same value.
attachment include in the message:
<xop:Include href="cid:http%3A%2F%2Ftempuri.org%2F1%2F634505586330493745" xmlns:xop="http://www.w3.org/2004/08/xop/include" />
content id for the attachment
Content-ID: <http://tempuri.org/1/634505586330493745>
The error in the mapping program is:
RuntimeException during appliction Java mapping com/sap/xi/tf/_ImportTrainingCertificateToImportClinicalSiteDocument_ Thrown: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Unexpected value <null> for node /ns0:ImportSitePersonnelTrainingCertificate/ns0:ImportTrainingCertificateRequest/ns0:TrainingCertificate/CertificateImage at com.sap.aii.mappingtool.tf7.Transformer.checkParserException(Transformer.java:172) at
I found this exact bug occurred in the JBoss application server as well and they have patched it:
https://issues.jboss.org/browse/JBPAPP-2098
Does anyone know if there is an existing patch for this issue from SAP?  We are on Netweaver 7.1, enhancement pack 1.
Thanks,
Kevin

Answer 1

Hi Kevin,
DId you ever get a solution to your problem?
Im sending a SOAP message to the Axis SOAP adapter with attachment ( from SOAP UI with MTOM enabled)  and I can see the attachment when i view the message in the runtime workbench.The future consumers of this service will also be sending the atatchment already MTOM'd.
However, I get a failled mapping with the same error as you mentioned.
I must mention that Im using integrated configuration, which means Java only (So no WS adapter ). Which also means (i think ) that the "Do not resolve XOP includes" in the operation mapping has no effect.
Regards
Adam