Re: Consuming E1 web services -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: Consuming E1 web services
From: "James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>
Date: Wed, 30 Jul 2014 12:03:10 -0700
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On 7/30/14 11:15 AM, Charles Wilt wrote:

If it's a SOAP web service, does it have a WSDL?

http://jde_e1/myservice?WSDL

If so, that should be all you need.

Syntactically, yes. But semantically, . . . .

After all, a web service request (as I found out writing a few of my own to run under IWS, and having to check the IWS logs to figure out what I was doing wrong) can be syntactically perfect, and still be garbage.

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Consuming E1 web services , Jon Paris

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.