Thorbjørn,

I have been around data exchange in 25+ years, from EDIfact to XML
and there is a lot of technology stuff that overcomplicate things -
try to sit in an European standardization process - whatever you make
always ends up in some sort of bilateral agreement between customers.

If anybody think that you just can code a EDIfact 96A based Invoice
based on the UN standards and shoot it into a SAP installation and
it will understand it - they have to think again.

The same goes for webservices - it looks like the promised land just
to run it up against a WSDL - in fact it is completly unnessacary.

When you recieve a XML message, who cares if this message also contains
a greeting to the senders grandmother in a version 5.1 - as long as it
holds it syntax and as long you can retrieve the data you need.

I do RAWREADING - that is to read the XML-tree raw and search what you
are looking for, you may include any <laurelAndHardy> or <donaldDuck>
segments wherever you please, who cares as long as you send the vital
data in segments that is understandable in the hirachical file structure

Henrik




Thorbjoern Ravn Andersen <ravn@xxxxxxxxxx>
Sent by: web400-bounces@xxxxxxxxxxxx
21-04-2010 22:01
Please respond to
Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx>


To
Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx>
cc

Subject
Re: [WEB400] Why use PHP? What are the disadvantages?






Den 21/04/10 22.17, hr@xxxxxxxxxxxx skrev:
Nope, that is Scott's ballgame - but powerEXT Core does write and reads
XML in very few
statements across HTTPAPI (client services) and CGIDEV2 (server
services)
(as well as
JSON etc.)

Ok, but I am pretty certain I will need SOAP :(

If not, I'll have a closer look.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.