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 / February 2005

Tip: Looking for answers? Try searching our database.

webservice limitations?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Detroit - 16 Feb 2005 17:41 GMT
all,
while converting a .net class file to a xml webservice i have encountered
some problems. First I cannot seem to be able to pass optional parameters to
a web method. I have also found problems with the sqldatareader as a "byref"
parameter of a web method. This problem entails not being able to return a
datareader from a webservice. I also tried to return it via a function and
had no luck. Are these limitiations of xml webservices or am I not being
creative enough?

For some scenarios instead of using optional parameters I have created
overloaded functions and used the "messagename" property of the webmethod to
uniquely identify the individual function when publishing the webmethod.

I have not found any real solution for the sqldatareader problem.

Please help!
Keenan Newton - 16 Feb 2005 18:58 GMT
Yes these are very much limitations of web services.  So would even
argue this is by  You can't pass anything by reference, nor do they
support optional parameters.
Dino Chiesa [Microsoft] - 22 Feb 2005 06:07 GMT
returning a dataReader from a webservice is like
sending someone an oceanliner for valentines day.

It doesn't make any sense.

The philosophy of webservices is message-oriented integration.  you need to
think in terms of sending and receiving discrete messages, not sending and
receiving objects such as datareader.

check this:
http://webservices.xml.com/pub/a/ws/2003/09/30/soa.html

re: "optional params are not supported"
True, if you are thinking in terms of VB calls.
But not true, if you are thinking in terms of extensible messages, with
optional pieces of those messages.  In other words, the message itself is
not optional, but the contents of the message may vary.  You can do this
with webservices.

-Dino

> Yes these are very much limitations of web services.  So would even
> argue this is by  You can't pass anything by reference, nor do they
> support optional parameters.

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.