6:18 p.m.
Author: jaredmorgs
Date: 2012-08-30 19:18:33 -0400 (Thu, 30 Aug 2012)
New Revision: 8837
Modified:
epp/docs/branches/5.2/Release_Notes/en-US/5.2.2_Release_Notes.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
epp/docs/branches/5.2/Release_Notes/en-US/sp_known.xml
epp/docs/branches/5.2/Release_Notes/en-US/sp_needinfo.xml
epp/docs/branches/5.2/Release_Notes/en-US/sp_resolved.xml
Log:
Final draft before release push
Modified: epp/docs/branches/5.2/Release_Notes/en-US/5.2.2_Release_Notes.xml
===================================================================
--- epp/docs/branches/5.2/Release_Notes/en-US/5.2.2_Release_Notes.xml 2012-08-30 12:52:33
UTC (rev 8836)
+++ epp/docs/branches/5.2/Release_Notes/en-US/5.2.2_Release_Notes.xml 2012-08-30 23:18:33
UTC (rev 8837)
@@ -62,7 +62,8 @@
</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 27)</remark></para>
+ <remark>Updated table from https://docspace.corp.redhat.com/docs/DOC-68705
(version 33)</remark>
+ <remark>20120831 - Just checking that REVISION 33 of the docspace above is
the FINAL version. I note it still contains CR versions of components.</remark>
<table frame="all" pgwide="1">
<title>Component Versions</title>
<tgroup cols="2" colsep="1">
@@ -195,43 +196,44 @@
</tgroup>
</table>
</chapter>
- <chapter>
- <title>Upgraded Components</title>
- <formalpara>
- <title>New Components</title>
- <para>The following new components warrant special mention.</para>
- </formalpara>
- <remark>NEEDINFO: anything we need to mention here?</remark>
-<!--<variablelist>
- <varlistentry>
- <term>Gatein JON Plugin</term>
- <listitem>
- <para>The Gatein JON plugin allows the portal to interact with JBoss
Operations Network. The plugin captures portlet and site statistics.</para>
- </listitem>
- </varlistentry>
-</variablelist>--> <formalpara>
- <title>Updated Components</title>
- <para>The following updated components warrant special
mention.</para>
- </formalpara>
- <remark>NEEDINFO: anything we need to mention here?</remark>
-<!--<variablelist>
- <varlistentry>
- <term>Java Content Repository</term>
- <listitem>
- <para>The JCR configuration has been corrected in the
configuration.properties file. The previous configuration was incorrect. </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Java Open Single Sign-on (JOSSO) </term>
- <listitem>
- <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>
-</variablelist>--> <note>
- <para>For detailed information about component versions included in this
release, refer to <xref
linkend="Release_Notes-Component_Features"/></para>
- </note>
- </chapter>
- <chapter id="Release_Notes-Documentation">
+<!--<chapter>
+ <title>Upgraded Components</title>
+ <formalpara>
+ <title>New Components</title>
+ <para>The following new components warrant special mention.</para>
+ </formalpara>
+ <remark>NEEDINFO: anything we need to mention here?</remark>
+ <variablelist>
+ <varlistentry>
+ <term>Gatein JON Plugin</term>
+ <listitem>
+ <para>The Gatein JON plugin allows the portal to interact with JBoss
Operations Network. The plugin captures portlet and site statistics.</para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ <formalpara>
+ <title>Updated Components</title>
+ <para>The following updated components warrant special mention.</para>
+ </formalpara>
+ <remark>NEEDINFO: anything we need to mention here?</remark>
+ <variablelist>
+ <varlistentry>
+ <term>Java Content Repository</term>
+ <listitem>
+ <para>The JCR configuration has been corrected in the
configuration.properties file. The previous configuration was incorrect. </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Java Open Single Sign-on (JOSSO) </term>
+ <listitem>
+ <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>
+ </variablelist>
+ <note>
+ <para>For detailed information about component versions included in this
release, refer to <xref
linkend="Release_Notes-Component_Features"/></para>
+ </note>
+</chapter>--> <chapter id="Release_Notes-Documentation">
<title>Documentation</title>
<para>
An <citetitle>Installation Guide</citetitle> and a
<citetitle>User Guide</citetitle> for JBoss Enterprise Portal Platform are
available at <ulink
url="http://access.redhat.com/knowledge/docs/JBoss_Enterprise_Portal...
type="http"/>. JBoss Enterprise Portal Platform specific documentation is
also available from this location, as is Site Publisher documentation.
</para>
@@ -261,21 +263,20 @@
</part>
<part>
<title>Enterprise Portal Platform</title>
- <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="needinfo.xml" encoding="XML"/>
- <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="known.xml" encoding="XML"/>
+<!--<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="needinfo.xml" encoding="XML"/>--> <xi:include
xmlns:xi="http://www.w3.org/2001/XInclude" href="known.xml"
encoding="XML"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="resolved.xml"/>
</part>
<part>
<title>Site Publisher Plug-in</title>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="sp_known.xml" encoding="XML"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="sp_resolved.xml" encoding="XML"/>
- <chapter id="Release_Notes-Issues_Resolved_Upstream">
- <title>Issues Resolved Upstream<remark>Issues Resolved
Upstream</remark></title>
- <para>This release contains Site Publisher issues resolved upstream by eXo
Platform. The following major issues fixed by eXo Platform have been verified by the JBoss
Enterprise Portal Platform Engineering team and included as part of this release.
</para>
- <para><remark>These issues have been pulled out of eXo
Platform's JIRA instance using a modified version of JOT. The issues included
here are CRITICAL and BLOCKER issues only. </remark></para>
- <remark>An issue with my extraction script from eXo JIRA is preventing me
from pulling out the following issues:
https://jira.exoplatform.org/secure/IssueNavigator.jspa?requestId=14125&a...
</remark>
- <remark>The script is abandonware, and I have no other way of doing
extraction.</remark>
-<!--<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="resolved_issues_eXo.xml" encoding="XML"/>-->
</chapter>
- </part>
+<!--<chapter id="Release_Notes-Issues_Resolved_Upstream">
+ <title>Issues Resolved Upstream<remark>Issues Resolved
Upstream</remark></title>
+ <para>This release contains Site Publisher issues resolved upstream by eXo
Platform. The following major issues fixed by eXo Platform have been verified by the JBoss
Enterprise Portal Platform Engineering team and included as part of this release.
</para>
+ <para><remark>These issues have been pulled out of eXo Platform's
JIRA instance using a modified version of JOT. The issues included here are CRITICAL and
BLOCKER issues only. </remark></para>
+ <remark>An issue with my extraction script from eXo JIRA is preventing me from
pulling out the following issues:
https://jira.exoplatform.org/secure/IssueNavigator.jspa?requestId=14125&a...
</remark>
+ <remark>The script is abandonware, and I have no other way of doing
extraction.</remark>
+ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="resolved_issues_eXo.xml" encoding="XML"/>
+</chapter>--> </part>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
href="Revision_History.xml"/>
</book>
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-08-30 12:52:33 UTC
(rev 8836)
+++ epp/docs/branches/5.2/Release_Notes/en-US/Revision_History.xml 2012-08-30 23:18:33 UTC
(rev 8837)
@@ -6,6 +6,34 @@
<simpara>
<revhistory>
<revision>
+ <revnumber>5.2.2-4</revnumber>
+ <date>Fri Aug 31 2012</date>
+ <author>
+ <firstname>Jared</firstname>
+ <surname>Morgan</surname>
+ <email/>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Release Notes FINAL draft with all comments and feedback
incorporated.</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+ <revision>
+ <revnumber>5.2.2-3</revnumber>
+ <date>Tue Aug 28 2012</date>
+ <author>
+ <firstname>Jared</firstname>
+ <surname>Morgan</surname>
+ <email/>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Release Notes draft with all issues currently flagged in BZ as
requiring release notes as of the date in this revision entry.</member>
+ </simplelist>
+ </revdescription>
+ </revision>
+ <revision>
<revnumber>5.2.2-2</revnumber>
<date>Tue Aug 21 2012</date>
<author>
Modified: epp/docs/branches/5.2/Release_Notes/en-US/known.xml
===================================================================
--- epp/docs/branches/5.2/Release_Notes/en-US/known.xml 2012-08-30 12:52:33 UTC (rev
8836)
+++ epp/docs/branches/5.2/Release_Notes/en-US/known.xml 2012-08-30 23:18:33 UTC (rev
8837)
@@ -1,38 +1,33 @@
-<?xml version='1.0'?>
+<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
-
-<chapter id = "known_issues">
- <title>Known Issues</title>
-
- <para>
+<chapter id="known_issues">
+ <title>Known Issues</title>
+ <para>
The following issues are known to exist in this release of JBoss Enterprise
Portal Platform, and will be fixed in a subsequent release.
</para>
- <remark>
- 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=795937"><...
- Add SCP Documentation to Admin Guide for GateIn Management</term>
- <listitem>
- <remark>Status: ON_QA</remark>
- <para>
- Secure Copy documentation was missing from the Administration Guide. The SCP
information is now present in the Administration Guide for Management Extensions and
Command Line Interface chapters.
+ <remark>BZ#801821 removed from document at the request of theute.</remark>
+ <variablelist>
+<!--<varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=801821">
+ <citetitle>BZ#801821</citetitle>
+ </ulink> - Ensure that starter web application is always started
last</term>
+ <listitem>
+ <remark>Status: CLOSED</remark>
+ <para>
+ If portal extension project is named with lowercase letter, it is possible that
it starts later then necessary services, and throws java.lang.IllegalStateException. To
workaround this issue, always use an uppercase first letter. This current functionality
will be improved in a future release.
</para>
- </listitem>
-</varlistentry>
-
-<varlistentry>
- <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=803567"><...
- Create Gatein/EPP JON Plugin Documentation</term>
- <listitem>
- <remark>Status: ON_QA</remark>
- <para>
- GateIn JON Plug-in information was missing from the documentation when the
plug-in was initially released in v5.2.1. The content has been added in to a dedicated
chapter in the Administration Guide in this release. Additionally, the Installation Guide
has been updated with JBoss ON installation guidance.
+ </listitem>
+</varlistentry>--> <varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=838973">
+ <citetitle>BZ#838973</citetitle>
+ </ulink> - Dashboard pages with special characters</term>
+ <listitem>
+ <remark>Status: CLOSED</remark>
+ <para>
+ A change to how dashboard page names were validated in another issue caused
dashboard page names containing special characters to no longer be considered as invalid.
If a dashboard name contains a special character, it is now replaced with an underscore in
the URL. This new functionality will be added to the Dashboard Portlet section of the User
Guide in a future release.
</para>
- </listitem>
-</varlistentry>
-
- </variablelist>
+ </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-08-30 12:52:33 UTC (rev
8836)
+++ epp/docs/branches/5.2/Release_Notes/en-US/needinfo.xml 2012-08-30 23:18:33 UTC (rev
8837)
@@ -1,110 +1,10 @@
-<?xml version='1.0'?>
+<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
-
-<chapter id = "needinfo_issues">
- <title>NEEDINFO</title>
-
- <para>
+<chapter id="needinfo_issues">
+ <title>NEEDINFO</title>
+ <para>
The following issues require more information from developers, or need to be
processed by the lead writer before they can be approved for Release Note inclusion.
</para>
- <remark>
- These tickets will not be included in Release Notes as they currently stand.
- This could be because the tickets have not been docs Ack'd (still at
release_note?)
- or the tickets have not been set to the correct resolution status (VERIFIED,
CLOSED).
- </remark>
- <variablelist>
-
-<varlistentry>
- <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=801821"><...
- Ensure that starter web application is always started last</term>
- <listitem>
- <para>The status is CLOSED, assigned to hfnukal(a)redhat.com.</para>
- <para>
- NEEDINFO: What needs to be mentioned in the doc specifically?
-
-CAUSE:
-
-CONSEQUENCE:
-
-FIX:
-
-RESULT:
- </para>
- </listitem>
-</varlistentry>
-
-<varlistentry>
- <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=813751"><...
- Portlet Bridge - NPE when loading styles via link element</term>
- <listitem>
- <para>The status is VERIFIED, assigned to kfinniga(a)redhat.com.</para>
- <para>
- Documentation quoted that the <link> element could be used to
import Rich Faces XCSS scripts and stylesheets using the following
syntax:</para><programlisting><link type="text/css"
rel="stylesheet"
href="/richFacesPortlet/faces/rfRes/org/richfaces/skin.xcss"/></programlisting><para>This
syntax is no longer correct, and results in a NPE. To correct the issue, use a4j:loadstyle
to import the scripts and stylesheets when using LoadStyleStrategy and LoadScriptStrategy
of NONE:</para><programlisting><a4j:loadScript
src="resource:////org/ajax4jsf/framework.pack.js"
type="text/javascript"/>
- <a4j:loadScript src="resource:////org/richfaces/ui.pack.js"
type="text/javascript"/>
- <a4j:loadStyle
src="resource:////org/richfaces/skin.xcss"/></programlisting>
- </listitem>
-</varlistentry>
-
-<varlistentry>
- <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=824863"><...
- groovy template should not print "null" string when variable is
null</term>
- <listitem>
- <para>The status is ON_QA, assigned to hfnukal(a)redhat.com.</para>
- <para>
- If a GateIn Template file (*.gtmpl) contained an <input> directive
that declared a variable as a value, and that variable resolved to null, the word
"null" would be substituted for the value instead of the value parameter being
present, but undefined. For example, <input class="key"
type="text" name="key" value="${key}"/> resolved to
<input class="key" type="text" name="key"
value="null"/>, instead of <input class="key"
type="text" name="key" value/>. The fix corrects the way null
values are handled, and now prints undefined parameters, instead of printing null as the
parameter value.
- </para>
- </listitem>
-</varlistentry>
-
-<varlistentry>
- <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=835369"><...
- WSRP: The supportedOptions element in the producers response to a getServiceDescription
request is missing the supported features</term>
- <listitem>
- <para>The status is VERIFIED, assigned to claprun(a)redhat.com.</para>
- <para>
- CAUSE:
-
-CONSEQUENCE:
-
-FIX:
-
-RESULT:
- </para>
- </listitem>
-</varlistentry>
-
-<varlistentry>
- <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=835375"><...
- Patch to enhance WSRP producers response to a getServiceDescription
request</term>
- <listitem>
- <para>The status is CLOSED, assigned to mweiler(a)redhat.com.</para>
- <para>
- Is a RN required for this issue? If so, please write CCFR.
-
-CAUSE:
-
-CONSEQUENCE:
-
-FIX:
-
-RESULT:
- </para>
- </listitem>
-</varlistentry>
-
-<varlistentry>
- <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=835578"><...
- Open an "Identity Transaction" only when it is necessary</term>
- <listitem>
- <para>The status is VERIFIED, assigned to mposolda(a)redhat.com.</para>
- <para>
- Hibernate transactions had to be started for each HTTP request from an anonymous
or authenticated user, which in turn required a new database connection from the
connection pool (an expensive operation if it is not required for the request). The fix
enables a new option, "lazyStartOfHibernateTransaction", which is set in
gatein.ear/02portal.war/WEB-INF/conf/organization/picketlink-idm/picketlink-idm-config.xml.
-</para>
-<programlisting>
-<option>
- <name>lazyStartOfHibernateTransaction</name>
- <value>false</value>
- </option>
-</programlisting>
-<para>If the value is set to true, the Hibernate transaction is started only when
required, and not for every request. The default value is false for
backwards-compatibility.
- </para>
- </listitem>
-</varlistentry>
-
- </variablelist>
+ <remark> These tickets will not be included in Release Notes as they currently
stand. This could be because the tickets have not been docs Ack'd (still at
release_note?) or the tickets have not been set to the correct resolution status
(VERIFIED, CLOSED). </remark>
</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-08-30 12:52:33 UTC (rev
8836)
+++ epp/docs/branches/5.2/Release_Notes/en-US/resolved.xml 2012-08-30 23:18:33 UTC (rev
8837)
@@ -1,125 +1,303 @@
-<?xml version='1.0'?>
+<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
-
-<chapter id = "resolved">
- <title>Resolved Issues</title>
- <para>
+<chapter id="resolved">
+ <title>Resolved Issues</title>
+ <para>
The following issues have been resolved in this release of JBoss Enterprise Portal
Platform.
</para>
- <variablelist>
-
-<varlistentry>
- <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=793425"><...
- Creating user with username differing only in case-senstive case popups unknown
error</term>
- <listitem>
- <remark>Status: VERIFIED</remark>
- <para>
- Picketlink IDM was performing case-sensitive comparison of user and group names
with information stored in OpenDS. Because OpenDS does not record user and group names in
a case-sensitive manner by default, cased user names such as "viLiam" were not
distinguishable from the user name "viliam". This issue affected search
retrieval, as well as user and group creation. The issue can be fixed by configuring
Picketlink IDM to compare user and group names in a case-insensitive way. In
picketlink-idm-config.xml, change the LDAPIdentityStore option
"allowNotCaseSensitiveSearch" to true. Setting this option will prevent any
Picketlink IDM exceptions relating to case insensitivity.
+ <variablelist>
+ <varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=793425">
+ <citetitle>BZ#793425</citetitle>
+ </ulink> - Creating user with username differing only in case-senstive case
popups unknown error</term>
+ <listitem>
+ <remark>Status: VERIFIED</remark>
+ <para>
+ Picketlink IDM was performing case-sensitive comparison of user and group names
with information stored in OpenDS. Because OpenDS does not record user and group names in
a case-sensitive manner by default, cased user names such as "viLiam"
were not distinguishable from the user name "viliam". This issue
affected search retrieval, as well as user and group creation. The issue can be fixed by
configuring Picketlink IDM to compare user and group names in a case-insensitive way. In
picketlink-idm-config.xml, change the LDAPIdentityStore option
"allowNotCaseSensitiveSearch" to true. Setting this option will prevent
any Picketlink IDM exceptions relating to case insensitivity.
</para>
- </listitem>
-</varlistentry>
-
-<varlistentry>
- <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=794403"><...
- Example skin looks scattered on the right side</term>
- <listitem>
- <remark>Status: VERIFIED</remark>
- <para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=794403">
+ <citetitle>BZ#794403</citetitle>
+ </ulink> - Example skin looks scattered on the right side</term>
+ <listitem>
+ <remark>Status: VERIFIED</remark>
+ <para>
An issue with the width of .UIWorkingWorkspace .UIPageBody set in the default
skin was not suitable for SimpleSkin distributed with the Application Server. The
incompatibility caused the right border of #UIPageBody to shift left and be hidden under
the JBoss Enterprise Portal Platform banner. The fix introduces an override to the
element causing the border shift, with a specific alignment rule that sets the width to
auto. The border of #UIPageBody is now rendered properly, aligned with the breadcrumbs
panel above it.
</para>
- </listitem>
-</varlistentry>
-
-<varlistentry>
- <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=798801"><...
- Fix the sample portal datasource file.</term>
- <listitem>
- <remark>Status: VERIFIED</remark>
- <para>
- It was discovered that the gatein-sample-portal-ds.xml file shipped with the
application server was out of sync with the gatein-ds.xml file. Customers that used the
sample portal datasource file experienced issues when the file was deployed together with
gatein-sample-portal.ear. Errors were logged to the application server's log, and the
sample portal would not correctly start. The fix rebases gatein-sample-portal-ds.xml in
line with gatein-ds.xml with the following fixes: The IDM database configuration is
declared before JCR; The Hypersonic data file location is now specified under the gatein
conf directory; and the IDM datastore was changed from local-tx-datasource to
no-tx-datasource. When gatein-sample-portal-ds.xml is deployed with
gatein-sample-portal.ear, the sample portal starts, and can be visited using
http://localhost:8080/sample-portal.
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=795937">
+ <citetitle>BZ#795937</citetitle>
+ </ulink> - Add SCP Documentation to Admin Guide for GateIn
Management</term>
+ <listitem>
+ <remark>Status: VERIFIED</remark>
+ <para>
+ Secure Copy documentation was missing from the Administration Guide. The SCP
information is now present in the Administration Guide for Management Extensions and
Command Line Interface chapters.
</para>
- </listitem>
-</varlistentry>
-
-<varlistentry>
- <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=807012"><...
- Remove possibly unused JARs from gatein.ear/lib</term>
- <listitem>
- <remark>Status: VERIFIED</remark>
- <para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=798801">
+ <citetitle>BZ#798801</citetitle>
+ </ulink> - Fix the sample portal datasource file.</term>
+ <listitem>
+ <remark>Status: VERIFIED</remark>
+ <para>
+ It was discovered that the gatein-sample-portal-ds.xml file shipped with the
application server was out of sync with the gatein-ds.xml file. Customers that used the
sample portal datasource file experienced issues when the file was deployed together with
gatein-sample-portal.ear. Errors were logged to the application server's log, and
the sample portal would not correctly start. The fix rebases gatein-sample-portal-ds.xml
in line with gatein-ds.xml with the following fixes: The IDM database configuration is
declared before JCR; The Hypersonic data file location is now specified under the gatein
conf directory; and the IDM datastore was changed from local-tx-datasource to
no-tx-datasource. When gatein-sample-portal-ds.xml is deployed with
gatein-sample-portal.ear, the sample portal starts, and can be visited using
http://localhost:8080/sample-portal.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=803776">
+ <citetitle>BZ#803776</citetitle>
+ </ulink> - Disable exposure of jmx stats for anonymous caches</term>
+ <listitem>
+ <remark>Status: VERIFIED</remark>
+ <para>
+ It was discovered that exposing information for anonymous caches using JMX
resulted in too much information being exposed. The configuration has been changed to
ensure JMX stats for anonymous caches display the correct information.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=807012">
+ <citetitle>BZ#807012</citetitle>
+ </ulink> - Remove possibly unused JARs from gatein.ear/lib</term>
+ <listitem>
+ <remark>Status: VERIFIED</remark>
+ <para>
It was discovered that the gatein.ear archive contained JAR files that were not
required in the enterprise version of the product. The fix removes the unnecessary JAR
files. JAR files applicable to both community and enterprise builds are retained for
platform stability.
</para>
- </listitem>
-</varlistentry>
-
-<varlistentry>
- <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=807279"><...
- Support WSRP applications for Export/Import</term>
- <listitem>
- <remark>Status: VERIFIED</remark>
- <para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=807279">
+ <citetitle>BZ#807279</citetitle>
+ </ulink> - Support WSRP applications for Export/Import</term>
+ <listitem>
+ <remark>Status: VERIFIED</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=809141"><...
- Sample extension datasource uses local-tx-datasource type</term>
- <listitem>
- <remark>Status: VERIFIED</remark>
- <para>
- It was discovered that the sample datasource file for portal extensions
-<filename>jboss-as/docs/examples/portal/gatein-sample-portal-ds.xml</filename>
specifies the incorrect datasource type for IDM. It should be no-tx-datasource for IDM
and
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=809141">
+ <citetitle>BZ#809141</citetitle>
+ </ulink> - Sample extension datasource uses local-tx-datasource
type</term>
+ <listitem>
+ <remark>Status: VERIFIED</remark>
+ <para>
+ It was discovered that the sample datasource file for portal extensions
+<filename>jboss-as/docs/examples/portal/gatein-sample-portal-ds.xml</filename>
specifies the incorrect datasource type for IDM. It should be no-tx-datasource for IDM
and
local-tx-datasource for JCR, instead of local-tx-datasource for both directive blocks. To
work around the issue, define the datasource type manually, following the guidelines in
this Release Note.
</para>
- </listitem>
-</varlistentry>
-
-<varlistentry>
- <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=812657"><...
- error when add new group the same with existing but different with lower and upper case
on mysql</term>
- <listitem>
- <remark>Status: VERIFIED</remark>
- <para>
- Picketlink IDM was performing case-sensitive comparison of group names with
information stored in MySQL DB. Because MySQL DB does not record group names in a
case-sensitive manner by default, cased group names such as "TEST_group" were
not distinguishable from the group name "test_group". This issue affected search
retrieval, as well as group creation. The issue can be fixed by configuring Picketlink IDM
to compare group names in case-insensitive way. In picketlink-idm-config.xml, change the
HibernateIdentityStore option "allowNotCaseSensitiveSearch" to true. Setting
this option will prevent any Picketlink IDM exceptions relating to case insensitivity.
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=809777">
+ <citetitle>BZ#809777</citetitle>
+ </ulink> - Improvement for the error handling of JCR index build error or
node corruption</term>
+ <listitem>
+ <remark>Status: VERIFIED</remark>
+ <para>
+ It was discovered that if the JCR index is broken, JCR stops. This caused a JCR
index build error or node corruption during portal and Site Publisher start-up. The fix
includes upgrades to the JCR which allows the portal to start correctly and log the data
corruption, rather instead of failing to start.
</para>
- </listitem>
-</varlistentry>
-
-<varlistentry>
- <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=813729"><...
- EPP configuration files use multiple version of kernel xsd definition</term>
- <listitem>
- <remark>Status: VERIFIED</remark>
- <para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=812657">
+ <citetitle>BZ#812657</citetitle>
+ </ulink> - error when add new group the same with existing but different
with lower and upper case on mysql</term>
+ <listitem>
+ <remark>Status: VERIFIED</remark>
+ <para>
+ Picketlink IDM was performing case-sensitive comparison of group names with
information stored in MySQL DB. Because MySQL DB does not record group names in a
case-sensitive manner by default, cased group names such as "TEST_group"
were not distinguishable from the group name "test_group". This issue
affected search retrieval, as well as group creation. The issue can be fixed by
configuring Picketlink IDM to compare group names in case-insensitive way. In
picketlink-idm-config.xml, change the HibernateIdentityStore option
"allowNotCaseSensitiveSearch" to true. Setting this option will prevent
any Picketlink IDM exceptions relating to case insensitivity.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=813388">
+ <citetitle>BZ#813388</citetitle>
+ </ulink> - Special characters in a text file content is not correctly
encoded after uploading.</term>
+ <listitem>
+ <remark>Status: VERIFIED</remark>
+ <para>
+ An issue with the view template for text files was not displaying special
characters correctly in files that were uploaded. After uploading a text file which
contained "ááááá ã ã ã óóóó", displaying the text file content in
ContentExplorer would reveal the following:
"ááááá ã
ã ã óóóó". The
issue was not present in the ContentExplorer WYSIWYG editor. The fix introduces
improvements to ContentExplorer that removes the double-encoding, which results in special
characters being displayed correctly.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=813729">
+ <citetitle>BZ#813729</citetitle>
+ </ulink> - EPP configuration files use multiple version of kernel xsd
definition</term>
+ <listitem>
+ <remark>Status: VERIFIED</remark>
+ <para>
It was discovered that several versions of kernel_1_*.xsd were referenced in XML
configutation files. While no harmful consequences existed by having these obsolete
templates declared, it made the XML files appear inconsistent. The fix removes all
kernel_1_[^2].xsd, and replaces these references with kernel_1_2.xsd which makes the XML
configuration files consistent.
</para>
- </listitem>
-</varlistentry>
-
-<varlistentry>
- <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=824855"><...
- Strange duplicated requests in gadget rendering</term>
- <listitem>
- <remark>Status: VERIFIED</remark>
- <para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=813751">
+ <citetitle>BZ#813751</citetitle>
+ </ulink> - Portlet Bridge - NPE when loading styles via link
element</term>
+ <listitem>
+ <remark>Status: VERIFIED</remark>
+ <para>
+ Documentation quoted that the <link> element could be used to
import Rich Faces XCSS scripts and stylesheets using the following syntax:</para>
+ <programlisting><link type="text/css"
rel="stylesheet"
href="/richFacesPortlet/faces/rfRes/org/richfaces/skin.xcss"/></programlisting>
+ <para>This syntax is no longer correct, and results in a NPE. To correct
the issue, use a4j:loadstyle to import the scripts and stylesheets when using
LoadStyleStrategy and LoadScriptStrategy of NONE:</para>
+ <programlisting><a4j:loadScript
src="resource:////org/ajax4jsf/framework.pack.js"
type="text/javascript"/>
+ <a4j:loadScript src="resource:////org/richfaces/ui.pack.js"
type="text/javascript"/>
+ <a4j:loadStyle
src="resource:////org/richfaces/skin.xcss"/></programlisting>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=818565">
+ <citetitle>BZ#818565</citetitle>
+ </ulink> - Portal container name is hardcoded in the
LocalizationFilter</term>
+ <listitem>
+ <remark>Status: VERIFIED</remark>
+ <para>
+ A hard-coded portal container name in the LocalizationFilter caused a NPE (NULL
container) if the default context path was changed. The fix introduces changes to the way
the portal container name is parsed by the LocalizationFilter, which corrects the issue.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=824855">
+ <citetitle>BZ#824855</citetitle>
+ </ulink> - Strange duplicated requests in gadget rendering</term>
+ <listitem>
+ <remark>Status: VERIFIED</remark>
+ <para>
It was discovered that certain gadgets on the dashboard were sending more
requests then necessary. The unnecessary requests caused a performance impact on page
loading times. The fix implements changes to how gadgets are rendered. Each gadget is
rendered individually, and only loads necessary data which fixes the performance issue.
</para>
- </listitem>
-</varlistentry>
-
-<varlistentry>
- <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=824860"><...
- Error while rendering doodle gadget when source is dead</term>
- <listitem>
- <remark>Status: VERIFIED</remark>
- <para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=824860">
+ <citetitle>BZ#824860</citetitle>
+ </ulink> - Error while rendering doodle gadget when source is
dead</term>
+ <listitem>
+ <remark>Status: VERIFIED</remark>
+ <para>
When the Doodle gadget was added to a dashboard, and the source website
supplying the gadget metadata was unavailable, the gadget was not loaded, and a user
interface error occurred. The fix introduces a more informative error message to all
gadgets that require external sources, which displays in the user interface at the time
the error occurs. This helps the user diagnose the problem easier, and fixes the issue.
</para>
- </listitem>
-</varlistentry>
-
-<varlistentry>
- <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=838973"><...
- Dashboard pages with special characters</term>
- <listitem>
- <remark>Status: CLOSED</remark>
- <para>
- A change to how dashboard page names were validated in another issue caused
dashboard page names containing special characters to no longer be considered as invalid.
If a dashboard name contains a special character, it is now replaced with an underscore in
the URL. This new functionality will be added to the Dashboard Portlet section of the User
Guide in a future release.
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=824863">
+ <citetitle>BZ#824863</citetitle>
+ </ulink> - groovy template should not print "null" string
when variable is null</term>
+ <listitem>
+ <remark>Status: VERIFIED</remark>
+ <para>
+ If a GateIn Template file (*.gtmpl) contained an <input> directive
that declared a variable as a value, and that variable resolved to null, the word
"null" would be substituted for the value instead of the value parameter
being present, but undefined. For example, <input class="key"
type="text" name="key"
value="${key}"/> resolved to <input
class="key" type="text" name="key"
value="null"/>, instead of <input
class="key" type="text" name="key"
value/>. The fix corrects the way null values are handled, and now prints
undefined parameters, instead of printing null as the parameter value.
</para>
- </listitem>
-</varlistentry>
-
- </variablelist>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=824907">
+ <citetitle>BZ#824907</citetitle>
+ </ulink> - Add ability to deactivate URL rewriting on WSRP
producer</term>
+ <listitem>
+ <remark>Status: VERIFIED</remark>
+ <para>
+ In the current WSRP implementation, the producer URL is rewritten at consumer
side so it can be accessed remotely.
+If users have static content at both the producer and consumer sides, they do not expect
those resources to be accessed from a remote producer. In these circumstances, it was
desirable to disable URL rewriting, however no such mechanism existed. The fix includes
enhancements to the WSRP, with the addition of the
"org.gatein.wsrp.producer.deactivateURLRewriting". If the parameter is
set to true, URL rewriting is disabled.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=829885">
+ <citetitle>BZ#829885</citetitle>
+ </ulink> - X.509 token in ws-security support in WSRP</term>
+ <listitem>
+ <remark>Status: VERIFIED</remark>
+ <para>
+ It was discovered that JBossWS supports X.509 token with WSSE, however the
functionality only partially worked. It was not possible to encrypt the entire message.
The fix introduces improvements to this aspect of JBossWS in WSRP, and corrects the
issue.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=831445">
+ <citetitle>BZ#831445</citetitle>
+ </ulink> - WSRP is failing when including OASIS WSRP WSDL</term>
+ <listitem>
+ <remark>Status: VERIFIED</remark>
+ <para>
+ OASIS changed the way HTTP WSRP WSDL requests were redirected. The requests
redirected to a HTTP 302 response that included an XML document with a public ID, but no
system ID. This caused an exception "SAXParseException: White spaces are required
between publicId and systemId" to be raised.
+The fix introduces changes to the JBossWS entity resolver, which now uses the WSDLs and
XSDs placed in the unzipped folder instead of the ones from the OASIS website.
+This corrects the issue, and restores expected functionality to Netunity v1 &
v2.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=832089">
+ <citetitle>BZ#832089</citetitle>
+ </ulink> - WSRP: getPortletProperties doesn't behave properly when
en empty set of property names is passed</term>
+ <listitem>
+ <remark>Status: VERIFIED</remark>
+ <para>
+ A problem detected with reading preferences from WLP 10.0.1 through a WSRP V1
endpoint caused the portlet properties to raise a NPE as a result of the interaction. This
issue has been fixed in the affected WSRP component, and the component updated for this
release. Reading the portlet properties via WSRP V1 now works as expected.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=835369">
+ <citetitle>BZ#835369</citetitle>
+ </ulink> - WSRP: The supportedOptions element in the producers response to
a getServiceDescription request is missing the supported features</term>
+ <listitem>
+ <remark>Status: VERIFIED</remark>
+ <para>
+ The WSRP Producer was ignoring several optional elements when returning a
service description response to the consumer, including the supportedOptions element. WSRP
Consumers that were relying on these optional elements to tailor their communication with
the producer could behave improperly based on wrong assumptions due to missing (though
optional) information. The WSRP Producer now properly emits the supportedOptions element
in its service description response, which allows Consumers to properly tailor their
behavior, and results in improved interoperability with third-party consumers.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=835375">
+ <citetitle>BZ#835375</citetitle>
+ </ulink> - Patch to enhance WSRP producers response to a
getServiceDescription request</term>
+ <listitem>
+ <remark>Status: CLOSED</remark>
+ <para>
+ A number of issues were discovered: 1) WSRP: getPortletProperties
doesn't behave properly when en empty set of property names is passed; 2) WSRP
type factories require a lang value to create a Property even though it's
optional according to XSD. This caused the requests to be rejected by the server with an
IllegalArgumentException: 'Property requires a non-null, non-empty
language'. The fix applies a patch to the affected files which corrects the
issue.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=835578">
+ <citetitle>BZ#835578</citetitle>
+ </ulink> - Open an "Identity Transaction" only when it is
necessary</term>
+ <listitem>
+ <remark>Status: VERIFIED</remark>
+ <para>
+ Hibernate transactions had to be started for each HTTP request from an anonymous
or authenticated user, which in turn required a new database connection from the
connection pool (an expensive operation if it is not required for the request). The fix
enables a new option, "lazyStartOfHibernateTransaction", which is set in
gatein.ear/02portal.war/WEB-INF/conf/organization/picketlink-idm/picketlink-idm-config.xml.
+</para>
+ <programlisting>
+<option>
+ <name>lazyStartOfHibernateTransaction</name>
+ <value>false</value>
+ </option>
+</programlisting>
+ <para>If the value is set to true, the Hibernate transaction is started
only when required, and not for every request. The default value is false for
backwards-compatibility.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=837029">
+ <citetitle>BZ#837029</citetitle>
+ </ulink> - Change of JBC configuration - LRU algorithm + separate
configuration for portal-system workspace</term>
+ <listitem>
+ <remark>Status: VERIFIED</remark>
+ <para>
+ A change made to the JBoss Cache cache algorithm caused performance issues for
some configuration scenarios. The fix introduces configuration with an improved algorithm.
The new algorithm references a new configuration file, which now loads correctly. This
corrects the performance issues.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
</chapter>
Modified: epp/docs/branches/5.2/Release_Notes/en-US/sp_known.xml
===================================================================
--- epp/docs/branches/5.2/Release_Notes/en-US/sp_known.xml 2012-08-30 12:52:33 UTC (rev
8836)
+++ epp/docs/branches/5.2/Release_Notes/en-US/sp_known.xml 2012-08-30 23:18:33 UTC (rev
8837)
@@ -3,9 +3,38 @@
]>
<chapter id="sp_known_issues">
<title>Known Issues</title>
- <para>
- The following issues are known to exist in this release of the JBoss Enterprise
Portal Platform Site Publisher Add-on, and will be fixed in a subsequent release.
+ <para>The following issues are known to exist in this release of the JBoss
Enterprise Portal Platform Site Publisher Add-on, and will be fixed in a subsequent
release.</para>
+ <remark>20120831 - Depending on the response from Martin to Thomas'
email about the following upgrade binaries I can include the following sentence and remove
the upgrade binaries instruction set. If this is not the correct way to proceed, I have
added Thomas' guidance about getting customers to remove the libraries after
server first-run (step 4 in that procedure.</remark>
+ <para>There are no known issues for the Site Publisher plug-in in this
release.</para>
+ <remark>And I would remove this release note if Martin will be providing this to
customers using KB.</remark>
+ <variablelist>
+ <varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=846276">
+ <citetitle>BZ#846276</citetitle>
+ </ulink> - Include upgrade binaries in SP package</term>
+ <listitem>
+ <remark>Status: ASSIGNED</remark>
+ <para>
+ During the migration from EPP-SP 5.1.x to EPP-SP 5.2.x the templates stored in
the JCR database were not updated to the latest version. The issue was discovered too late
in the release cycle.
</para>
- <remark> 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>
- <remark>NEEDINFO: There are currently no Known Issues in BZ for Site Publisher
according to the filters Is this correct? </remark>
-<!--<variablelist/>--></chapter>
+ <para>To work around this issue, the binaries containing the UpgradePlugins
have been added to the EPP-SP package, so customers who migrate from an older EPP-SP
release can add them to their installation manually. Follow these steps:
+
+ </para>
+ <orderedlist>
+ <listitem>
+ <para>Download Site Publisher binary from the Customer
Portal.</para>
+ </listitem>
+ <listitem>
+ <para>Extract jars from the archive to
<filename><replaceable>EPP_HOME</replaceable>/jboss-as/server/<replaceable>PROFILE</replaceable>/lib</filename>
folder.</para>
+ </listitem>
+ <listitem>
+ <para>Start the server.</para>
+ </listitem>
+ <listitem>
+ <para>Remove the jar libraries from the server after starting Site
Publisher for the first time.</para>
+ </listitem>
+ </orderedlist>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+</chapter>
Modified: epp/docs/branches/5.2/Release_Notes/en-US/sp_needinfo.xml
===================================================================
--- epp/docs/branches/5.2/Release_Notes/en-US/sp_needinfo.xml 2012-08-30 12:52:33 UTC (rev
8836)
+++ epp/docs/branches/5.2/Release_Notes/en-US/sp_needinfo.xml 2012-08-30 23:18:33 UTC (rev
8837)
@@ -4,17 +4,13 @@
<chapter id = "sp_needinfo_issues">
<title>NEEDINFO</title>
-
- <para>
- The following issues require more information from developers, or need to be
processed by the lead writer before they can be approved for Release Note inclusion.
- </para>
- <remark>
+ <para>The following issues require more information from developers, or need to
be processed by the lead writer before they can be approved for Release Note
inclusion.</para>
+ <remark>
These tickets will not be included in Release Notes as they currently stand.
This could be because the tickets have not been docs Ack'd (still at
release_note?)
or the tickets have not been set to the correct resolution status (VERIFIED,
CLOSED).
- </remark>
+ </remark>
<variablelist>
-#846276 ASSIGNED - hfnukal(a)redhat.com - Include upgrade binaries in SP package
</variablelist>
</chapter>
Modified: epp/docs/branches/5.2/Release_Notes/en-US/sp_resolved.xml
===================================================================
--- epp/docs/branches/5.2/Release_Notes/en-US/sp_resolved.xml 2012-08-30 12:52:33 UTC (rev
8836)
+++ epp/docs/branches/5.2/Release_Notes/en-US/sp_resolved.xml 2012-08-30 23:18:33 UTC (rev
8837)
@@ -6,5 +6,31 @@
<para>
The following issues have been resolved in this release of the JBoss Enterprise
Portal Platform Site Publisher Add-on.
</para>
- <remark>NEEDINFO: There are currently no Resolved Issues in BZ for Site Publisher
according to the filters Is this correct? </remark>
-<!--<variablelist/>--></chapter>
+ <remark>20120831 - Because we don't have any BZ captured Site Publisher
issues marked as resolved for this release, I propose the following
wording.</remark>
+ <para>There are no resolved issues for the Site Publisher plug-in in this
release.</para>
+ <remark>20120831 - but because this may not be a good message to send to
customers, how about this as a compromise.</remark>
+ <para>Site Publisher issues affecting this release were fixed upstream in eXo
Platform for this release.</para>
+<!--<variablelist>
+ <varlistentry>
+ <term><ulink
url="https://bugzilla.redhat.com/show_bug.cgi?id=846276">
+ <citetitle>BZ#846276</citetitle>
+ </ulink> - Include upgrade binaries in SP package</term>
+ <listitem>
+ <remark>Status: ASSIGNED</remark>
+ <para>
+ During the migration from EPP-SP 5.1.x to EPP-SP 5.2.x the templates stored in
the JCR database were not updated to the latest version. The issue was discovered too late
in the </para>
+ <para>To work around this issue, the binaries containing the UpgradePlugins
have been added to the EPP-SP package, so customers who migrate from an older EPP-SP
release can add them to their installation manually. Follow these
steps:<orderedlist>
+ <listitem>
+ <para>Download Site Publisher binary from the Customer
Portal.</para>
+ </listitem>
+ <listitem>
+ <para>Extract jars from the archive to
<filename><replaceable>EPP_HOME</replaceable>/jboss-as/server/<replaceable>PROFILE</replaceable>/lib</filename>
folder.
+</para>
+ </listitem>
+ <listitem>
+ <para>Start the server.</para>
+ </listitem>
+ </orderedlist></para>
+ </listitem>
+ </varlistentry>
+</variablelist>--></chapter>