title: web services api: to wrap or not to wrap?
body: <p>When providing a web services API (well, let's say SOAP), do you provide a library wrapper along with it to make it "easier" for people to use?  Or do you just package up a WSDL and documentation for it and let people figure out what to do with it?</p>
  
  <p>What are people doing usually?  I've seen a bunch of examples where the wrapper is provided, but it has always seemed counter-productive to me.</p>