Author: smumford
Date: 2011-05-04 02:32:28 -0400 (Wed, 04 May 2011)
New Revision: 6444
Modified:
epp/docs/branches/5.1/Release_Notes/en-US/5.1.1_Release_Notes.xml
epp/docs/branches/5.1/Release_Notes/en-US/Book_Info.xml
epp/docs/branches/5.1/Release_Notes/en-US/Revision_History.xml
epp/docs/branches/5.1/Release_Notes/en-US/known_issues.xml
epp/docs/branches/5.1/Release_Notes/en-US/need_info.xml
epp/docs/branches/5.1/Release_Notes/en-US/resolved_issues.xml
Log:
Compiled full Resolved Issues list and added component version details.
Modified: epp/docs/branches/5.1/Release_Notes/en-US/5.1.1_Release_Notes.xml
===================================================================
--- epp/docs/branches/5.1/Release_Notes/en-US/5.1.1_Release_Notes.xml 2011-05-04 04:18:44
UTC (rev 6443)
+++ epp/docs/branches/5.1/Release_Notes/en-US/5.1.1_Release_Notes.xml 2011-05-04 06:32:28
UTC (rev 6444)
@@ -13,6 +13,7 @@
<para>
By integrating proven open source frameworks such as JBoss Seam, Hibernate, Tomcat and
JBoss Cache JBoss Enterprise Portal Platform takes advantage of innovations in the open
source community. As well, JBoss Enterprise Portal Platform version 5.1.1 is fully tested
and supported by Red Hat, and is certified to work on many leading enterprise hardware and
software products.
</para>
+
</section>
<section id="sect-5.1.1_Release_Notes-New_and_Upgraded_Components">
@@ -25,20 +26,79 @@
<para>
</para>
+
</listitem>
+
</varlistentry>
+
</variablelist>
<variablelist
id="vari-5.1.1_Release_Notes-New_and_Upgraded_Components-Upgraded_Components">
<title><emphasis role="bold">Upgraded
Components</emphasis></title>
<varlistentry>
- <term></term>
+ <term>JBoss EAP</term>
<listitem>
<para>
-
+ The Enterprise Application Platform has been upgraded to 5.1.1-GA.
</para>
</listitem>
</varlistentry>
+ <varlistentry>
+ <term>JBoss Portlet Bridge</term>
+ <listitem>
+ <para>
+ The JBoss Portlet Bridge component has been upgraded to version
2.1.1.GA.EPP51.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>JBoss Cache</term>
+ <listitem>
+ <para>
+ The JBoss Cache component has been upgraded to version 3.2.7 (as
part of the EAP upgrade).
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>eXo JCR</term>
+ <listitem>
+ <para>
+ The eXo JAva Content Repository has been upgraded to version
1.12.8.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>PicketLink</term>
+ <listitem>
+ <para>
+ The PicketLink IDM component has been upgraded to version 1.1.8-GA.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Seam</term>
+ <listitem>
+ <para>
+ Seam has been upgraded to 2.2.3.EAP5 (as part of the EAP upgrade).
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>WSRP</term>
+ <listitem>
+ <para>
+ The WSRP component has been upgraded to 2.0.1-GA.
+ </para>
+ </listitem>
+ </varlistentry>
</variablelist>
+ <para>
+ More details about the component versions that make up JBoss Enterprise Portal
Platform 5.1.1 can be found in <xref
linkend="sect-5.1.1_Release_Notes-Component_Versions"/>
+ </para>
+ <!-- Source Metadata
+ URL:
https://issues.jboss.org/browse/JBEPP-897
+ Author [w/email]: Honza Fnukal (hfnukal(a)redhat.com)
+ License: Red Hat?
+ -->
</section>
<section id="sect-5.1.1_Release_Notes-Component_Versions">
@@ -62,129 +122,231 @@
<tbody>
<row>
<entry>
- JBoss Enterprise Application Platform
+ EAP
</entry>
<entry>
+ 5.1.1-GA
</entry>
</row>
<row>
<entry>
- eXo Kernel
+ eXo junit
</entry>
+ <entry>
+ 1.2.1-GA
+ </entry>
+ </row>
+ <row>
+ <entry>
+ eXo kernel
+ </entry>
<entry>
+ 2.2.8-GA
</entry>
</row>
<row>
<entry>
eXo Core
</entry>
- <entry>
+ <entry>
+ 2.3.8-GA
</entry>
</row>
<row>
<entry>
eXo WS
</entry>
- <entry>
+ <entry>
+ 2.1.8-GA
</entry>
</row>
<row>
<entry>
eXo JCR
</entry>
- <entry>
+ <entry>
+ 1.12.8-CP01
</entry>
</row>
<row>
<entry>
- JBoss Cache
+ Apache Schindig
</entry>
- <entry>
+ <entry>
+ 1.0-r790473-Patch04
</entry>
</row>
<row>
<entry>
- Apache Shindig
+ Simple Captcha
</entry>
- <entry>
+ <entry>
+ 1.1.1-GA-Patch01
</entry>
</row>
<row>
<entry>
- Simple Captcha
+ GateIn Parent
</entry>
- <entry>
+ <entry>
+ 1.0.1-GA
</entry>
</row>
<row>
<entry>
+ GateIn dep
+ </entry>
+ <entry>
+ 1.0.2-GA
+ </entry>
+ </row>
+ <row>
+ <entry>
GateIn Common
</entry>
- <entry>
+ <entry>
+ 2.0.3-GA
</entry>
</row>
<row>
<entry>
GateIn WCI
</entry>
- <entry>
+ <entry>
+ 2.0.2-GA
</entry>
</row>
<row>
<entry>
GateIn PC
</entry>
- <entry>
+ <entry>
+ 2.2.0-GA
</entry>
</row>
<row>
<entry>
GateIn WSRP
</entry>
- <entry>
+ <entry>
+ 2.0.1-EPP51-GA
</entry>
</row>
<row>
<entry>
GateIn MOP
</entry>
- <entry>
+ <entry>
+ 1.0.3-GA
</entry>
</row>
<row>
<entry>
+ GateIn SSO
+ </entry>
+ <entry>
+ 1.0.2-epp-GA
+ </entry>
+ </row>
+ <row>
+ <entry>
PicketLink IDM
</entry>
- <entry>
+ <entry>
+ 1.1.8-GA
</entry>
</row>
<row>
<entry>
Chromattic
</entry>
- <entry>
+ <entry>
+ 1.0.3
</entry>
</row>
<row>
<entry>
Portlet Bridge
</entry>
- <entry>
+ <entry>
+ 2.1.1.GA.EPP51
</entry>
</row>
<row>
<entry>
- GateIn SSO
+ Seam
</entry>
- <entry>
+ <entry>
+ 2.2.3.EAP5
</entry>
</row>
+ <row>
+ <entry>
+ Richfaces
+ </entry>
+ <entry>
+ 3.3.1.SP3
+ </entry>
+ </row>
+ <row>
+ <entry>
+ Groovy
+ </entry>
+ <entry>
+ 1.6.5
+ </entry>
+ </row>
+ <row>
+ <entry>
+ Commons DBCP
+ </entry>
+ <entry>
+ 1.2.2
+ </entry>
+ </row>
+ <row>
+ <entry>
+ Commons IO
+ </entry>
+ <entry>
+ 1.4
+ </entry>
+ </row>
+ <row>
+ <entry>
+ Commons Lang
+ </entry>
+ <entry>
+ 2.4
+ </entry>
+ </row>
+ <row>
+ <entry>
+ HSQLDB
+ </entry>
+ <entry>
+ 1.8.0.7
+ </entry>
+ </row>
+ <row>
+ <entry>
+ JBoss Cache
+ </entry>
+ <entry>
+ 3.2.7
+ </entry>
+ </row>
</tbody>
</tgroup>
</table>
+ <!-- Source Metadata
+ URL:
https://docspace.corp.redhat.com/docs/DOC-64265
+ Author: Thomas Heute (theute(a)redhat.com)
+ License: Red Hat is the Holder.
+ -->
</section>
-
- <section id="sect-5.1.1_Release_Notes-Installation">
+
+ <section id="sect-5.1.1_Release_Notes-Installation">
<title>Installation</title>
<para>
The JBoss Enterprise Portal Platform Installation Guide contains details of software
and hardware requirements as well as detailed installation instructions.
@@ -195,37 +357,33 @@
</section>
- <section>
- <title>Resolved Issues</title>
- <para>
- The following is a list of issues fixed in this release:
- </para>
- <xi:include href="resolved_issues.xml"
xmlns:xi="http://www.w3.org/2001/XInclude" />
- </section>
-
- <section>
- <title>Known Issues</title>
- <para>
+ <section id="sect-5.1.1_Release_Notes-Resolved_Issues">
+ <title>Resolved Issues</title>
+ <para>
+ The following is a list of issues fixed in this release:
+ </para>
+ <xi:include href="resolved_issues.xml"
xmlns:xi="http://www.w3.org/2001/XInclude" />
+
+ </section>
+
+ <section id="sect-5.1.1_Release_Notes-Known_Issues">
+ <title>Known Issues</title>
+ <para>
+ There are no known issues in this release of JBoss Enterprise Portal Platform
+ </para>
+ <!-- <para>
The following is a list of known issues in this release:
</para>
- <xi:include href="known_issues.xml"
xmlns:xi="http://www.w3.org/2001/XInclude" />
- </section>
-
- <section>
+ <xi:include href="known_issues.xml"
xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
+ </section>
+
+ <!-- <section>
<title><remark>NEEDINFO</remark></title>
<xi:include href="need_info.xml"
xmlns:xi="http://www.w3.org/2001/XInclude" />
- </section>
- <!-- <section>
- <title>Security Issues</title>
- <variablelist>
-
- </variablelist>
- </section> -->
-
- <section id="sect-5.1.1_Release_Notes-Migration">
+ </section> -->
+
+ <section id="sect-5.1.1_Release_Notes-Migration">
<title>Migration</title>
- <section id="sect-5.1.1_Release_Notes-Migration-From_4.3_Stream">
- <title>From 4.3 Stream</title>
<para>
JBoss Enterprise Portal Platform 5 is based upon an entirely new core architecture
and is not backwards compatible with JBoss Enterprise Portal Platform 4.3.
</para>
@@ -238,20 +396,11 @@
<para>
Red Hat JBoss Customer Support can be accessed at <ulink type="http"
url="https://www.redhat.com/apps/support/" />.
</para>
-
</section>
-
- <section id="sect-5.1.1_Release_Notes-Migration-From_5.x_Stream">
- <title>From 5.x Stream</title>
- <para>
- Anything that needs to go in here!
- </para>
- </section>
- </section>
-
<section id="sect-5.1.1_Release_Notes-Site_Publisher">
- <title><remark>Site Publisher</remark></title>
+ <title><remark>Site Publisher</remark>
+ </title>
<remark>DOCS NOTE: Do we still want this here?</remark>
<para>
Site Publisher provides many additional features for organizations looking to enable
line of business resources to directly manage sites, pages and content within the context
of the portal versus through integration with an external web content management system.
@@ -281,9 +430,7 @@
<para>
This document explains how to install and verify the installation of JBoss
Enterprise Portal Platform using different installation methods.
</para>
-
</listitem>
-
</varlistentry>
<varlistentry>
<term>User Guide</term>
@@ -291,9 +438,7 @@
<para>
This document provides an easy to follow guide to the functions and options
available in JBoss Enterprise Portal Platform. It is intended to be accessible and useful
to both experienced and novice portal users.
</para>
-
</listitem>
-
</varlistentry>
<varlistentry>
<term>Reference Guide</term>
@@ -303,6 +448,14 @@
</para>
</listitem>
</varlistentry>
+ <varlistentry>
+ <term>Site Publisher</term>
+ <listitem>
+ <para>
+ Dedicated Installation and User Guides provide information on
installing, configuring and using the JBoss Enterprise Portal Platform Site Publisher
extension. These documents assume the required JBoss Enterprise Portal Platform installion
is present and functioning properly.
+ </para>
+ </listitem>
+ </varlistentry>
</variablelist>
</para>
<para>
@@ -367,7 +520,6 @@
</para>
</formalpara>
</section>
-
+
<xi:include href="Revision_History.xml"
xmlns:xi="http://www.w3.org/2001/XInclude" />
-</article>
-
+</article>
\ No newline at end of file
Modified: epp/docs/branches/5.1/Release_Notes/en-US/Book_Info.xml
===================================================================
--- epp/docs/branches/5.1/Release_Notes/en-US/Book_Info.xml 2011-05-04 04:18:44 UTC (rev
6443)
+++ epp/docs/branches/5.1/Release_Notes/en-US/Book_Info.xml 2011-05-04 06:32:28 UTC (rev
6444)
@@ -7,7 +7,7 @@
<title>5.1.1 Release Notes</title>
<subtitle>For use with JBoss Enterprise Portal Platform 5.1.1</subtitle>
<edition>1</edition>
- <pubsnumber>1.0</pubsnumber>
+ <pubsnumber>1.1</pubsnumber>
<productname>JBoss Enterprise Portal Platform</productname>
<productnumber>5.1</productnumber>
<abstract>
Modified: epp/docs/branches/5.1/Release_Notes/en-US/Revision_History.xml
===================================================================
--- epp/docs/branches/5.1/Release_Notes/en-US/Revision_History.xml 2011-05-04 04:18:44 UTC
(rev 6443)
+++ epp/docs/branches/5.1/Release_Notes/en-US/Revision_History.xml 2011-05-04 06:32:28 UTC
(rev 6444)
@@ -7,6 +7,20 @@
<title>Revision History</title>
<simpara>
<revhistory>
+ <revision>
+ <revnumber>1-1.1</revnumber>
+ <date>Wed May 4 2011</date>
+ <author>
+ <firstname>Scott</firstname>
+ <surname>Mumford</surname>
+ <email>smumford(a)redhat.com</email>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Compiled full Resolved Issues list and added
component version details.</member>
+ </simplelist>
+ </revdescription>
+ </revision>
<revision>
<revnumber>1-1.0</revnumber>
<date>Thu Apr 28 2011</date>
Modified: epp/docs/branches/5.1/Release_Notes/en-US/known_issues.xml
===================================================================
--- epp/docs/branches/5.1/Release_Notes/en-US/known_issues.xml 2011-05-04 04:18:44 UTC
(rev 6443)
+++ epp/docs/branches/5.1/Release_Notes/en-US/known_issues.xml 2011-05-04 06:32:28 UTC
(rev 6444)
@@ -1,72 +1,9 @@
-<?xml version='1.0'?>
+<?xml version='1.0' encoding='utf-8' ?>
<!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "5.1.1_Release_Notes.ent">
+%BOOK_ENTITIES;
]>
-<!-- release notes text customfield_12310211 -->
-
-
<variablelist>
-
- <!--
https://issues.jboss.org/browse/JBEPP-610 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-610"
/></term>
- <listitem>
- <para>
- Customers should be aware that passwords entered into the portal and remembered
with the <emphasis>Remember me</emphasis> option are stored in the JCR
database in plain text. This presents a possible security vulnerability.
- </para>
- </listitem>
- </varlistentry>
-
- <!--
https://issues.jboss.org/browse/JBEPP-780 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-780"
/></term>
- <listitem>
- <para>
- Cause: The two JBoss Cache instances created by PicketLink were calling on the
same configuration file in idm-configuration.xml and, as a result, were using the same
cluster names.
- </para>
- <para>
- Consequence: This could lead to conflicts as the same JBoss Cache instance could
join the same channel twice.
- </para>
- <para>
- Fix: Two configuration files were created and added to the distribution package
and the Portal configuration was customized to call on the different files.
- </para>
- <para>
- Result: JBoss Cache instances can now run simultaneously without conflict.
- </para>
- </listitem>
- </varlistentry>
-
- <!--
https://issues.jboss.org/browse/JBEPP-904 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-904"
/></term>
- <listitem>
- <para>
- Cause: EPP doesn't set content-type on css-files added via
gatein-resources.xml.
- </para>
- <para>
- Consequence: This means IE9 ignores these css-files due to new security
policy. In the console it states: SEC7113: CSS was ignored due to mime type mismatch.
- </para>
- <para>
- Workaround: Add the following setContentType code to the CSS portion of the
ResourceRequestFilter.java file:
-<programlisting language="Java" role="Java">....
-if (uri.endsWith(".css"))
- {
- final OutputStream out = response.getOutputStream();
- // New code start
- httpResponse.setContentType("text/css; charset=UTF-8");
- // New code end
- final BinaryOutput output = new BinaryOutput()
- {
- public Charset getCharset()
- {
- return UTF_8;
- }
-....
-</programlisting>
- </para>
- <para>
- Result: Content-types will be set and IE9 will render the Portal as
expected.
- </para>
- </listitem>
- </varlistentry>
-
+ <!-- release notes text customfield_12310211 -->
</variablelist>
+
Modified: epp/docs/branches/5.1/Release_Notes/en-US/need_info.xml
===================================================================
--- epp/docs/branches/5.1/Release_Notes/en-US/need_info.xml 2011-05-04 04:18:44 UTC (rev
6443)
+++ epp/docs/branches/5.1/Release_Notes/en-US/need_info.xml 2011-05-04 06:32:28 UTC (rev
6444)
@@ -1,196 +1,9 @@
-<?xml version='1.0'?>
+<?xml version='1.0' encoding='utf-8' ?>
<!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "5.1.1_Release_Notes.ent">
+%BOOK_ENTITIES;
]>
-<!-- release notes text customfield_12310211 -->
-
-
<variablelist>
-
- <!--
https://issues.jboss.org/browse/JBEPP-459 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-459"
/></term>
- <listitem>
- <para>
- Original Text:
-Thread safety issue leading to "Error while rendering the porlet
-java.lang.NullPointerException at
org.exoplatform.portal.webui.component.UIBreadcumbsPortlet.loadSelectedPath(UIBreadcumbsPortlet.java:69)"
under load.
-</para>
-<para>
-Cause: A bug in the double-check locking code.
-</para>
-<para>
-Consequence: A NullPointerException thrown from Breadcrumbs portlet under load.
-</para>
-<para>
- Fix: Volatile specifier added to eventMap field to prevent reordering.
-</para>
-<para>
- Result: NPE is no longer thrown.
-</para>
-<para>
- Proposed text:
-A bug in double-check locking code caused a NullPointerException to be thrown from the
Breadcrumbs portlet when under load. A 'volatile' java specifier was added to the
eventMap to prevent reordering, which resolved the issue. The portlet no longer throws the
NPE.
- </para>
- </listitem>
- </varlistentry>
+ <!-- release notes text customfield_12310211 -->
+</variablelist>
- <!--
https://issues.jboss.org/browse/JBEPP-597 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-597"
/></term>
- <listitem>
- <para>
- Cause: NEEDINFO What allowed the javascript to be executed? Or what what missing
that would have prevented it?
- </para>
- <para>
- Consequence: This allowed javascript snippets to be executed when creating a
new page through the Portal Dashboard.
- </para>
- <para>
- Fix: Groovy encoding methods have been added to the code to prevent this
(NEEDINFO Is this correct? What was added/removed that stops javascript?)
- </para>
- <para>
- Result: Javascript is no longer invoked when entered into page fields.
- </para>
- </listitem>
- </varlistentry>
-
- <!--
https://issues.jboss.org/browse/JBEPP-733 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-733"
/></term>
- <listitem>
- <para>
- The upload service will not work with Internet Explorer 7, any application using
the upload service (such as EPP SP) will not behave correctly with this web browser unless
if a name has been provided. A patch is available.
- </para>
- <para>
- NEEDINFO: Has this issue been corrected for 5.1.1? I.E. Has the patch been
incorporated into the product? And should this now be a "Resolved Issue"
- </para>
- </listitem>
- </varlistentry>
-
- <!--
https://issues.jboss.org/browse/JBEPP-773 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-773"
/></term>
- <listitem>
- <para>
- Cause: NEEDINFO (Was there a definite 'cause' [eg code bug or missing
code?])
- </para>
- <para>
- Consequence: The 'Preferences' tab would only appear in some portlets
if that portlet's portal.xml file had been modified to include it.
- </para>
- <para>
- Fix: The UIFormInputSet.java and UIPortletForm.java files have been
patched...NEEDINFO (what was added in the patch?)
- </para>
- <para>
- Result: The 'Preferences' tab now appears in all portlets?
- </para>
- </listitem>
- </varlistentry>
-
- <!--
https://issues.jboss.org/browse/JBEPP-779 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-779"
/></term>
- <listitem>
- <para>
- Configuration moved from jar file to portal.war.
- </para>
- <para>
- <remark>Does this need a release note?</remark>
- </para>
- </listitem>
- </varlistentry>
-
- <!--
https://issues.jboss.org/browse/JBEPP-794 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-794"
/></term>
- <listitem>
- <para>
- Cause: NEEDINFO
- </para>
- <para>
- Consequence: Resources (js, css, etc) added to new portlets with the
doHeaders() method were added twice.
- </para>
- <para>
- Fix: A patch has been applied that... NEEDINFO (What does the patch do?)
- </para>
- <para>
- Result: New resources are only linked once.
- </para>
- </listitem>
- </varlistentry>
-
- <!--
https://issues.jboss.org/browse/JBEPP-848 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-848"
/></term>
- <listitem>
- <para>
- Cause: A bug in data caching prevented some changes to Portal navigation from
reloading in real time.
- </para>
- <para>
- Consequence: When changing a group navigation priority, the reordering of the
groups was only happening after logging out.
- </para>
- <para>
- Fix: The UIPageNavigationForm.java has been patched...NEEDINFO (what does the
patch do?)
- </para>
- <para>
- Result: Now data updates immediately, without the user needing to log out.
- </para>
- </listitem>
- </varlistentry>
-
- <!--
https://issues.jboss.org/browse/JBEPP-857 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-857"
/></term>
- <listitem>
- <para>
- Cause: NEEDINFO (Code bug? Caching issue? Data writing issue? Permission
issue?)
- </para>
- <para>
- Consequence: WSRP 'Strict Mode' was not properly restored when EPP
was started.
- </para>
- <para>
- Fix: An upgrade to WSRP 2.0.1 GA corrects this issue.
- </para>
- <para>
- Result: WSRP Strict Mode is now implemented at startup.
- </para>
- </listitem>
- </varlistentry>
-
- <!--
https://issues.jboss.org/browse/JBEPP-899 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-899"
/></term>
- <listitem>
- <para>
- Cause: NEEDINFO Why couldn't MOPPortalStructuralAccess close POMSession
properly?
- </para>
- <para>
- Consequence: An NPE was thrown (from GTNPORTAL-1868)?
- </para>
- <para>
- Fix: A code change in MOPPortalStructureAccess.java requires EPP to save the
session instead of closing it.
- </para>
- <para>
- Result: MOPPortalStructuralAccess can now close the POMSession properly and
the NPE no longer occurs.
- </para>
- </listitem>
- </varlistentry>
-
- <!--
https://issues.jboss.org/browse/JBEPP-902 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-902"
/></term>
- <listitem>
- <para>
- Cause: In previous Portal versions, page definitions were held in system memory
before being written when starting the Portal.
- </para>
- <para>
- Consequence: This could cause an Out Of Memory error if a large number of
pages were defined in the XML descriptors (NEEDINFO How many is 'many' pages?).
- </para>
- <para>
- Fix: The transaction has now been split so that not all page definitions are
held in memory prior to being written.
- </para>
- <para>
- Result: The Out Of Memory error is no longer encountered (NEEDINFO No upper
limit on page numbers now?)
- </para>
- </listitem>
- </varlistentry>
-
-</variablelist>
\ No newline at end of file
Modified: epp/docs/branches/5.1/Release_Notes/en-US/resolved_issues.xml
===================================================================
--- epp/docs/branches/5.1/Release_Notes/en-US/resolved_issues.xml 2011-05-04 04:18:44 UTC
(rev 6443)
+++ epp/docs/branches/5.1/Release_Notes/en-US/resolved_issues.xml 2011-05-04 06:32:28 UTC
(rev 6444)
@@ -1,48 +1,159 @@
-<?xml version='1.0'?>
+<?xml version='1.0' encoding='utf-8' ?>
<!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!ENTITY % BOOK_ENTITIES SYSTEM "5.1.1_Release_Notes.ent">
+%BOOK_ENTITIES;
]>
-<!-- release notes text customfield_12310211 -->
+<variablelist>
+ <!-- release notes text customfield_12310211 --> <!--
https://issues.jboss.org/browse/JBEPP-400 --> <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-400"
/></term>
+ <listitem>
+ <para>
+ Warning messages were found in the server log when starting JBoss Enterprise Portal
Platform 5 without an active internet connection. This was because the Java EE Webservices
Metadata Handler 2.0 schema was requested via the network at start up. The schema is now
bundled with the WSRP which allows JBoss Enterprise Portal Platform to start without
producing error messages if there is no internet connection.
+ </para>
+ </listitem>
-<variablelist>
-
- <!--
https://issues.jboss.org/browse/JBEPP-400 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-400"
/></term>
- <listitem>
- <para>
- Warning messages were found in the server log when starting EPP 5 without an
active internet connection. This was because the Java EE Webservices Metadata Handler 2.0
schema was requested via the network at start up. The schema is now bundled with the WSRP
which allows EPP to start without producing error messages if there is no internet
connection.
- </para>
- </listitem>
- </varlistentry>
+ </varlistentry>
+ <!--
https://issues.jboss.org/browse/JBEPP-459 --> <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-459"
/></term>
+ <listitem>
+ <para>
+ A thread safety issue in the breadcrumb portlet could lead to NullPointerException
under load.The issue has been fixed.
+ </para>
- <!--
https://issues.jboss.org/browse/JBEPP-890 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-890"
/></term>
- <listitem>
- <para>
- Exceptions thrown by the handleFaceletNotFound method (when a facelet file was
not found) were being obscured by FaceletViewHandler as the response object was not a
subtype of HttpServletResponse (it is a instance of PortletResponse).
- </para>
- <para>
- FaceletPortletViewHandler.java has been updated to handle instances of both
HttpServletResponse and PortletResponse response objects.
- </para>
- <para>
- (Text taken from same issue in 4.3.CP06 Release Notes JBEPP-447
http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/4.3/ht...)
- </para>
- </listitem>
- </varlistentry>
+ </listitem>
- <!--
https://issues.jboss.org/browse/JBEPP-896 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-896"
/></term>
- <listitem>
- <para>
- The Single Sign On (SSO) AbstractLogoutFilter in EPP would read request
parameters before setting the character encoding. When a form was submitted with non-UTF-8
characters (while SSO was enabled) the values could be garbled on output.
- </para>
- <para>
- An upgrade of the SSO component to version 1.0.2-epp-GA (which includes a
patch to the AbstractLogoutFilter code) resolves this issue and non-UTF-8 characters are
now specified correctly.
- </para>
- </listitem>
- </varlistentry>
+ </varlistentry>
+ <!--
https://issues.jboss.org/browse/JBEPP-597 --> <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-597"
/></term>
+ <listitem>
+ <para>
+ The name of a dashboard page entered by user was not properly encoded before being
returned on the web browser. This allowed javascript snippets to be executed when creating
a new page through the Portal Dashboard. The name of the page is now properly HTML encoded
before being returned and javascript is no longer invoked when entered into page fields.
+ </para>
+ </listitem>
+
+ </varlistentry>
+ <!--
https://issues.jboss.org/browse/JBEPP-610 --> <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-610"
/></term>
+ <listitem>
+ <para>
+ Previous versions of JBoss Enterprise Portal Platform wrote saved passwords to the
JCR database in plain text. This created a possible security risk as user passwords could
be obtained with an SQL query. Passwords are now encrypted when written to the database,
negating the security risk.
+ </para>
+
+ </listitem>
+
+ </varlistentry>
+ <!--
https://issues.jboss.org/browse/JBEPP-733 --> <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-733"
/></term>
+ <listitem>
+ <para>
+ A bug cause the JBoss Enterprise Portal Platform upload service to not work properly
with Internet Explorer 7. As a result, any application using the upload service (such as
Site Publisher) would not behave correctly with this web browser unless a name was
provided. The bug has been fixed and the upload service now works as expected in all
browsers (including IE7).
+ </para>
+
+ </listitem>
+
+ </varlistentry>
+ <!--
https://issues.jboss.org/browse/JBEPP-773 --> <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-773"
/></term>
+ <listitem>
+ <para>
+ A bug prevented the 'Preferences' tab from appearing in some portlets. The
tab would only appear in portlets that were customized during the first deployment through
the portal.xml descriptor. Non-customized portlets would not show a 'Preferences'
tab. The UIFormInputSet.java and UIPortletForm.java files have been patched to fix the
issue and now the tab now appears in all portlets that have configurable preferences.
+ </para>
+
+ </listitem>
+
+ </varlistentry>
+ <!--
https://issues.jboss.org/browse/JBEPP-780 --> <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-780"
/></term>
+ <listitem>
+ <para>
+ The two JBoss Cache instances created by PicketLink were calling on the same
configuration file in idm-configuration.xml and, as a result, were using the same cluster
names. This could lead to conflicts as the same JBoss Cache instance could join the same
channel twice. Separate configuration files were added to the distribution package and the
Portal configuration was customized to call on the different files. JBoss Cache instances
can now run simultaneously without conflict.
+ </para>
+
+ </listitem>
+
+ </varlistentry>
+ <!--
https://issues.jboss.org/browse/JBEPP-794 --> <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-794"
/></term>
+ <listitem>
+ <para>
+ When adding resources (js, css, etc) to the Head of the HTML response with the
doHeaders method a bug was encountered which caused those resources to be added twice. A
patch has been applied to fix the bug and new resources are now only linked once.
+ </para>
+
+ </listitem>
+
+ </varlistentry>
+ <!--
https://issues.jboss.org/browse/JBEPP-848 --> <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-848"
/></term>
+ <listitem>
+ <para>
+ A bug in data caching prevented some changes to Portal navigation from reloading in
real time. When changing a group navigation priority, the reordering of the groups was
only happening after a log-out. The UIPageNavigationForm.java has been patched to correct
this and navigation changes now update immediately, without the user needing to log-out.
+ </para>
+
+ </listitem>
+
+ </varlistentry>
+ <!--
https://issues.jboss.org/browse/JBEPP-857 --> <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-857"
/></term>
+ <listitem>
+ <para>
+ WSRP Strict mode was previously set only via listeners, which were not triggered at
startup since they don't yet exist at that time. This meant that WSRP Strict Mode was
not properly restored when JBoss Enterprise Portal Platform was started. An upgrade to
WSRP 2.0.1 GA corrects this issue and WSRP Strict Mode is now properly restored from
persistent state at startup.
+ </para>
+
+ </listitem>
+
+ </varlistentry>
+ <!--
https://issues.jboss.org/browse/JBEPP-890 --> <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-890"
/></term>
+ <listitem>
+ <para>
+ Exceptions thrown by the handleFaceletNotFound method (when a facelet file was not
found) were being obscured by FaceletViewHandler as the response object was not a subtype
of HttpServletResponse (it is a instance of PortletResponse).
FaceletPortletViewHandler.java has been updated to handle instances of both
HttpServletResponse and PortletResponse response objects.
+ </para>
+
+ </listitem>
+
+ </varlistentry>
+ <!--
https://issues.jboss.org/browse/JBEPP-896 --> <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-896"
/></term>
+ <listitem>
+ <para>
+ The Single Sign On (SSO) AbstractLogoutFilter in JBoss Enterprise Portal Platform
would read request parameters before setting the character encoding. When a form was
submitted with non-UTF-8 characters (while SSO was enabled) the values could be garbled on
output. An upgrade of the SSO component to version 1.0.2-epp-GA (which includes a patch to
the AbstractLogoutFilter code) resolves this issue and Non-UTF-8 characters are now
specified correctly.
+ </para>
+
+ </listitem>
+
+ </varlistentry>
+ <!--
https://issues.jboss.org/browse/JBEPP-899 --> <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-899"
/></term>
+ <listitem>
+ <para>
+ MOPPortalStructuralAccess was improperly closing the POMSession that was under
control of another Portal component, leaving that component unable to properly access JCR
state. An NPE was thrown when other components tried to access the closed POMSession.
MOPPortalStructureAccess now simply saves the session instead of saving *and* closing it.
Since MOPPortalStructuralAccess doesn't close the POMSession anymore, it can still be
used by components upstream without issue.
+ </para>
+
+ </listitem>
+
+ </varlistentry>
+ <!--
https://issues.jboss.org/browse/JBEPP-902 --> <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-902"
/></term>
+ <listitem>
+ <para>
+ In previous Portal versions, page definitions were held in system memory before being
written when starting the Portal. This could cause an Out Of Memory error if a large
number of pages were defined in the XML descriptors. The transaction has now been split so
that not all page definitions are held in memory prior to being written and the Out Of
Memory error is no longer encountered.
+ </para>
+
+ </listitem>
+
+ </varlistentry>
+ <!--
https://issues.jboss.org/browse/JBEPP-904 --> <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-904"
/></term>
+ <listitem>
+ <para>
+ JBoss Enterprise Portal Platform doesn't set content-type on css-files added via
gatein-resources.xml. This causes Internet Explorer 9 to ignore these css-files due to new
security policy (a console message states: SEC7113: CSS was ignored due to mime type
mismatch). The ResourceRequestFilter.java file has been modified to set the content type
so that content-types will be set and Internet Explorer 9 will render the Portal as
expected.
+ </para>
+
+ </listitem>
+
+ </varlistentry>
+
</variablelist>
+