Understanding PeopleSoft Compliance with JSR 168

Portlets obtain their context via the Portlet API functions such as access to user profile information for the current user, participation in the portal window and action event model, access to web client information, sharing of information with other portlets, and a standard way of storing and retrieving per-user/per-instance portlet data persistently. PeopleTools portlet container supports the Java Portlet API 1.0. The Java Portlet API provides a URL-rewriting mechanism for creating links to trigger actions within a portlet without requiring knowledge about how URLs are structured in the particular web application. Portlets are grouped in a portal application by bundling them in a single web application archive file (WAR) with a portlet deployment descriptor file. In addition, the API provides a means of sharing data among portlets of the same portal application.

The PeopleSoft JSR 168 engine accepts all of the required window states as well as any custom window states. However, although the engine allows any window state, PeopleSoft JSR 168 does not react to them. Portlets always appear to have a Normal amount of screen space.

In the current release, the PeopleSoft JSR 168 engine doesn't support the caching of portlet content based on caching elements that are embedded in the portlet; any caching tags in the portlet are ignored. However, the engine does support caching by using the PSCACHECONTROL content reference attribute.

See Implementing Pagelet Caching.

The PeopleSoft JSR 168 engine supports all of the required portlet modes, which are:

• VIEW

• EDIT

• HELP