|
Home > Archive > BizTalk Server General > September 2004 > Biztalk Mapper Bug Regarding Namespaces
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Biztalk Mapper Bug Regarding Namespaces
|
|
| Mark Allanson 2004-09-23, 9:18 am |
| Hi guys,
I beleive I have found a bug with the Biztalk 2004 mapper regarding
its handling of XML docuents that contain nodes of the same name, but
existing in different namespaces. We have been able to confirm the bug
here on multiple machines, however I would like to gauge other peoples
experiences before submitting a case to MS.
1. Create a nice simple schema that adheres to the simple document
below.
<RootNode>
<MyNode>MyData</MyNode>
<myns:MyNode xmlns:myns="http://tempuri.org/MyNodeNS">MyData2</myns:MyNode>
</RootNode>
2.You can use the same doc type as the destination of your map if you
like. Create a new map, set the source and destination schemas to the
schema created above, then link the myns:MyNode nodes on each side of
the map to each other (ie (src) myns:MyNode <----> myns:MyNode (dest).
3. Save your map, exit the map, the reload the map, and voila, find
that your mappings have now jumped from linking the namespaced nodes
to linking the non-namespaced nodes.
If you try the same thing when the desintation schema does not contain
a non-namespaced node you will get a dialog box when opening the map
that you have invalid links.
Cheers,
Mark
| |
| Tatyana Yakushev [MSFT] 2004-09-24, 5:49 pm |
| Click on the Mapper grid and set "Ignore Namespaces for Links" to "false".
When this property is set to 'true' you should not change target namespace in your schemas because it will cause all links to disappear.
Tatyana
--------------------
>From: mark.allanson@accenture.com (Mark Allanson)
>Newsgroups: microsoft.public.biztalk.general
>Subject: Biztalk Mapper Bug Regarding Namespaces
>Date: 23 Sep 2004 03:24:19 -0700
>Organization: http://groups.google.com
>Lines: 32
>Message-ID: <31898636.0409230224.24af280@posting.google.com>
>NNTP-Posting-Host: 213.234.34.19
>Content-Type: text/plain; charset=ISO-8859-1
>Content-Transfer-Encoding: 8bit
>X-Trace: posting.google.com 1095935059 648 127.0.0.1 (23 Sep 2004 10:24:19 GMT)
>X-Complaints-To: groups-abuse@google.com
>NNTP-Posting-Date: Thu, 23 Sep 2004 10:24:19 +0000 (UTC)
>Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!news-out.cwix.com!newsfeed.cwix.com!border1.nntp.dca.giganews.com!nntp.giganews.com!news.glorb.com!
postnews1.google.com!not-for-mail
>Xref: cpmsftngxa06.phx.gbl microsoft.public.biztalk.general:19790
>X-Tomcat-NG: microsoft.public.biztalk.general
>
>Hi guys,
>
>I beleive I have found a bug with the Biztalk 2004 mapper regarding
>its handling of XML docuents that contain nodes of the same name, but
>existing in different namespaces. We have been able to confirm the bug
>here on multiple machines, however I would like to gauge other peoples
>experiences before submitting a case to MS.
>
>1. Create a nice simple schema that adheres to the simple document
>below.
>
><RootNode>
> <MyNode>MyData</MyNode>
> <myns:MyNode xmlns:myns="http://tempuri.org/MyNodeNS">MyData2</myns:MyNode>
></RootNode>
>
>2.You can use the same doc type as the destination of your map if you
>like. Create a new map, set the source and destination schemas to the
>schema created above, then link the myns:MyNode nodes on each side of
>the map to each other (ie (src) myns:MyNode <----> myns:MyNode (dest).
>
>3. Save your map, exit the map, the reload the map, and voila, find
>that your mappings have now jumped from linking the namespaced nodes
>to linking the non-namespaced nodes.
>
>If you try the same thing when the desintation schema does not contain
>a non-namespaced node you will get a dialog box when opening the map
>that you have invalid links.
>
>Cheers,
>
>Mark
>
--
This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.
|
|
|
|
|