Again,
Thank you for the clarification.
I now understand that in the examples given below, that some of the
services do nothing more than report data that does not require a
parameters - such as customer or product lists.
I would strongly recommend that a WSDL be provided for all
services.From a developer perspective, it would simplify what services
are available, what parameters, and what the output would be.
Generally code gets updated much quicker than documentation, so the
WSDL would always be in concert with the version of the services being
provided.
On Jun 2, 12:44 pm, Larry <
Larry.Erick...@gmail.com> wrote:
> >The goal of Datafusion documentation is to provide the urls where a companies web service is located, the Restful methods used to call these urls, and examples of the xml messages responses you are expected to get back. A typical WSDL file is not required, but can be given if wanted. All of the documentation provided by Etech, Milnor, and Chicago contains the information you need. For example in Etechs DFetechTunnelCommunicationWebService.doc it explains that Etech provides a url \etech\dataFusion\tunnelcommunications which can be called with an HTTP GET request and returns xml. On a jobsite this currently would exist athttp://railpro1/etech/datafusion/tunnelcommunications, but this could change as network configurations sometimes vary job to job. This url does not take any parameters. None of Etech web services currently take parameters, although they may in the future.
>
> Milnor gives examples such as
> GEThttp://mildata1/datafusion/service.asmx/DFcustomerListreturns the
> > documentation?- Hide quoted text -
>
> - Show quoted text -