http://www.endeca.com/MDEX/conversation/1/0
The ContentElementConfig Complex Type
The ContentElementConfig type is a sort of "Abstract Base Class". Types that extend ContentElementConfig are logical representations of a chunk of data. A ContentElementConfig can provide a "projection" of data that is determined by its State. A custom ContentElementConfig must be paired with a handler function written in XQuery to work properly; the ContentElementConfig identifies the handler to call and provides appropriate configuration information for that handler. The actual subtype polymorphism is accomplished in a request by applying xsi:type to the specific ContentElementConfig instance in the request. Schemas that extend the ContentElementConfig are permitted to redeclare Handler with a default. This would look like:
<complexType name="MyContentElementConfig">
<complexContent>
<extension base="ContentElementConfig">
<attribute default="MyDefault" name="HandlerNamespace" type="cs_v1_0:NonEmptyString" use="optional" />
<attribute default="MyDefaultFn" name="HandlerFunction" type="cs_v1_0:NonEmptyString" use="optional" />
</extension>
</complexContent>
</complexType>

Subtypes (12)
AnalyticsConfigderived by extension AttributeGroupListConfigderived by extension AvailableSearchKeysConfigderived by extension BreadcrumbConfigderived by extension LQLConfigderived by extension NavigationMenuConfigderived by extension PropertyListConfigderived by extension RecordCountConfigderived by extension RecordDetailsConfigderived by extension RecordListConfigderived by extension SearchAdjustmentConfigderived by extension ValueSearchConfigderived by extension
Complex Type ContentElementConfig
The ContentElementConfig type does not allow mixed content. There is no restriction on type derivation. 
 CollapseClick here to hide comment XML Instance
<... HandlerFunction="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. Id="cs_v1_0:NonEmptyString"Click here to hide Comment This attribute is required.></...>

 Collapse Attributes

Name Type Summary
HandlerFunction NonEmptyString
This attribute is required. Its form is unqualified.
Show details. Click here to see detail
 
HandlerNamespace NonEmptyString
This attribute is required. Its form is unqualified.
Show details. Click here to see detail
 
Id NonEmptyString
This attribute is required. Its form is unqualified.
Show details. Click here to see detail
 

 Collapse XML
-<complexType  name="ContentElementConfig">
-<annotation>
-<documentation>
The ContentElementConfig type is a sort of "Abstract Base Class". Types that extend ContentElementConfig are logical representations of a chunk of data. A ContentElementConfig can provide a "projection" of data that is determined by its State. A custom ContentElementConfig must be paired with a handler function written in XQuery to work properly; the ContentElementConfig identifies the handler to call and provides appropriate configuration information for that handler. The actual subtype polymorphism is accomplished in a request by applying xsi:type to the specific ContentElementConfig instance in the request. Schemas that extend the ContentElementConfig are permitted to redeclare Handler with a default. This would look like:
-<complexType  name="MyContentElementConfig">
-<complexContent>
-<extension  base="ContentElementConfig">
<attribute  default="MyDefault"  name="HandlerNamespace"  type="cs_v1_0:NonEmptyString"  use="optional" />
<attribute  default="MyDefaultFn"  name="HandlerFunction"  type="cs_v1_0:NonEmptyString"  use="optional" />
</extension>
</complexContent>
</complexType>
</documentation>
</annotation>
<attribute  name="Id"  type="cs_v1_0:NonEmptyString"  use="required" />
<attribute  name="HandlerNamespace"  type="cs_v1_0:NonEmptyString"  use="required" />
<attribute  name="HandlerFunction"  type="cs_v1_0:NonEmptyString"  use="required" />
</complexType>

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