Re: Microsoft .NET frontending IBM i

WSDL is a standard. The WSDL should define the service itself (endpoint,
operations, etc.) but not the data. The schemas do that and you still have
those even when using a straight POST.

Thanks,
Todd Allen
EDPS
Electronic Data Processing Services
tallen@xxxxxxxxxxxx




"Maurice O'Prey"
<Maurice.Oprey@xm
li5.com> To
Sent by: "'Web Enabling the AS400 /
web400-bounces@mi iSeries'" <web400@xxxxxxxxxxxx>
drange.com cc

Subject
2010-10-11 15:04 Re: [WEB400] Microsoft .NET
frontending IBM i

Please respond to
Web Enabling the
AS400 / iSeries
<web400@midrange.
com>

Aaron Bartell wrote
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. <snip>
you will inevitably say to yourself: why not simplify this approach to

use
HTTP

POST + simple XML (like I said earlier in this post).

Isn't that just prolonging the problem? Lazy programmers talking to other
lazy programmers?

I kind of thought WSDL was a standard? (if not lets go back to exchanging
CSV text files). One system to another (one system) is not an option.

Maurice O'Prey

-----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.