|
| There comes another critical problem, without orchestration, it is impossible
to use SOAP adapter in the send port, therefore, how can the web service call
executed?
"Tommy" wrote:
[vbcol=seagreen]
> Thanks, Doug. That is helpful. My question falls in the second requirement,
> which the orchestration will send requests to multiple subscribers at
> runtime.
> I figured out a solution based on your idea, I'd really appreciate any comment
>
> A. Create an orchestration that will consume the incoming message, use self
> correlated direct binding port to send the message back to the message box.
> The orchestration will also promote a flag into the message context
> indicating new message is ready.
>
> B. In runtime, each participated web service send port, subscribes to the
> particular message type with the ‘ready’ flag
>
> C. Each individual SOAP send port executes its corresponding web service and
> then in the receive pipeline, promote the CorrelationToken declared in stepA
>
> D. The orchestration in step A will get notified once the CorrelationToken
> is promoted and aggregate the messages afterwards.
>
>
> "Doug Girard [MSFT]" wrote:
>
|
|