|
Updated: 9/1/2002; 7:03:27 PM.
 |
Wednesday, January 23, 2002 |
In response to this, tav writes: someone please tell sam that google has been doing this for a long time now... i've noticed it on around 0.3% (totally random number ;p) of google searches. Got it, thanks! Kinda freaked me out when I saw it, but as a low frequency random sample kinds thing, it seems OK.
8:36:03 PM 
|
|
Jon Udell writes:
Richer descriptions of messages, and tools that exploit those richer descriptions, will make life even better for "mom" -- if this extra sophistication doesn't gum up the works.
Is WSDL gum, or grease, or maybe a little of both?
Answer: WSDL is a roadmap. Both gum or grease need to actually touch the moving parts to have an affect. WSDL does neither. Look at a SOAP message and try to find the reference to the WSDL. It isn't there. Never has been. Look at the SOAP specification and try to find the reference to a WSDL. It isn't there either.
 Look at a bridge. Imagine the architectural drawings that came first and greatly influenced the construction. Can you imagine a bridge of any significance being built without a roadmap?
Many SOAP stacks these days come with automatic roadmap dispensers. Simply append a "?WSDL" to the URL and out pops the description of the service. Many alpha males will tell you that they don't need to ask for directions. But I suspect that these roadmap dispensers will be heavily used.
4:17:55 PM
|
|
It looks like there is motion to resolve the two proposals vying for the title of the design for the next major release of Ant. I gave some advice on how to resolve this, and made an offer of assistance.
9:43:24 AM
|
|
What? Could there possibly be yet another Apache SOAP implementation looming in the near future? It looks like HP is looking to donate a cousin to their HP SOAP implementation to Apache. From what I can tell so far, they have better integration with Cocoon, and weaker support for things like references to values. Looks like there might be a good possibility for synergy...
I especially like the consise statement of their requirements:
- Required use of existing standards rather than proprietary solutions
- Required flexibility and extensibility that allows adding/removing stages of processing
- Required Plug and Play support that enables the customization of processing
8:49:26 AM
|
|
Simon Fell says that he found the building and running of Axis to be pretty painless; What more can a person ask for?  He's looking to test out SOAP Messages with Attachments support for interop with pocketSOAP.
Speaking of interop, it looks like I've not updates the Apache SOAP interop test to run against the latest 4s4c endpoint and the old endpoint has been removed. Time to update the test script and rerun...
8:36:42 AM
|
|
|
