BizTalk Rule Composer究竟是如何设置“文档类型”的？用于XML模式。 [英] How exactly does BizTalk Rule Composer set the "Document Type" for an XML schema.

问题描述

我注意到在我的开发机器上，文档类型"按预期"工作。 

I noticed that on my development machine, the document type works "as expected". 

但是当我将架构和业务规则部署到QA机器时，试图添加新规则，xpath更短，因为"文档类型"是更短。 似乎就像一个复出就是用文件
类型命名物理模式文件名（或者手动更改文档类型）。 

But when I deployed schema and business rule to QA machine, then tried to add a new rule, the xpath was shorter, because the "document type" was shorter.  Seems like one get-around was to name the physical schema filename with the document type (or manually change the Document Type). 

所以在开发人员的系统和质量保证或其他系统，"文件类型"究竟是怎样的？填充（即使我知道我可以覆盖它）。 因此，最佳做法是将模式命名为文档类型？ 

So on both the developer's system and the QA or other systems, how exactly does the "Document Type" get populated (even though I know I can override it).  So it looks like the best practice is to name the schema with the document type? 

示例，如果我将模式复制到名称如MyBRESchema.xsd，即使内容.xsd与另一个文件相同，即"文档类型"。被设置为"MyBREScehma"。

Example, if I copy the schema to a name such as MyBRESchema.xsd, even though the contents of the .xsd is the same as another file, the "Document Type" is set to "MyBREScehma".

谢谢，

Neal Walters 

Neal Walters 

推荐答案

通常我'我总是首先针对BizTalk中部署的模式创建一个词汇表。在这种情况下，文档类型与BizTalk文档类型匹配，即：目标命名空间＃根元素。通过这种方式，我可以在不同环境中提取和移动规则
而不会出现任何问题。

Normally I've always created a vocabulary first against a schema deployed in BizTalk. In that scenario the Document Type matches the BizTalk Document Type i.e.: the target namespace#the root element. This way I have been able to extract and move the rules across different environments without any problems.

您所描述的行为类似于移动文件时的行为跨越VS的项目。

What you're describing is the behaviour similar to that observed when you move files across projects in VS.

问候。

这篇关于BizTalk Rule Composer究竟是如何设置“文档类型”的？用于XML模式。的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！