2.5.4.5 Protocol-Specific Details

Using remote operations (ROPs)

Creating a strongly typed message by using ROPs

Figure 12: Creating a strongly typed message by using ROPs

Note The ROPs are sent via RPC or MAPI extensions for HTTP. Several ROPs can be batched into a single request, as described in [MS-OXCROPS].

  1. The client creates a message per the use case described in section 2.5.3.

  2. The client prepares a list of property-value pairs that will be set on the message. The property-value pairs include the message class and the required properties associated with the specific message class value.

  3. The client issues a RopSetProperties ROP request ([MS-OXCROPS] section 2.2.8.6) to the Exchange server to set the property-value pairs on the message.

  4. The Exchange server returns success or failure of the operation.

  5. The client issues a RopSaveChangesMessage ROP request ([MS-OXCROPS] section 2.2.6.3) to the Exchange server to persist the changes.

  6. The Exchange server returns success or failure of the save operation. This operation can fail when any of the required properties associated with the selected message class are not present.

Using Exchange ActiveSync

Creating a strongly typed message by using Exchange ActiveSync

Figure 13: Creating a strongly typed message by using Exchange ActiveSync

  1. The client creates a new message per the use case described in section 2.5.3.

  2. The client prepares a list of XML schema item-value pairs to be set on the message. The item-value pairs include the XML schema class name that corresponds to the kind of strongly typed message that is desired and the required items associated with the specific schema class.

  3. The client uses the Sync command request ([MS-ASCMD] section 2.2.2.21) with an Add element, as described in [MS-ASCMD] section 2.2.3.7.2, to add the required schema items to the message.

  4. The Exchange server responds with HTTP status code 200 (OK).

Using Exchange Web Services

Creating a strongly typed message by using Exchange Web Services

Figure 14: Creating a strongly typed message by using Exchange Web Services

  1. The client uses the HTTPS/SOAP CreateItemSoapIn request WSDL message, as described in  [MS-OXWSMSG] section 3.1.4.2, to create a new message item in the specified folder. The Message element contains the properties and child elements that specify the message class and the required properties associated with the specified message class.

  2. The Client Access server responds with a CreateItemSoapOut response WSDL message, as described in [MS-OXWSMSG] section 3.1.4.2, which includes a ResponseCode element specifying the status of the operation and an ItemId element whose value uniquely identifies the new message.

Show: