Set the list-rendering context

Learn about how set the list-rendering context in IBM Digital Data Connector.

To establish the list-rendering context, you add the following tag to the presentation template:

[Plugin:ListRenderingContext action="set" extension-id="bean list provider id" profile="profile name"]

Replace the bean list provider id variable by the ID that identifies the DDC plug-in instance through which to render this list. If the addressed DDC plug-in is the generic XML DDC plug-in or a DDC plug-in that delegates its requests to that provider, identify the list-rendering profile. The XML DDC plug-in uses the identified profile to transform the XML data into bean list objects. Custom DDC plug-ins might or might not require this profile parameter.

To address one of the two DDC plug-ins provided with IBM WebSphere Portal v8.5, use one of the following values for the extension-id parameter:

ibm.portal.ddc.xml

Use this value for addressing the generic XML DDC plug-in.

ibm.portal.ddc.sr

Use this value for addressing the DDC plug-in used by the social lists feature.

If we use one of the providers, set the profile parameter.

Depending on the choice, the addressed DDC plug-in can support or even require that you pass extra information through the attribute parameters. For details about which information is supported or required with the DDC plug-ins, read the documentation about the DDC plug-in that we use.

• Nesting lists
  We can render nested lists by nesting list-rendering contexts. Nested lists can be useful if the individual entries in the list contain associated information in the form of a list as well. For example, we might want to show a list of communities, including all the community members for each community. In this case, we can retrieve the individual lists of community members by rendering nested lists from within the individual items of the community list.

Example

Here is an example of how to set a list-rendering context that uses the generic Atom list-rendering profile to retrieve the list of public IBM communities:

[Plugin:ListRenderingContext action="set" extension-id="ibm.portal.ddc.xml" profile="ibm.portal.atom" attribute="source=https://www.ibm.com/connections/communities/service/atom/catalog/public" compute=“always“]

To test this example, you probably must adjust the outbound HTTP connection to allow the portal to access the source URL. For more information, read Outbound HTTP connection.

Parent The list-rendering context

Related concepts:

Outbound HTTP connection
The generic XML Digital Data Connector plug-in