10:45 p.m.
Author: smumford
Date: 2011-07-04 23:45:04 -0400 (Mon, 04 Jul 2011)
New Revision: 6820
Modified:
epp/docs/branches/5.1/Release_Notes/en-US/5.1.1_Release_Notes.xml
epp/docs/branches/5.1/Release_Notes/en-US/Book_Info.xml
epp/docs/branches/5.1/Release_Notes/en-US/Revision_History.xml
epp/docs/branches/5.1/Release_Notes/en-US/resolved_issues.xml
epp/docs/branches/5.1/Release_Notes/publican.cfg
Log:
Updates for new Publication process and Release Notes work
Modified: epp/docs/branches/5.1/Release_Notes/en-US/5.1.1_Release_Notes.xml
===================================================================
--- epp/docs/branches/5.1/Release_Notes/en-US/5.1.1_Release_Notes.xml 2011-07-05 03:15:46
UTC (rev 6819)
+++ epp/docs/branches/5.1/Release_Notes/en-US/5.1.1_Release_Notes.xml 2011-07-05 03:45:04
UTC (rev 6820)
@@ -3,7 +3,7 @@
<!ENTITY % BOOK_ENTITIES SYSTEM "5.1.1_Release_Notes.ent">
%BOOK_ENTITIES;
]>
-<article status="draft">
+<article>
<xi:include href="Book_Info.xml"
xmlns:xi="http://www.w3.org/2001/XInclude" />
<section id="sect-5.1.1_Release_Notes-Introduction">
<title>Introduction</title>
@@ -17,23 +17,10 @@
</section>
<section id="sect-5.1.1_Release_Notes-New_and_Upgraded_Components">
- <title>New and Upgraded Components</title>
- <variablelist
id="vari-5.1.1_Release_Notes-New_and_Upgraded_Components-New_Components">
- <title>New Components</title>
- <varlistentry>
- <term></term>
- <listitem>
- <para>
-
- </para>
-
- </listitem>
-
- </varlistentry>
-
- </variablelist>
+ <title>Upgraded Components</title>
+
<variablelist
id="vari-5.1.1_Release_Notes-New_and_Upgraded_Components-Upgraded_Components">
- <title><emphasis role="bold">Upgraded
Components</emphasis></title>
+ <title></title>
<varlistentry>
<term>JBoss EAP</term>
<listitem>
@@ -46,7 +33,7 @@
<term>JBoss Portlet Bridge</term>
<listitem>
<para>
- The JBoss Portlet Bridge component has been upgraded to version
2.1.1.GA.EPP51.
+ The JBoss Portlet Bridge component has been upgraded to version 2.1.1.GA.EPP51.
<!--JBEPP-888-->
</para>
</listitem>
</varlistentry>
@@ -62,7 +49,7 @@
<term>eXo JCR</term>
<listitem>
<para>
- The eXo JAva Content Repository has been upgraded to version
1.12.8.
+ The eXo Java Content Repository has been upgraded to version 1.12.8-GA.
<!--JBEPP-728-->
</para>
</listitem>
</varlistentry>
@@ -70,7 +57,7 @@
<term>PicketLink</term>
<listitem>
<para>
- The PicketLink IDM component has been upgraded to version 1.1.8-GA.
+ The PicketLink IDM component has been upgraded to version 1.1.8-GA.
<!--JBEPP-858-->
</para>
</listitem>
</varlistentry>
@@ -86,7 +73,7 @@
<term>WSRP</term>
<listitem>
<para>
- The WSRP component has been upgraded to 2.0.1-GA.
+ The WSRP component has been upgraded to 2.0.1-GA. <!--JBEPP-789-->
</para>
</listitem>
</varlistentry>
@@ -170,7 +157,7 @@
</row>
<row>
<entry>
- Apache Schindig
+ Apache Shindig
</entry>
<entry>
1.0-r790473-Patch04
@@ -277,7 +264,7 @@
Seam
</entry>
<entry>
- 2.2.3.EAP5
+ 2.2.3.EAP5-13.ep5.el6
</entry>
</row>
<row>
@@ -285,7 +272,7 @@
Richfaces
</entry>
<entry>
- 3.3.1.SP3
+ 3.3.1.SP3.1.ep5.el6
</entry>
</row>
<row>
@@ -471,7 +458,7 @@
<term>Site Publisher</term>
<listitem>
<para>
- Dedicated Installation and User Guides provide information on
installing, configuring and using the JBoss Enterprise Portal Platform Site Publisher
extension. These documents assume the required JBoss Enterprise Portal Platform installion
is present and functioning properly.
+ Dedicated Installation and User Guides provide information on
installing, configuring and using the JBoss Enterprise Portal Platform Site Publisher
extension. These documents assume the required JBoss Enterprise Portal Platform
installation is present and functioning properly.
</para>
</listitem>
</varlistentry>
@@ -490,8 +477,8 @@
<ulink type="http" url="https://access.redhat.com/home "
/>
</para>
</formalpara>
- <formalpara
id="form-5.1.1_Release_Notes-_Product_Support_and_License_Website_Links_-JBoss_Customer_Suport_Portal_Downloads">
- <title>JBoss Customer Suport Portal Downloads</title>
+ <formalpara
id="form-5.1.1_Release_Notes-_Product_Support_and_License_Website_Links_-JBoss_Customer_Support_Portal_Downloads">
+ <title>JBoss Customer Support Portal Downloads</title>
<para>
<ulink type="http"
url="https://access.redhat.com/jbossnetwork/restricted/listSoftware....
/>
</para>
@@ -541,4 +528,4 @@
</section>
<xi:include href="Revision_History.xml"
xmlns:xi="http://www.w3.org/2001/XInclude" />
-</article>
\ No newline at end of file
+</article>
Modified: epp/docs/branches/5.1/Release_Notes/en-US/Book_Info.xml
===================================================================
--- epp/docs/branches/5.1/Release_Notes/en-US/Book_Info.xml 2011-07-05 03:15:46 UTC (rev
6819)
+++ epp/docs/branches/5.1/Release_Notes/en-US/Book_Info.xml 2011-07-05 03:45:04 UTC (rev
6820)
@@ -3,13 +3,13 @@
<!ENTITY % BOOK_ENTITIES SYSTEM "5.1.1_Release_Notes.ent">
%BOOK_ENTITIES;
]>
-<articleinfo id="arti-5.1.1_Release_Notes-a5.1.1_Release_Notes">
+<articleinfo id="arti-5.1.1_Release_Notes-5.1.1_Release_Notes">
<title>5.1.1 Release Notes</title>
- <subtitle>For use with JBoss Enterprise Portal Platform
&VX;</subtitle>
+ <subtitle>For use with JBoss Enterprise Portal Platform
&VZ;</subtitle>
<productname>JBoss Enterprise Portal Platform</productname>
<productnumber>5.1</productnumber>
- <edition>1</edition>
- <pubsnumber>1.3</pubsnumber>
+ <edition>2.1</edition>
+ <pubsnumber>5.1.1</pubsnumber>
<abstract>
<para>
These release notes contain important information related to JBoss Enterprise
Portal Platform &VX; 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.1/Release_Notes/en-US/Revision_History.xml
===================================================================
--- epp/docs/branches/5.1/Release_Notes/en-US/Revision_History.xml 2011-07-05 03:15:46 UTC
(rev 6819)
+++ epp/docs/branches/5.1/Release_Notes/en-US/Revision_History.xml 2011-07-05 03:45:04 UTC
(rev 6820)
@@ -7,6 +7,20 @@
<title>Revision History</title>
<simpara>
<revhistory>
+ <revision>
+ <revnumber>2.1-5.1.1</revnumber>
+ <date>Monday June 27 2011</date>
+ <author>
+ <firstname>Scott</firstname>
+ <surname>Mumford</surname>
+ <email>smumford(a)redhat.com</email>
+ </author>
+ <revdescription>
+ <simplelist>
+ <member>Updated for 5.1.1 Release.</member>
+ </simplelist>
+ </revdescription>
+ </revision>
<revision>
<revnumber>1-1.3</revnumber>
<date>Thu Jun 02 2011</date>
Modified: epp/docs/branches/5.1/Release_Notes/en-US/resolved_issues.xml
===================================================================
--- epp/docs/branches/5.1/Release_Notes/en-US/resolved_issues.xml 2011-07-05 03:15:46 UTC
(rev 6819)
+++ epp/docs/branches/5.1/Release_Notes/en-US/resolved_issues.xml 2011-07-05 03:45:04 UTC
(rev 6820)
@@ -51,7 +51,7 @@
<term><ulink url="https://issues.jboss.org/browse/JBEPP-773"
/></term>
<listitem>
<para>
- A bug prevented the 'Preferences' tab from appearing in some portlets.
The tab would only appear in portlets that were customized during the first deployment
through the portal.xml descriptor. Non-customized portlets would not show a
'Preferences' tab. The UIFormInputSet.java and UIPortletForm.java files have been
patched to fix the issue and now the tab now appears in all portlets that have
configurable preferences.
+ A bug prevented the 'Preferences' tab from appearing in some portlets. The tab
would only appear in portlets that were customized during the first deployment through the
<filename>portal.xml</filename> descriptor. Non-customized portlets would not
show a 'Preferences' 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>
@@ -61,7 +61,7 @@
<term><ulink url="https://issues.jboss.org/browse/JBEPP-780"
/></term>
<listitem>
<para>
- The two JBoss Cache instances created by PicketLink were calling on the same
configuration file in idm-configuration.xml and, as a result, were using the same cluster
names. This could lead to conflicts as the same JBoss Cache instance could join the same
channel twice. Separate configuration files were added to the distribution package and the
Portal configuration was customized to call on the different files. JBoss Cache instances
can now run simultaneously without conflict.
+ 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. 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>
@@ -81,7 +81,7 @@
<term><ulink url="https://issues.jboss.org/browse/JBEPP-848"
/></term>
<listitem>
<para>
- A bug in data caching prevented some changes to Portal navigation from reloading
in real time. When changing a group navigation priority, the reordering of the groups was
only happening after a log-out. The UIPageNavigationForm.java has been patched to correct
this and navigation changes now update immediately, without the user needing to log-out.
+ 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> has been patched to correct
this and navigation changes now update immediately, without the user needing to log-out.
</para>
</listitem>
</varlistentry>
@@ -91,7 +91,7 @@
<term><ulink url="https://issues.jboss.org/browse/JBEPP-857"
/></term>
<listitem>
<para>
- WSRP Strict mode was previously set only via listeners, which were not triggered
at startup since they don't yet exist at that time. This meant that WSRP Strict Mode
was not properly restored when JBoss Enterprise Portal Platform was started. An upgrade to
WSRP 2.0.1 GA corrects this issue and WSRP Strict Mode is now properly restored from
persistent state at startup.
+ WSRP Strict mode was previously set only via listeners, which were not triggered
at start up since they don't yet exist at that time. This meant that WSRP Strict Mode
was not properly restored when JBoss Enterprise Portal Platform was started. An upgrade to
WSRP 2.0.1 GA corrects this issue and WSRP Strict Mode is now properly restored from
persistent state at start up.
</para>
</listitem>
</varlistentry>
@@ -101,7 +101,7 @@
<term><ulink url="https://issues.jboss.org/browse/JBEPP-890"
/></term>
<listitem>
<para>
- Exceptions thrown by the handleFaceletNotFound method (when a facelet file was
not found) were being obscured by FaceletViewHandler as the response object was not a
subtype of HttpServletResponse (it is a instance of PortletResponse).
FaceletPortletViewHandler.java has been updated to handle instances of both
HttpServletResponse and PortletResponse response objects.
+ Exceptions thrown by the <literal>handleFaceletNotFound</literal> method
(when a facelet file was not found) were being obscured by
<literal>FaceletViewHandler</literal> as the response object was not a subtype
of <literal>HttpServletResponse</literal> (it is a instance of
<literal>PortletResponse</literal>).
<filename>FaceletPortletViewHandler.java</filename> has been updated to handle
instances of both <literal>HttpServletResponse</literal> and
<literal>PortletResponse</literal> response objects.
</para>
</listitem>
</varlistentry>
@@ -111,7 +111,7 @@
<term><ulink url="https://issues.jboss.org/browse/JBEPP-896"
/></term>
<listitem>
<para>
- The Single Sign On (SSO) AbstractLogoutFilter in JBoss Enterprise Portal
Platform would read request parameters before setting the character encoding. When a form
was submitted with non-UTF-8 characters (while SSO was enabled) the values could be
garbled on output. An upgrade of the SSO component to version 1.0.2-epp-GA (which includes
a patch to the AbstractLogoutFilter code) resolves this issue and Non-UTF-8 characters are
now specified correctly.
+ The Single Sign On (SSO) <literal>AbstractLogoutFilter</literal> 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 <literal>AbstractLogoutFilter</literal> code)
resolves this issue and Non-UTF-8 characters are now specified correctly.
</para>
</listitem>
</varlistentry>
@@ -121,7 +121,7 @@
<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.
+ When starting previous Portal versions, page definitions were held in system memory
before being written. This could cause an <literal>Out Of Memory</literal>
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 <literal>Out Of Memory</literal> error is no longer encountered.
</para>
</listitem>
</varlistentry>
@@ -131,7 +131,15 @@
<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.
+ JBoss Enterprise Portal Platform doesn't set content-type on css-files added via
<filename>gatein-resources.xml</filename>. This causes Internet Explorer 9 to
ignore these css-files due to new security policy.
+ </para>
+ <para>
+ A console message reads:
+ </para>
+<screen>SEC7113: CSS was ignored due to mime type mismatch
+</screen>
+ <para>
+ 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>
Modified: epp/docs/branches/5.1/Release_Notes/publican.cfg
===================================================================
--- epp/docs/branches/5.1/Release_Notes/publican.cfg 2011-07-05 03:15:46 UTC (rev 6819)
+++ epp/docs/branches/5.1/Release_Notes/publican.cfg 2011-07-05 03:45:04 UTC (rev 6820)
@@ -5,3 +5,6 @@
xml_lang: en-US
brand: JBoss
show_remarks: 1
+cvs_branch: ENG-RHEL-6-DOCS
+cvs_root: :ext:cvs.devel.redhat.com:/cvs/dist
+cvs_pkg: JBoss_Enterprise_Portal_Platform-5.1.1_Release_Notes-5.1-web-__LANG__
\ No newline at end of file