Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / Web Services / March 2005

Tip: Looking for answers? Try searching our database.

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

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
drb - 11 Mar 2005 14:57 GMT
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...)
drb - 15 Mar 2005 16:47 GMT
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...

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.