wsdl.exe problem

[Nick Locke]

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 StolenVehicleSe rvice.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/...hicle:SOAPport.

Service Description with namespace
http://namespaces.xxxx-yyyyy.org.uk/.../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.

[John Saunders]

"Nick Locke" <ni********@21j ubileepark.comw rote in message
news:_u******** ************@ec lipse.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, please supply a small reproducer.

John

[Andrew Brook]

Hi Nick,

Unfortunately i'm no expert with wsdl.exe, but in the past i found that i
had to explicitly tell wsdl.exe where any external xsd schemas were (even
when they were in the same directory)

C:\WSDL>wsdl /si /l:VB StolenVehicleSe rvice.wsdl simpleschema.xs d
complexschema.x sd evenmorecomplex .xsd

Hope this helps,
Andrew

"Nick Locke" <ni********@21j ubileepark.comw rote in message
news:_u******** ************@ec lipse.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 StolenVehicleSe rvice.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/...hicle:SOAPport.

Service Description with namespace
http://namespaces.xxxx-yyyyy.org.uk/.../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]

"John Saunders" <john.saunder s at trizetto.comwro te:

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\exampl e" to avoid having to change anything.

My wsdl command line is "wsdl /si /l:VB stolenvehiclese rvice.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/S...hicleTypes.xsd
http://nick.21jubileepark.com/wsdl/S...finitions.wsdl
http://nick.21jubileepark.com/wsdl/S...leService.wsdl

I hope those links all work!

[RYoung]

Try this:

wsdl /l:VB /si stolenvehiclese rvice.wsdl stolenvehiclede finitions.wsdl
stolenvehiclety pes.xsd contexttypes.xs d simpletypes.xsd

Worked for me,
Ron

"Nick Locke" <ni********@21j ubileepark.comw rote in message
news:NP******** *************** *******@eclipse .net.uk...

"John Saunders" <john.saunder s at trizetto.comwro te:

>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\exampl e" to avoid having to change anything.

My wsdl command line is "wsdl /si /l:VB stolenvehiclese rvice.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/S...hicleTypes.xsd
http://nick.21jubileepark.com/wsdl/S...finitions.wsdl
http://nick.21jubileepark.com/wsdl/S...leService.wsdl

I hope those links all work!

[Nick Locke]

"RYoung" <rcyoungatinksp otdev.comwrote in message
news:O1******** ******@TK2MSFTN GP02.phx.gbl...

Try this:

wsdl /l:VB /si stolenvehiclese rvice.wsdl stolenvehiclede finitions.wsdl
stolenvehiclety pes.xsd contexttypes.xs d 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.

[RYoung]

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.

Thanks,
Ron

"Nick Locke" <ni********@21j ubileepark.comw rote in message
news:Xr******** ************@ec lipse.net.uk...

>
"RYoung" <rcyoungatinksp otdev.comwrote in message
news:O1******** ******@TK2MSFTN GP02.phx.gbl...

>Try this:

wsdl /l:VB /si stolenvehiclese rvice.wsdl stolenvehiclede finitions.wsdl
stolenvehiclet ypes.xsd contexttypes.xs d 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]

"RYoung" <rcyoungatinksp otdev.comwrote in message
news:u$******** ******@TK2MSFTN GP03.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

[RYoung]

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" <ni********@21j ubileepark.comw rote in message
news:bp******** ************@ec lipse.net.uk...

"RYoung" <rcyoungatinksp otdev.comwrote in message
news:u$******** ******@TK2MSFTN GP03.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

[Nick Locke]

XMLSpy did virtually nothing to help the splitting process become an
intuitive one. It was hard graft with manual copies between files and
constant validation to make sure all was still ok. I really do believe that
the tools are not quite there yet!

"RYoung" <rcyoungatinksp otdev.comwrote in message
news:eW******** ******@TK2MSFTN GP03.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" <ni********@21j ubileepark.comw rote in message
news:bp******** ************@ec lipse.net.uk...

>"RYoung" <rcyoungatinksp otdev.comwrote in message
news:u$******* *******@TK2MSFT NGP03.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