Digital Data Connector rendering flow

1. The Web Content Viewer portlet renders a list definition content item.

2. The WCM rendering engine retrieves the associated presentation template to render the appropriate content item.

3. The presentation template renders a [Plugin:ListRenderingContext] tag.

   This tag establishes the current list-rendering context.

4. The presentation template renders a component reference that points to a list appearance component.

5. The selection rule contained in the list appearance component triggers the bean list creation process in the DDC framework.

   The framework identifies the target DDC plugin-in by inspecting the list-rendering context.

6. The addressed DDC plugin-in determines which data to load, and how to filter and sort the data, based on information pulled from the provided list-rendering context.

7. The DDC plugin-in loads the data and transforms it into a corresponding bean list data structure.

   The generic XML DDC plug-in implements this step by applying the list-rendering profile the list-rendering context references to the loaded XML data.

8. The DDC plugin-in passes the resulting bean list object back to the list appearance component.

9. The WCM rendering engine produces the markup for the data contained in the bean list.

   WCM design components can access the individual attributes of the items in the bean list using the [AttributeResource] tag.

Parent IBM Digital Data Connector (DDC) for WebSphere Portal