"Nick Locke" <nick.locke@21jubileepark.com> wrote in message
news:_uSdnZDA0Kmt99vYRVnygg@eclipse.net.uk...
>I have a fairly simple structure:
>
> - Simple Types in an XSD
> - Complex Types (one file) in another XSD, importing the Simple Types
> - More Complex Types (second file) in another XSD, again importing the
> Simple Types
> - A WSDL Definitions file, importing the two Complex Types files
> - A WSDL Service file, importing the WSDL Definitions file
>
> I have put all that together with XML Spy and that seems happy. I can
> also parse the WSDL Service file from SOAPSonar and end up with everything
> correctly imported.

"Nick Locke" <nick.locke@21jubileepark.com> wrote in message
news:NP6dnducYKAhMtrYnZ2dnUVZ8qOdnZ2d@eclipse.net.uk...
> "John Saunders" <john.saunders at trizetto.com> wrote:
>> Nick, please supply a small reproducer.
>
> Hopefully, this is small enough! I have hardcoded full "file://" URIs in
> response to an earlier recommendation - that means you need everything in
> a
> directory "c:\wsdl\example" to avoid having to change anything.
>
> My wsdl command line is "wsdl /si /l:VB stolenvehicleservice.wsdl". I
> have
> also tried providing all of the other files names on the command line as
> suggested in Andrew's post.
>
> I get the same results with/without full URI references and with/without
> the
> extra files on the command.
>
> I really hope that I have done something stupid which is easy to find!
>
> Many thanks for your help.
>
> Nick
>
> My first attempt at this with the files as attachments seems not to have
> appeared in the group. So, I have put the files on my server:
>
> http://nick.21jubileepark.com/wsdl/SimpleTypes.xsd
> http://nick.21jubileepark.com/wsdl/ContextTypes.xsd
> http://nick.21jubileepark.com/wsdl/StolenVehicleTypes.xsd
> http://nick.21jubileepark.com/wsdl/StolenVehicleDefinitions.wsdl
> http://nick.21jubileepark.com/wsdl/StolenVehicleService.wsdl
>
> I hope those links all work!
>

"Nick Locke" <nick.locke@21jubileepark.com> wrote in message
news:_uSdnZDA0Kmt99vYRVnygg@eclipse.net.uk...
>I have a fairly simple structure:
>
> - Simple Types in an XSD
> - Complex Types (one file) in another XSD, importing the Simple Types
> - More Complex Types (second file) in another XSD, again importing the
> Simple Types
> - A WSDL Definitions file, importing the two Complex Types files
> - A WSDL Service file, importing the WSDL Definitions file
>
> I have put all that together with XML Spy and that seems happy. I can
> also parse the WSDL Service file from SOAPSonar and end up with everything
> correctly imported.
>
> BUT, wsdl.exe does this:
>
> C:\WSDL>wsdl /si /l:VB StolenVehicleService.wsdl
>
> Microsoft (R) Web Services Description Language Utility
>
> [Microsoft (R) .NET Framework, Version 2.0.50727.42]
>
> Copyright (C) Microsoft Corporation. All rights reserved.
>
> Error: Cannot find definition for
> http://namespaces.xxxx-yyyyy.org.uk/20061029/Definitions/StolenVehicle:SOAPport.
>
> Service Description with namespace
> http://namespaces.xxxx-yyyyy.org.uk/20061029/Definitions/StolenVehicle is
> missing.
>
> Parameter name: name
>
>
>
> I can see details of a similar problem in MSDN etc, but that dates back to
> 2003. Can someone please shed some light on what I need to do?
>
>
>
> Thanks.
>
>

"Nick Locke" <nick.locke@21jubileepark.com> wrote in message
news:Xr6dnSUPK_ixJNrYRVnysg@eclipse.net.uk...
>
> "RYoung" <rcyoungatinkspotdev.com> wrote in message
> news:O1yQ6wS$GHA.1560@TK2MSFTNGP02.phx.gbl...
>> Try this:
>>
>> wsdl /l:VB /si stolenvehicleservice.wsdl stolenvehicledefinitions.wsdl
>> stolenvehicletypes.xsd contexttypes.xsd simpletypes.xsd
>>
>> Worked for me,
>> Ron
>
> Thanks Ron. I can only assume that, somewhere along the line, I was
> mis-spelling one of the file names or something equally amateurish! Many
> thanks.
>

