Simon Fell > Its just code
Making solid progress on the attachments support, I've got SwA working with Apache SOAP 2.2, Apache Axis and IONA's XMLBus, tried but failed with GLUE, which appears to be a bug on their end [they expect a content-length header, which is optional]. Also got some DIME support put together [My thanks to David Buksbaum for the DIME packaging code]. Anyone got a server with DIME support i can bounce some messages off ?
Back to the UDDI discussion, "For instance: my user inputs customer data for my CRM app, and I use a service to send the data. If the server is down, or unavailable, wouldn't using UDDI to find the nearest store-and-forward or caching service be a good idea? This is just off the top of my head. Transport agnostic roll-over seems like a huge win, IMO.". Hmmmmm, have to think about this one, off the top of my head, I would say if you have a reliable store and forward transport [my particular favourite being MSMQ], why would you even bother with the initial HTTP attempt ?
I just posted some comments on the current draft SOAP 1.2 encoding spec.
DaveNet: DIY Web Services. As Dave points out Radio supports both XML-RPC and SOAP, but unfortuantly fails to tell you enough to actually make a SOAP call, after a few guesses [starting from Sam's captured request], I figured out what a valid request should look like, here's a PocketSOAP generated request [captured with the ever faithful proxyTrace]
POST http://localhost:5335/ HTTP/1.1
Content-Type: text/xml; charset=UTF-8
Accept-Charset: UTF-8, UTF-16
And the VB code to generate it
Revised WSDL 1.1 Schema's posted.