Simon Fell > Its just code
James got my point, but we disagree on the fix, I'd rather WSDL was fixed, than we work around it with tool support.
Patrick Logan Writes : Fortunately the tools I use write the WSDL for me. I have to write the interface in Java first, which is significantly less of a pain than writing WSDL. That certainly works, and I've been known to do something similar myself, but either your tools have to have a really good set of defaults, or you have to understand what its generated, and tweak as necessary.
I'm trying to get Radio to subscribe to the ThinkGeek what's new file, but it won't take it. Not sure why, its RSS 0.91, so it should work, right ?
James, I think you might be missing my point, I agree that the correct approach is to write the WSDL first, the write the server and/or client code from that. But for any non-trivial service, writing the entire WSDL by hand [even with a good xml editor] is painful and error prone. For one of the projects I'm working on, we manually write the XSD schemas for the messages [the Schema editor in XmlSpy is great for this], and then we have a simple XML file that details the rest of the info, this makes it easy to author the interface before the implementation. Finally we have a little tool that glues it all together and spits out a WSDL version.
Grrrhhhhhghhghghgh, it appears that in fixing the empty array bug, I introduced another bug. If you're using arrays, then i'd skip the 1.2.2 release and wait for the next one.