BizTalk Framework 2.0 compliant schemas Generate Warnings in BizTalk Editor (276676)
The information in this article applies to:
- Microsoft BizTalk Server 2000
This article was previously published under Q276676 SYMPTOMS When you import a Microsoft BizTalk Framework 2.0-compliant schema
into the BizTalk Editor, you may receive the following error messages: Generating warnings for "Renamed Nodes and
Specification Validation"...
Warning: The Order attribute of the
ElementType "biztalk_1" has been ignored.
Warning: The Order attribute of
the ElementType "header" has been ignored.
Warning: The Order attribute of
the ElementType "delivery" has been ignored.
Warning: The Order attribute
of the ElementType "message" has been ignored.
Warning: The Order
attribute of the ElementType "to" has been ignored.
Warning: The Order
attribute of the ElementType "state" has been ignored.
Warning: The Order
attribute of the ElementType "from" has been ignored.
Warning: The Order
attribute of the ElementType "manifest" has been ignored.
Warning: The
Order attribute of the ElementType "document" has been ignored.
Warning:
The Order attribute of the ElementType "attachment" has been ignored.
Warning: The Order attribute of the ElementType "body" has been ignored.
Warning: The schema name "biztalk_1.xml" differs from the root element name
"biztalk_1".
Warning: Record "message" - The Minimum Occurrences property
has not been set.
Warning: Record "message" - The Maximum Occurrences
property has not been set.
Warning: Record "to" - The Minimum Occurrences
property has not been set.
Warning: Record "to" - The Maximum Occurrences
property has not been set.
Warning: Field "referenceID" - The Required
property must be set for a field that is an Element.
Warning: Record
"from" - The Minimum Occurrences property has not been set.
Warning:
Record "from" - The Maximum Occurrences property has not been set.
Warning: Field "referenceID" - The Required property must be set for a field
that is an Element.
Warning: Record "manifest" - The Minimum Occurrences
property has not been set.
Warning: Record "manifest" - The Maximum
Occurrences property has not been set.
Completed warning generation.
Editor validation - 22 warning(s) CAUSE Schemas are not being imported with the XDR import
module.RESOLUTION To resolve this problem, you must import BizTalk Framework
2.0-compliant schemas by using the XDR import module. STATUSMicrosoft has confirmed that this is a
problem in BizTalk Server 2000.
MORE INFORMATION The warnings refer to XDR properties that are not supported
in the BizTalk Editor. These warnings are not critical.
During the
XDR import, the BizTalk Editor imports the schema as is. If minOccurs/maxOccurs has not been set in the original XDR schema, the BizTalk Editor
does not set the values during the import. However, minOccurs and maxOccurs both default to 1 if unspecified.
| Modification Type: | Major | Last Reviewed: | 10/10/2003 |
|---|
| Keywords: | kbpending kbprb KB276676 |
|---|
|