Nelson's Weblog: tech / webservices

Document/literal SOAP

One thing people who hate SOAP say is that the XML for SOAP is ugly. That used to be a problem because of rpc/encoded style. But thanks mostly to WS-I the SOAP community has moved on to the simpler document/literal.

The nice thing about doc/lit is that it's really just any ol' XML message with two SOAP tags wrapped around it. SOAP says very little about what's inside your message, just that it should have a namespace and it should be describable via XML Schema. Here's an example:

<?xml version='1.0' encoding='UTF-8'?>
<soap:Envelope>
  xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
  xmlns="http://example.com/myAppSchema">
  <soap:Header>
    <username>nelson</username>
    <password>ossifrage</password>
  </soap:Header>
  <soap:Body>
    <purchase>
      <product>Soul Harvest</product>
      <isbn>0842329250</isbn>
    </purchase>
  </soap:Body>
</soap:Envelope>

The stuff in black is the app's data. The rest is what you need to turn some random XML into a SOAP message.

Even those two SOAP tags might seem like too much, but they give you a couple things. The headers give you a transport-neutral way to add header metadata to a message, and SOAP Faults (not shown) give you a structured way to indicate detailed errors.

If you're comfortable parsing XML, you're comfortable parsing doc/lit SOAP. But SOAP also offers the possibility of automatic data bindings (no parsing required) and WSDL (service description). Alas, those technologies still don't work so well in Perl, Python, or PHP where doc/lit support is weak. It does work pretty well in Java and .NET.

tech • webservices
2004-09-12 16:48 Z


Mastodon @nelson@tech.lgbt Linkblog Sun 2024-11-17 City99 console font Sat 2024-11-16 Lorraine Gervais Sill Justin's Linklog Thune 2004 blog campaign Fri 2024-11-15 Open source garage door Thu 2024-11-14 NZ parliament protest Wed 2024-11-13 bzfs BenQ Programming Monitor Tue 2024-11-12 California slow vote counting Sand pile visualization Miniflux The Animal in Decorative Art Mon 2024-11-11 MyNoise Criterion Collection Supercut Sun 2024-11-10 ActivityBot Chair causes display failure Neft Daşları Fri 2024-11-08 Self-hosted Bluesky Red crab migration Search Archives 2023 12 11 10 09 08 07 06 05 04 03 02 01 2022 12 11 10 09 08 07 06 05 04 03 02 01 2021 12 11 10 09 08 07 06 05 04 03 02 01 2020 12 11 10 09 08 07 06 05 04 03 02 01 2019 12 11 10 09 08 07 06 05 04 03 02 01 2018 12 11 10 09 08 07 06 05 04 03 02 01 2017 12 11 10 09 08 07 06 05 04 03 02 01 2016 12 11 10 09 08 07 06 05 04 03 02 01 2015 12 11 10 09 08 07 06 05 04 03 02 01 2014 12 11 10 09 08 07 06 05 04 03 02 01 2013 12 11 10 09 08 07 06 05 04 03 02 01 2012 12 11 10 09 08 07 06 05 04 03 02 01 2011 12 11 10 09 08 07 06 05 04 03 02 01 2010 12 11 10 09 08 07 06 05 04 03 02 01 2009 12 11 10 09 08 07 06 05 04 03 02 01 2008 12 11 10 09 08 07 06 05 04 03 02 01 2007 12 11 10 09 08 07 06 05 04 03 02 01 2006 12 11 10 09 08 07 06 05 04 03 02 01 2005 12 11 10 09 08 07 06 05 04 03 02 01 2004 12 11 10 09 08 07 06 05 04 03 02 01 2003 12 11 10 09 08 07 06 05 04 03 02 01 2002 12 11 10 09 08 07 06 05 04 03 02 01 2001 12 11 10 09 08 07 One good site MDN Nelson Minar nelson@monkey.org Blog licensed under a Creative Commons License		Document/literal SOAP One thing people who hate SOAP say is that the XML for SOAP is ugly. That used to be a problem because of rpc/encoded style. But thanks mostly to WS-I the SOAP community has moved on to the simpler document/literal. The nice thing about doc/lit is that it's really just any ol' XML message with two SOAP tags wrapped around it. SOAP says very little about what's inside your message, just that it should have a namespace and it should be describable via XML Schema. Here's an example: <?xml version='1.0' encoding='UTF-8'?> <soap:Envelope> xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns="http://example.com/myAppSchema"> <soap:Header> <username>nelson</username> <password>ossifrage</password> </soap:Header> <soap:Body> <purchase> <product>Soul Harvest</product> <isbn>0842329250</isbn> </purchase> </soap:Body> </soap:Envelope> The stuff in black is the app's data. The rest is what you need to turn some random XML into a SOAP message. Even those two SOAP tags might seem like too much, but they give you a couple things. The headers give you a transport-neutral way to add header metadata to a message, and SOAP Faults (not shown) give you a structured way to indicate detailed errors. If you're comfortable parsing XML, you're comfortable parsing doc/lit SOAP. But SOAP also offers the possibility of automatic data bindings (no parsing required) and WSDL (service description). Alas, those technologies still don't work so well in Perl, Python, or PHP where doc/lit support is weak. It does work pretty well in Java and .NET. tech • webservices 2004-09-12 16:48 Z Nelson's Weblog • tech • webservices