I agree with this advice, I would advise you to stay away from SOAP unless you absolutely cannot avoid it for some reason, and even then. It is worth noting that a number of the high profile public web services that deployed SOAP support a few years ago, such as Amazon, have subsequently abandoned it, and moved to simpler and more robust protocols using REST, XMLRPC, and/or JSON.
On Fri, Apr 9, 2010 at 3:57 PM, Geoff Crawford <[email protected]> wrote: > At 03:45 PM 4/9/2010, Chris Freyer wrote: > >> Hi all. I'm new to OpenLaszlo but not to web apps or UI design. >> >> I'm attempting to consume some of my own web services from an OL >> frontend. The web services are just EJBs that are exposed using Java >> EE's "@WebService" annotation. I'm attempting to use the <soap> tag, >> but there seems to be a lot of XML overhead on the OL side. Am I >> missing something? Is there a simple way to do it? Should I prefer >> the <javarpc> tag instead? Any best practice info appreciated. >> >> FYI: This is a new project, and I don't have to use EJBs. Its just >> an easy way to generate XML-based services. >> > > Have you looked at the full SOAP spec? It's not just that > there's overhead in the XML, which by the way is there in > *any* consumer because the WSDL is passed across. There's > the whole overhead of building the responses from the > prototype's. There's very little simple when it comes > to SOAP. You'll be a lot happier if you want something > trimmer with JRPC, but you may be happiest with the > fullest set of functionality with some kind of JSON > interface. But that's up to you. > > > ======================================================================= > Geoff Crawford Phone: (973) 361 - 4224 > Innov8 Computer Solutions, LLC FAX: (973) 537 - 6946 > 711 Route 10 East, Suite 204 Email: [email protected] > Randolph NJ 07869 Web: http://www.processwareerp.com > > ProcessWare ERP for the Chemical Industry > > -- Henry Minsky Software Architect [email protected]
