http://www.endeca.com/MDEX/conversation/1/0
The Request Complex Type
The Request type contains a a state describing the records to be selected and how they are viewed and multiple content element configurations to describe what summarizations are to be performed. Both the state and the content element configurations are first transformed by the specified operators, which describe how a request to the MDEX is to differ from the prior request. Typically, a Request is constructed from the Results returned by a previous invocation. The State and ContentElementConfig elements are obtained from the Request element in the prior Results. The Operator sequence will usually be obtained by choosing embedded operators from the ContentElement sequence in the prior Results. The requester may also attach arbitrary XML to the request via the PassThrough element, to be returned unchanged in the response.
Local elements (5)
OuterTransactionId State Operator ContentElementConfig PassThrough
Complex Type Request
The Request type does not allow mixed content. There is no restriction on type derivation. 
 CollapseClick here to hide comment XML Instance
<...>
-Begin Sequence [1...1]
<OuterTransactionId>cs_v1_0:NonEmptyString</OuterTransactionId> [0..1]
<State>cs_v1_0:State</State> [1..1]
<Operator>cs_v1_0:Operator</Operator> [0..*]
<ContentElementConfig Id="cs_v1_0:NonEmptyString"Click here to hide Comment This attribute is required. HandlerNamespace="cs_v1_0:NonEmptyString"Click here to hide Comment This attribute is required. HandlerFunction="cs_v1_0:NonEmptyString"Click here to hide Comment This attribute is required.>cs_v1_0:ContentElementConfig</ContentElementConfig> [0..*]
<PassThrough>cs_v1_0:CatchAll</PassThrough> [0..1]
End Sequence
</...>

 Collapse Attributes

Name Type Summary
No Attributes

 Collapse XML
-<complexType  name="Request">
-<annotation>
-<documentation>
The
<code>Request</code>
type contains a a state describing the records to be selected and how they are viewed and multiple content element configurations to describe what summarizations are to be performed. Both the state and the content element configurations are first transformed by the specified operators, which describe how a request to the MDEX is to differ from the prior request. Typically, a
<code>Request</code>
is constructed from the
<code>Results</code>
returned by a previous invocation. The
<code>State</code>
and
<code>ContentElementConfig</code>
elements are obtained from the
<code>Request</code>
element in the prior
<code>Results</code>
. The
<code>Operator</code>
sequence will usually be obtained by choosing embedded operators from the
<code>ContentElement</code>
sequence in the prior
<code>Results</code>
. The requester may also attach arbitrary XML to the request via the
<code>PassThrough</code>
element, to be returned unchanged in the response.
</documentation>
</annotation>
-<sequence>
<element  minOccurs="0"  name="OuterTransactionId"  type="cs_v1_0:NonEmptyString" />
<element  name="State"  type="cs_v1_0:State" />
<element  maxOccurs="unbounded"  minOccurs="0"  name="Operator"  type="cs_v1_0:Operator" />
<element  maxOccurs="unbounded"  minOccurs="0"  name="ContentElementConfig"  type="cs_v1_0:ContentElementConfig" />
<element  minOccurs="0"  name="PassThrough"  type="cs_v1_0:CatchAll" />
</sequence>
</complexType>

 Collapse Uses
 Collapse Used-By
 Collapse Element (2)
 
Generated by WSDLdoc ©