Forum Discussion

sirclaudio's avatar
sirclaudio
New Contributor
15 years ago

MTOM and soap 1.2 .net service -> Bad Request

I'm trying to invoke a .net web service with soap 1.2, WS-A and MTOM using SoapUI 3.5.1 and 3.6 open source, but the answer is always 400 - Bad Request. Looking at the exception thrown, .net is com...
sirclaudio's avatar
sirclaudio
New Contributor
15 years ago
I've downloaded soapui 4.0.0 source and changed a line in file com.eviware.soapui.impl.wsdl.submit.transports.http.support.attachments.AttachmentUtils:



line 382:

 public static String buildMTOMContentType( String header, String action, SoapVersion soapVersion )
 {
  int ix = header.indexOf( "boundary" );
  String contentType = "multipart/related; type=\"application/xop+xml\"; start=\"" + ROOTPART_SOAPUI_ORG + "\"; "
    + "start-info=\"" + soapVersion.getContentType();

  if( soapVersion == SoapVersion.Soap12 && action != null )
  {
   //contentType += "\"; action=\"" + action;
   contentType += "; action=\\\"" + action + "\\\"";
  }
  // nested or not? see
  // http://www.eviware.com/forums/index.php?topic=2866.new#new
  // contentType += "; action=\\\"" + action + "\\\"\"; action=\"" + action;

  return contentType + "\"; " + header.substring( ix );
 }


With this, root mime part is equal to the start-info tag, which is what the standard says, making invocations to .Net Mtom services successful