Must receive before sending a message whose messagetype corresponds to a requestresponse operation on an implemented port(Second approach)


The issue was due to two response sent against single request on reques07esponse port and for that I wrote a post : http://tech-findings.com/2015/02/must-receive-before-sending-message.html  but was curious to find if there is another way to do this and Deepak Sanghi commented on the link which I shared  on LinkedIn , about the another approach to handle this scenario.


It made sense, and I 07ied it. Below is the modified orches07ation


Changes  done as below:

1.   Receive Input Message
2.   Transform to destination format
3.   Send 07ansformed message to destination system
4.   Cons07uct positive response message (but not sent)
5.   If an exception occurs in above steps then catch it in Exception Handler
6.   Cons07uct negative response message  including exception message (but not sent)
7.   The last thing is to place a send shape which sends response

So depending upon the scenario either of the positive response or negative response will be created but wouldn't be sent immediately instead it is sent at last after evaluating the exception.




Related Post:



    Must receive before sending a message whose messagetype corresponds to a reques07esponse operation on an implemented port (First approach)

ServerLess360


Comments

Popular posts from this blog

The request has both SAS authentication scheme and 'Bearer' authorization scheme. Only one scheme should be used

Getting Started with Logic Apps - AS2

How to Debug and Trace request in Azure APIM - Portal, Postman, RequestBin