BUG: You cannot create a map that accepts multiple input message schemas in the same namespace in BizTalk Server 2004 (883376)
The information in this article applies to:
- Microsoft BizTalk Server 2004 Standard Edition
- Microsoft BizTalk Server 2004 Enterprise Edition
- Microsoft BizTalk Server 2004 Developer Edition
- Microsoft BizTalk Server 2004 Partner Edition
SYMPTOMSIn Microsoft BizTalk Server 2004, when you create a map that accepts multiple input message schemas in the same namespace, BizTalk Mapper displays only the first message and its elements in the source schema display in the auto-generated map .btm file. When you expand the other input messages in the source schema, the namespace string is empty.CAUSEThis problem occurs when the input message schemas have the same namespace. Only one import statement for each unique namespace is generated in the auto-generated map.RESOLUTIONTo resolve this problem, use Notepad to modify the map file and to manually add the missing schemas. To do this, follow these steps: Note In this example, assume that your input message schemas are Part1.xsd and Part2.xsd and that both schemas belong to the http://SomeNameSpace namespace. - Click Start, click Run, type notepad, and then click OK.
- Click File, and then click Open.
- In the Files of type list, click All Files.
- Locate and then click your .btm file, and then click Open.
- In your map file, locate the following line of code:
<xs:import schemaLocation=".\part1.xsd" namespace=http://somenamespace /> - Click the end of line, press ENTER, and then type the following code:
<xs:import schemaLocation=".\part2.xsd" namespace=http://somenamespace /> - On the File menu, click Save.
- Exit Notepad.
STATUS Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.MORE INFORMATIONThe problem that is described in this article does not occur in Microsoft BizTalk Server 2004 Service Pack 1 (SP1).
| Modification Type: | Major | Last Reviewed: | 9/9/2004 |
|---|
| Keywords: | kbfix kbtshoot kbbug KB883376 kbAudDeveloper kbAudEndUser |
|---|
|