Are you agreeing with me? I said that WSDL is used when you need
standardization (that would be the traditional web service space), and
JSON/REST is good when you don't need standardization. I'm not sure,but yes
indeed you might actually be agreeing with me...
Yep, based on that statement I think we are in agreement.
Do you have any idea how annoying statements like that are?
Yes, actually I would imagine they are quite annoying. Sounds like we are
both annoying so let's get to the details...
I have the time, I just have a hard time trying to justify giving you yet
another EGL tutorial when you can't be bothered to figure it out yourself.
That is the same as me saying you haven't taken the time to do the
equivalent in RPG or PHP. We will let this argument slip lower on the
priority list for now.
You haven't even bothered to answer the basics: is this an XML/SOAP
request? JSON/REST? What?
Good point, let's set the stage for how I see many web services working
these days. Note this is just my experience and I am sure everyone has
different opinions and experiences in this space.
For 99.9% of all web services we have XML and HTTP being used. Of those I
would say roughly 95% use XSD's to define the "rules". Of those I would say
around 60% use SOAP (and nearly 100% of SOAP web services use WSDL's). For
the other 40% a variety of methods are used including what I am about to
document here. Note that these are NOT web services where you have control
over both ends of the spectrum.
In an effort to keep things in "real world complexities" we will take the
XSD to repeating structures on both the request and response vs. doing
helloworld type services (i.e. header and detail type scenario). The basic
premise will be to use the XSD to document what the request and response
look like. The composed XML will be occupied from hard-coded values as that
isn't what we are testing here. The web service will expect an HTTP POST
with non-SOAP XML as it's content (again we are not using WSDL and thus will
not be using SOAP as it unnecessary overhead). The response needs to be
parsed into the languages native data types per the schema.
If you are willing to engage in such a comparison of EGL vs. Java. vs. RPG
vs. PHP I will do the work of putting together the XSD and the web service
to call. Your responsibility would be EGL and I can do the Java and RPG (we
would need a volunteer for PHP as I don't have a dev environment setup for
that at the moment). The purpose of this is to see what is required of each
language environment to invoke a common web service.
Let me know if you are game...