Release Notes for JSR-168 Container 1.0.3

Contents
Version History

Version 1.0.3
Issues Addressed
Known Issues

Version 1.0.2.143983
Issues Addressed
Known Issues

Version 1.0.2
Issues Addressed
Known Issues

Version 1.0
Known Issues

Version History

Version 1.0.3 released September 14, 2004

Version 1.0.2.143983 released July 21, 2004

Version 1.0.2 released June 8, 2004

Version 1.0 released September 1, 2003

Version 1.0.3
Issues Addressed

- JSR 168 is certified on Solaris 8 and 9.

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.
- Using the includes method on PortletRequestDispacher with html pages fails on Weblogic.(Issue #37784)
- The Portal and Portlet Container cannot be on the same application server if the Portlet Container uses a period (.) as the gateway space. (Issue #37786)
  Workaround: Use the servlet context (web app name) as the gateway space for the Portlet Container.
- The JSR 168 container has not been tested and is not supported for non-English implementations. (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).

Version 1.0.2.143983
Issues Addressed

- This release fixes an issue where user information was not being read. (Issue #33247)
- GetRemoteUser returning null issue corrected. (Issue #35424)

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.
- Using the includes method on PortletRequestDispacher with html pages fails on Weblogic.(Issue #37784)
- The Portal and Portlet Container cannot be on the same application server if the Portlet Container uses a period (.) as the gateway space. (Issue #37786)
  Workaround: Use the servlet context (web app name) as the gateway space for the Portlet Container.
- The JSR 168 container has not been tested and is not supported for non-English implementations. (Issue #37787)
- Render parameters are not stored between requests. This specifically fails the Sun TCK tests using WebLogic on Unix. (Issue #37783)

Version 1.0.2
Issues Addressed

- getInputStream and getReader methods fixed.
- Final 1.0 version of the Portlet API supported.

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.
- Using the includes method on PortletRequestDispacher with html pages fails on Weblogic.(Issue #37784)
- The Portal and Portlet Container cannot be on the same application server if the Portlet Container uses a period (.) as the gateway space. (Issue #37786)
  Workaround: Use the servlet context (web app name) as the gateway space for the Portlet Container.
- The JSR 168 container has not been tested and is not supported for non-English implementations. (Issue #37787)

Version 1.0
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 PortletURLs 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)