element <updateBlock> (local)

complex, 2 attributes, 3 elements

locally within updateRequestType complexType in hsdl.xsd; see XML source

XML Representation Summary

("rollbackBlockAndFail" | "rollbackBlockAndContinue" | "ignore")

Content model elements (3):

Included in content model of elements (1):

XML Source (see within schema source)

<xsd:element maxOccurs="unbounded" minOccurs="1" name="updateBlock" type="updateBlockType">

<xsd:annotation>

<xsd:documentation>

A sequence of operations grouped by a common context in the XML document sharing
the same failure semantics.

</xsd:documentation>

</xsd:annotation>

Attribute Detail (all declarations; 2/2)

anonymous simpleType (restriction of xsd:string)

locally within updateBlockType complexType

This attribute controls how error conditions raised by individual operations within an updateBlock affect the entire updateRequest message. Error conditions can trigger one of the following actions: <dl> <dt>rollbackBlockAndFail</dt> <dd> If any operation within the updateBlock fails, all enclosed operations are rolled back to their initial state and the updateRequest ends in a failure condition. </dd> <dt>rollbackBlockAndContinue</dt> <dd> If any operation within the updateBlock fails, all enclosed operations are rolled back to their initial state and execution proceeds to the next updateBlock. </dd> <dt>ignore</dt> <dd> Failures within an individual updateBlock do not trigger a rollback or a failure in the updateRequest. A failure simply terminates execution of the updateBlock. Successful operations are tagged in the updateResponse. Execution continues at the next updateBlock. </dd> </dl>

Anonymous simpleType

restriction of xsd:string

XML Source (see within schema source)

<xsd:attribute name="onError" use="required">

<xsd:annotation>

<xsd:documentation>

This attribute controls how error conditions raised by individual operations
within an

updateBlock

affect the entire

updateRequest

message. Error conditions
can trigger one of the following actions:

<dl>

<dt>

rollbackBlockAndFail

</dt>

<dd>

If any operation within the

updateBlock

fails, all enclosed operations
are rolled back to their initial state and the

updateRequest

ends in a
failure condition.

</dd>

<dt>

rollbackBlockAndContinue

</dt>

<dd>

If any operation within the

updateBlock

fails, all enclosed operations
are rolled back to their initial state and execution proceeds to the
next

updateBlock

</dd>

<dt>

ignore

</dt>

<dd>

Failures within an individual

updateBlock

do not trigger a rollback
or a failure in the

updateRequest

. A failure simply terminates execution
of the

updateBlock

. Successful operations are tagged in the

updateResponse

.
Execution continues at the next

updateBlock

</dd>

</dl>

</xsd:documentation>

</xsd:annotation>

<xsd:simpleType>

<xsd:restriction base="xsd:string">

<xsd:enumeration value="rollbackBlockAndFail"/>

<xsd:enumeration value="rollbackBlockAndContinue"/>

<xsd:enumeration value="ignore"/>

</xsd:restriction>

</xsd:simpleType>

locally within updateBlockType complexType

This item specifies an XPath expression that establishes global context for this updateBlock. The selection must specify an xdb:blue. With this context established, the enclosed operation's select attributes select nodes within this global context. It is not an error to match zero nodes with this select attribute. The empty node set is simply the context for the enclosed operations, and their minOccurs and maxOccurs attributes dictate success or failure.

XML Source (see within schema source)

<xsd:attribute name="select" type="string" use="required">

<xsd:annotation>

<xsd:documentation>

This item specifies an XPath expression that establishes global context
for this

updateBlock

. The selection must specify an

xdb:blue

.
With this context established, the enclosed operation's

select

attributes select nodes within this global context. It is not
an error to match zero nodes with this

select

attribute. The empty node set is simply
the context for the enclosed operations, and their

minOccurs

and

maxOccurs

attributes
dictate success or failure.

</xsd:documentation>

</xsd:annotation>

Content Element Detail (all declarations; 3/3)

deleteRequestType, complex content

locally within updateBlockType complexType

XML Source (see within schema source)

<xsd:element maxOccurs="unbounded" minOccurs="0" name="deleteRequest" type="deleteRequestType"/>

insertRequestType, complex content

locally within updateBlockType complexType

XML Source (see within schema source)

<xsd:element maxOccurs="unbounded" minOccurs="0" name="insertRequest" type="insertRequestType"/>

replaceRequestType, complex content

locally within updateBlockType complexType

XML Source (see within schema source)

<xsd:element maxOccurs="unbounded" minOccurs="0" name="replaceRequest" type="replaceRequestType"/>

Namespace:	http://schemas.microsoft.com/hs/2001/10/core
Type:	updateBlockType
Content:	complex, 2 attributes, 3 elements
Defined:	locally within updateRequestType complexType in hsdl.xsd; see XML source

Type:	anonymous simpleType (restriction of xsd:string)
Use:	required
Defined:	locally within updateBlockType complexType

Type:	string
Use:	required
Defined:	locally within updateBlockType complexType