直接绑定端口的相关性 [英] Correlation on direct bound ports

问题描述

下面是使用直接绑定在Orch和一组单独的发送端口之间尝试消息传递的示例设计：

Below is the design of a sample to try out messaging between Orch and a separate set of send ports using direct binding:

模式作为Web服务公开。

A schema is exposed as a web service.

业务流程有一个接收端口来接受Web服务请求并发回响应。业务流程中的

An orchestration has a receive port to accept the web service request and send response back.

，在收到请求后，将应用地图，并使用发送端口将不同类型的新消息发送到msgbox。此示例中的已发送消息是带有where子句的简单选择表操作。

in the orchestration, after receiving the request, a map is applied and the new message of a different type is sent to msgbox using a send port. The sent message in this sample is a simple select table operation with a where clause.

单独的双向发送端口需要订阅此选择 表 操作消息类型并使用针对数据库的WCF SQL适配器运行查询，获取结果作为选择响应。

A separate two way Send port needs to subscribe to this Select table op Message type and run the query using a WCF SQL adapter against a db, get the results back as a Select Response.

现在回到业务流程，直接绑定接收端口需要订阅上述发送端口的Select Response。

此响应现在将映射到响应消息类型，并在Web服务的接收端口的响应中发回。

This response will now be mapped to the response message type and sent back in the response of the Receive port of the Web service.

我无法分别在发送和接收时使用初始化和跟随关联来实现上面突出显示的粗体（尝试设置属性，如
< span style ="text-decoration：underline"> https://stackoverflow.com/questions/4850529/correlation-on-messagebox-direct-bound-ports ）。我知道这可以通过合作伙伴业务流程端口或仅使用消息传递来实现。但是这里的目标是
，以便使用直接绑定在业务流程和端口之间实现相同的目标。

I have been unable to use initializing and following correlations at send and receive respectively to achieve the highlighted above in bold (tried to set properties as in https://stackoverflow.com/questions/4850529/correlation-on-messagebox-direct-bound-ports) . I understand this can be achieved using partner orchestration ports or with messaging only  but the goal here is to achieve the same between orchestrations and ports using direct binding.

感谢任何输入。

 

推荐答案

当您使用diorect绑定端口时，当您从直接绑定端口发布消息时，您还需要提升同一组属性，然后主编排将收到消息。

Well when you are using diorect bound port, you also need to promote the same set of properties when you publish the messages from the direct bound port then the main orchestration will recieve the message.

您需要的是 

What you need is 

1）动态发送端口应发回一条响应消息，该消息的类型与业务流程向此发送端口发送的消息类型不同。 

1) The dynamic send port should send back a response message which is of different message type than the one sent by the orchestration to this send port. 

2）在动态发送端口上，您需要在发送到直接绑定发送端口的消息中最初提升的属性。因此，创建一个管道组件并将这些属性提升到发送端口
将发布回消息框的消息上下文。

2) ON you dynamic send port you need to promotoe the properties that were initially promoted in the message sent to the direct bound send port . SO create a pipeline component and promote those properties to the context of the message that the send port will publish back to the message box.

但是我想问一下，为什么呢你想使用直接绑定端口和发送端口没有绑定到任何业务流程（甚至是双向直接绑定端口）？将WCF端口直接附加到业务流程的问题是什么，它将为您节省大量的资金。工作
，因为业务流程将自动收回消息。

But I want to ask, why do you want to use a direct bound port and send port not bound to any orchestration (even a two way direct bound port)? what is the issue with attaching the WCF port directly to the orchestration, it will save you lot of  work as orchestration will automatically get the messages back.

这篇关于直接绑定端口的相关性的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！