Topic
  • 2 replies
  • Latest Post - ‏2013-08-15T17:54:14Z by JagadishVemugunta
JagadishVemugunta
JagadishVemugunta
37 Posts

Pinned topic Incorrect content-type while using mtom.xsl

‏2013-08-15T02:29:23Z |

Inbound - SAOP message with base-64 encoded

 

Outbound - MTOM to the backend service
 
Simple request rule using store:///mtom.xsl  ( The content-Type on the outbound is going as multipart/related; boundary="b54e9d9d-2675-4fdc-b1e1-c4babf6726fb"; type="text/xml") .

The MTOM specs expects the message to be multipart/related; boundary="b54e9d9d-2675-4fdc-b1e1-c4babf6726fb"; start-info="application/soap+xml"; type="application/xop+xml

 

Am I doing anything wrong, Please advise.

thanks,Jagadish

 

  • HermannSW
    HermannSW
    6065 Posts

    Re: Incorrect content-type while using mtom.xsl

    ‏2013-08-15T17:49:54Z  

    Does your mtom.xsl transform action output to OUTPUT directly?

    If not, please remove a results action and directly output to OUTPUT.

    If that does not help, please raise a PMR and refer to the "MUST" passages in the MTOM spec here:
    http://www.w3.org/TR/soap12-mtom/#mime-serialization
     

    Hermann.

  • JagadishVemugunta
    JagadishVemugunta
    37 Posts

    Re: Incorrect content-type while using mtom.xsl

    ‏2013-08-15T17:54:14Z  
    • HermannSW
    • ‏2013-08-15T17:49:54Z

    Does your mtom.xsl transform action output to OUTPUT directly?

    If not, please remove a results action and directly output to OUTPUT.

    If that does not help, please raise a PMR and refer to the "MUST" passages in the MTOM spec here:
    http://www.w3.org/TR/soap12-mtom/#mime-serialization
     

    Hermann.

    I have raised the PMR. The transform action of mtom.xsl has output as "OUTPUT". I don't have results action.