Re: Fighting WSDL.exe

"David Jessee" <DavidJessee@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B19B6813-9DB0-4F1F-A813-0EA37FBCF0A5@xxxxxxxxxxxxxxxx
You're going to have to forgive me on being a little vauge, but I've not
dealt with this in a while (totally jaded about web services, here :-)

but...

The problem is with your import statement. The wsdl.exe is going to try
to
resolve the import by processing it as a URI. try expressing it as
"file://c:/......"

Be aware, though, that you may end up with issues down the road, depending
on how you move forward.

The MS implementation of Web Services makes the assumption, at runtime,
that
no one ever created a WSDL file and, therefore, it doesn't perform any
validation against the original WSDL file OR the original schema.

just take a good close look at the generated code when you're done (esp
the
attributes attached to the abstract server) to make sure nothing strange
happened.

Side note...When you're doing web services via studio, you're,
unfortunately, wasting your time creating this contract first and then
creating code based on the contract since, as mentioned earlier, the
contract
is never enforced, by default. After creating a number of web services
using
the WSDL-first approach, I realized that you're doing work that, once the
implementation is completed, really won't have much of a payoff.

I have to disagree with this. It's true that if you want schema validation
you have to do it yourself. There's an article about this on MSDN. Sorry I
don't have the URL handy. I've followed that article and have implemented
schema validation on input and on output, and it works nicely.

I also use the classes generated by WSDL.EXE. I used to inherit from the
service class it generates, but I now manipulate the XML directly, so only
use the other classes it generates.

John


.

Relevant Pages

  • Re: SOAP project
    ... As for those webservice which doesn't interop well between different ... it is often caused by the message contract not well defined. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Converting an application to support Web Services ...
    ... I know what web services is ... want some details resources ... ... if u have Search function in some component and want extract it to the ... > WS the first step you need to undertake is to create contract. ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
  • RE: Fighting WSDL.exe
    ... dealt with this in a while (totally jaded about web services, ... validation against the original WSDL file OR the original schema. ... creating code based on the contract since, as mentioned earlier, the contract ... If a document-literal binding in a DESCRIPTION does not specify the ...
    (microsoft.public.dotnet.framework.aspnet.webservices)