Structure of list-rendering profiles

A list-rendering profile consists of a set of name-value pairs.

These name-value pairs define the following aspects:

• The name of the profile in a format so the profile can be referenced from the [Plugin:ListRenderingContext] tag.

• The process of dividing a single XML document into a list of separate items.

• The extraction of individual item attributes from data contained in those items.

  The resulting set of item attribute defines the set of attributes accessible in the IBM DDC list designs using the tag...

  [AttributeResource attributeName=""]

• The extraction of list properties from the complete XML document.

  The resulting set of list properties defines the set of key values used with the tag...

  [Plugin:ListRenderingContext action="getListProperty" key=""]

• The translated item attribute titles to be shown to the site designers when they use the dialog "Insert a tag" in the WCM authoring portlet.

  The list of attribute titles helps the site designers choose the correct attributeName parameter values for the [AttributeResource] tag.

WebSphere Portal v8.5 supports the following two types of list-rendering profiles:

• XPath centric type of profile.

  Uses XPath statements to define the data transformation. This data transformation contains the aspects of dividing the XML document and the extraction of item attributes and list properties as listed before.

• Custom type of profile.

  Does not define a data transformation, but registers only the set of supported item attributes shown in the Insert a tag dialog. With a custom type profile, the corresponding bean list provider is responsible for providing the respective values for the attribute names that are claimed to be supported in the custom profile.

Parent Integrate remote XML data