As mentioned in my previous post , WWSAPI follows a common pattern to set properties (which in most cases are just configuration settings). Each property structure consists of three fields: id , value and valueSize . The field id is an enum value of the property. The enum value has a corresponding type...

When you use WsUtil to generate stub code and then work with the generated structures, you may get E_INVALIDARG when making the call to the service and, with WWSAPI tracing turned on, see the error message “ A NULL WS_STRUCT_DESCRIPTION was specified. ”. WS_STRUCT_DESCRIPTION is one of the WWSAPI...

One of the design principles of WWSAPI is to be very stringent at the API contract, as we believe ambiguous or loose API contract does not help developers write high quality applications. Being stringent means not only to document the API contract clearly, but also to enforce at runtime that the contract...

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 the same set of fields: a property id, a pointer...

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 information. When HTTP transport is used, WWSAPI...

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: the namespace, the content type for HTTP binding and...