Author: jaredmorgs
Date: 2012-03-29 00:33:27 -0400 (Thu, 29 Mar 2012)
New Revision: 8663
Modified:
epp/docs/branches/5.2/Installation_Guide/en-US/Book_Info.xml
epp/docs/branches/5.2/Installation_Guide/en-US/DatabaseConfiguration.xml
epp/docs/branches/5.2/Installation_Guide/en-US/Getting_Started.xml
epp/docs/branches/5.2/Installation_Guide/en-US/HTTPSConfiguration.xml
epp/docs/branches/5.2/Installation_Guide/en-US/Installation_Guide.xml
epp/docs/branches/5.2/Installation_Guide/en-US/Revision_History.xml
epp/docs/branches/5.2/Release_Notes/en-US/5.2.1_Release_Notes.xml
epp/docs/branches/5.2/Release_Notes/en-US/Book_Info.xml
epp/docs/branches/5.2/Release_Notes/en-US/Revision_History.xml
epp/docs/branches/5.2/Release_Notes/en-US/known.xml
epp/docs/branches/5.2/Release_Notes/en-US/needinfo.xml
epp/docs/branches/5.2/Release_Notes/en-US/resolved.xml
Log:
changes from today
Modified: epp/docs/branches/5.2/Installation_Guide/en-US/Book_Info.xml
===================================================================
--- epp/docs/branches/5.2/Installation_Guide/en-US/Book_Info.xml 2012-03-28 15:37:01 UTC
(rev 8662)
+++ epp/docs/branches/5.2/Installation_Guide/en-US/Book_Info.xml 2012-03-29 04:33:27 UTC
(rev 8663)
@@ -9,7 +9,7 @@
<productname>JBoss Enterprise Portal Platform</productname>
<productnumber>5.2</productnumber>
<edition>5.2.1</edition>
- <pubsnumber>12</pubsnumber>
+ <pubsnumber>13</pubsnumber>
<abstract>
<para>This book provides information about obtaining, installing and running
JBoss Enterprise Portal Platform and its add-ons. It forms part of the complete document
suite along with the <citetitle>User Guide</citetitle> and
<citetitle>Reference Guide</citetitle> available at <ulink
url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platf...
type="http"/>.
</para>
Modified: epp/docs/branches/5.2/Installation_Guide/en-US/DatabaseConfiguration.xml
===================================================================
--- epp/docs/branches/5.2/Installation_Guide/en-US/DatabaseConfiguration.xml 2012-03-28
15:37:01 UTC (rev 8662)
+++ epp/docs/branches/5.2/Installation_Guide/en-US/DatabaseConfiguration.xml 2012-03-29
04:33:27 UTC (rev 8663)
@@ -164,7 +164,7 @@
<para>Open
<filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable>PROFILE</replaceable>/deploy/gatein-ds.xml</filename>
in a text editor.</para>
</step>
<step>
- <para>Locate the
<jndi-name>gatein-idm</jndi-name> directives that affect JCR
datasource descriptors: </para>
+ <para>Locate the
<jndi-name>gatein-idm</jndi-name> directives that affect IDM
datasource descriptors: </para>
<itemizedlist>
<listitem>
<para><connection-url></para>
Modified: epp/docs/branches/5.2/Installation_Guide/en-US/Getting_Started.xml
===================================================================
--- epp/docs/branches/5.2/Installation_Guide/en-US/Getting_Started.xml 2012-03-28 15:37:01
UTC (rev 8662)
+++ epp/docs/branches/5.2/Installation_Guide/en-US/Getting_Started.xml 2012-03-29 04:33:27
UTC (rev 8663)
@@ -88,7 +88,7 @@
<formalpara>
<title>Supported Installations</title>
<para>
- For the latest information on supported JBoss Enterprise Portal
Platform technology combinations, refer to <ulink
url="http://www.jboss.com/products/platforms/portals/testedconfigura...;.
+ For the latest information on supported JBoss Enterprise Portal
Platform technology combinations, refer to <ulink
url="http://www.redhat.com/resourcelibrary/articles/jboss-enterprise...;.
</para>
</formalpara>
</section>
Modified: epp/docs/branches/5.2/Installation_Guide/en-US/HTTPSConfiguration.xml
===================================================================
--- epp/docs/branches/5.2/Installation_Guide/en-US/HTTPSConfiguration.xml 2012-03-28
15:37:01 UTC (rev 8662)
+++ epp/docs/branches/5.2/Installation_Guide/en-US/HTTPSConfiguration.xml 2012-03-29
04:33:27 UTC (rev 8663)
@@ -43,13 +43,13 @@
<para>Understand the command-line parameters of
<command>keytool</command> as documented in the <ulink
url="http://docs.oracle.com/javase/1.5.0/docs/tooldocs/solaris/keyto...
Java Tools documentation</ulink> </para>
</listitem>
<listitem>
- <para>Know the JDK keystore password (default is
"<literal>changeme</literal>").</para>
+ <para>Obtain the JDK keystore password. For new installations, the
default JDK password is
"<literal>changeme</literal>".</para>
</listitem>
</itemizedlist>
</taskprerequisites>
<procedure>
<step>
- <para>Navigate
to<filename><replaceable>JBOSS_HOME</replaceable>/jboss-as/server/<replaceable>PROFILE</replaceable>/conf/</filename></para>
+ <para>Navigate to
<filename><replaceable>JBOSS_HOME</replaceable>/jboss-as/server/<replaceable>PROFILE</replaceable>/conf/</filename></para>
</step>
<step>
<para>Generate the keystore by executing the following command. Ensure you
substitute the <replaceable>values</replaceable> with information relevant
to your organization, and record the information for later use:</para>
@@ -61,11 +61,11 @@
<para>You must enable elevated privileges to execute this command.
</para>
</important>
<programlisting>[conf]# keytool -importkeystore -srckeystore
<replaceable>server.keystore</replaceable> -alias
<replaceable>epp5key</replaceable> -destkeystore
$JAVA_HOME/jre/lib/security/cacerts</programlisting>
- <para>When prompted, provide the destination (JDK) keystore password, as
well as the source keystore password you created in the previous step.</para>
+ <para>When prompted, provide the destination JDK keystore password you
obtained in the prerequisites, as well as the source keystore password you created in the
previous step. </para>
</step>
<step>
<para>Execute the following command to verify the keystore file has been
correctly imported into the JDK keystore:</para>
- <programlisting>[conf]# keytool -list -keystore
/usr/java/<replaceable>JDK_VERSION</replaceable>/jre/lib/security/cacerts
-alias <replaceable>epp5key</replaceable></programlisting>
+ <programlisting>[conf]# keytool -list -keystore
$JAVA_HOME/jre/lib/security/cacerts -alias
<replaceable>epp5key</replaceable></programlisting>
<formalpara>
<title>Result</title>
<para>The command returns one PrivateKeyEntry</para>
Modified: epp/docs/branches/5.2/Installation_Guide/en-US/Installation_Guide.xml
===================================================================
--- epp/docs/branches/5.2/Installation_Guide/en-US/Installation_Guide.xml 2012-03-28
15:37:01 UTC (rev 8662)
+++ epp/docs/branches/5.2/Installation_Guide/en-US/Installation_Guide.xml 2012-03-29
04:33:27 UTC (rev 8663)
@@ -1,5 +1,6 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!-- This document was created with Syntext Serna Free. --><!DOCTYPE book PUBLIC
"-//OASIS//DTD DocBook XML V4.5//EN"
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+<!-- This document was created with Syntext Serna Free. -->
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
<!ENTITY % BOOK_ENTITIES SYSTEM "Installation_Guide.ent">
%BOOK_ENTITIES;
]>
Modified: epp/docs/branches/5.2/Installation_Guide/en-US/Revision_History.xml
===================================================================
--- epp/docs/branches/5.2/Installation_Guide/en-US/Revision_History.xml 2012-03-28
15:37:01 UTC (rev 8662)
+++ epp/docs/branches/5.2/Installation_Guide/en-US/Revision_History.xml 2012-03-29
04:33:27 UTC (rev 8663)
@@ -9,6 +9,22 @@
<simpara>
<revhistory>
<revision>
+ <revnumber>5.2.1-13</revnumber>
+ <date>Thu Mar 29 2012</date>
+ <author>
+ <firstname>Jared</firstname>
+ <surname>Morgan</surname>
+ <email/>
+ </author>
+ <revdescription>
+ <simplelist>
+ <
member>https://bugzilla.redhat.com/show_bug.cgi?id=794440 -
Incorporated Docs QE feedback as prescribed in the bug. NEEDINFO on keytool
issue.</member>
+ <
member>https://bugzilla.redhat.com/show_bug.cgi?id=794386 - corrected
JCR to IDM in the prescribed Docs QE feedback.</member>
+ <
member>https://bugzilla.redhat.com/show_bug.cgi?id=793548 - Updated
supported configurations link to display the correct
redhat.com address, per Docs QE
feedback.</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+ <revision>
<revnumber>5.2.1-12</revnumber>
<date>Tue Mar 20 2012</date>
<author>
Modified: epp/docs/branches/5.2/Release_Notes/en-US/5.2.1_Release_Notes.xml
===================================================================
--- epp/docs/branches/5.2/Release_Notes/en-US/5.2.1_Release_Notes.xml 2012-03-28 15:37:01
UTC (rev 8662)
+++ epp/docs/branches/5.2/Release_Notes/en-US/5.2.1_Release_Notes.xml 2012-03-29 04:33:27
UTC (rev 8663)
@@ -23,7 +23,7 @@
</chapter>
<chapter id="Release_Notes-Component_Features">
<title>Component Versions </title>
- <para><remark>Updated table from
https://docspace.corp.redhat.com/docs/DOC-68705 (version 20)</remark></para>
+ <para><remark>Updated table from
https://docspace.corp.redhat.com/docs/DOC-68705 (version 23)</remark></para>
<table frame="all" pgwide="1">
<title>Component Versions</title>
<tgroup cols="2" colsep="1">
@@ -90,11 +90,11 @@
</row>
<row>
<entry>GateIn WSRP</entry>
- <entry>2.1.1-EPP521-GA</entry>
+ <entry>2.1.4-EPP521-GA</entry>
</row>
<row>
<entry>GateIn MOP</entry>
- <entry>1.1.1-GA</entry>
+ <entry>1.1.2-GA</entry>
</row>
<row>
<entry>GateIn SSO</entry>
@@ -110,7 +110,7 @@
</row>
<row>
<entry>Portlet Bridge</entry>
- <entry>2.3.0.GA.EPP521</entry>
+ <entry>2.3.0.CP01.EPP521</entry>
</row>
<row>
<entry>Seam</entry>
@@ -166,17 +166,9 @@
<varlistentry>
<term>Gatein JON Plugin</term>
<listitem>
- <para>The Gatein JON plugin allows the portal to interact with JBoss
Operations Network <remark><more info
required>.</remark></para>
+ <para>The Gatein JON plugin allows the portal to interact with JBoss
Operations Network. The plugin captures portlet and site statistics.</para>
</listitem>
</varlistentry>
- <varlistentry>
- <term>
- <remark>Shiny New Component Number 2</remark>
- </term>
- <listitem>
- <para><remark>Some info about the shiny new component
</remark></para>
- </listitem>
- </varlistentry>
</variablelist>
<formalpara>
<title>Updated Components</title>
@@ -186,7 +178,7 @@
<varlistentry>
<term>Java Content Repository</term>
<listitem>
- <para><remark>Anything particularly new about the JCR this time
around? </remark></para>
+ <para>The JCR configuration has been corrected in the
configuration.properties file. The previous configuration was incorrect. </para>
</listitem>
</varlistentry>
<varlistentry>
@@ -195,14 +187,6 @@
<para>Packaging changes require different file paths for JOSSO. Refer to
the Reference Guide "Java Open Single Sign-On Project" section for more
information.</para>
</listitem>
</varlistentry>
- <varlistentry>
- <term>
- <remark>Shiny New Component Number 3</remark>
- </term>
- <listitem>
- <para><remark>Some info about the shiny new component
</remark></para>
- </listitem>
- </varlistentry>
</variablelist>
<note>
<para>For detailed information about component versions included in this
release, refer to <xref
linkend="Release_Notes-Component_Features"/></para>
Modified: epp/docs/branches/5.2/Release_Notes/en-US/Book_Info.xml
===================================================================
--- epp/docs/branches/5.2/Release_Notes/en-US/Book_Info.xml 2012-03-28 15:37:01 UTC (rev
8662)
+++ epp/docs/branches/5.2/Release_Notes/en-US/Book_Info.xml 2012-03-29 04:33:27 UTC (rev
8663)
@@ -9,7 +9,7 @@
<productname>JBoss Enterprise Portal Platform</productname>
<productnumber>5.2</productnumber>
<edition>5.2.1</edition>
- <pubsnumber>5</pubsnumber>
+ <pubsnumber>7</pubsnumber>
<abstract>
<para>
These release notes contain important information related to JBoss Enterprise
Portal Platform &VZ; that may not be currently available in the Product Manuals. You
should read these Release Notes in their entirety before installing the product.
Modified: epp/docs/branches/5.2/Release_Notes/en-US/Revision_History.xml
===================================================================
--- epp/docs/branches/5.2/Release_Notes/en-US/Revision_History.xml 2012-03-28 15:37:01 UTC
(rev 8662)
+++ epp/docs/branches/5.2/Release_Notes/en-US/Revision_History.xml 2012-03-29 04:33:27 UTC
(rev 8663)
@@ -8,8 +8,8 @@
<simpara>
<revhistory>
<revision>
- <revnumber>5.2.1-5</revnumber>
- <date>Tue Mar 27 2012</date>
+ <revnumber>5.2.1-7</revnumber>
+ <date>Thu Mar 29 2012</date>
<author>
<firstname>Jared</firstname>
<surname>Morgan</surname>
@@ -17,7 +17,7 @@
</author>
<revdescription>
<simplelist>
- <member>Cumulative draft run of Release Notes doc using BZ extraction
script for JBoss Enterprise Portal Platform 5.2.1 GA. Now with Bug status and assigned
engineer.</member>
+ <member>All Release Note triage by me is complete. Over to the SMEs to
complete their RN entries.</member>
</simplelist>
</revdescription>
</revision>
Modified: epp/docs/branches/5.2/Release_Notes/en-US/known.xml
===================================================================
--- epp/docs/branches/5.2/Release_Notes/en-US/known.xml 2012-03-28 15:37:01 UTC (rev
8662)
+++ epp/docs/branches/5.2/Release_Notes/en-US/known.xml 2012-03-29 04:33:27 UTC (rev
8663)
@@ -9,12 +9,22 @@
The following issues are known to exist in JBoss Enterprise Portal Platform,
and will be fixed in a subsequent release.
</para>
<remark>
- Do some of these issues look more like Resolved Issues? If they do, its because
the ticket has not been set to the correct
- resolution status (VERIFIED, CLOSED).
+ Do some of these issues look more like <emphasis>Resolved
Issues</emphasis>? If they do, its because the ticket has not been set to the
correct
+ Resolved Issue status (VERIFIED, CLOSED).
</remark>
<variablelist>
<varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=807279"><...
- Support WSRP applications for Export/Import</term>
+ <listitem>
+ <remark>Status: NEW</remark>
+ <para>
+ When WSRP is added to a page, and a user attempts to export the page using the
portal management functions, an exception displays stating WSRP is not supported. This
issue is being investigated, and will be included in a future release of the portal. There
is no workaround to this issue.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
<term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=794440"><...
- Docs: Instructions on how to set up the https connector are incomplete</term>
<listitem>
<remark>Status: ASSIGNED</remark>
@@ -29,9 +39,7 @@
<listitem>
<remark>Status: ON_QA</remark>
<para>
- CAUSE: Due to error in PicketLink IDM it was trying to remove user in store
where it was not present
-
-FIX: Code and logic was corrected to remove user only in proper identity store
(
https://issues.jboss.org/browse/PLIDM-36)
+ It was discovered that an error in the PicketLink IDM caused a problem with
removing an LDAP User from a read/write user store, when the user was not present in the
IDM database. The fix introduces logic improvements to user management that ensures a user
can only be removed from the correct identity store.
</para>
</listitem>
</varlistentry>
@@ -67,6 +75,37 @@
</varlistentry>
<varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=793319"><...
- Remove IP addresses from picketlink msad example config files</term>
+ <listitem>
+ <remark>Status: ON_QA</remark>
+ <para>
+ It was discovered that the Microsoft Active Directory (MSAD) configuration files
(<filename>picketlink-idm-msad-config.xml</filename> and
<filename>picketlink-idm-msad-readonly-config.xml</filename>) contained a
providerURL property with an IP address specified. The IP address was interpreted by
customers as required and mandatory, instead of being interpreted as a value that needed
to be changed to an valid IP address used in the customer's implementation. The fix
replaces the numerical IP address with replaceable values that are more prescriptive to
users, which corrects the originally reported issue.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=793910"><...
- GTNPORTAL-1940 calender doesnt disappear if tab is used for navigation</term>
+ <listitem>
+ <remark>Status: ON_QA</remark>
+ <para>
+ It was discovered that when users tabbed away from the calendar field, the
calendar dialog persisted. Users had to click outside the calendar field to close the
calendar dialog. The fix introduces updated behavior which ensures the calendar dialog
closes on tab navigation away from the field. This corrects the originally reported
issue.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=794181"><...
- Some first name and last name parameters are reversed in Japanese message bundle of
UserInfoPortlet</term>
+ <listitem>
+ <remark>Status: ON_QA</remark>
+ <para>
+ An issue was found in UserInfoPortlet concerning the
+"firstname" and "lastname" Japanese field translations. The first
name and last name field translations were swapped, which made it difficult for Japanese
users to populate the correct fields with appropriate name data. The fix correct the
labels for the firstname and lastname fields, which corrects the originally reported
issue.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
<term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=793259"><...
- IE6 User Interface problems</term>
<listitem>
<remark>Status: ON_QA</remark>
@@ -77,14 +116,44 @@
</varlistentry>
<varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=793639"><...
- Create additional portal objects for external groups</term>
+ <listitem>
+ <remark>Status: ON_QA</remark>
+ <para>
+ If a user manually added users or groups into a Java Content Repository or LDAP,
the required objects were not created because some necessary listeners were not called as
they would be if the Organization API was used. This could result in exceptions in some
situations, because the required JCR objects for a particular user or group were not
correctly initialized. The fix introduces the CoreOrganizationInitializer plugin
(exo.portal.component.initializer), which monitors the JCR and LDAP for changes and
initiates the listeners when required. The plugin is disabled by default, but can be
enabled by a portal administrator by uncommenting the block in
<filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable>PROFILE</replaceable>/deploy/gatein.ear/02portal.war/WEB-INF/conf/configuration.xml</filename>,
which imports the configuration stored in the initializer-configuration.xml file.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
<term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=793804"><...
- logged in user's role change doesn't take effect on the UI after a certain
amount of "cache" time or user logs out and re-login.</term>
<listitem>
<remark>Status: ON_QA</remark>
<para>
- It was discovered that changing memberships of already authenticated users did
not immediately take effect. If a user had administrative membership revoked, and remained
logged onto the portal, the privileges were still accessible for up to 30 minutes until
the user permissions cache was refreshed. This could permit the user to perform
undesirable actions in the portal. The fix introduces a new listener
"MembershipUpdateListener" which has been added to
<replaceable>JBOSS_HOME</replaceable>/server/<replaceable>PROFILE</replaceable>/deploy/gatein.ear/02portal.war/WEB-INF/conf/organization/organization-configuration.xml
directive file. The listener immediately updates authenticated user memberships based on
information in the ConversationRegistry. Changes to user memberships now take effect
immediately, which corrects the originally reported issue.
+ It was discovered that changing memberships of already authenticated users did
not immediately take effect. If a user had administrative membership revoked, and remained
logged onto the portal, the privileges were still accessible for up to 30 minutes until
the user permissions cache was refreshed. This could permit the user to perform
undesirable actions in the portal. The fix introduces a new listener
"MembershipUpdateListener" which has been added to
<filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable>PROFILE</replaceable>/deploy/gatein.ear/02portal.war/WEB-INF/conf/organization/organization-configuration.xml</filename>
directive file. The listener immediately updates authenticated user memberships based on
information in the ConversationRegistry. Changes to user memberships now take effect
immediately, which corrects the originally reported issue.
</para>
</listitem>
</varlistentry>
+<varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=794394"><...
- Invalid page title of page causes unability to edit node</term>
+ <listitem>
+ <remark>Status: ON_QA</remark>
+ <para>
+ An issue with field value validation in page title fields caused angle brackets
to be added verbatim to the page title. These verbatim characters resulted in portal page
errors because the angle brackets were not substituted with HTML character references when
the form was saved. The fix introduces NoHTMLTagValidator logic in page title fields,
which prevents verbatim angle brackets from being entered into the field. Angle brackets
can be included in titles, providing the correct HTML character references are declared:
&lt; and &gt;
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=803544"><...
- ViewExpiredException when using Portlet Bridge over WSRP with WS Security</term>
+ <listitem>
+ <remark>Status: ON_QA</remark>
+ <para>
+ The cookie session handler was not being set on each request from the producer
and the consumer when ws-security was enabled. A session was created on each request, and
any portlets that relied on sessions would not function properly. The fix implements
changes to the order of the web service handlers that ensure the session is properly added
on each invocation between the consumer and producer. Sessions now work properly with WSRP
when WS-Security is enabled
+ </para>
+ </listitem>
+</varlistentry>
+
</variablelist>
</chapter>
Modified: epp/docs/branches/5.2/Release_Notes/en-US/needinfo.xml
===================================================================
--- epp/docs/branches/5.2/Release_Notes/en-US/needinfo.xml 2012-03-28 15:37:01 UTC (rev
8662)
+++ epp/docs/branches/5.2/Release_Notes/en-US/needinfo.xml 2012-03-29 04:33:27 UTC (rev
8663)
@@ -26,130 +26,15 @@
</varlistentry>
<varlistentry>
- <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=806965"><...
- PortletModes and WindowStates are not properly broadcasting events in
webui</term>
- <listitem>
- <para>The status is ASSIGNED, assigned to ghu(a)redhat.com.</para>
- <para>
- PATCH NAME:
- 806915
-PRODUCT NAME:
- JBoss Enterprise Portal Platform (EPP)
-VERSION:
- 5.2.0.GA
-SHORT DESCRIPTION:
- Bug 793905 PortletModes and WindowStates are not properly broadcasting events in
webui.
-LONG DESCRIPTION:
- PortletModes and WindowStates are not properly broadcasting events in webui.
Further details can be found in Bug 793905.
-MANUAL INSTALL INSTRUCTIONS:
- replace the jar
-$EPP5_HOME/server/$PROFILE/deploy/gatein.ear/lib/exo.portal.webui.portal-5.2.0.GA.jar
- with the patched one.
-COMPATIBILITY:
- N/A
-DEPENDENCIES:
- N/A
-SUPERSEDES:
- N/A
-SUPERSEDED BY:
- EPP 5.2.GA
-CREATOR:
- Gary Hu
-DATE:
- Mar 26, 2012
- </para>
- </listitem>
-</varlistentry>
-
-<varlistentry>
- <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=798987"><...
- Update outdated cache and clustering setup.</term>
- <listitem>
- <para>The status is MODIFIED, assigned to
jbpapp-maint(a)redhat.com.</para>
- <para>
- ==IS THIS A RELEASE NOTE, OR A DOCS CHANGE?==
- </para>
- </listitem>
-</varlistentry>
-
-<varlistentry>
- <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=793319"><...
- Remove IP addresses from picketlink msad example config files</term>
- <listitem>
- <para>The status is ON_QA, assigned to hfnukal(a)redhat.com.</para>
- <para>
- ==CUSTOMER FACING ISSUE REQUIRES RELEASE NOTE==
-
-CAUSE:
-
-CONSEQUENCE:
-
-FIX:
-
-RESULT:
- </para>
- </listitem>
-</varlistentry>
-
-<varlistentry>
- <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=793910"><...
- GTNPORTAL-1940 calender doesnt disappear if tab is used for navigation</term>
- <listitem>
- <para>The status is ON_QA, assigned to hfnukal(a)redhat.com.</para>
- <para>
- ==HELPDESK TICKET REQUIRES CCFR REVIEW BY SME==
-
-CAUSE: It was discovered that when users tabbed away from the calendar field, the
calendar dialog persisted.
-
-CONSEQUENCE: Users had to click outside the calendar field to close the calendar dialog.
-
-FIX: The fix introduces updated behavior to the [component name], which ensures the
calendar dialog closes on tab navigation away from the field
-
-RESULT: This corrects the originally reported issue.
- </para>
- </listitem>
-</varlistentry>
-
-<varlistentry>
- <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=794181"><...
- Some first name and last name parameters are reversed in Japanese message bundle of
UserInfoPortlet</term>
- <listitem>
- <para>The status is ON_QA, assigned to hfnukal(a)redhat.com.</para>
- <para>
- ==NEEDINFO==
-
-CAUSE:
-
-CONSEQUENCE:
-
-FIX:
-
-RESULT:
- </para>
- </listitem>
-</varlistentry>
-
-<varlistentry>
- <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=794432"><...
- Upgrade eXo JCR to 1.14.6 (and dependencies)</term>
- <listitem>
- <para>The status is ON_QA, assigned to hfnukal(a)redhat.com.</para>
- <para>
- CAUSE:
-
-CONSEQUENCE:
-
-FIX:
-
-RESULT:
- </para>
- </listitem>
-</varlistentry>
-
-<varlistentry>
<term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=794445"><...
- Admin console does not display JBoss info: only OS info is shown</term>
<listitem>
<para>The status is ON_QA, assigned to hfnukal(a)redhat.com.</para>
<para>
- ==PARTIAL RELEASE NOTE CONTENT PROVIDED==
+ == RELEASE NOTE CONTENT REQUIRES SME REVIEW ==
CAUSE: When admin-console is opened in the browser, no JBoss-related info is shown in the
console and a JON error message is logged.
-CONSEQUENCE:
+CONSEQUENCE: The JON error confused users who were accustomed to seeing standard JBoss
error messages on other Middleware platforms.
FIX: The fix includes improvements to the console error message, standardizing it with
the format used in other Middleware products.
</para>
@@ -179,16 +64,6 @@
</varlistentry>
<varlistentry>
- <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=793639"><...
- Create additional portal objects for external groups</term>
- <listitem>
- <para>The status is ON_QA, assigned to mposolda(a)redhat.com.</para>
- <para>
- If a user manually added users or groups into a Java Content Repository or LDAP,
the required objects were not created because some necessary listeners were not called as
they would be if the Organization API was used. This could result in exceptions in some
situations, because the required JCR objects for a particular user or group were not
correctly initialized. The fix introduces the CoreOrganizationInitializer plugin
(exo.portal.component.initializer), which monitors the JCR and LDAP for changes and
initiates the listeners when required. The plugin is disabled by default, but can be
enabled by a portal administrator by uncommenting the block in
JBOSS_HOME/server/[PROFILE]/deploy/gatein.ear/02portal.war/WEB-INF/conf/configuration.xml,
which imports the configuration stored in the initializer-configuration.xml file.
- </para>
- </listitem>
-</varlistentry>
-
-<varlistentry>
<term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=794235"><...
- The display name of login user should be configurable in UIUserInfoPortlet</term>
<listitem>
<para>The status is ON_QA, assigned to mposolda(a)redhat.com.</para>
@@ -199,32 +74,6 @@
</varlistentry>
<varlistentry>
- <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=794394"><...
- Invalid page title of page causes unability to edit node</term>
- <listitem>
- <para>The status is ON_QA, assigned to mstrukel(a)redhat.com.</para>
- <para>
- CAUSE: Entered text becomes part of portal page HTML as-is, including special
characters like angle brackets
-CONSEQUENCE: Entered text can break a portal page
-FIX: Prevent entry of angle brackets using NoHTMLTagValidator
-RESULT: Text that could break a portal page can't be entered any more. If angle
brackets are desired in the output, character references can be used - < and
>
- </para>
- </listitem>
-</varlistentry>
-
-<varlistentry>
- <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=794395"><...
- invalid page title causes the edit node dialog to disappear</term>
- <listitem>
- <para>The status is ON_QA, assigned to mstrukel(a)redhat.com.</para>
- <para>
- CAUSE: Entered text becomes part of portal page HTML as-is, including special
characters like angle brackets
-CONSEQUENCE: Entered text can break a portal page
-FIX: Prevent entry of angle brackets using NoHTMLTagValidator
-RESULT: Text that could break a portal page can't be entered any more. If angle
brackets are desired in the output, character references can be used - < and
>
- </para>
- </listitem>
-</varlistentry>
-
-<varlistentry>
<term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=794376"><...
- Navigation labels are shortened but not looking good in multibyte
languages</term>
<listitem>
<para>The status is ON_QA, assigned to theute(a)redhat.com.</para>
@@ -243,21 +92,6 @@
</varlistentry>
<varlistentry>
- <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=793571"><...
- GTNPORTAL-1673 make UI validation regular expressions configurable by
users</term>
- <listitem>
- <para>The status is CLOSED, assigned to claprun(a)redhat.com.</para>
- <para>
- Several fields requiring user names where previously
-validated using hardcoded logic, thus preventing users from easily changing
-which user names were acceptable for their requirements. A new configurable
-validator has been implemented that can be configured by users without having
-to modify the source code thus allowing users to more easily change the format
-for valid user names.
- </para>
- </listitem>
-</varlistentry>
-
-<varlistentry>
<term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=794350"><...
- Breadcrumb Portlet doesn't update when a language change occurs</term>
<listitem>
<para>The status is CLOSED, assigned to hfnukal(a)redhat.com.</para>
@@ -276,26 +110,6 @@
</varlistentry>
<varlistentry>
- <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=793938"><...
- Replicated seesion is corrupted in Portlet Bridge Seam application</term>
- <listitem>
- <para>The status is CLOSED, assigned to kfinniga(a)redhat.com.</para>
- <para>
- Cause:
-Clustered Seam Booking demo Portlet throws exception when node that user session was
using fails, or is shutdown, and is transferred to remaining node
-
-Consequence:
-Portlet ceases to work due to org.gatein.pc.api.PortletInvokerException
-
-Fix:
-Call defaultReadObject() when de-serializing PortalIdentity
-
-Result:
-Session correctly restored for Seam Booking portlet after failover to remaining node
- </para>
- </listitem>
-</varlistentry>
-
-<varlistentry>
<term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=793999"><...
- PBR-284: rich:simpleTogglePanel does not work when placing two portlets in a
page</term>
<listitem>
<para>The status is CLOSED, assigned to kfinniga(a)redhat.com.</para>
@@ -335,142 +149,6 @@
</varlistentry>
<varlistentry>
- <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=793651"><...
- Authenticated credentials are stored as attribute in HTTP session during clustered
setup</term>
- <listitem>
- <para>The status is CLOSED, assigned to mposolda(a)redhat.com.</para>
- <para>
- Release notes docs status: Not Yet Documented
-
-NOTE: I am not sure how to proceed with Release Notes because this issue has not been
reported by any customer and it's security issue visible only by RedHat and eXo.
-
-CAUSE: Previously we had credentials of authenticated user stored as attribute in Http
Session
-
-FIX: Now credentials are not stored in HttpSession but in separate component
AuthenticationRegistry. It is safer and it means that there is no chance that Credentials
will be replicated to different cluster node during authentication process.
- </para>
- </listitem>
-</varlistentry>
-
-<varlistentry>
- <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=793838"><...
- Provide support for a newer JOSSO version</term>
- <listitem>
- <para>The status is CLOSED, assigned to mposolda(a)redhat.com.</para>
- <para>
- Due to a changed Java Open Single Sign On JOSSO agent API, it was only possible
to upgrade JOSSO to v1.8.1. An upstream fix was applied to JBoss Enterprise Portal
Platform which allows later JOSSO versions to be applied after v1.8.1. A changed JOSSO
agent API between JOSSO versions v1.8.1 and v1.8.2 requires different packaging, which has
changed some procedures. Refer to the updated procedures in the
<citetitle>Reference Guide</citetitle> "Java Open Single Sign-On
Project" section for more details.
- </para>
- </listitem>
-</varlistentry>
-
-<varlistentry>
- <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=794129"><...
- Log level improvement in FallbackIdentityStoreRepository class (PicketLink
IDM)</term>
- <listitem>
- <para>The status is CLOSED, assigned to mposolda(a)redhat.com.</para>
- <para>
- CAUSE: Class FallbackIdentityStoreRepository from library Picketlink IDM was
using insufficient logging in some places, because some errors were reported into log with
log level INFO, which may cause that customer can miss some important error messages.
-
-FIX: It's fixed in library Picketlink IDM. I added SEVERE logging
-instead of INFO for all exceptions, which are not propagated to the caller. For
-those, which are propagated there is FINER logging, but it seems to be
-sufficient since the exception should be processed and logged by the caller.
-
-btw. I used SEVERE category instead of ERROR, because Picketlink IDM is using
-JDK logging and it does not support ERROR category (categories are SEVERE,
-WARN, INFO, FINE, FINER, FINEST)
- </para>
- </listitem>
-</varlistentry>
-
-<varlistentry>
- <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=794356"><...
- Clicking on User management tabs can cause the "no results found"
popup</term>
- <listitem>
- <para>The status is CLOSED, assigned to mposolda(a)redhat.com.</para>
- <para>
- PROBLEM: An issue with the No Result Found pop-up causes it to display
-after first searching for a non-existent user string, then searching for a
-string that is known to exist.
-
-FIX: This was UI issue and it has been fixed in particular UI components
-related to OrganizationManagementPortlet. Now popup "No results found" is
-displayed only in valid situations, when really no results are found.
-
-This issue has same cause like GateIn issue GTNPORTAL-1517, which has been
-fixed in GateIn longer time ago. So we fixed it in EPP by backport related
-source files from GateIn.
- </para>
- </listitem>
-</varlistentry>
-
-<varlistentry>
- <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=794454"><...
- Images are processed by PortalRequestHandler</term>
- <listitem>
- <para>The status is CLOSED, assigned to mposolda(a)redhat.com.</para>
- <para>
- CAUSE: Problem is caused by incorrect mapping of staticResource handler in
-controller.xml . StaticResource handler is mapped after PortalRequestHandler,
-which means that all images are firstly processed by PortalRequestHandler. This
-is non-sense and it results that incorrect HTTP header "Cache-control:
-no-cache" is used for images and some non-sense operations are called (like
-calling DataStorage.getPortalConfig with argument "favicon.ico" ).
-
-FIX: Thing is that images should be processed only by
-StaticResourceHandler and not by PortalRequestHandler at all. So I changed the
-order in controller.xml configuration, and I've added StaticResourceHandler
-before PortalRequestHandler (it was opposite before).
- </para>
- </listitem>
-</varlistentry>
-
-<varlistentry>
- <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=794456"><...
- WebAppController needs to start RequestLifeCycle for every processing (including static
resource processing)</term>
- <listitem>
- <para>The status is CLOSED, assigned to mposolda(a)redhat.com.</para>
- <para>
- CAUSE: WebAppController needs to start
-RequestLifeCycle for every processing (including static resource processing).
-And starting of requestLifeCycle is quite expensive as it requires starting of
-Hibernate transaction among other things. This means that we need to start
-Hibernate transaction for processing of images and other static resources,
-which does not makes sense and it's not ideal from performance perspective.
-
-FIX: Adding new method to WebRequestHandler class, so handlers can decide
-if they need to start RequestLifeCycle or not. Handlers for sending requests to
-portal (like PortalRequestHandler) needs to start transaction, but handlers for
-processing static resources (like StaticResourceHandler) don't need it. So now
-we are not starting Hibernate transaction anymore for processing images.
- </para>
- </listitem>
-</varlistentry>
-
-<varlistentry>
- <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=794320"><...
- Enable customization of LocalConfig service by extending existing
implementations</term>
- <listitem>
- <para>The status is CLOSED, assigned to mstrukel(a)redhat.com.</para>
- <para>
- CAUSE: Many methods in LocaleConfigImpl, and
-LocaleConfigServiceImpl were final or private.
-
-CONSEQUENCE: Users were unable to reuse existing implementation by extending
-and overriding - they were forced to copy-paste in order to implement
-alternative behaviour.
-
-FIX: Remove final from methods, make private method protected.
-
-RESULT: Users should now be able to extend, and override the default
-LocaleConfig implementation.
- </para>
- </listitem>
-</varlistentry>
-
-<varlistentry>
- <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=793959"><...
- Richfaces portlet after session expiration generates incorrect request
(resource)</term>
- <listitem>
- <para>The status is CLOSED, assigned to mwringe(a)redhat.com.</para>
- <para>
- == IS THIS INCLUDED IN EPP 5.2.1, AND DOES IT REQUIRE RN? ==
- </para>
- </listitem>
-</varlistentry>
-
-<varlistentry>
<term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=794349"><...
- Application Registry has double entries for some applications</term>
<listitem>
<para>The status is CLOSED, assigned to mwringe(a)redhat.com.</para>
@@ -481,46 +159,6 @@
</varlistentry>
<varlistentry>
- <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=794402"><...
- Consistent initialization order of servlets/portlets at deploy and
hot-deploy</term>
- <listitem>
- <para>The status is CLOSED, assigned to mwringe(a)redhat.com.</para>
- <para>
- == HELPDESK CASE THAT WILL REQUIRE CCFR ==
-
-CAUSE:
-
-CONSEQUENCE:
-
-FIX:
-
-RESULT:
- </para>
- </listitem>
-</varlistentry>
-
-<varlistentry>
- <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=794463"><...
- ResourceIDs are sometimes lost when serving portlet resources</term>
- <listitem>
- <para>The status is CLOSED, assigned to mwringe(a)redhat.com.</para>
- <para>
- == IS THIS ISSUE FOR EPP 5.2.1, AND DOES IT REQUIRE RN ==
- </para>
- </listitem>
-</varlistentry>
-
-<varlistentry>
- <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=794357"><...
- possible to clone or copy system nodes in edit navigation</term>
- <listitem>
- <para>The status is CLOSED, assigned to nscavell(a)redhat.com.</para>
- <para>
- == ISSUE SEEMS TO BE RESOLVED. ISSUE WAS KNOWN BEFORE. DRAFTED RESOLVE ISSUE RN
FOR SME REVIEW ==
-
-An issue with node copy or clone behavior allowed users to copy or clone a system node
but not delete the node. This was caused by the node already being a system node, and
therefore could not be deleted based on context. This issue has been fixed and included in
this release of the product.
- </para>
- </listitem>
-</varlistentry>
-
-<varlistentry>
<term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=794396"><...
- Deleting created subnode populates NPE and parent node is not properly
deleted</term>
<listitem>
<para>The status is CLOSED, assigned to nscavell(a)redhat.com.</para>
@@ -530,40 +168,5 @@
</listitem>
</varlistentry>
-<varlistentry>
- <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=793701"><...
- XSD NS references have bad URL in organization-configuration.xml</term>
- <listitem>
- <para>The status is CLOSED, assigned to hfnukal(a)redhat.com.</para>
- <para>
- ==NEEDINFO==
-
-The XMLNS URLs
-in the 02portal.war/WEB-INF/conf/organization/organization-configuration.xml file's
namespace declaration contained an incorrect namespace URL. The fix corrects the issue for
new installations. If you have created a custom server profile, ensure you manually
change
www.<replaceable>exoplaform</replaceable>.org to
www.<replaceable>exoplatform</replaceable>.org in the
-namespace declaration of the file.
- </para>
- </listitem>
-</varlistentry>
-
-<varlistentry>
- <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=793909"><...
- PicketLink fails to match identity object type due to whitespaces in its
DN</term>
- <listitem>
- <para>The status is CLOSED, assigned to mposolda(a)redhat.com.</para>
- <para>
- CAUSE: PicketLink does not account for spaces in domain
-names when it verifies identity. If the user enters spaces in the domain name,
-the following exception is thrown:
-"org.picketlink.idm.common.exception.IdentityException: Cannot recognize
-identity object type by its DN". There is no workaround for this issue, apart
-from ensuring no spaces are included in domain names.
-
-FIX: It's fixed only in Picketlink IDM library. Now it supports comparison of Ldap
DN, so DN are considered
-equal even if these DN have some whitespaces in path.
-LDAPIdentityStoreRepository is refactored according to it.
-
-TestCase is also added for it into Picketlink IDM library.
- </para>
- </listitem>
-</varlistentry>
-
</variablelist>
</chapter>
Modified: epp/docs/branches/5.2/Release_Notes/en-US/resolved.xml
===================================================================
--- epp/docs/branches/5.2/Release_Notes/en-US/resolved.xml 2012-03-28 15:37:01 UTC (rev
8662)
+++ epp/docs/branches/5.2/Release_Notes/en-US/resolved.xml 2012-03-29 04:33:27 UTC (rev
8663)
@@ -20,6 +20,16 @@
</varlistentry>
<varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=793571"><...
- GTNPORTAL-1673 make UI validation regular expressions configurable by
users</term>
+ <listitem>
+ <remark>Status: CLOSED</remark>
+ <para>
+ Several fields requiring user names were previously validated using hardcoded
logic, which prevented users from easily changing what user name formats were acceptable
for their requirements. The fix implements ExpressionValidator, which permits user name
validation changes without having to customize the source code. The validator allows users
to specify the format required for valid user names, which overrides the default field
validation present in the portal.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
<term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=794400"><...
- able to save wsrp producer property with non-valid name</term>
<listitem>
<remark>Status: CLOSED</remark>
@@ -63,6 +73,18 @@
</varlistentry>
<varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=793938"><...
- Replicated seesion is corrupted in Portlet Bridge Seam application</term>
+ <listitem>
+ <remark>Status: CLOSED</remark>
+ <para>
+ An issue with de-serialization discovered in
org.gatein.pc.api.PortletInvokerException caused the
+Clustered Seam Booking demo Portlet to throw an exception when the user session node
failed or shutdown, and the user session transferred to another node. The fix implements
changes to org.gatein.pc.api.PortletInvokerException that calls defaultReadObject() when
de-serializing PortalIdentity.
+The Session is correctly restored for the Seam Booking portlet after the user session is
transferred to an available node.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
<term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=793387"><...
- Administration portlets not accessible when reconnection to LDAP from another
instance</term>
<listitem>
<remark>Status: CLOSED</remark>
@@ -73,6 +95,16 @@
</varlistentry>
<varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=793838"><...
- Provide support for a newer JOSSO version</term>
+ <listitem>
+ <remark>Status: CLOSED</remark>
+ <para>
+ Due to a changed Java Open Single Sign On JOSSO agent API, it was only possible
to upgrade JOSSO to v1.8.1. An upstream fix was applied to JBoss Enterprise Portal
Platform which allows later JOSSO versions to be applied after v1.8.1. A changed JOSSO
agent API between JOSSO versions v1.8.1 and v1.8.2 requires different packaging, which has
changed some procedures. Refer to the updated procedures in the
<citetitle>Reference Guide</citetitle> "Java Open Single Sign-On
Project" section for more details.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
<term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=793956"><...
- Support for system property substitution in PicketLink IDM configuration</term>
<listitem>
<remark>Status: CLOSED</remark>
@@ -97,6 +129,57 @@
</varlistentry>
<varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=794129"><...
- Log level improvement in FallbackIdentityStoreRepository class (PicketLink
IDM)</term>
+ <listitem>
+ <remark>Status: CLOSED</remark>
+ <para>
+ It was discovered that the Picketlink IDM FallbackIdentityStoreRepository class
was using INFO logging instead of an elevated log level. Customers could miss important
error information in the logs because INFO is commonly used for non-critical errors. The
fix implements SEVERE logging category changes for all exceptions that are not propagated
to the caller. For exceptions that are propagated to the caller, FINER logging is
configured because these exceptions should be processed and logged by the caller.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=794356"><...
- Clicking on User management tabs can cause the "no results found"
popup</term>
+ <listitem>
+ <remark>Status: CLOSED</remark>
+ <para>
+ A User Interface issue with the "No Result Found" pop-up caused it to
display when a user first searched for a non-existent user string, then searched for a
string that was known to exist. Users experienced issues with finding user records because
the pop-up suggested there were no valid results when valid results existed. The fix
implements changes to OrganizationManagementPortlet, which ensure the "No results
found" pop-up is displayed only when no results are found.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=794454"><...
- Images are processed by PortalRequestHandler</term>
+ <listitem>
+ <remark>Status: CLOSED</remark>
+ <para>
+ It was discovered that an incorrect mapping order in controller.xml caused
PortalRequestHandler to process images. Because PortalRequestHandler was not designed to
process images, incorrect HTTP header information was used for images. The fix corrects
the mapping order in controller.xml so StaticResourceHandler is declared before
PortalRequestHandler. This ensures the appropriate handler is called to manage images.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=794456"><...
- WebAppController needs to start RequestLifeCycle for every processing (including static
resource processing)</term>
+ <listitem>
+ <remark>Status: CLOSED</remark>
+ <para>
+ A performance impact was discovered in the WebAppController that required
RequestLifeCycle to be started for all processing, including static resources. Because
RequestLifeCycle requires Hibernate transactions, this service needed to be started for
all processing, which introduced a performance implication. The fix adds a new method
(getRequireLifeCycle) to the WebRequestHandler class, which allows handlers to decide
whether RequestLifeCycle is required to complete the transaction. Hibernate is only called
for handlers sending requests to the portal, and not for handlers processing images.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=794320"><...
- Enable customization of LocalConfig service by extending existing
implementations</term>
+ <listitem>
+ <remark>Status: CLOSED</remark>
+ <para>
+ It was discovered that many methods in LocaleConfigImpl, and
+LocaleConfigServiceImpl were declared final or private. Users were unable to reuse an
existing implementation by extending and overriding the methods, and were forced to make a
copy of the method to implement customized behavior. The fix removes the final declaration
from these methods, and declares private methods as protected. This allows users to extend
and override the default LocaleConfig implementation.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
<term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=794437"><...
- NullPointerException upgrading EPP from 5.1 to 5.2</term>
<listitem>
<remark>Status: CLOSED</remark>
@@ -122,12 +205,43 @@
<listitem>
<remark>Status: CLOSED</remark>
<para>
- It was discovered that an imported remote gadget title could contain more than
255 characters. If a user tried to edit a gadget with more than 255 characters in the
title, an error message will appear on save: "The length of the text in field
"Description :" must be between "0" and "255"
characters.". The fix allows gadgets to have an unrestricted title length, which
fixes the originally reported issue.
+ It was discovered that an imported remote gadget description could contain more
than 255 characters. If a user tried to edit a gadget with more than 255 characters in the
description, an error message displayed: <literal>"The length of the text in
field "Description :" must be between "0" and "255"
characters."</literal>. The fix allows gadgets to have an unrestricted
description length, which fixes the originally reported issue.
</para>
</listitem>
</varlistentry>
<varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=794402"><...
- Consistent initialization order of servlets/portlets at deploy and
hot-deploy</term>
+ <listitem>
+ <remark>Status: CLOSED</remark>
+ <para>
+ Spring-specific portlet and servlet initialization ordering requirements caused
Spring-based portlets to work when the server was first started, but fail on hot
deployment. The fix introduces updates to the WCI component that allow manual registration
of web applications that use a servlet. By specifying the load-on-start values between the
registration portlet and the spring portlet, the way a portlet is initialized in relation
to a servlet can be controlled. This fix only controls when the web application is
registered in WCI with regards to another servlet, and not the servlet ordering with
respect to portlets. There are multiple steps which need to be manually configured. Refer
to the Bugzilla directly for more information and links to setup information.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=794463"><...
- ResourceIDs are sometimes lost when serving portlet resources</term>
+ <listitem>
+ <remark>Status: CLOSED</remark>
+ <para>
+ It was discovered that ResourceIDs were sometimes lost when serving resources
during a portlet invocation. This would cause the resourceIds to be null, resulting in
resources not being properly fetched. The fix implements logic changes that now provide
additional checks within the portal for resourceIDs. Resources now function more reliably,
particularly when using the portlet bridge over WSRP.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=794357"><...
- possible to clone or copy system nodes in edit navigation</term>
+ <listitem>
+ <remark>Status: CLOSED</remark>
+ <para>
+ An issue with node copy or clone behavior allowed users to copy or clone a
system node but not delete the node. This was caused by the node already being a system
node, and therefore could not be deleted based on context. This issue
+has been fixed and included in this release of the product.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
<term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=793246"><...
- Logo portlet on Dashboard - url validation</term>
<listitem>
<remark>Status: CLOSED</remark>
@@ -139,6 +253,17 @@
</varlistentry>
<varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=793701"><...
- XSD NS references have bad URL in organization-configuration.xml</term>
+ <listitem>
+ <remark>Status: CLOSED</remark>
+ <para>
+ The XMLNS URLs in the
<filename>02portal.war/WEB-INF/conf/organization/organization-configuration.xml</filename>
file's NAMESPACE declaration contained an incorrect namespace URL. The fix corrects
the issue for new installations. If you have created a custom server profile, ensure you
manually change
www.<replaceable>exoplaform</replaceable>.org to
www.<replaceable>exoplatform</replaceable>.org in the
+NAMESPACE declaration of the file.
+ </para>
+ </listitem>
+</varlistentry>
+
+<varlistentry>
<term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=794319"><...
- Upgrade openid4java to resolve CVE-2011-4314</term>
<listitem>
<remark>Status: CLOSED</remark>
@@ -158,5 +283,15 @@
</listitem>
</varlistentry>
+<varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=793909"><...
- PicketLink fails to match identity object type due to whitespaces in its
DN</term>
+ <listitem>
+ <remark>Status: CLOSED</remark>
+ <para>
+ An issue in PicketLink identity verification resulted in domain names containing
spaces causing the following exception to be raised: <literal>Cannot recognize
identity object type by its DN</literal>. The fix implements changes to
LDAPIdentityStoreRepository comparison logic, which compares the LDAP domain name with the
domain name containing spaces. The logic ignores spaces in the domain name and searches
for an overall character match. Domains that have a character match pass validation, which
corrects the originally reported issue.
+ </para>
+ </listitem>
+</varlistentry>
+
</variablelist>
</chapter>