Well said.
I will also add that many have no idea when given a WSDL. I often hear
"OK. I generated my code from your WSDL. It does not work. What do I do
now?" This is almost always from .NET clients. This is not a dig (well,
maybe it is) but it's the truth.
Thanks,
Todd Allen
EDPS
Electronic Data Processing Services
tallen@xxxxxxxxxxxx
Kevin Turner
<kevin.turner@cor
altree.co.uk> To
Sent by: "'Web Enabling the AS400 /
web400-bounces@mi iSeries'" <web400@xxxxxxxxxxxx>
drange.com cc
Subject
2010-10-11 10:34 Re: [WEB400] Microsoft .NET
frontending IBM i
Please respond to
Web Enabling the
AS400 / iSeries
<web400@midrange.
com>
We use the simple XML approach (from a server perspective) for our IBMi web
services. We have also (as previously alluded) refer to them as RESTful.
The fact is that they are not really RESTful because they are not always
making direct use of the available verbs to perform the tasks - however we
get away with it because the definition of REST is a bit loose. The
problem arises when third party consumers of your simple XML web services
want your published WSDL or XML schema or whatever. People these days
expect to be supplied with a WSDL so that they can use it to generate their
proxy classes, effectively writing the web service client for them (or the
bulk of it). Give them documentation instead of a WSDL and they don't know
where to start.
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On
Behalf Of Aaron Bartell
Sent: 11 October 2010 15:17
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] Microsoft .NET frontending IBM i
You don't need to know a lot about WSDL's until you start developing
more complex data streams that talk to many different platforms and
languages. In the end, if you are offering public web services, you
will inevitably become familiarized with WSDL/XSD/XML because not
everyone does it like Microsoft. And then once you become familiar
with WSDL/XSD/XML and have to "debug" it for your customers, you will
inevitably say to yourself: why not simplify this approach to use HTTP
POST + simple XML (like I said earlier in this post).
Just my experience of the roughly 10yrs I have been doing web services
(with the last 6 years doing it almost fulltime).
Aaron Bartell
http://mowyourlawn.com
http://mowyourlawn.com/blog/
On Mon, Oct 11, 2010 at 8:22 AM, <TAllen@xxxxxxxxxxxx> wrote:
<shakes head>
I find it baffling that someone developing web services cannot interpret
or
read a WSDL or XML schema. It's not uncommon. I run into it all the
time.
Thanks,
Todd Allen
EDPS
Electronic Data Processing Services
tallen@xxxxxxxxxxxx
Richard Schoen
<richard@rjssoftw
are.com> To
Sent by: "web400@xxxxxxxxxxxx"
web400-bounces@mi <web400@xxxxxxxxxxxx>
drange.com cc
Subject
2010-10-11 09:09 Re: [WEB400] Microsoft .NET
frontending IBM i
Please respond to
Web Enabling the
AS400 / iSeries
<web400@midrange.
com>
Isn't that the point of object oriented development. Building black
boxes :-)
Just a minute. Let me get my hammer and chisel. Clang...Clang...
Ouch :-)
Try bending your mind around it and you might find that the better way it
to NOT hand code WSDL..... Clang...Clang...
Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business
Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site: http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
----------------------------------------------------
message: 9
date: Mon, 11 Oct 2010 09:00:20 -0400
from: TAllen@xxxxxxxxxxxx
subject: Re: [WEB400] Microsoft .NET frontending IBM i
Then I'd say you are working with a black box, letting the WSDL be
generated for you. That may work great, until you need to interpret or
read the WSDL or schemas while debugging or troubleshooting.
Thanks,
Todd Allen
EDPS
Electronic Data Processing Services
tallen@xxxxxxxxxxxx
This communication and any transmitted documents are intended to be
confidential. If there is a problem with this transmission, please contact
the sender. If the reader of this message is not the intended recipient, or
the employee or agent responsible to deliver it to the intended recipient,
you are hereby notified that any dissemination, distribution or copying of
this communication is strictly prohibited.
--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.
--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/web400.
NOTICE: The information in this electronic mail transmission is intended by
CoralTree Systems Ltd for the use of the named individuals or entity to
which it is directed and may contain information that is privileged or
otherwise confidential. If you have received this electronic mail
transmission in error, please delete it from your system without copying or
forwarding it, and notify the sender of the error by reply email or by
telephone, so that the sender's address records can be corrected.
--------------------------------------------------------------------------------
CoralTree Systems Limited
25 Barnes Wallis Road
Segensworth East, Fareham
PO15 5TT
Company Registration Number 5021022.
Registered Office:
12-14 Carlton Place
Southampton, UK
SO15 2EA
VAT Registration Number 834 1020 74.
This communication and any transmitted documents are intended to be confidential. If there is a problem with this transmission, please contact the sender. If the reader of this message is not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited.
midrange.com
