Re: WSDL Generated Proxy Classes?

Hi,

Arpan wrote:
The advantage of generating a
WSDL file is that each client can download the WSDL file and generate
proxy "on the fly".

But what proxy classes do, the same can be done using business objects.
In other words, the logic that a proxy class encapsulates, the same
logic can be implemented using a business object i.e. both of them can
be used to retrieve data dynamically but using WSDL means the client
has to save the proxy file (along with the disco & results.discomap
files though not necessarily) in his machine thus consuming disk space
but with business objects, the client needn't save anything on his hard
disk.

I think that you're missing the point that web services are not tied to a technology or an environment, and that the proxy classes can be (and often are, for example in ATLAS) generated dynamically during runtime. In that scenario, nothing is saved on the client, and a description file is needed. The .NET way of using "static" web references to consume web services is, IMHO, rather the exception.

I think that everything which SOAP does can be done in other more efficient ways, for example using simpler AJAX. But SOAP offers an additional level of comfort for the user, which explains why it's "bloated" (which is the most common criticism found against SOAP based web services).

HTH,
Laurent


Moreover to access the methods & properties in a proxy file, the client
has to pass commands to the Web Service (which maybe preceded by first
finding where the Web Service exists using DISCO) but with business
objects, there isn't any need for clients to use any extra tools like
WSDL.exe & DISCO.exe to access the business object's methods &
properties.

Both Web Services & business objects require compiled objects that are
implemented in ASP.NET pages. An ASP.NET book for beginners states that
the ONLY difference between Web Services & business objects is that
with Web Services, the compiled object (i.e. the proxy class) can
reside anywhere on the Internet. In other words, the ASP.NET page can
be located on a client's home computer in New York while the Web
Service resides on a server which is in Tokyo. But even business
objects that reside on a server in Tokyo can be accessed by an ASP.NET
page which is located in a client's machine in New York!

So what's the difference between Web Services & business objects or
what are the advantages of using Web Services (using WSDLs & sometimes
DISCOs) over business objects?

Thanks,

Regards,

Arpan
--
Laurent Bugnion, GalaSoft
Software engineering: http://www.galasoft-LB.ch
Private/Malaysia: http://mypage.bluewin.ch/lbugnion
Support children in Calcutta: http://www.calcutta-espoir.ch
.

Relevant Pages

  • Re: link problem in a C++ web service client
    ... > Java web services and need to test them with C++ clients. ... I'm having problems with the C++ client. ... > reference to the service WSDL and named the reference donow11service, ... > Creating web service proxy file for donow11service ... ...
    (microsoft.public.dotnet.languages.vc)
  • Re: SOAP header
    ... when design the old version web services, ... header from client request, and let client to set the SOAP header ... since client is using old proxy which does not ...
    (microsoft.public.vc.language)
  • How to copy data from CLR object to its proxy?
    ... On the client, I have a type myAssembly.myClass from the same assembly ... really fill in the fields of object parameters to web services without ... is there any sensible way to copy the data from a CLR object ... to its Web Service proxy? ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
  • Re: Add Web Service advice
    ... Are you referring to using a base WSDL contract to describe the webservice ... we would still have the issue of the client proxy ... >> versions of these business objects for use with the webservice methods. ...
    (microsoft.public.dotnet.framework.webservices)
  • Re: WCF Proxies
    ... It's not so much that ASMX web services aren't meeting your needs, ... Essentially, you've got a network composed of A, B, and C - and a client ... So the client generates a proxy for the WSDL. ... with additional servers to be added later. ...
    (microsoft.public.dotnet.framework.webservices.enhancements)