Xlang Engine中的错误与否？ [英] Bug in Xlang Engine or not ?

问题描述

好的，这是一个故事，但如果你有1个发送形状你可能会遇到两次路由故障吗？


今天我一直忙于解决这个问题。我想我在编排引擎中发现了一个BUG，但我不太确定。

Ok, it's quite a story but if you have 1 Send shape could you ever get two routing failures ?
Today I have been busy with this problem. I think I have found a BUG in the orchestration engine but I am not really sure.

读取我的BizTalk结果>>  这里 <<

Have a read of my BizTalk Findings >> HERE <<

请让我知道你的想法，甚至更好的解释为什么事情就像它们一样....

Please let me know what you think, or even better explain why things are as they are....

 

推荐答案

回到BizTalk 2009我做了类似这样的事情只是为了让它编译。 BizTalk扩展有很多编译问题，直到在此修补程序中解决了这些问题：
http://support.microsoft .com / kb / 977428

我想做的一点是编译的技巧是添加一个只用分号的表达式形状。是的虚假表达听起来与你的相似。这导致编译以某种方式工作。你仍然可以在BizTalk 2010
中执行这个分号技巧，但你不应该像BizTalk 2009那样得到编译问题。

What I would do to sort of trick the compilation was to add an expression shape with just a semicolon. Yeah bogus expression which sounds similar to yours. This causes the compilation to work somehow. You can still do this semicolon trick in BizTalk 2010 but you should not get the compilation issues like with BizTalk 2009.

我看到一个orchestraton命名冲突会导致虚假订阅当跨多个业务流程存在相同的消息名称时。由于某种原因，编译将其转换为具有过滤器的2个单独的接收形状。你的问题听起来像这样的事情是
。为了解决这个问题，我回顾了两个业务流程中消息和消息类型的相同名称，并完全改变了它，这很有效。

I have seen an orchestraton naming collision lead to a false subscription when there is the same name of a message across more than one orchestration. For some reason the compilation turned this into 2 separate receives shapes with filters. Your issue sounds like something like this. To resolve the issue I looked back through for the same names on messages and message types across both orchestrations and changed it completely and this worked.

谢谢，

这篇关于Xlang Engine中的错误与否？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！