JSR-168 Consumer 1.0 SP5 - released December 2005
JSR-168 Consumer 1.0 SP4
- released September 2005
JSR-168 Consumer 1.0.3
- released September 2004
JSR-168 Consumer
1.0.2.143983 - released July 2004
JSR-168 Consumer 1.0.2
- released June 2004
JSR-168 Consumer 1.0
- released September 2003
For the most recent support matrix, see the Interoperability page of the
Plumtree Support Center.
- Plumtree JSR-168 Consumer is certified with JSR-168 TCK Acceptance
Test on the following application servers and operating systems:
- Application Servers: BEA
Weblogic 8.1, Apache Tomcat 5.0.28, IBM Websphere 6.0.1
- Operating Systems: Windows 2003, Red Hat Linux ES 3, SUSE Linux
ES 9, Sun Solaris 8, IBM AIX 5.2
Issues Addressed
- Sample portlets (GooglePortlet, RSSPortlet, JspPortlet) are supported
on all listed application and platforms.
Known Issues
- TCK test PORTLETCONTEXT:GetRequestDispatcherNullTest fails with
container Websphere 6.0.1. (Issue # 49037)
- When JSR-168 Consumer is set up on Remote Container (instead of
container running portal) the following tests fail on all application servers:
- ACTIONREQUEST: CheckActionRequestParameterTest
- ACTIONREQUEST: CheckIsPortletModeAllowedTest
- ACTIONREQUEST: GetContextPathTest
- PORTLETSESSION: InvalidatePortletAndServletSessionTest
- RENDERREQUEST: GetContextPathTest
Issues
Addressed
- Added support for sharing
portlets across a session.
- Certified with JSR-168
TCK acceptance test completion.
- Including HTML pages in a PortletRequestDispacher fails on WebLogic.
(Issue #37784)
- The portal and a JSR-168 portlet
cannot be on the same application server if the portlet uses a period (.)
as the gateway space. (Issue #37786)
Workaround: Use the servlet
context (web app name) as the gateway space for the portlet.
- The JSR-168 Consumer has not been
tested using non-English locales. (Issue #37787)
- Render parameters are not
stored between requests. This specifically fails the Sun TCK tests using WebLogic on Unix. (Issue
#37783)
- The User Preferences for a
user in Portal 4.5WS must be set in an external
source and imported into the portal.
- JSR 168 is certified on
Solaris 8 and 9.
- JSR 168 is certified on
Windows Server 2003.
- Portlets on a page do not
share sessions. The portlet specification assumes that portlets on the
same page share the same session, whereas portlets on the Plumtree portal
always have their own session. (Issue #32217)
Workaround: If a developer wants to share information
between portlets in a web application, use Portlet Context.
- Including HTML pages in a PortletRequestDispacher
fails on Weblogic. (Issue #37784)
- The portal and a JSR-168 portlet
cannot be on the same application server if the portlet uses a period (.)
as the gateway space. (Issue #37786)
Workaround: Use the servlet context (web app name) as the
gateway space for the portlet.
- The JSR-168 Consumer has not
been tested using non-English locales. (Issue #37787)
- Render parameters are not
stored between requests. This specifically fails the Sun TCK tests using
WebLogic on Unix. (Issue #37783)
- The scope of exported
variables (var) for renderURL and actionURL tags has been incorrectly set
to javax.portlet.PortletURL instead of String. (Issue #37785).
- The User Preferences for a
user in the Portal 4.5WS, must be set in an external source and imported
into the portal.
- This release fixes an issue
where user information was not being read. (Issue #33247)
- GetRemoteUser returning null
issue corrected. (Issue #35424)
- Portlets on a page do not
share sessions. The portlet specification assumes that portlets on the
same page share the same session, whereas portlets on the Plumtree portal
always have their own session. (Issue #32217)
Workaround: If a developer wants to share information
between portlets in a Web application, use Portlet Context.
- Including html pages in a
PortletRequestDispacher fails on Weblogic. (Issue #37784)
- The Portal and JSR-168 portlet
cannot be on the same application server if the portlet uses a period (.)
as the gateway space. (Issue #37786)
Workaround: Use the servlet context (web app name) as the
gateway space for the portlet.
- The JSR-168 Consumer has not
been tested using non-English locales. (Issue #37787)
- Render parameters are not
stored between requests. This specifically fails the Sun TCK tests using
WebLogic on Unix. (Issue #37783)
- getInputStream and getReader
methods fixed.
- Final 1.0 version of the
Portlet API supported.
- Portlets on a page do not
share sessions. The portlet specification assumes that portlets on the
same page share the same session, whereas portlets on the Plumtree portal
always have their own session. (Issue #32217)
Workaround: If a developer wants to share information
between portlets in a Web application, use Portlet Context.
- Including html pages in a
PortletRequestDispacher fails on Weblogic.(Issue #37784)
- The Portal and JSR-168 portlet
cannot be on the same application server if the portlet uses a period (.)
as the gateway space. (Issue #37786)
Workaround: Use the servlet context (web app name) as the
gateway space for the portlet.
- The JSR-168 Consumer has not
been tested using non-English locales. (Issue #37787)
Known Issues
- Portlets on a page do not
share session-The portlet specification assumes that portlets on the same
page share the same session, whereas portlets on the Plumtree portal
always have their own session. (Issue #32217)
Workaround: If a developer wants to share information
between portlets in a web application, use Portlet Context.
- getInputStream() and
getReader() methods do not work on portlet URLs dues to gateway
considerations. RequestParameters are not affected.
- The autodeployment of the
PtPortletContainer.war is successful on Weblogic but jsr168_
install/weblogic_deployment.log may report failure. (Issue #23452)