http://www.endeca.com/MDEX/conversation/1/0
The State Complex Type
The State type contains inputs that affect the set of records to operate on. Currently it just contains all filters (including selected refinements). Clients should usually not construct this themselves, except for the initial empty state -- instead they should provide operators to be used by the service to transform the state.
Local elements (9)
SelectedRefinementFilter SearchFilter RecordFilter RecordKind DataSourceFilter DataSourceFilterString SelectionFilter SelectionFilterString RangeFilter
Complex Type State
The State type does not allow mixed content. There is no restriction on type derivation. 
 CollapseClick here to hide comment XML Instance
<...>
-Begin Sequence [1...1]
<SelectedRefinementFilter Name="cs_v1_0:NonEmptyString"Click here to hide Comment This attribute is required. Spec="cs_v1_0:NonEmptyString">cs_v1_0:SelectedRefinementFilter</SelectedRefinementFilter> [0..*]
<SearchFilter Key="cs_v1_0:NonEmptyString"Click here to hide Comment This attribute is required. RelevanceRankingStrategy="cs_v1_0:NonEmptyString" Mode="cs_v1_0:SearchMode" EnableSnippeting="boolean" SnippetLength="unsignedLong">cs_v1_0:SearchFilter</SearchFilter> [0..*]
<RecordFilter Name="cs_v1_0:NonEmptyString"Click here to hide Comment This attribute is required.>cs_v1_0:RecordFilter</RecordFilter> [0..*]
<RecordKind>cs_v1_0:RecordKind</RecordKind> [0..*]
-Begin Choice [0...1]
<DataSourceFilterString>cs_v1_0:NonEmptyString</DataSourceFilterString> [1..1]
End Choice
-Begin Choice [0...1]
<SelectionFilterString>cs_v1_0:NonEmptyString</SelectionFilterString> [1..1]
End Choice
<RangeFilter AttributeName="cs_v1_0:NonEmptyString"Click here to hide Comment This attribute is required.>cs_v1_0:RangeFilter</RangeFilter> [0..*]
End Sequence
</...>

 Collapse Attributes

Name Type Summary
No Attributes

 Collapse XML
-<complexType  name="State">
-<annotation>
<documentation> The State type contains inputs that affect the set of records to operate on. Currently it just contains all filters (including selected refinements). Clients should usually not construct this themselves, except for the initial empty state -- instead they should provide operators to be used by the service to transform the state. </documentation>
</annotation>
-<sequence>
<element  maxOccurs="unbounded"  minOccurs="0"  name="SelectedRefinementFilter"  type="cs_v1_0:SelectedRefinementFilter" />
<element  maxOccurs="unbounded"  minOccurs="0"  name="SearchFilter"  type="cs_v1_0:SearchFilter" />
<element  maxOccurs="unbounded"  minOccurs="0"  name="RecordFilter"  type="cs_v1_0:RecordFilter" />
<element  maxOccurs="unbounded"  minOccurs="0"  name="RecordKind"  type="cs_v1_0:RecordKind" />
-<choice  minOccurs="0">
<element  name="DataSourceFilter"  type="lql_parser_types:StandaloneFilter" />
<element  name="DataSourceFilterString"  type="cs_v1_0:NonEmptyString" />
</choice>
-<choice  minOccurs="0">
<element  name="SelectionFilter"  type="lql_parser_types:StandaloneFilter" />
<element  name="SelectionFilterString"  type="cs_v1_0:NonEmptyString" />
</choice>
<element  maxOccurs="unbounded"  minOccurs="0"  name="RangeFilter"  type="cs_v1_0:RangeFilter" />
</sequence>
</complexType>

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