I have spent the last 3 hours attempting to create wse proxy classes
for (xmethods.com) web services using wsewsdl2.exe (SP2 & SP3).    The
results were amazing.

Out of 34 randomly selected WSDLs, only 6 were successful.  The vast
majority choked with "Specified cast is not valid" or "Invalid wsdl
file".   XmlSpy had no problem dealing with these wsdls, they were
parsed and messages were (automatically) created and invocations seemed
to work normally.

I assume i am asleep and will wake shortly to realize that this was
just a terrible nightmare.  But if not, can someone please comment on
this.  I get the distinct impression that I am alone in using WSE
because i have not been able to find any substantive record of others
complaining.  How can the success rate be only 20% and the MS
development community not be up-in-arms.

Now i understand that compatibility issues have plagued the market (web
services) for the past few years - I am not a polyanna. But <20%?  No
way! The the VS2003 version of wsdl.exe had a far better success
rate... maybe 70-80%.

I dont want to rant.  But I need help in deciding what to do with WSE.
Any answers (or even opinions) to the following questions would be
greatly appreciated.

1) Is the pitifully poor performance of (WseWsdl2.exe) a shock to
anyone?   Have others seen this problem or am i alone in my
frustration.

2) Can anyone explain why this is the case?

3) Is there anything i can do about it - other than code the proxies
myself.

4) Is WSE a real solution that Microsoft expects us to use in
production, or is it just a proof-of-concept, technology-preview,
stopgap measure that Microsoft is using to keep us busy while they
cookup the real solution?