5. GenticsContentPortlet

5.1. Introduction

The GenticsContentPortlet basically is a variation of the “GenticsContentModule” (Section 4) with some deprecated features removed and some new features added. The following sections will just describe the differences, for additional information see the documentation of the GenticsContentModule.

5.2. Removed Features

The following list of features has been removed from the GenticsContentPortlet

  • <plist> in the content (can be replaced by Velocity)

  • <pxnl> in the content (can be replaced by Velocity)

  • <insert> in the content (can be replaced by Velocity)

  • <pobject> in the content (can be replaced by Velocity)

5.3. Parameters

Additionally to the Parameters of the GenticsContentModule, the GenticsContentPortlet supports the following pnode parameters.

Table 5.11.  Portlet parameters for GenticsContentPortlet

NameTypeDefaultDescription
backendurlStringNULL URL to the Gentics Content.Node 5 Backend for support of rendering content which was fetched from the backend. This is also needed for the support of frontend editing in conjunction with Gentics Content.Node 5. The backend URL must be reachable from the Portal Server, NOT the client.
backendcookieStringNULL Comma separated list of names of cookies which need to be forwarded to the request to the backend to fetch the content.
backendmodeBooleanfalse

This setting switches the source for fetching the rendered content: When set to false (which is the default), the content is fetched from the configured Content Repository. When set to true , the content is fetched from the linked backend (Gentics Content.Node 5) via the configured backendurl .

proxyprefixString/GCN5_Portal/GCN/

Prefix for requests which are directed to the backend. The prefix must direct the request to a Proxy Servlet, that proxies the request to the backend (since the backend itself normally is not available via the same hostname).

Since fetching content from Gentics Content.Node 5 requires a valid Gentics Content.Node 5 Session, this will only work, when the Portal User has logged in and was authenticated via a “GCNAuthenticationManager” (Section 8.3.7) .

5.4. Additional Events of the GenticsContentPortlet

Additionally to the Events described for the GenticsContentModule, the GenticsContentPortlet will throw the following events:

Table 5.12. Events of the GenticsContentPortlet

NameDescriptionEvent properties
onContentLoadErrorThis event is triggered when a content cannot be loaded (either from the datasource or from the backend) due to an error in the underlying system.
NameDescription
contentidThe contentid if the content which could not be loaded