Simon Fell > Its just code > November 2004
So I just this in an email, is it legit? looks legit, contains pointers to pages on microsoft.com that mention the sending company, but the participate button takes you to www8.survey-poll.com not to surveysite. Trawling whois indicates that survey-poll is registered to surveySite in Canada. I think it's legit, but I'm not 100% sure, I actually did the survey, and the reason I'm still not sure, is that after 2 questions it asks you for your email address and seems to indicate that the survey is over (having not answered a single question yet about a Microsoft product). So, (Scoble, you out there?) is this legit and just a survey problem, or a good scam ? How am I supposed to differentiate this against other email that claims to be from Microsoft and isn't. If Microsoft wants me to take their survey (or anything else for that matter that comes in an email), the content better be hosted on www.microsoft.com, or its just not going to fly anymore.
Rich Salz gives WSDL 2.0 a good kicking, frankly the W3C's involvement in Web Services to date has been something of a fiasco in my mind, Soap 1.2 took way too long, now WSDL 2.0 is a mess, Its going to be a long time before either of these become relevant if they ever do.
If you're interesting in doing outbound & inbound compression from a .NET web services client without having to modify any WSDL generated code, check out this tech note on sforce.
Its entirely possible that I'm missing something, but it appears that what seems to me to be the most obvious use case for EndpointReferences is not supported in WSE 2.0.
It seems to me that the most obvious way to get an EndpointReference is to make a soap call to get one, but WSE 2.0 doesn't seem to support this, if I write a service that returns an EndpointReference object, then trying to generate the WSDL will choke with a reflection error. I manually hacked up a WSDL that included a EPR element in its return, and wseWsdl2.exe choked on trying to generate that operation. Is this a WSE problem, is this a WS-Addressing problem ? (there's no XSD schema in the spec, there's no mention of how it fits with WSDL), or did I just miss something ? What does an operation that returns an EPR look like in WSDL ?
While I'm griping about WSE2.0, its a pity the docs don't call out exactly which version of specs it supports, it includes a link to the WS-Addressing spec, but that link now holds the Aug 2004 rev of the spec, which WSE 2.0 most certainly does not implement.