Simon Fell > Its just code
Just re-ran all the round 2 tests with the new serialization metadata support, things look really good, the errors in echoStructArray for a number of toolkits has gone. I'm pretty sure at this point all the remaining round 2 failures, are server problems, not PocketSOAP problems.
Yahoo glitch trips up e-mail. An outage on Yahoo Groups, a collection of discussion lists based on various interests, prevents millions of members from receiving e-mail from their cohorts. [CNET News.com] That explains why SOAPBuilders has been quiet all day.
Transcript of the recent Web Services Interop chat on MSDN.
Ari Pernick tries the WSDL BDG and finds that vs.net can't quite handle the result. I'll try it myself with vs.net in a bit and report back. Just some quick comments: if you want to see what to replace anyType with, just take a look at the values of xsi:type in the original messages. And in this case, there is only ONE output, it just happens to be a structure. [Sam Ruby's Radio Weblog] ok, so on the request side, the two parts can be s:string rather than s:anyType. For the response, you'll need a schema to describe the struct, something like
<s:element name="flerror" type="s:boolean"/>
<s:element name="message" type="s:string"/>
Then use this type as the type in the response message
<part name="return" type="types:pingResponse" xmlns:types="http://www.weblogs.com/" />
Garth says that my editor button bar problem is related to the theme. Not having much luck getting it fixed, I swapped themes, but my desktop site stayed on the big radio theme, I even checked that the #desktopWebsiteTemplate.txt had been updated, which it had. (I can't find the post, but I posted to the Radio DG about this a while back). Its odd that it works fine on W2k/IE5.5, have to try and find a W2K/IE6 machine to check it on.
Jon Udell - WSDL Interop Adventures