|
Home > Archive > BizTalk Server General > October 2005 > How to handle multiple response message types on a Send-Receive port?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
How to handle multiple response message types on a Send-Receive port?
|
|
| SumYungBizTalker 2005-10-03, 6:01 pm |
| Hello!
I have an orchestration that uses a two-way (request-response) port pattern,
with a direction of Send-Receive, i.e. I send a message and wait for a
response message. If it matters, physically, this is an HTTP port. Problem:
the response message could match one of several schemas, all of which,
conceptually, would be considered "positive" or non-error messages. In the
orchestration designer, I can, of course, only specify one message type
(i.e. schema) for the response message. Other than typing the response
message on the port agnostically (i.e. XmlDocument or String), is there
another way to handle this? I've considered using inbound maps to transform
all the possible response message schemas to a common schema, and then set
that common type as the response message, but that isn't ideal. Is it
possible to set a single Request message type, but have multitple possible
Response message types in a scenario like this?
Thanks
| |
| Jan Eliasen 2005-10-04, 2:49 am |
| On Mon, 3 Oct 2005 10:59:56 -0700, "SumYungBizTalker"
<nomail@noserver.com> wrote:
>I have an orchestration that uses a two-way (request-response) port pattern,
>with a direction of Send-Receive, i.e. I send a message and wait for a
>response message. If it matters, physically, this is an HTTP port. Problem:
>the response message could match one of several schemas, all of which,
>conceptually, would be considered "positive" or non-error messages. In the
>orchestration designer, I can, of course, only specify one message type
>(i.e. schema) for the response message. Other than typing the response
>message on the port agnostically (i.e. XmlDocument or String), is there
>another way to handle this? I've considered using inbound maps to transform
>all the possible response message schemas to a common schema, and then set
>that common type as the response message, but that isn't ideal. Is it
>possible to set a single Request message type, but have multitple possible
>Response message types in a scenario like this?
This is not tested:
Let your receive-shape receive a document of the type
System.Xml.XmlDocument
Then, do a decide-shape, that will put the receive message into the
correct message you have defined,. Use the BTS.MessageType property on
the incoming document to do that.
Hope this works.
--
Jan Eliasen, representing himself and not the company he works for.
|
|
|
|
|