Hi Neter,
The XML schema specification provides two means to use multiple schemas
together. One is the Import instruction, and the other is the Include
instruction. The Import instruction is used to bring in schema from other
namespaces. The include instruction is used to combine schemas that have
the same target namespaces.
It is not valid to use Import to combine schemas that have the same target
namespace.
Breaking one schema into multiple files can be problematic and by best
practice should be avoided. But if you must do this, you can use the
include instruction in XML schema to accomplish this.
I hope this helps
Dan Rogers
Microsoft Corporation
--------------------
From: "Neter Smith" <ne*****@gmail.com>
References: <e7**************@TK2MSFTNGP12.phx.gbl>
<Ge**************@cpmsftngxa10.phx.gbl>
Subject: Re: WDSL Import Error
Date: Thu, 16 Dec 2004 15:03:02 -0500
Lines: 80
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2527
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
X-RFC2646: Format=Flowed; Original
Message-ID: <#o**************@TK2MSFTNGP09.phx.gbl>
Newsgroups: microsoft.public.dotnet.framework.webservices
NNTP-Posting-Host: 206.208.224.161
Path:
cpmsftngxa10.phx.gbl!TK2MSFTFEED02.phx.gbl!TK2MSFT NGP08.phx.gbl!TK2MSFTNGP09
..phx.gbl
Xref: cpmsftngxa10.phx.gbl
microsoft.public.dotnet.framework.webservices:8140
X-Tomcat-NG: microsoft.public.dotnet.framework.webservices
If I collapse the schema files (there were 3 includes in the WSDL) I can
successfully generate the proxy stubs. It was my understanding and
interpretation of the spec that multiple includes could contain the same
targetNamespace.
Also
http://support.microsoft.com/?id=822411 states a symptom of " When
the
Web Services Description Language (WSDL) imports a schema that includes
multiple schema by using the xsd:include element, and when these schemas
include any command schema, the WSDL tool (Wsdl.exe) cannot generate the
proxy for the Web service." was addressed in the hotfix - this does not
seem
to be the case.
As I have a workaround, I can continue with development, but is this not
what was supposed to be addressed with the hotfix?
Thanks!
"Dan Rogers" <da***@microsoft.com> wrote in message
news:Ge**************@cpmsftngxa10.phx.gbl...
Hi,
This error is going to happen if a schema in the imported WSDL files Types
section has an xs:import statement in it that imports a schema that has
the
same target namespace as the schema that contains the import statement.
Either the WSDL in question is incorrectly formed, or the schema's should
be combined.
I hope this helps
Dan Rogers
Microsoft Corporation
--------------------
From: "Neter Smith" <ne*****@gmail.com>
Subject: WDSL Import Error
Date: Thu, 16 Dec 2004 13:10:06 -0500
Lines: 22
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2527
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
X-RFC2646: Format=Flowed; Original
Message-ID: <e7**************@TK2MSFTNGP12.phx.gbl>
Newsgroups: microsoft.public.dotnet.framework.webservices
NNTP-Posting-Host: 206.208.224.161
Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFT NGP08.phx.gbl!TK2MSFTNGP12 phx.gbl
Xref: cpmsftngxa10.phx.gbl
microsoft.public.dotnet.framework.webservices:8131
X-Tomcat-NG: microsoft.public.dotnet.framework.webservices
I have run into a problem when trying to import a WSDL reference under VS
2003 and 1.1 of the framework. It appears as if it is in the generation
of
the proxy that things are failing.
When I add the reference, I get the following error:
C:\Inetpub\wwwroot\WebServices\samples\WSDL\dotnet \OblixSampleForDotNetWSDL\ Web
References\localhost\Reference.map(1): Custom tool error: Unable to import
WebService/Schema. A schema with the namespace 'http://www.oblix.com/' has
already been added.
I have applied the two following hotfixes
http://support.microsoft.com/?id=822411 and
http://support.microsoft.com/?id=823639 and am still seeing the problem.
Anyone have any ideas?
Thanks
D.
