The dsp:renderContentItem JSP tag has two responsibilities:
For a JSP response, it locates and dispatches to a rendering JSP page. The
dsp:renderContentItemtag uses theContentItemToRendererPathcomponent to determine the path of the JSP page to include.It sets an
HttpServletRequest.contentItemattribute to the specifiedcontentItem. This provides a well-known attribute for rendering pages to pull data from; however, this attribute is set for the duration of theincludeonly.
The dsp:renderContentItem tag supports the following tag attributes:
contentItem(required) - TheContentItemto locate a rendering JSP page for. The value of thecontentItemrequest attribute is also set to thisContentItem, for the duration of theinclude.format(optional) – Specifies whether the response should be serialized into JSON or XML. Acceptable values arejsonorxml.webApp(optional) - The web application that theincludeis relative to. By default, the current web application is used, but by passing another value in thewebAppattribute, you can specify anincludethat is relative to a different web application. The value ofwebAppmay either be the content root of the target web application (in which case, it must begin with a slash) or the display name ofwebApp(in which case, it is located via Oracle ATG’sWebAppRegistry; see the ATG Platform Programming Guide for more information on theWebAppRegistry).var(optional) – The name of the request attribute to set. You can usevarto override the default request attribute name ofcontentItem.
Similar to dsp:include, dsp:renderContentItem supports either nested dsp:param tags or dynamic attributes for setting additional parameters.

