KB838795 talks about a problem whereby "When a schema has multiple
imports that contain the same namespace, and the first import includes
any other schemas, if a referenced element is not defined in the first
import, the element reference is not resolved. Also, element types
that are defined in imports do not appear under the Data Structure
Type property."

Hotfix 838795 is supposed to fix this problem, but in my situation, it
hasn't. In my model, one schema 'includes' another. The hotfix doesn't
appear to work if the Included schema has a blank target namespace,
and the including schema has a non-blank target namespace (which is
allowed; see "Schemas that use other Schemas" in help).

Can anyone verify my theory?

To reproduce the problem:

(1) Create a schema Included.xsd. Within it, create a Complex Type
with a referenced element child, and a non-referenced element child
(or just referenced element children if you prefer). Let's assume that
ComplexType is called "MyComplexType". Leave the Target Namespace for
this schema blank.

(2) Create a schema Including.xsd, and give it a non-blank target
namespace.

(3) Within the Imports property for this schema, Include the
Included.xsd schema.

(4) Save both schemas and reload.

(5) Now create a new record node in Including.xsd and choose
"MyComplexType" as the Data Structure Type.

Look what happens... the referenced elements within the Including.xsd
schema are unresolved! .... or did I do something wrong? I've got the
roll-up package installed, plus of course, the hotfix.

Glynn

[ Post a follow-up to this message ]

This KB is totally unrelated to your problem.
I only met one customer who needed the KB (without the KB some nodes are not
 displayed at the schema tree).

I will investigate your problem and get back to you.

Regards,
Tatyana

--------------------
>From: glynnatimmins@hotmail.com (Glynn Timmins)
>Newsgroups: microsoft.public.biztalk.general
>Subject: BTS 2004 Hotfix 838795: How to prove it doesn't completely fix the
 problem.
>Date: 28 Jul 2004 06:25:42 -0700
>Organization: http://groups.google.com
>Lines: 39
>Message-ID: <5228d043.0407280525.7db4f27d@posting.google.com>
>NNTP-Posting-Host: 213.194.32.211
>Content-Type: text/plain; charset=ISO-8859-1
>Content-Transfer-Encoding: 8bit
>X-Trace: posting.google.com 1091021143 23007 127.0.0.1 (28 Jul 2004 13:25:4
3 GMT)
>X-Complaints-To: groups-abuse@google.com
>NNTP-Posting-Date: Wed, 28 Jul 2004 13:25:43 +0000 (UTC)
>Path: cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.su
l.t-online.de!t-online.de!newsfeed.gamma.ru!Gamma.RU!
news.maxwell.syr.edu!postnews2.google.com!not-for-mail
>Xref: cpmsftngxa10.phx.gbl microsoft.public.biztalk.general:17966
>X-Tomcat-NG: microsoft.public.biztalk.general
>
>KB838795 talks about a problem whereby "When a schema has multiple
>imports that contain the same namespace, and the first import includes
>any other schemas, if a referenced element is not defined in the first
>import, the element reference is not resolved. Also, element types
>that are defined in imports do not appear under the Data Structure
>Type property."
>
>Hotfix 838795 is supposed to fix this problem, but in my situation, it
>hasn't. In my model, one schema 'includes' another. The hotfix doesn't
>appear to work if the Included schema has a blank target namespace,
>and the including schema has a non-blank target namespace (which is
>allowed; see "Schemas that use other Schemas" in help).
>
>Can anyone verify my theory?
>
>To reproduce the problem:
>
>(1) Create a schema Included.xsd. Within it, create a Complex Type
>with a referenced element child, and a non-referenced element child
>(or just referenced element children if you prefer). Let's assume that
>ComplexType is called "MyComplexType". Leave the Target Namespace for
>this schema blank.
>
>(2) Create a schema Including.xsd, and give it a non-blank target
>namespace.
>
>(3) Within the Imports property for this schema, Include the
>Included.xsd schema.
>
>(4) Save both schemas and reload.
>
>(5) Now create a new record node in Including.xsd and choose
>"MyComplexType" as the Data Structure Type.
>
>Look what happens... the referenced elements within the Including.xsd
>schema are unresolved! .... or did I do something wrong? I've got the
>roll-up package installed, plus of course, the hotfix.
>
>Glynn
>


--

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 mess
age are best directed to the newsgroup/thread from which they originated.

[ Post a follow-up to this message ]

The problem you see is a bug in System.XML (which is part of .net framework,
 not BizTalk).
It is fixed in .net framework version 2.0 (code name Whidbey) that is planne
d to release next year.

If possible you should try to use non-empty namespace.(If you want to includ
e this schema into several other schemas with different namespaces you may h
ave to have
several copies of this schema, one for every namespace)
If not possible you can contact PSS and see if you can get QFE for the probl
em.

Thanks,
Tatyana

--------------------
>X-Tomcat-ID: 655267018
>References: <5228d043.0407280525.7db4f27d@posting.google.com>
>MIME-Version: 1.0
>Content-Type: text/plain
>Content-Transfer-Encoding: 7bit
>From: tatyanam@online.microsoft.com (Tatyana Yakushev [MSFT])
>Organization: Microsoft
>Date: Wed, 28 Jul 2004 19:58:35 GMT
>Subject: RE: BTS 2004 Hotfix 838795: How to prove it doesn't completely fix
 the problem.
>X-Tomcat-NG: microsoft.public.biztalk.general
>Message-ID: <LbBnB1NdEHA.3424@cpmsftngxa10.phx.gbl>
>Newsgroups: microsoft.public.biztalk.general
>Lines: 81
>Path: cpmsftngxa10.phx.gbl
>Xref: cpmsftngxa10.phx.gbl microsoft.public.biztalk.general:17993
>NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122
>
>This KB is totally unrelated to your problem.
>I only met one customer who needed the KB (without the KB some nodes are no
t displayed at the schema tree).
>
>I will investigate your problem and get back to you.
>
>Regards,
>Tatyana
>
>-------------------- 
>news.maxwell.syr.edu!postnews2.google.com!not-for-mail 
>
>
>--
>
>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 mes
sage are best directed to the newsgroup/thread from which they originated.
>
>


--

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 mess
age are best directed to the newsgroup/thread from which they originated.

[ Post a follow-up to this message ]

Thanks again Tatyana, I do appreciate your help.

[ Post a follow-up to this message ]

Brilliant, thanks! At least that takes the mystery out of it, and I do
appreciate your efforts. My problem now is that the Included schema is
986Kb, 6 copies of that are going to bloat my project somewhat. I'll
take your advice and try the PSS route.

Best regards,

Glynn

[ Post a follow-up to this message ]