Lost in history

Blogs focused on WWSAPI: the new native web services stack from Microsoft

June, 2009

  • Lost in history

    Common WWSAPI errors: wrong property value size

    • 0 Comments
    WWSAPI properties are designed to control the behavior of the WWSAPI objects like service proxy, channel, XML reader/writer, etc. Each property has a property id, an associated value type, a target object and allowed actions. All property structures have...
  • Lost in history

    WWSAPI to WCF interop 10: WsUtil.exe, the silver bullet

    • 1 Comments
    In my previous post on interoperating with WCF BasicHttpBinding endpoint , I explained that you had to set the channel properties to match SOAP version and addressing version on the server side. Wouldn’t it be great if you don’t have to do all that? That...
  • Lost in history

    Common WWSAPI errors: addressing version mismatch

    • 1 Comments
    WWSAPI supports two WS-Addressing versions: the existing W3C recommendation version ( 1.0 ) and the older 2004/08 version ( 0.9 ). WS-Addressing defines a set of SOAP headers to describe the message recipient, targeted action and some other basic messaging...
  • Lost in history

    Common WWSAPI errors: SOAP version mismatch

    • 0 Comments
    There are two versions of SOAP supported by WWSAPI and most other web services stacks: SOAP 1.1 and SOAP 1.2 . Although the basic message layout in the two SOAP versions is the same (Header and Body inside Envelope), there are three main differences:...
Page 1 of 1 (4 items)