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 / October 2003

Tip: Looking for answers? Try searching our database.

Creating Web service from the interface (WSDL)

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
James Bradley - 06 Oct 2003 20:35 GMT
Hello all,

I am new to .NET and web services so any guidance is appreciated!

I have created a (C#) web service the .NET way, creating the code
first and having .NET auto generate the WSDL.  This was pretty
straightforward, and after adding a few atrributes to clean up the
SOAP requests and responses, I have a nice interface.

Now, what I want to do is lock down the interface (WSDL) and code to
that, not the other way around.  So, I grabbed a copy of the WSDL and
started a new solution.

I have two projects, one a simple project that builds the abstract
class for the webservice (WSDL /Server), and the other which includes
the .CS from that.  I then derive from this base class and implement
my service.  I have copied all of the attributes and prototypes
straight from the base class.  I have changed the namespace/class
structure to more accurately represent the final resting place for
this service.

Now, when I add a test project and attempt to add a Web Reference to
my service, it fails.  I select my .WSDL through localhost, and the
response is "The specified module could not be found".  I have no idea
what the real problem is here, but the IIS log is showing two entries,
401 then 500 for the WSDL.  I'm not sure what authorization problem I
am having to access the WSDL, and I don't know how to find any details
beyond this message.

Do I still need an ASMX page, or is this irrelevant now that I am
working from the WSDL?

Does anyone know of some tutorials on doing this kind of thing?  All I
can find are articles based on code --> interface for .NET, now the
other way around.

I really hope that I can do this, because I want to have my interface
locked down and I will soon need to deal with nillable value types :-(

Thanks for any help you can give!

Jami
richlm - 11 Oct 2003 20:43 GMT
Hi James

First I think you are taking an excellent approach! One
of the best ways to fully understand web services is to
start with the WSDL, and you are sort of going that route.

I think the article:
"Place XML Message Design Ahead of Schema Planning to
Improve Web Service Interoperability" from MSDN magazine
might help - link at
http://msdn.microsoft.com/msdnmag/issues/02/12/webservices
design/default.aspx

Please let us know if it helps.

Richard.

>-----Original Message-----
>Hello all,
[quoted text clipped - 41 lines]
>
>.

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



©2009 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.