By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,617 Members | 1,751 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,617 IT Pros & Developers. It's quick & easy.

WSDL.exe tool and separate (nested) XSD schema file(s)?

P: n/a
drb
Hi,

Newbie question #2 - hope that's OK!

I'm trying to create a WSDL file using one or more XSD schema files. While
WSDL.exe doesn't seem to support the XSD "import" function, if I include a
single huge XSD schema file on the command line input to WSDL.exe, I can
essentially achieve the desired result. (So, first question: is it true that
WSDL.exe does not support *any* kind of <wsdl:import ...> or <xsd:import...>
function?)

Ideally, I would like to divide the XSD schema file into a hierarchical
series of files so that a single file containing common types can be included
in other files, etc. But, I can't get this to work - I've tried having both
the same and different namespaces for common and specific types, and tried
every combination of the schema files (after the WSDL file) on the WSDL.exe
command line. Each time I get some kind of error (varies) about things not
importing, that elements are missing, etc. Am I out of luck with this
approach? I hate the idea of having one huge schema file for maintainance
reasons...

Thanks for any guidance! (If there's a better newsgroup to ask this
question, please let me know...)
Nov 23 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
drb
I think I managed to partially answer my own question. WSDL does support the
import command, but there appears to be a known problem with importing XML
schemas that include other XML schemas, which is exactly what I am trying to
do (see KB #s 823639 - 823641, 822411, 821544).

Supposedly there is a hotfix rollup; but I've already got .NET Framework 1.1
SP1 with all available updates (via Windows Update) applied. Should I
already have this fix then? Or is this something only a $99 call to support
can answer?! Any suggestions/guidance?

Thanks...
Nov 23 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.