Portlet Properties

Optional. Hint to the skeleton to position the portlet titlebar on the top, bottom, left, or right side of the portlet. You must build your own skeleton to support this property. Following are the numbers used in the .portal file for each orientation value: top=0, left=1, right=2, bottom=3.

Change the value for this property only if you want to override the default orientation provided by the .portlet file.

Optional. If you want to use a class for preprocessing (for example, authentication) prior to rendering the portlet, enter the fully qualified name of that class. That class should implement the interface com.bea.netuix.servlets.controls.content.backing.JspBacking or extend com.bea.netuix.servlets.controls.content.backing.AbstractJspBacking.

See the Tutorial Portal in the Portal Samples for examples of backing files.

Optional. Performance setting for books, pages, and portlets that use backing files.

When Thead Safe is set to "true," an instance of a backing file is shared among all books, pages, or portlets that request the backing file. You must synchronize any instance variables that are not thread safe.

When Thread Safe is set to "false," a new instance of a backing file is created each time the backing file is requested by a different book, page, or portlet.

You can override the orientation in each instance of the portlet (in the Portal Designer).

Optional. Rendering hint that can be used by the skeleton to render the portlet in either expanded or packed mode. You must build your own skeleton to support this property.

When packed="false" (the default), the portlet takes up as much horizontal space as it can.

When packed="true," the portlet takes up as little horizontal space as possible.

From an HTML perspective, this property is most useful when the window is rendered using a table. When packed="false," the table's relative width would likely be set to "100%." When packed="true," the table width would likely remain unset.

Optional. To enhance performance, set to "true" to cache the portlet. For example, portlets that call Web services perform frequent, expensive processing. Caching Web service portlets greatly enhances performance.

Do not set this to "true" if you are doing your own caching.

Optional. Select the multichannel devices in which the portlet can be viewed. The dialog list of devices comes from <project>\WEB-INF\client-classifications.xml.

In the Manage Portlet Classifications dialog:

1. Select whether you want to enable or disable classifications for the portlet.
2. Move the client classifications you want to enable or disable from the Available Classifications to the Selected Classifications, and click OK.

When you disable classifications for a portlet, the portlet is automatically enabled for the classifications you did not select for disabling.

Portlets that have the "transient-session" value applied generally have the same behavior as existing portlets; however, in failover cases, the persisted request attributes will disappear on the failed-over-to server. In the failover case, you must write forward JSPs to handle this contingency gracefully by, at a minimum, not expecting any particular request attribute to be populated; ideally you should include the ability to either repopulate automatically or present the user with a link to re-run the last action to repopulate the request attributes. For non-failover cases, request attributes will be persisted, providing a performance advantage for non-postback portlets identical to default "session" peristence portlets.

Portlets that have the "none" value applied will never have request attributes available on refresh requests; you must write forward JSPs to assume that they will not be available. You can use this option to completely remove the framework-induced session memory loading for persisted request attributes.

Optional. If you want to use a class for preprocessing (for example, authentication) prior to rendering the portlet's mode page (such as the edit page), enter the fully qualified name of that class. That class should implement the interface com.bea.netuix.servlets.controls.content.backing.JspBacking or extend com.bea.netuix.servlets.controls.content.backing.AbstractJspBacking.

See the Tutorial Portal in the Portal Samples for examples of backing files.

Optional. The primary uses are to allow content scrolling and content height-setting.

For scrolling, enter one of the following attributes:

• overflow-y:auto - Enables vertical (y-axis) scrolling
• overflow-x:auto - Enables horizontal (x-axis) scrolling
• overflow:auto - Enables vertical and horizontal scrolling

For setting height, enter the following attribute:

height:200px

where 200px is any valid HTML height setting.

You can also set other style properties for the content as you would using the Presentation Style property. The properties are applied to the component's content/child <div> tag.

Optional. The primary uses are to allow content scrolling and content height-setting.

For scrolling, enter a stylesheet class that uses one of the following attributes:

• overflow-y:auto - Enables vertical (y-axis) scrolling
• overflow-x:auto - Enables horizontal (x-axis) scrolling
• overflow:auto - Enables vertical and horizontal scrolling

For setting height, enter a stylesheet class that uses the following attribute:

height:200px

where 200px is any valid HTML height setting.

You can also set other style properties for the content as you would using the Presentation Class property. The properties are applied to the component's content/child <div> tag.