If WSDL is the web description language of a method, then why do not we define it the function in english. What is the advantage of having a structured form for the WSDL?
Sol-> The reason WSDL is not in english and is in XML is so that other programs can read this XML and generate function prototypes for developers. For example, microsoft provides WSDPrint.wsdl file which defines the functions for sending a print job to a webservice enabled printer. Programs like gSoap can read this WSDL and then create function stubs like CreatePrintJobRequest() and SendPrintJobRequest() with all the necessary parameters. The developer then just needs to implement the reuired portions inside the function and complete the implementation. A Java developer can also use this WSDL to create Java function stubs and so this gives a lot of freedom for the language of implementation.
Sol-> The reason WSDL is not in english and is in XML is so that other programs can read this XML and generate function prototypes for developers. For example, microsoft provides WSDPrint.wsdl file which defines the functions for sending a print job to a webservice enabled printer. Programs like gSoap can read this WSDL and then create function stubs like CreatePrintJobRequest() and SendPrintJobRequest() with all the necessary parameters. The developer then just needs to implement the reuired portions inside the function and complete the implementation. A Java developer can also use this WSDL to create Java function stubs and so this gives a lot of freedom for the language of implementation.
Powered by ScribeFire.
No comments:
Post a Comment