Sam Ruby's approach to bridging SOAP and raw XML over HTTP

After listening to my keynote at the Applied XML DevCon, Sam posted this idea for a way to bridge XML over HTTP and SOAP. The basic model is to make a message receiver do one of two things:

- Convert from SOAP to raw XML by removing the Envelope/Body if there is not Envelope/Header
- Convert from raw XML to SOAP by adding an Envelope/Body and an empty Envelope/Header

If all message receivers did this, we could go between SOAP messages without headers and raw XML transparently. Sam proposes making this SOAP 1.3, but I don't know if we really need to do that. We might just be able to build this functionality into clients and services.

You could carry this idea further and build a service that maps an HTTP GET with a querystring to an XML document with SOAP around it if desired.

I like it.


Posted Oct 21 2004, 04:15 PM by tim-ewald

Comments

kesav wrote re: Sam Ruby's approach to bridging SOAP and raw XML over HTTP
on 10-22-2004 9:32 AM
I am developing a similar architecture for my SOA needs. I am mimicing java axis with method signature

public Document executeService(Document input);

but I modify my WSDL generation mechanism to throw proper schema information. So when I get raw XML i could use command pattern to execute the actual application logic. This will give me a roubust SOA development with less no.of web methods to expose. With the current approach of tight coupling with WebMethod syntax and WSDL generation we are forced to have static signatures and static class definition corresponds to XML schema. If we can decouple WSDL generation mechanism and allow raw XML to pass then a generic service execution layer can be built.

-kesav
IFTF's Future Now wrote Google Maps: A Step Towards a Worldwide Atlas
on 03-12-2005 2:31 PM
There's a very interesting, modestly technical explanation on engadget.com on how to make your own annotated multimedia Google maps. While creating your own google maps a very cool new hack, It will be interesting to see how Keyhole and Google geonotes, gpstracks, and locative media, can be -combined- and -shared- worldwide; and how we'll share -all- attributes geodata layers and media, for any given place: art, media, cultural, social, historical, infrastructure, physical,etc. So far, with a few major obvious exceptions, a lot of geoweb experimentation still seems to be on discrete, non-interoperable, maps, atlases, location services, and locative media experiences - even where exercising new semantic web techniques using xml/gml/wfs and xml/rdf/, xml/svg. etc. I am very encouraged by Sam Ruby's approach to bridging Soap and raw xml over http: This gives me some hope for a future of blended hypermedia and geodata, Since most of our hardcore mainstream GIS brothers and sisters seem to be buying into soap/uddi web services big time. The legacy worldwide web is mostly encyclopedic, let's hope the new semantic geospatial web can, ideally become a worldwide altas of interoperable mdia and layers and wiki atlas of contextual media....

Add a Comment

(required)  
(optional)
(required)  
Remember Me?