可以从一个发送端口获取传递通知吗? [英] Possible to Get Delivery Notification from only one Send Port?

查看:63
本文介绍了可以从一个发送端口获取传递通知吗?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

以下是我们的情景。

1。业务流程具有带有DeliveryNotification的硬绑定发送端口 设置为'已发送'发布带有类型X的消息

1. Orchestration which has a Hard bound Send Port with DeliveryNotification set to 'Transmitted' publishing Message with Type X

2。另一个独立发送端口订阅类型X并执行它

2. Another Independent send port subscribing to Type X and doing it's bit

现在问题是当消息从Orchestration发布时它具有属性
AckRequired 设置为'True',因此两个发送端口(一个连接到Orchestration,一个独立订阅纯粹基于消息类型)正在将交付通知发布回到正在搞乱的业务流程,是
有可能只有绑定到Orchestration的Send Port Hard会生成此传递通知吗?因为我们只想了解这一点。

Now the problem is when the message is published from Orchestration it has the Property AckRequired set to 'True', so both send ports (one hooked up to Orchestration and one Independent one subscribing purely based on Message type) are publishing the Delivery Notification back to the Orchestration which is messing things up, is it possible that only the Send Port Hard bound to the Orchestration generate this delivery notification? as we only want to know about that.

谢谢

Syed

推荐答案

有点讨厌,但是你可以创建一个自定义管道组件,它将AckRequired重置为false并使用它独立SendPort中管道中的pipelinecomponent。

Somewhat nasty, but you could create a custom pipelinecomponent which resets the AckRequired to false and use this pipelinecomponent in a pipeline in the independent SendPort.

BTW:独立SendPort的目的是什么?是否可以更新业务流程以包含额外发送到独立SendPort?

BTW: what is the purpose of the independent SendPort? Is it possible to update the orchestration to include a additional Send to the independent SendPort?

问候,

René


这篇关于可以从一个发送端口获取传递通知吗?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