"Nick Locke" <nick.locke@21jubileepark.com> wrote in message
news:bpadnYBA6oGaRdrYRVnyhA@eclipse.net.uk...
> "RYoung" <rcyoungatinkspotdev.com> wrote in message
> news:u$J4zST$GHA.4316@TK2MSFTNGP03.phx.gbl...
>> Your welcome.
>> Did you design the WSDL with XmlSpy? I've been experimenting with
>> designing contracts up front using XmlSpy and was wondering if you could
>> share any reasons why you chose that approach.
>
> Good question! Yes I did design the WSDL (and the XSDs) with XMLSpy. I
> decided to go "contract first" because it seemed the right hting to do as
> I shall have many different "consumers" and they will all want to sign-off
> a spec before any code is cut. Having tried both ways around, it also
> seemed to be a bit cleaner that way.
>
> I chose the tool because it seemed to be fairly well respected in the
> write-ups. That said, I am a bit disappointed with the level of sanity
> checking that it does - it is very eay to get something which says "valid"
> only to find that either wsdl.exe or SOAPSonar chokes. I only have an
> evaluation copy at the moment - my team will need to decide whether they
> need a full copy or whether, for what we need, Notepad will do the job.
>
> Does that help?
>
> Nick
>

"John Saunders" <john.saunders at trizetto.com> wrote:
> Nick, please supply a small reproducer.

"RYoung" <rcyoungatinkspotdev.com> wrote in message
news:O1yQ6wS$GHA.1560@TK2MSFTNGP02.phx.gbl...
> Try this:
>
> wsdl /l:VB /si stolenvehicleservice.wsdl stolenvehicledefinitions.wsdl
> stolenvehicletypes.xsd contexttypes.xsd simpletypes.xsd
>
> Worked for me,
> Ron

"RYoung" <rcyoungatinkspotdev.com> wrote in message
news:u$J4zST$GHA.4316@TK2MSFTNGP03.phx.gbl...
> Your welcome.
> Did you design the WSDL with XmlSpy? I've been experimenting with
> designing contracts up front using XmlSpy and was wondering if you could
> share any reasons why you chose that approach.

"RYoung" <rcyoungatinkspotdev.com> wrote in message
news:eWd1xGV$GHA.5112@TK2MSFTNGP03.phx.gbl...
> Thanks Nick,
>
> I'm currently reading "Service Oriented Architecture" by Thomas Erl,
> published by Prentice Hall, in which Erl elaborates on the composability
> of WSDL to form new services, and the .xsd, .wsdl files you posted
> certainly demonstrated that aspect, I believe.
>
> Anyways, thanks for your response on that - I agree that contract first in
> a tool other than VS does seem to put me in a different state of mind, I
> actually like that separation and ability to focus on aspects of the
> application/system.
>
> I haven't had much success developing anything close to what you have
> posted with XmlSpy's WSDL editor, - that is in as far as the separation
> you've achieved between types, service operations, and definitions, but
> I'm definetly going to study those files, if you don't mind, and most
> likely will learn that approach.
>
> Ron
>
> "Nick Locke" <nick.locke@21jubileepark.com> wrote in message
> news:bpadnYBA6oGaRdrYRVnyhA@eclipse.net.uk...
>> "RYoung" <rcyoungatinkspotdev.com> wrote in message
>> news:u$J4zST$GHA.4316@TK2MSFTNGP03.phx.gbl...
>>> Your welcome.
>>> Did you design the WSDL with XmlSpy? I've been experimenting with
>>> designing contracts up front using XmlSpy and was wondering if you could
>>> share any reasons why you chose that approach.
>>
>> Good question! Yes I did design the WSDL (and the XSDs) with XMLSpy. I
>> decided to go "contract first" because it seemed the right hting to do as
>> I shall have many different "consumers" and they will all want to
>> sign-off a spec before any code is cut. Having tried both ways around,
>> it also seemed to be a bit cleaner that way.
>>
>> I chose the tool because it seemed to be fairly well respected in the
>> write-ups. That said, I am a bit disappointed with the level of sanity
>> checking that it does - it is very eay to get something which says
>> "valid" only to find that either wsdl.exe or SOAPSonar chokes. I only
>> have an evaluation copy at the moment - my team will need to decide
>> whether they need a full copy or whether, for what we need, Notepad will
>> do the job.
>>
>> Does that help?
>>
>> Nick
>>
>
>