Author: smumford
Date: 2011-08-29 04:11:39 -0400 (Mon, 29 Aug 2011)
New Revision: 7246
Modified:
epp/docs/branches/5.2/Release_Notes/en-US/Book_Info.xml
epp/docs/branches/5.2/Release_Notes/en-US/known_issues.xml
epp/docs/branches/5.2/Release_Notes/en-US/need_info.xml
epp/docs/branches/5.2/Release_Notes/en-US/not_documented.xml
epp/docs/branches/5.2/Release_Notes/en-US/resolved_issues.xml
Log:
Created draft version to capture new 5.2.0 JIRA filters
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 2011-08-29 07:26:59 UTC (rev
7245)
+++ epp/docs/branches/5.2/Release_Notes/en-US/Book_Info.xml 2011-08-29 08:11:39 UTC (rev
7246)
@@ -4,7 +4,7 @@
%BOOK_ENTITIES;
]>
<articleinfo id="arti-5.1.1_Release_Notes-5.1.1_Release_Notes">
- <title>5.1.1 Release Notes</title>
+ <title>5.2.0 Release Notes</title>
<subtitle>For use with JBoss Enterprise Portal Platform
&VZ;</subtitle>
<productname>JBoss Enterprise Portal Platform</productname>
<productnumber>5.2</productnumber>
Modified: epp/docs/branches/5.2/Release_Notes/en-US/known_issues.xml
===================================================================
--- epp/docs/branches/5.2/Release_Notes/en-US/known_issues.xml 2011-08-29 07:26:59 UTC
(rev 7245)
+++ epp/docs/branches/5.2/Release_Notes/en-US/known_issues.xml 2011-08-29 08:11:39 UTC
(rev 7246)
@@ -5,24 +5,18 @@
<variablelist>
- <!--
https://issues.jboss.org/browse/JBEPP-1079 -->
+ <!--
https://issues.jboss.org/browse/JBEPP-715 -->
<varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1079"
/></term>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-715"
/></term>
<listitem>
+ <remark>JIRA is OPEN</remark>
+
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
- Pre-release testing has found that attempting to edit a category that does
not have a description will produce the following error:
-<screen>IllegalArgumentException: Must pass a non null String
-</screen>
- </para>
- <para>
- A patch that corrects this behavior is available from
<CSP>, as are the required installation instructions.
- </para>
- </warning>
+ <para>
+ </para>
+
</listitem>
</varlistentry>
Modified: epp/docs/branches/5.2/Release_Notes/en-US/need_info.xml
===================================================================
--- epp/docs/branches/5.2/Release_Notes/en-US/need_info.xml 2011-08-29 07:26:59 UTC (rev
7245)
+++ epp/docs/branches/5.2/Release_Notes/en-US/need_info.xml 2011-08-29 08:11:39 UTC (rev
7246)
@@ -1,125 +1,4 @@
-<?xml version='1.0'?>
-<!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
-]>
-
-<variablelist>
-
- <!--
https://issues.jboss.org/browse/JBEPP-764 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-764"
/></term>
- <listitem>
-
-
- <para>
- To isolate multiple clusters running on the same network, the JBoss Cache and
JGroups configuration files used in JBoss Enterprise Portal Platform have been updated to
include partition name (-g) and multicast address (-u) properties used in JBoss Enterprise
Application Platform.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!--
https://issues.jboss.org/browse/JBEPP-874 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-874"
/></term>
- <listitem>
-
-
- <para>
- It was found that, in previous versions of JBoss Enterprise Portal Platform,
using JCR addNode within a transaction caused a javax.transaction.HeuristicMixedException
(internally, org.exoplatform.services.transaction.TransactionException caused by
org.jboss.cache.lock.TimeoutException) when the new node was first accessed. This has been
corrected by ensuring that loading data into cache occurs outside the current
transaction.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!--
https://issues.jboss.org/browse/JBEPP-884 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-884"
/></term>
- <listitem>
-
-
- <para>
- Changed level of error message for JS compressor
- </para>
-
- </listitem>
- </varlistentry>
-
- <!--
https://issues.jboss.org/browse/JBEPP-961 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-961"
/></term>
- <listitem>
-
-
- <para>
- Release Notes need more information about the issue and how it was fixed.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!--
https://issues.jboss.org/browse/JBEPP-1010 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1010"
/></term>
- <listitem>
-
-
- <para>
- This issue requires more information to be included in the 5.1.1 Release Notes.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!--
https://issues.jboss.org/browse/JBEPP-1013 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1013"
/></term>
- <listitem>
-
-
- <para>
- This issue needs more information to be provided for the 5.1.1 Release Notes.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!--
https://issues.jboss.org/browse/JBEPP-1018 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1018"
/></term>
- <listitem>
-
-
- <para>
- If this issue requires a Release Note, more information (about how the problem
presented to users and how it was fixed) is required.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!--
https://issues.jboss.org/browse/JBEPP-1023 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1023"
/></term>
- <listitem>
-
-
- <para>
- This issue requires more information about how it was resolved if it requires a
5.1.1 Release Note.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!--
https://issues.jboss.org/browse/JBEPP-1036 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1036"
/></term>
- <listitem>
-
-
- <para>
- This issue requires more information about the underlying cause and the fix
implemented if it requires a 5.1.1 Release Note.
- </para>
-
- </listitem>
- </varlistentry>
-
-</variablelist>
+<para>
+There are no issues that require more information at this time.
+</para>
Modified: epp/docs/branches/5.2/Release_Notes/en-US/not_documented.xml
===================================================================
--- epp/docs/branches/5.2/Release_Notes/en-US/not_documented.xml 2011-08-29 07:26:59 UTC
(rev 7245)
+++ epp/docs/branches/5.2/Release_Notes/en-US/not_documented.xml 2011-08-29 08:11:39 UTC
(rev 7246)
@@ -1,3 +1,38 @@
-<para>
-All Issues are documented.
-</para>
+<?xml version='1.0'?>
+<!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+
+
+<variablelist>
+
+ <!--
https://issues.jboss.org/browse/JBEPP-599 -->
+ <varlistentry>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-599"
/></term>
+ <listitem>
+
+
+ <para>
+ If a portal is deleted from its own Site management page (that is; if a user
deletes the portal they are currently logged into), the resultant redirect returns the
user to the public mode of the default portal (/portal/public/classic) .
+
+The user should be redirected to the private mode of the default portal
(/portal/private/classic).
+
+
+ </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>
+
+ </listitem>
+ </varlistentry>
+
+</variablelist>
Modified: epp/docs/branches/5.2/Release_Notes/en-US/resolved_issues.xml
===================================================================
--- epp/docs/branches/5.2/Release_Notes/en-US/resolved_issues.xml 2011-08-29 07:26:59 UTC
(rev 7245)
+++ epp/docs/branches/5.2/Release_Notes/en-US/resolved_issues.xml 2011-08-29 08:11:39 UTC
(rev 7246)
@@ -5,372 +5,6 @@
<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 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>
- </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
<literal>NullPointerException</literal> under load. The issue has been fixed
in this release.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!--
https://issues.jboss.org/browse/JBEPP-566 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-566"
/></term>
- <listitem>
-
-
- <para>
- A bug which prompted users to <guilabel>Save and Close</guilabel> an
<emphasis>Edit Portlet</emphasis> dialog if a tab in the window was clicked
but the mouse cursor was removed from the tab before the mouse button was released has
been corrected in this release.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!--
https://issues.jboss.org/browse/JBEPP-568 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-568"
/></term>
- <listitem>
-
-
- <para>
- In previous releases of JBoss Enterprise Portal Platform, users found that, when
creating sub-nodes of system nodes (<literal>portal navigation</literal>,
<literal>group navigation</literal>, <literal>register</literal>
etc.), these new nodes were not visible once created. This issue, and a related issue
encountered when attempting to '<emphasis>Cut</emphasis>' sub-nodes of
system nodes, have been resolved in this latest release.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!--
https://issues.jboss.org/browse/JBEPP-597 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-597"
/></term>
- <listitem>
-
-
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <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>
- </warning>
-
- </listitem>
- </varlistentry>
-
- <!--
https://issues.jboss.org/browse/JBEPP-723 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-723"
/></term>
- <listitem>
-
-
- <para>
- A bug in the <code>UIUserInGroup.setValues()</code> code caused
previous versions of JBoss Enterprise Portal Platform to throw an error when users
attempted to navigate to a new page within the Group management view of the Organization
portlet by any method other than the page indicator buttons. This release includes a patch
which resolves this issue and allows users to navigate between pages using various UI
elements.
- </para>
- <para>
- Further details can be found in <ulink type="http"
url="https://issues.jboss.org/browse/GTNPORTAL-1356"></ul...
-
- </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 caused 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-768 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-768"
/></term>
- <listitem>
-
-
- <para>
- An issue with the <emphasis
role="bold">FileUpload</emphasis> demo not populating file information
fields has been corrected with an upgrade to the Portlet Bridge component.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!--
https://issues.jboss.org/browse/JBEPP-771 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-771"
/></term>
- <listitem>
-
-
- <para>
- Prior to this release, CAS ticket validation failed when the JBoss Enterprise
Portal Platform instance was set up with SSL. This has been fixed with an upgrade to the
SSO component. CAS ticket validation now works as expected with
<literal>http</literal> and <literal>https</literal> addresses.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!--
https://issues.jboss.org/browse/JBEPP-772 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-772"
/></term>
- <listitem>
-
-
- <para>
- In this release of JBoss Enterprise Portal Platform,
<systemitem>JndiMultiplexedJBossCacheRegionFactory</systemitem> is used for
IDM second level caching. This makes it easier to switch to TCP.
- </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 '<emphasis>Preferences</emphasis>' tab
from appearing in some portlets. The tab would only appear in portlets that were
customized during the first deployment through the
<literal>portal.xml</literal> descriptor.
- </para>
- <para>
- Non-customized portlets would not show a
'<emphasis>Preferences</emphasis>' tab. The
<filename>UIFormInputSet.java</filename> and
<filename>UIPortletForm.java</filename> 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 <filename>idm-configuration.xml</filename> 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.
- </para>
- <para>
- 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-782 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-782"
/></term>
- <listitem>
-
-
- <para>
- It was found that separate instances of JBoss Enterprise Portal Platform 5.1
deployed on the same network and started with the
'<literal>Default</literal>' server profile would communicate as if in
a cluster.
- </para>
- <para>
- This behavior has been resolved with new cluster configuration.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!--
https://issues.jboss.org/browse/JBEPP-786 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-786"
/></term>
- <listitem>
-
-
- <para>
- An error in the XML definition in the
<filename>gatein_objects_1_0</filename> file was found to cause errors in
Eclipse environments when using the default <filename>pages.xml</filename> or
<filename>navigation.xml</filename> files.
- </para>
- <para>
- This was because the file did not include
'<literal>VISIBLE</literal>' in the allowed values of the
'<parameter>visibility</parameter>' element. This error has been
corrected.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!--
https://issues.jboss.org/browse/JBEPP-788 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-788"
/></term>
- <listitem>
-
-
- <para>
- Custom WSRP <systemitem>RegistrationPolicy</systemitem>
implementations were not properly handled in previous versions of JBoss Enterprise Portal
Platform.
- </para>
- <para>
- This caused an exception when the product was started. This issue has been
resolved.
- </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
<literal>doHeaders</literal> 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-811 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-811"
/></term>
- <listitem>
-
-
- <para>
- A race condition, encountered when more than one portal user attempts to create
a page at the same time has been adressed in this release. The issue presented if two
pages were created simultaneously, with one process finishing slightly after the first,
but before the first process had redirected to the new page. This scenario would result in
the second page overwriting the first.
- </para>
- <para>
- Patches which resolve the page creation issue have been applied to this
release. However, further development will be required in later iterations to resolve
concurrency issues completely.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!--
https://issues.jboss.org/browse/JBEPP-813 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-813"
/></term>
- <listitem>
-
-
- <para>
- An issue with navigational elements not being correctly translated into
languages with a country variant has been resolved in this release. Navigation elements
are now translated correctly.
- </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
<filename>UIPageNavigationForm.java</filename> file 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-854 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-854"
/></term>
- <listitem>
-
-
- <warning>
- <title>Not Public Yet - RHT+eXo</title>
- <para>
- In previous versions of JBoss Enterprise Portal Platform, an error would be
encountered when slashes were used in the context path of a portlet. This issue has been
corrected in this release.
- </para>
- </warning>
-
- </listitem>
- </varlistentry>
-
- <!--
https://issues.jboss.org/browse/JBEPP-856 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-856"
/></term>
- <listitem>
-
-
- <para>
- Problems encountered when trying to run various gadgets (including the RSS
Reader) in a portal instance using secure https mode has been resolved in this release.
All gadgets should now render and behave as expect in both
<literal>http</literal> and <literal>https</literal> modes.
- </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
when the service started since they did not 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 start up.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!--
https://issues.jboss.org/browse/JBEPP-873 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-873"
/></term>
- <listitem>
-
-
- <para>
- Previous versions of JBoss Enterprise Portal Platform encountered problems when
attempting to access files though the WebDAV interface if the file name included special
characters. An upstream patch ensures characters are escaped correctly and resolves the
issue.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!--
https://issues.jboss.org/browse/JBEPP-883 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-883"
/></term>
- <listitem>
-
-
- <para>
- Some mistranslations in <systemitem>webui_ja.properties</systemitem>
have been corrected in this release of JBoss Enterprise Portal Platform.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!--
https://issues.jboss.org/browse/JBEPP-887 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-887"
/></term>
- <listitem>
-
-
- <para>
- A conflict between the
<systemitem>javax.portlet.faces.extension.resetModeViewId</systemitem> the
portlet.xml configuration file and the error page specified by the error-page tag in
web.xml has been resolved in an upgrade of the JBoss Portlet Bridge component.
- </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
<systemitem>handleFaceletNotFound</systemitem> method (when a facelet file was
not found) were being obscured by <systemitem>FaceletViewHandler</systemitem>
as the response object was not a subtype of
<systemitem>HttpServletResponse</systemitem> (it is an instance of
<systemitem>PortletResponse</systemitem>).
<filename>FaceletPortletViewHandler.java</filename> has been updated to handle
instances of both HttpServletResponse and PortletResponse response objects.
- </para>
-
- </listitem>
- </varlistentry>
-
<!--
https://issues.jboss.org/browse/JBEPP-893 -->
<varlistentry>
<term><ulink
url="https://issues.jboss.org/browse/JBEPP-893"
/></term>
@@ -384,158 +18,30 @@
</listitem>
</varlistentry>
- <!--
https://issues.jboss.org/browse/JBEPP-896 -->
+ <!--
https://issues.jboss.org/browse/JBEPP-1013 -->
<varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-896"
/></term>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1013"
/></term>
<listitem>
<para>
- The Single Sign On (SSO)
<systemitem>AbstractLogoutFilter</systemitem> 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 <systemitem>AbstractLogoutFilter</systemitem> code) resolves
this issue and Non-UTF-8 characters are now specified correctly.
+ The demo iFrame portlet was setup to use the GateIn blog as an example page.
With the new GateIn blog, the portal is redirected so that the blog takes the full page.
The location has changed to point to
gatein.org homepage which doesn't do any
redirection.
</para>
</listitem>
</varlistentry>
- <!--
https://issues.jboss.org/browse/JBEPP-899 -->
+ <!--
https://issues.jboss.org/browse/JBEPP-1018 -->
<varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-899"
/></term>
+ <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1018"
/></term>
<listitem>
<para>
- <systemitem>MOPPortalStructuralAccess</systemitem> was improperly
closing the <systemitem>POMSession</systemitem> that was under control of
another Portal component, leaving that component unable to properly access JCR state.
+ Previous versions of JBoss Enterprise Portal Platform did not honor the location
of the WSRP consumer configuration file specified in wsrp-configuration.xml. This made it
impossible to use any configuration file other than the default. This version of JBoss
Enterprise Portal Platform honors the configuration file location by adding the ability to
configure consumers from an InputStream similar to the method used by the producer
configuration. Administrators can now use custom consumer configuration files instead of
needing to modify the default file.
</para>
- <para>
- An NPE was thrown when other components tried to access the closed
<systemitem>POMSession</systemitem>.
<systemitem>MOPPortalStructureAccess</systemitem> now saves the session
instead of saving <emphasis role="bold">and</emphasis> closing it.
- </para>
- <para>
- Since <systemitem>MOPPortalStructuralAccess</systemitem> no
longer closes the POMSession, 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>
-
- <!--
https://issues.jboss.org/browse/JBEPP-945 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-945"
/></term>
- <listitem>
-
-
- <para>
- An error that caused IntegrationCache to not be invalidated when calling
invalidateAll() on PicketlinkIDMCacheService MBean has been corrected in this release.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!--
https://issues.jboss.org/browse/JBEPP-954 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-954"
/></term>
- <listitem>
-
-
- <para>
- Attempting to remove an inexistent ConsumerGroup would cause a
NullPointerException. JCRRegistrationPersistenceManager now properly handles the
situation.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!--
https://issues.jboss.org/browse/JBEPP-955 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-955"
/></term>
- <listitem>
-
-
- <para>
- Local state was improperly initialized causing a NullPointerException when
attempting to insert a new ConsumerGroup. Properly retrieving the state from the JCR
persistence fixed the issue.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!--
https://issues.jboss.org/browse/JBEPP-958 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-958"
/></term>
- <listitem>
-
-
- <para>
- In previous JBoss Enterprise Portal Platform versions, calling
org.exoplatform.webui.form.UIFormCheckBoxInput.setValue() with a String value of
'true', would result in the value being interpreted as 'false' as only
Boolean values (not String values) were parsed. This behavior has been corrected by
recognizing string values when entered and converting them to boolean values.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!--
https://issues.jboss.org/browse/JBEPP-966 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-966"
/></term>
- <listitem>
-
-
- <para>
- In previous versions of JBoss Enterprise Portal Platform, the ErrorLoginServlet
did not return the HTTP header content-type. This could be problematic when running the
portal instance behind Apache loadbalancer. An upstream patch has been incorporated in
this release to address the issue.
- </para>
-
- </listitem>
- </varlistentry>
-
- <!--
https://issues.jboss.org/browse/JBEPP-987 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-987"
/></term>
- <listitem>
-
-
- <para>
- The JCR cache configuration files in JBoss Enterprise Portal Platform 5.1.1 have
been moved from the
/JBOSS_HOME/server/PROFILE/deploy/gatein.ear/lib/exo.portal.component.common-<version>.jar
to /JBOSS_HOME/server/PROFILE/deploy/gatein.ear/02portal.war/WEB-INF/conf/.
-
-This change created problems when attempting to start upgraded versions of JBoss
Enterprise Portal Platform that had the original file path stored in the JCR_CONFIG table
in the database. To resolve the issue, duplicates of the configuration files have been
retained in the original location. This also ensures backward compatibility, without the
need to change the database.
-
-Note:
-After this change, if configuration changes to the JCR cache are required, it is
important that the JCR_CONFIG table be updated to use the "war:" prefix instead
of "classpath:" (for example; file:war:/conf/jcr/jbosscache/local/config.xml).
- </para>
-
- </listitem>
- </varlistentry>
-
- <!--
https://issues.jboss.org/browse/JBEPP-1019 -->
- <varlistentry>
- <term><ulink
url="https://issues.jboss.org/browse/JBEPP-1019"
/></term>
- <listitem>
-
-
- <para>
- A bug which caused the day of the month in the calendar pop-up to not be
translated has been corrected in this release.
- </para>
-
- </listitem>
- </varlistentry>
-
</variablelist>