BizTalk 停止并清除所有规则触发

发布于 2024-09-12 14:14:03 字数 449 浏览 17 评论 0原文

以下是本质上的规则:

If the node does not exist then do not continue with the next rule.

If the node does exist then continue with the next rule.

这是通过设置规则的优先级,然后在对现有节点进行初始检查时停止并清除所有规则触发来完成的。

我已经在规则编辑器中进行了测试,并且第一条规则被触发。但是,这并不能阻止下一条规则的触发。它继续并失败,因为显然在 xml 中找不到该节点。

有没有人知道为什么即使该操作明确表示“停止并清除所有规则触发”,它仍会继续?

是否有某种 BizTalk - 重置主机实例,重新启动 Visual Studio 技巧?

我在另一条规则中做到了这一点,效果很好......

The following is essentially the rule:

If the node does not exist then do not continue with the next rule.

If the node does exist then continue with the next rule.

This is accomplished by setting the priority on the rules and then by Halt and clear all rule firings - on the initial check for nodes existing.

I've tested in the rule composer and the first rule is fired. However, this doesn't stop the next rule from firing. It continues and fails because obviously the node is not found in the xml.

Has anybody any ideas why it would continue even though the action specifically say's halt and clear all rule firings?

Is there some kind of BizTalk - reset the host instance, restart visual studio trick?

I've done this in another rule and it works fine...

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

记忆之渊 2024-09-19 14:14:03

看起来引擎好像同时运行了所有规则。我已经通过使用特定的 XPath 规则来解决这个问题。

It seems as though the engine runs all the rules at once. I've managed to get around the problem by using specific XPath for the rules.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文