• BizTalk Exception: Calling web services with Mixed OneWay and SolicitResponse Operations


    BizTalk Exception: Calling web services with Mixed One-Way and Solicit-Response Operations

     


    There was a failure executing the response(receive) pipeline:

     "Microsoft.BizTalk.DefaultPipelines.XMLReceive, Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "XML disassembler"

    Send Port:

    "ShippingMessageProcess_1.0.0.0_ShippingMessageProcess.ShippingMessageOrch_Port_ShippingWebServices_769f78805327fa55"

    URI: "http://swsmis009/ShippingWebServicesApp/ShippingWebServicesApp.asmx"

    Reason: The body part is NULL.

     

    ***

    Generally, after deploying the project, a solicit-response send port will be created and bound to the orchestration. In this case, the above exception will occur when consuming the one-way web methods via a solicit-response physical web port.

     

    You have to split the web services into two pieces, one web service only contains one-way web methods, and another web service only contains two-way (request / response) web methods. Then you can create two different ports in your orchestration and bind them to two different physical send ports, one that is one-way and one that is two-way.

     

     

     

     

  • 相关阅读:
    小孩子要過來了
    生產相關流程記錄
    關于會議記錄
    打算開始了解smartClient
    陽新出貨掃描上線
    纸版相关流程了解记录
    2007年上半年團隊建設計划
    关于小家伙的教育问题
    股市感想
    最近是不是有些消極?
  • 原文地址:https://www.cnblogs.com/rickie/p/750666.html
Copyright © 2020-2023  润新知