Pipeline disassembler and assembler components use XSD schemas to process messages. The schemas contain information such as the list of promoted properties, distinguished fields, annotations for flat file messages, and annotations for XML envelopes.

Standard disassembler and assembler components support retrieval of deployed schemas by using the schema type name and message type. Some components retrieve by using both the schema type name and the message type, while others (for example, the Flat File Disassembler) retrieve only by the schema type.

Pipeline components that receive XML messages determine the message type by examining the message root element and namespace. For example, the message type for the following XML is "http://MyDocument.org#MyDocument".

<ns0:MyDocument xmlns:ns0="http://MyDocument.org">
   …
</ns0:MyDocument>

If a schema does not have a namespace defined for it, the message type is "<rootNode>". For example, if the preceding example XML had no namespace, the message type would be "MyDocument".

Standard pipeline components use the message type to retrieve the appropriate schema from the database. Default XML receive and send pipelines always determine which schema to load by using the message type dynamically discovered at runtime from the message XML content (unless the pipeline component is set to allow unrecognized messages). The XML Disassembler can remove the message envelope by using this mechanism; however, the XML Assembler cannot create an envelope for an outgoing message without knowing what envelope schema to use. To create an envelope in the XML Assembler or a header and trailer in the Flat File Assembler, you must create a custom send pipeline and define the schemas in Pipeline Designer.

Schema resolution by message type may not work if several versions of the same schema are intentionally or accidentally deployed in the database (for example, in a side-by-side deployment or if multiple scenarios do not have unique message types). If schema resolution by message type fails, a "schema ambiguity" error is added to the event log. To ensure that schema resolution by message type succeeds, do one of the following:

• Define the schemas in the same BizTalk project as your custom pipeline.
• Sign the assembly with the schemas with the same key as the assembly containing the pipelines.
• Explicitly specify schemas in pipeline components (message type names should be unique across the Configuration database).

Important  When schemas in the same assembly share a message type, you must not include the schemas in the same pipeline component assembly due to the limitations of ambiguity resolution; instead, reference schemas that are external to the pipeline component assembly. Ambiguity resolution does not work when schemas and pipeline components are in the same assembly, even if schema type names are explicitly specified in pipeline components in custom pipelines.

Note  Custom pipeline components that use IPipelineContext to obtain deployed schemas should obtain schemas by schema type only if the schema type name is not specified for the component at run time, and obtain schemas by message type only if the schema type information is not available when the component is run.

See Also

Pipeline Components