issues and restrictions related to standard portlets publish and subscribe mechanisms

The following known issues and restrictions exist with portlet communication.

• The pop-up menu functionality requires browsers with JavaScript on the client.

• Complex Java types can only be transferred between portlets if they are deployed in a shared class loader.

  Use basic Java types, such as java.lang.String or java.util.HashMap for compound data. Custom classes must be installed in a IBM WebSphere Application Server shared library available to both portlets or must be directly installed into the directory WP_PROFILE/PortalServer/config.

  JSR 286 events with XML bindings allow us to transfer complex data types between portlets in different class loaders. However, to avoid the performance penalty incurred by XML serialization, follow the previous recommendations.

• When we import sample Struts WAR files including the file pbstrutsExample.war into Rational Application Developer Version 6, it reports broken links. We can ignore this warning message.

• Rational Application Developer lists WS-I warnings for wsdl:binding errors.

  WS-I compliance warning messages will be displayed in the Problems view for Click-to-Action enabled portlets. We can ignore them in the Click-to-Action WSDL resources. To prevent these warning messages from being displayed...

  1. Select...
     Window | Preferences | Workbench | Capabilities | Web Service Developer | Web Services Development

  2. Click Apply.

  3. Set..
     Window | Preferences | Web Services | WS-I Compliance | Ignore compliance

  4. Click Apply.

  To remove the compliance warnings from the Problems view open the project's pop-up menu in the Project Explorer and select Run Validation.

• If multiple cross-page wires marked with the switch page flag are triggered at the same time, all wire targets are invoked. However, the target page to which a user gets directed cannot be predicted unambiguously.

• Cross-page wires for standard portlets are executed before redirecting to the target page. Therefore cross-page target portlets must not assume they are executed on the target page.

• Wires created on a root page do not apply to derived pages created by referencing the root page. While such pages do inherit the content of the original page, this inheritance does not apply to wires; we have to explicitly create the wires for the derived page.

• Cooperative Java Server Faces (JSF) portlets that you developed using older versions of Rational Application Developer Version 6 can contain code that does not work with IBM WebSphere Portal v8.5. If this occurs, replace the file jsf-portlet.jar in the failing WAR file with the version in the latest fix pack level.

• Cooperative portlet action declarations with multiple input parameters configured in the WSDL file are not supported.

Note regarding the IBM Portlet API

The IBM Portlet API is deprecated. Do not use it for development of new portlets. If we need information about portlet communication for IBM Portlet API-based portlets, see IBM WebSphere Portal V8.0 documentation.

Parent Portlet communication