Author: smumford
Date: 2010-10-12 01:40:34 -0400 (Tue, 12 Oct 2010)
New Revision: 4628
Added:
epp/docs/branches/EPP_5_0_Branch/Release_Notes/en-US/Release_Notes.ent
epp/docs/branches/EPP_5_0_Branch/Release_Notes/en-US/Release_Notes.xml
Removed:
epp/docs/branches/EPP_5_0_Branch/Release_Notes/en-US/5.0.1_Release_Notes.ent
epp/docs/branches/EPP_5_0_Branch/Release_Notes/en-US/5.0.1_Release_Notes.xml
Modified:
epp/docs/branches/EPP_5_0_Branch/Release_Notes/en-US/Book_Info.xml
epp/docs/branches/EPP_5_0_Branch/Release_Notes/en-US/Revision_History.xml
Log:
Removing versioning from Release Notes
Deleted: epp/docs/branches/EPP_5_0_Branch/Release_Notes/en-US/5.0.1_Release_Notes.ent
===================================================================
---
epp/docs/branches/EPP_5_0_Branch/Release_Notes/en-US/5.0.1_Release_Notes.ent 2010-10-12
05:16:11 UTC (rev 4627)
+++
epp/docs/branches/EPP_5_0_Branch/Release_Notes/en-US/5.0.1_Release_Notes.ent 2010-10-12
05:40:34 UTC (rev 4628)
@@ -1,4 +0,0 @@
-<!ENTITY HOLDER "Red Hat, Inc">
-<!ENTITY YEAR "2010">
-<!ENTITY PRODUCT "JBoss Enterprise Portal Platform">
-<!ENTITY VERSION "5.0.1">
Deleted: epp/docs/branches/EPP_5_0_Branch/Release_Notes/en-US/5.0.1_Release_Notes.xml
===================================================================
---
epp/docs/branches/EPP_5_0_Branch/Release_Notes/en-US/5.0.1_Release_Notes.xml 2010-10-12
05:16:11 UTC (rev 4627)
+++
epp/docs/branches/EPP_5_0_Branch/Release_Notes/en-US/5.0.1_Release_Notes.xml 2010-10-12
05:40:34 UTC (rev 4628)
@@ -1,558 +0,0 @@
-<?xml version='1.0' encoding='utf-8' ?>
-<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
-]>
-<article id="JBEPP_5_0_Release_Notes">
- <xi:include href="Book_Info.xml"
xmlns:xi="http://www.w3.org/2001/XInclude" />
- <section id="sect-Release_Notes-Introduction">
- <title>Introduction</title>
- <para>
- &PRODUCT; offers an intuitive, easy to manage user interface and a proven core
infrastructure to enable organizations to quickly build dynamic web sites in a highly
reusable way. By bringing the principals of Open Choice to the presentation layer,
&PRODUCT; &VERSION; maximizes existing skills and technology investments.
- </para>
- <para>
- By integrating proven open source frameworks such as JBoss Seam, Hibernate, Tomcat and
JBoss Cache &PRODUCT; takes advantage of innovations in the open source community. As
well, &PRODUCT; version &VERSION; is fully tested and supported by Red Hat, and is
certified to work on many leading enterprise hardware and software products.
- </para>
- </section>
-
-<!-- <section>
- <title>New Features</title>
- <variablelist>
-
- </variablelist>
- </section> -->
-
- <section id="sect-Release_Notes-Architecture_of_PRODUCT_VERSION">
- <title>Component Versions</title>
- <para>
- This section details the versions of the components which create the JBoss Enterprise
Portal Platform 5.0.1.
- </para>
- <table>
- <title>JBoss Enterprise Portal Platform Component Versions</title>
- <tgroup cols="2">
- <thead>
- <row>
- <entry>
- Component
- </entry>
- <entry>
- Version
- </entry>
- </row>
- </thead>
- <tbody>
- <row>
- <entry>
- JBoss Enterprise Application Platform
- </entry>
- <entry>
- 5.0.1-GA
- </entry>
- </row>
- <row>
- <entry>
- JBoss Cache
- </entry>
- <entry>
- 3.2.4
- </entry>
- </row>
- <row>
- <entry>
- GateIn Common
- </entry>
- <entry>
- 2.0.2-GA
- </entry>
- </row>
- <row>
- <entry>
- GateIn WCI
- </entry>
- <entry>
- 2.0.1-GA
- </entry>
- </row>
- <row>
- <entry>
- GateIn PC
- </entry>
- <entry>
- 2.1.1-GA
- </entry>
- </row>
- <row>
- <entry>
- GateIn WSRP
- </entry>
- <entry>
- 1.1.1-GA
- </entry>
- </row>
- <row>
- <entry>
- GateIn MOP
- </entry>
- <entry>
- 1.0.2-GA
- </entry>
- </row>
- <row>
- <entry>
- GateIn SSO
- </entry>
- <entry>
- 1.0.0-epp
- </entry>
- </row>
- <row>
- <entry>
- PicketLink IDM
- </entry>
- <entry>
- 1.1.5.GA
- </entry>
- </row>
- <row>
- <entry>
- eXo JCR
- </entry>
- <entry>
- 1.12.3-GA
- </entry>
- </row>
- <row>
- <entry>
- eXo Kernel
- </entry>
- <entry>
- 2.2.3-GA
- </entry>
- </row>
- <row>
- <entry>
- Portlet Bridge
- </entry>
- <entry>
- 2.0.0
- </entry>
- </row>
- <row>
- <entry>
- Chromattic
- </entry>
- <entry>
- 1.0.1
- </entry>
- </row>
- <row>
- <entry>
- Apache Shindig
- </entry>
- <entry>
- 1.0-r790473-Patch03
- </entry>
- </row>
- </tbody>
- </tgroup>
- </table>
- </section>
-
- <section id="sect-Release_Notes-Certified_Environments">
- <title>Installation</title>
- <para>
- The JBoss Enterprise Portal Platform Installation Guide contains details of software
and hardware requirements as well as detailed installation instructions.
- </para>
- <para>
- The Installation Guide can be found online at <ulink type="http"
url="http://docs.redhat.com/docs/">http://docs.redhat.com/do...;.
- </para>
- </section>
-
- <section id="Issues-fixed-in-this-release">
- <title>
- Issues fixed in this release
- </title>
-<!-- Commented out for current release. Retaining the text to be reused in future
release drafts.
- <warning>
- <title>Draft</title>
- <para>
- These entries are drafts. They have been drawn from comments and associated JIRAs from
the list at:
- <ulink type="http"
url="https://jira.jboss.org/secure/IssueNavigator.jspa?mode=hide&...;.
- </para>
- <para>
- <emphasis role="bold">They are likely not technically correct at the
moment</emphasis>, but they will serve as a basis and will be corrected in
subsequent iterations after technical and QE reviews.
- </para>
- </warning> -->
- <para>
- Following is a list of issues fixed in this release:
- </para>
- <variablelist>
- <varlistentry>
- <term><ulink type="http"
url="https://jira.jboss.org/browse/JBEPP-452"></ulink>...
- <listitem>
- <para>
- &PRODUCT;'s <literal>request.getLocale()</literal> was only
reflecting a user's browser language preference, regardless of what language was set
in the portal itself.
- </para>
- <para>
- A fix was installed to address this issue and return values that are aligned with
the rest of the portal.
- </para>
- <para>
- As a result, portlets use the preferred locale of the portal user and not the
locale from the http servlet request.
- </para>
- <para>
- Refer to the source commit logs in the above JIRA for specific code
changes in this fix.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><ulink type="http"
url="https://jira.jboss.org/browse/JBEPP-403"></ulink>...
- <listitem>
- <para>
- The language fix implemented for <ulink type="http"
url="https://jira.jboss.org/browse/JBEPP-452"></ulink> also corrected
an issue wherein a failed login attempt would present the login form in an incorrect
language (that is; not the language set for the portal).
- </para>
- <para>
- Refer to the source commit logs in the above JIRA for specific
code changes in this fix.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><ulink type="http"
url="https://jira.jboss.org/browse/JBEPP-383"></ulink>...
- <listitem>
- <para>
- The language fix also corrected an issue which caused language settings for
languages with country variants (such as Chinese - China and Chinese - Taiwan) were not
stored between logins.
- </para>
- <para>
- Refer to the source commit logs in the above JIRA for specific
code changes in this fix.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><ulink type="http"
url="https://jira.jboss.org/browse/JBEPP-393"></ulink>...
- <listitem>
- <para>
- The Shindig Gadget Server was reporting malformed security tokens after a gadget
was added to a portal. The error was originating from the
<literal>org.apache.shindig.gadgets.servlet.RpcServlet</literal>'s
<literal>doPost</literal> processing method. This method of reading POST
requests from the servlet's input stream was being corrupted if the
<literal>InputStream</literal> had already been read (in the recorded case, by
<literal>RequestDumperValve</literal>).
- </para>
- <para>
- This error was resolved with a patch to Apache Shindig which allows a reset of
the input stream before the <literal>doPost</literal> method is invoked.
- </para>
- <para>
- Refer to the source commit logs in the above JIRA for specific
code changes in this fix.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><ulink type="http"
url="https://jira.jboss.org/browse/JBEPP-390"></ulink>...
- <listitem>
- <para>
- A bug in PicketLink IDM meant that changing the LDAP group membership type of a
user to anything other than 'member' would appear to delete that user from the
group. This was caused by the PicketLink IDM UI not showing any memberships other than
'member', even if other types were correctly retained in the underlying database.
- </para>
- <para>
- This issue has been fixed with an updated PicketLink jar.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><ulink type="http"
url="https://jira.jboss.org/browse/JBEPP-363"></ulink>...
- <listitem>
- <para>
- The updated PicketLink jar has also resolved an issue encountered when deleting
registered portal users from LDAP.
- </para>
- <para>
- Information about users deleted from LDAP would still be retained in the
database and those user accounts would appear in the portal user list. If one of these
legacy accounts was then edited, the inconsistences would prevent any further login
attempts from succeeding until the user session was cleared.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><ulink type="http"
url="https://jira.jboss.org/browse/JBEPP-477"></ulink>...
- <listitem>
- <para>
- The updated PicketLink IDM component removes case-sensitivity from the username
field of the portal login page.
- </para>
- <para>
- This allows users whose login names contain capital letters to authenticate
successfully, regardless of the case used in the username field of the login form.
- </para>
- <para>
- Note that the password field remains case-sensitive for security.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><ulink type="http"
url="https://jira.jboss.org/browse/JBEPP-368"></ulink>...
- <listitem>
- <para>
- The datasource defined in
<filename>jboss-epp-5.0/jboss-as/docs/examples/portal/gatein-sample-portal-ds.xml</filename>
has been updated from <literal>local-tx-datasource</literal> to
<literal>no-tx-datasource</literal>.
- </para>
- <para>
- This update prevents exceptions being thrown by the JCR when the name of the
datasource in <filename>server/default/deploy/gatein-ds.xml</filename> is
changed to suit operational requirements.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><ulink type="http"
url="https://jira.jboss.org/browse/JBEPP-342"></ulink>...
- <listitem>
- <para>
- Node names were being displayed incorrectly if they contained accentuated
characters. For example; if the site language was German, the SiteMap node would display
as <literal>Seiten&uuml;bersicht</literal> instead of
<emphasis role="bold">Seitenübersicht</emphasis>.
- </para>
- <para>
- Language <filename>.properties</filename> files have been updated to
escape special characters correctly and languages that contain special characters now
render as expected.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><ulink type="http"
url="https://jira.jboss.org/browse/JBEPP-192"></ulink>...
- <listitem>
- <para>
- When changing a portlet title it was possible to exploit an XSS vulnerability. A
fix has been applied to encode the content before rendering.
- </para>
- <para>
- Refer to the source commit logs in the above JIRA for specific
code changes in this fix.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><ulink type="http"
url="https://jira.jboss.org/browse/JBEPP-167"></ulink>...
- <listitem>
- <para>
- A bug in the IBM JDK (1.5) prevented &PRODUCT; from
starting correctly when using the <literal>default</literal> configuration
profile.
- </para>
- <para>
- This release includes a copy of the
<filename>jcip-annotations.jar</filename> in the
<filename>/server/default/lib</filename> directory as a workaround.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><ulink type="http"
url="https://jira.jboss.org/browse/JBEPP-448"></ulink>...
- <listitem>
- <para>
- Users and group management replication was not successful in a
clustered environment, producing the following exception:
- </para>
-<programlisting language="Java">java.io.NotSerializableException: Type
TypeModel[name=org.exoplatform.commons.utils.LazyPageList] is not serializable
- at
org.exoplatform.commons.serialization.serial.ObjectWriter.write(ObjectWriter.java:209)
- at
org.exoplatform.commons.serialization.serial.ObjectWriter.write(ObjectWriter.java:82)
- at
org.exoplatform.commons.serialization.serial.ObjectWriter.replaceObject(ObjectWriter.java:238)
-</programlisting>
- <para>
- The issue has been corrected in this release as the
relevant classes have been made serializable.
- </para>
- <para>
- Refer to the source commit logs in the above JIRA for specific
code changes in this fix.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term><ulink type="http"
url="https://jira.jboss.org/browse/JBEPP-470"></ulink>...
- <listitem>
- <para>
- Adding a WSRP portlet to a category using the application
registry was leading to the following exception:
- </para>
-<programlisting language="Java">ERROR [portal:UIPortalApplication] Error
during the processAction phase
-org.chromattic.api.UndeclaredRepositoryException: javax.jcr.RepositoryException: Illegal
path entry: "app:": Illegal path entry: "app:": Illegal path entry:
"app:"</programlisting>
- <para>
- This has been resolved with code that properly handles the
'/' character in an application name.
- </para>
- <para>
- Refer to the source commit logs in the above JIRA for specific
code changes in this fix.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
- </section>
-
- <section id="sect-Release_Notes-_Known_Issues_with_this_release_">
- <title> Known Issues with this release </title>
- <section
id="sect-Release_Notes-_Known_Issues_with_this_release_-General_Known_Issues">
- <title>General Known Issues</title>
- <para>
- A list of general issues in this release can be found at:
- </para>
- <para>
- <ulink type="http"
url="https://jira.jboss.org/secure/IssueNavigator.jspa?mode=hide&...
- </para>
- </section>
-
-<!-- <section>
- <title>Security Issues</title>
- <variablelist>
- <varlistentry>
- <term>No issues</term>
- <listitem>
- <para>
- Any security related JIRA issues that need to go in here? JIRA says no.
- </para>
- <para>
- If there aren't any JIRAs that need to be documented here, I'll remove this
section.
- </para>
- </listitem>
- </varlistentry>
- </variablelist>
- </section>-->
-
- </section>
-
- <section>
- <title>Recommended Practices</title>
-<!--DOC TODO: This Information should be in the Installtion Guide. Move for 5.1.0
release.-->
- <para>
- &PRODUCT; &VERSION; includes four pre-configured user accounts for testing
and evaluation purposes. These accounts can be used for direct access to the portal.
- </para>
- <para>
- For security reasons, before going in production, you should restrict the access to
the login servlet to POST.
- </para>
- <para>
- To do so, edit the file
<filename>$JBOSS_HOME/server/[configuration]/gatein.ear/02portal.war/WEB-INF/web.xml</filename>
and add:
- </para>
-<programlisting language="XML" role="XML"><![CDATA[
-<security-constraint>
- <web-resource-collection>
- <web-resource-name>login</web-resource-name>
- <url-pattern>/login</url-pattern>
- <http-method>GET</http-method>
- <http-method>PUT</http-method>
- <http-method>DELETE</http-method>
- <http-method>HEAD</http-method>
- <http-method>OPTIONS</http-method>
- <http-method>TRACE</http-method>
- </web-resource-collection>
- <auth-constraint/>
-</security-constraint> ]]></programlisting>
- <para>
- Doing this will render the login links provided on the front page inactive.
- </para>
-
- </section>
-
- <section>
- <title>Migration from Enterprise Portal Platform 4.3</title>
- <para>
- Enterprise Portal Platform 5 is based upon an entirely new core architecture and is
not backwards compatible with Enterprise Portal Platform 4.3.
- </para>
- <para>
- As a value added part of an enterprise subscription the JBoss Portal team is working
to develop a set of migration utilities (which may take the form of documentation, guides
and/or scripts) to assist customers in migration. We intend to release these utilities in
a future revision of JBoss Enterprise Portal Platform 5.x.
- </para>
- <para>
- For customers seeking to begin a migration prior to the availability of any Red Hat
provided migration utilities, please contact Red Hat JBoss Support for migration advice.
Red Hat JBoss support will be the main communication channel for migration knowledge as it
is developed.
- </para>
- <para>
- Red Hat JBoss Customer Support can be accessed <ulink type="http"
url="https://www.redhat.com/apps/support/">here</ulink>.
- </para>
- </section>
-
- <section id="Tech-previews">
- <title>Technology Previews</title>
- <warning>
- <title>Support</title>
- <para>
- Technology Preview features are not fully supported under Red Hat subscription
level agreements (SLAs), may not be functionally complete, and are not intended for
production use. However, these features provide early access to upcoming product
innovations, enabling customers to test functionality and provide feedback during the
development process. As Red Hat considers making future iterations of Technology Preview
features generally available, we will provide commercially reasonable efforts to resolve
any reported issues that customers experience when using these features.
- </para>
- </warning>
- <section>
- <title>Site Publisher</title>
- <para>
- &PRODUCT; 5.1 will include an optional web content authoring system add-on
called Site Publisher. A technical preview is available for download from the <ulink
type="http"
url="https://support.redhat.com/jbossnetwork/restricted/softwareDeta...
Hat Customer Support Portal</ulink>.
- </para>
- <para>
- Site Publisher provides many additional features for organizations looking to enable
line of business resources to directly manage sites, pages and content within the context
of the portal versus through integration with an external web content management system.
- </para>
- </section>
- </section>
-
- <section id="sect-Release_Notes-_Documentation_">
- <title> Documentation </title>
- <para>
- Visit <ulink type="http"
url="http://docs.redhat.com/docs/en-US/index.html">http://do...
for further documentation regarding &PRODUCT;.
- </para>
- <para>
- This documentation includes:
- </para>
- <para>
- <variablelist>
- <varlistentry>
- <term>Installation Guide</term>
- <listitem>
- <para>
- This document explains how to install and verify the installation of &PRODUCT;
using different installation methods.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>User Guide</term>
- <listitem>
- <para>
- This document provides an easy to follow guide to the functions and options
available in &PRODUCT;. It is intended to be accessible and useful to both experienced
and novice portal users.
- </para>
- </listitem>
- </varlistentry>
- <varlistentry>
- <term>Reference Guide</term>
- <listitem>
- <para>
- This is a high-level usage document. It deals with more advanced topics than the
Installation and User guides, adding new content or taking concepts discussed in the
earlier documents further. It aims to provide supporting documentation for advanced users
of &PRODUCT;. Its primary focus is on advanced use of the product and it assumes an
intermediate or advanced knowledge of the technology and terms.
- </para>
-
- </listitem>
- </varlistentry>
- </variablelist>
- </para>
- <para>
- The online documentation will be updated as necessary so be sure to check the site
regularly, especially when a new version of &PRODUCT; is released.
- </para>
- </section>
-
- <section
id="sect-Release_Notes-Product_Support_and_License_Website_Links">
- <title> Product Support and License Website Links </title>
- <formalpara>
- <title>Red Hat JBoss Customer Support</title>
- <para>
- <ulink type="http"
url="https://access.redhat.com/home
"></ulink>
- </para>
- </formalpara>
- <formalpara>
- <title>JBoss Customer Suport Portal Downloads</title>
- <para>
- <ulink type="http"
url="https://access.redhat.com/jbossnetwork/restricted/listSoftware....
- </para>
- </formalpara>
- <formalpara>
- <title>Support Processes</title>
- <para>
- <ulink
url="https://access.redhat.com/support/policy/support_process.html&q...
- </para>
- </formalpara>
- <formalpara>
- <title> Production Support Scope of Coverage </title>
- <para>
- <ulink
url="https://access.redhat.com/support/offerings/production/soc.html...
- </para>
- </formalpara>
- <formalpara>
- <title> Production Support Service Level Agreement </title>
- <para>
- <ulink
url="https://access.redhat.com/support/offerings/production/sla.html...
- </para>
- </formalpara>
- <formalpara>
- <title> Developer Support Scope of Coverage</title>
- <para>
- <ulink
url="https://access.redhat.com/support/offerings/developer/soc.html&...
- </para>
- </formalpara>
- <formalpara>
- <title> Developer Support Service Level Agreement</title>
- <para>
- <ulink
url="https://access.redhat.com/support/offerings/developer/sla.html&...
- </para>
- </formalpara>
- <formalpara>
- <title> Product Update and Support Policy</title>
- <para>
- <ulink
url="https://access.redhat.com/support/policy/updates/jboss_notes/&q...
- </para>
- </formalpara>
- <formalpara>
- <title> JBoss End User License Agreement</title>
- <para>
- <ulink
url="http://www.redhat.com/licenses/jboss_eula.html"></ul...
- </para>
- </formalpara>
- </section>
-
- <xi:include href="Revision_History.xml"
xmlns:xi="http://www.w3.org/2001/XInclude" />
-</article>
Modified: epp/docs/branches/EPP_5_0_Branch/Release_Notes/en-US/Book_Info.xml
===================================================================
--- epp/docs/branches/EPP_5_0_Branch/Release_Notes/en-US/Book_Info.xml 2010-10-12 05:16:11
UTC (rev 4627)
+++ epp/docs/branches/EPP_5_0_Branch/Release_Notes/en-US/Book_Info.xml 2010-10-12 05:40:34
UTC (rev 4628)
@@ -2,10 +2,10 @@
<!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
]>
<articleinfo id="arti-Release_Notes-Release_Notes">
- <title>5.0.1 Release Notes</title>
- <subtitle>For use with JBoss Enterprise Portal Platform 5.0.1</subtitle>
+ <title>Release Notes</title>
+ <subtitle>For use with JBoss Enterprise Portal Platform 5.0.?</subtitle>
<edition>1</edition>
- <pubsnumber>1.7</pubsnumber>
+ <pubsnumber>1.0</pubsnumber>
<productname>JBoss Enterprise Portal Platform</productname>
<productnumber>5</productnumber>
<abstract>
Added: epp/docs/branches/EPP_5_0_Branch/Release_Notes/en-US/Release_Notes.ent
===================================================================
--- epp/docs/branches/EPP_5_0_Branch/Release_Notes/en-US/Release_Notes.ent
(rev 0)
+++ epp/docs/branches/EPP_5_0_Branch/Release_Notes/en-US/Release_Notes.ent 2010-10-12
05:40:34 UTC (rev 4628)
@@ -0,0 +1,4 @@
+<!ENTITY HOLDER "Red Hat, Inc">
+<!ENTITY YEAR "2010">
+<!ENTITY PRODUCT "JBoss Enterprise Portal Platform">
+<!ENTITY VERSION "5.0.1">
Added: epp/docs/branches/EPP_5_0_Branch/Release_Notes/en-US/Release_Notes.xml
===================================================================
--- epp/docs/branches/EPP_5_0_Branch/Release_Notes/en-US/Release_Notes.xml
(rev 0)
+++ epp/docs/branches/EPP_5_0_Branch/Release_Notes/en-US/Release_Notes.xml 2010-10-12
05:40:34 UTC (rev 4628)
@@ -0,0 +1,558 @@
+<?xml version='1.0' encoding='utf-8' ?>
+<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
"http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
+]>
+<article id="JBEPP_5_0_Release_Notes">
+ <xi:include href="Book_Info.xml"
xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <section id="sect-Release_Notes-Introduction">
+ <title>Introduction</title>
+ <para>
+ &PRODUCT; offers an intuitive, easy to manage user interface and a proven core
infrastructure to enable organizations to quickly build dynamic web sites in a highly
reusable way. By bringing the principals of Open Choice to the presentation layer,
&PRODUCT; &VERSION; maximizes existing skills and technology investments.
+ </para>
+ <para>
+ By integrating proven open source frameworks such as JBoss Seam, Hibernate, Tomcat and
JBoss Cache &PRODUCT; takes advantage of innovations in the open source community. As
well, &PRODUCT; version &VERSION; is fully tested and supported by Red Hat, and is
certified to work on many leading enterprise hardware and software products.
+ </para>
+ </section>
+
+<!-- <section>
+ <title>New Features</title>
+ <variablelist>
+
+ </variablelist>
+ </section> -->
+
+ <section id="sect-Release_Notes-Architecture_of_PRODUCT_VERSION">
+ <title>Component Versions</title>
+ <para>
+ This section details the versions of the components which create the JBoss Enterprise
Portal Platform 5.0.1.
+ </para>
+ <table>
+ <title>JBoss Enterprise Portal Platform Component Versions</title>
+ <tgroup cols="2">
+ <thead>
+ <row>
+ <entry>
+ Component
+ </entry>
+ <entry>
+ Version
+ </entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>
+ JBoss Enterprise Application Platform
+ </entry>
+ <entry>
+ 5.0.1-GA
+ </entry>
+ </row>
+ <row>
+ <entry>
+ JBoss Cache
+ </entry>
+ <entry>
+ 3.2.4
+ </entry>
+ </row>
+ <row>
+ <entry>
+ GateIn Common
+ </entry>
+ <entry>
+ 2.0.2-GA
+ </entry>
+ </row>
+ <row>
+ <entry>
+ GateIn WCI
+ </entry>
+ <entry>
+ 2.0.1-GA
+ </entry>
+ </row>
+ <row>
+ <entry>
+ GateIn PC
+ </entry>
+ <entry>
+ 2.1.1-GA
+ </entry>
+ </row>
+ <row>
+ <entry>
+ GateIn WSRP
+ </entry>
+ <entry>
+ 1.1.1-GA
+ </entry>
+ </row>
+ <row>
+ <entry>
+ GateIn MOP
+ </entry>
+ <entry>
+ 1.0.2-GA
+ </entry>
+ </row>
+ <row>
+ <entry>
+ GateIn SSO
+ </entry>
+ <entry>
+ 1.0.0-epp
+ </entry>
+ </row>
+ <row>
+ <entry>
+ PicketLink IDM
+ </entry>
+ <entry>
+ 1.1.5.GA
+ </entry>
+ </row>
+ <row>
+ <entry>
+ eXo JCR
+ </entry>
+ <entry>
+ 1.12.3-GA
+ </entry>
+ </row>
+ <row>
+ <entry>
+ eXo Kernel
+ </entry>
+ <entry>
+ 2.2.3-GA
+ </entry>
+ </row>
+ <row>
+ <entry>
+ Portlet Bridge
+ </entry>
+ <entry>
+ 2.0.0
+ </entry>
+ </row>
+ <row>
+ <entry>
+ Chromattic
+ </entry>
+ <entry>
+ 1.0.1
+ </entry>
+ </row>
+ <row>
+ <entry>
+ Apache Shindig
+ </entry>
+ <entry>
+ 1.0-r790473-Patch03
+ </entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </section>
+
+ <section id="sect-Release_Notes-Certified_Environments">
+ <title>Installation</title>
+ <para>
+ The JBoss Enterprise Portal Platform Installation Guide contains details of software
and hardware requirements as well as detailed installation instructions.
+ </para>
+ <para>
+ The Installation Guide can be found online at <ulink type="http"
url="http://docs.redhat.com/docs/">http://docs.redhat.com/do...;.
+ </para>
+ </section>
+
+ <section id="Issues-fixed-in-this-release">
+ <title>
+ Issues fixed in this release
+ </title>
+<!-- Commented out for current release. Retaining the text to be reused in future
release drafts.
+ <warning>
+ <title>Draft</title>
+ <para>
+ These entries are drafts. They have been drawn from comments and associated JIRAs from
the list at:
+ <ulink type="http"
url="https://jira.jboss.org/secure/IssueNavigator.jspa?mode=hide&...;.
+ </para>
+ <para>
+ <emphasis role="bold">They are likely not technically correct at the
moment</emphasis>, but they will serve as a basis and will be corrected in
subsequent iterations after technical and QE reviews.
+ </para>
+ </warning> -->
+ <para>
+ Following is a list of issues fixed in this release:
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term><ulink type="http"
url="https://jira.jboss.org/browse/JBEPP-452"></ulink>...
+ <listitem>
+ <para>
+ &PRODUCT;'s <literal>request.getLocale()</literal> was only
reflecting a user's browser language preference, regardless of what language was set
in the portal itself.
+ </para>
+ <para>
+ A fix was installed to address this issue and return values that are aligned with
the rest of the portal.
+ </para>
+ <para>
+ As a result, portlets use the preferred locale of the portal user and not the
locale from the http servlet request.
+ </para>
+ <para>
+ Refer to the source commit logs in the above JIRA for specific code
changes in this fix.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><ulink type="http"
url="https://jira.jboss.org/browse/JBEPP-403"></ulink>...
+ <listitem>
+ <para>
+ The language fix implemented for <ulink type="http"
url="https://jira.jboss.org/browse/JBEPP-452"></ulink> also corrected
an issue wherein a failed login attempt would present the login form in an incorrect
language (that is; not the language set for the portal).
+ </para>
+ <para>
+ Refer to the source commit logs in the above JIRA for specific
code changes in this fix.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><ulink type="http"
url="https://jira.jboss.org/browse/JBEPP-383"></ulink>...
+ <listitem>
+ <para>
+ The language fix also corrected an issue which caused language settings for
languages with country variants (such as Chinese - China and Chinese - Taiwan) were not
stored between logins.
+ </para>
+ <para>
+ Refer to the source commit logs in the above JIRA for specific
code changes in this fix.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><ulink type="http"
url="https://jira.jboss.org/browse/JBEPP-393"></ulink>...
+ <listitem>
+ <para>
+ The Shindig Gadget Server was reporting malformed security tokens after a gadget
was added to a portal. The error was originating from the
<literal>org.apache.shindig.gadgets.servlet.RpcServlet</literal>'s
<literal>doPost</literal> processing method. This method of reading POST
requests from the servlet's input stream was being corrupted if the
<literal>InputStream</literal> had already been read (in the recorded case, by
<literal>RequestDumperValve</literal>).
+ </para>
+ <para>
+ This error was resolved with a patch to Apache Shindig which allows a reset of
the input stream before the <literal>doPost</literal> method is invoked.
+ </para>
+ <para>
+ Refer to the source commit logs in the above JIRA for specific
code changes in this fix.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><ulink type="http"
url="https://jira.jboss.org/browse/JBEPP-390"></ulink>...
+ <listitem>
+ <para>
+ A bug in PicketLink IDM meant that changing the LDAP group membership type of a
user to anything other than 'member' would appear to delete that user from the
group. This was caused by the PicketLink IDM UI not showing any memberships other than
'member', even if other types were correctly retained in the underlying database.
+ </para>
+ <para>
+ This issue has been fixed with an updated PicketLink jar.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><ulink type="http"
url="https://jira.jboss.org/browse/JBEPP-363"></ulink>...
+ <listitem>
+ <para>
+ The updated PicketLink jar has also resolved an issue encountered when deleting
registered portal users from LDAP.
+ </para>
+ <para>
+ Information about users deleted from LDAP would still be retained in the
database and those user accounts would appear in the portal user list. If one of these
legacy accounts was then edited, the inconsistences would prevent any further login
attempts from succeeding until the user session was cleared.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><ulink type="http"
url="https://jira.jboss.org/browse/JBEPP-477"></ulink>...
+ <listitem>
+ <para>
+ The updated PicketLink IDM component removes case-sensitivity from the username
field of the portal login page.
+ </para>
+ <para>
+ This allows users whose login names contain capital letters to authenticate
successfully, regardless of the case used in the username field of the login form.
+ </para>
+ <para>
+ Note that the password field remains case-sensitive for security.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><ulink type="http"
url="https://jira.jboss.org/browse/JBEPP-368"></ulink>...
+ <listitem>
+ <para>
+ The datasource defined in
<filename>jboss-epp-5.0/jboss-as/docs/examples/portal/gatein-sample-portal-ds.xml</filename>
has been updated from <literal>local-tx-datasource</literal> to
<literal>no-tx-datasource</literal>.
+ </para>
+ <para>
+ This update prevents exceptions being thrown by the JCR when the name of the
datasource in <filename>server/default/deploy/gatein-ds.xml</filename> is
changed to suit operational requirements.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><ulink type="http"
url="https://jira.jboss.org/browse/JBEPP-342"></ulink>...
+ <listitem>
+ <para>
+ Node names were being displayed incorrectly if they contained accentuated
characters. For example; if the site language was German, the SiteMap node would display
as <literal>Seiten&uuml;bersicht</literal> instead of
<emphasis role="bold">Seitenübersicht</emphasis>.
+ </para>
+ <para>
+ Language <filename>.properties</filename> files have been updated to
escape special characters correctly and languages that contain special characters now
render as expected.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><ulink type="http"
url="https://jira.jboss.org/browse/JBEPP-192"></ulink>...
+ <listitem>
+ <para>
+ When changing a portlet title it was possible to exploit an XSS vulnerability. A
fix has been applied to encode the content before rendering.
+ </para>
+ <para>
+ Refer to the source commit logs in the above JIRA for specific
code changes in this fix.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><ulink type="http"
url="https://jira.jboss.org/browse/JBEPP-167"></ulink>...
+ <listitem>
+ <para>
+ A bug in the IBM JDK (1.5) prevented &PRODUCT; from
starting correctly when using the <literal>default</literal> configuration
profile.
+ </para>
+ <para>
+ This release includes a copy of the
<filename>jcip-annotations.jar</filename> in the
<filename>/server/default/lib</filename> directory as a workaround.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><ulink type="http"
url="https://jira.jboss.org/browse/JBEPP-448"></ulink>...
+ <listitem>
+ <para>
+ Users and group management replication was not successful in a
clustered environment, producing the following exception:
+ </para>
+<programlisting language="Java">java.io.NotSerializableException: Type
TypeModel[name=org.exoplatform.commons.utils.LazyPageList] is not serializable
+ at
org.exoplatform.commons.serialization.serial.ObjectWriter.write(ObjectWriter.java:209)
+ at
org.exoplatform.commons.serialization.serial.ObjectWriter.write(ObjectWriter.java:82)
+ at
org.exoplatform.commons.serialization.serial.ObjectWriter.replaceObject(ObjectWriter.java:238)
+</programlisting>
+ <para>
+ The issue has been corrected in this release as the
relevant classes have been made serializable.
+ </para>
+ <para>
+ Refer to the source commit logs in the above JIRA for specific
code changes in this fix.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term><ulink type="http"
url="https://jira.jboss.org/browse/JBEPP-470"></ulink>...
+ <listitem>
+ <para>
+ Adding a WSRP portlet to a category using the application
registry was leading to the following exception:
+ </para>
+<programlisting language="Java">ERROR [portal:UIPortalApplication] Error
during the processAction phase
+org.chromattic.api.UndeclaredRepositoryException: javax.jcr.RepositoryException: Illegal
path entry: "app:": Illegal path entry: "app:": Illegal path entry:
"app:"</programlisting>
+ <para>
+ This has been resolved with code that properly handles the
'/' character in an application name.
+ </para>
+ <para>
+ Refer to the source commit logs in the above JIRA for specific
code changes in this fix.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </section>
+
+ <section id="sect-Release_Notes-_Known_Issues_with_this_release_">
+ <title> Known Issues with this release </title>
+ <section
id="sect-Release_Notes-_Known_Issues_with_this_release_-General_Known_Issues">
+ <title>General Known Issues</title>
+ <para>
+ A list of general issues in this release can be found at:
+ </para>
+ <para>
+ <ulink type="http"
url="https://jira.jboss.org/secure/IssueNavigator.jspa?mode=hide&...
+ </para>
+ </section>
+
+<!-- <section>
+ <title>Security Issues</title>
+ <variablelist>
+ <varlistentry>
+ <term>No issues</term>
+ <listitem>
+ <para>
+ Any security related JIRA issues that need to go in here? JIRA says no.
+ </para>
+ <para>
+ If there aren't any JIRAs that need to be documented here, I'll remove this
section.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </section>-->
+
+ </section>
+
+ <section>
+ <title>Recommended Practices</title>
+<!--DOC TODO: This Information should be in the Installtion Guide. Move for 5.1.0
release.-->
+ <para>
+ &PRODUCT; &VERSION; includes four pre-configured user accounts for testing
and evaluation purposes. These accounts can be used for direct access to the portal.
+ </para>
+ <para>
+ For security reasons, before going in production, you should restrict the access to
the login servlet to POST.
+ </para>
+ <para>
+ To do so, edit the file
<filename>$JBOSS_HOME/server/[configuration]/gatein.ear/02portal.war/WEB-INF/web.xml</filename>
and add:
+ </para>
+<programlisting language="XML" role="XML"><![CDATA[
+<security-constraint>
+ <web-resource-collection>
+ <web-resource-name>login</web-resource-name>
+ <url-pattern>/login</url-pattern>
+ <http-method>GET</http-method>
+ <http-method>PUT</http-method>
+ <http-method>DELETE</http-method>
+ <http-method>HEAD</http-method>
+ <http-method>OPTIONS</http-method>
+ <http-method>TRACE</http-method>
+ </web-resource-collection>
+ <auth-constraint/>
+</security-constraint> ]]></programlisting>
+ <para>
+ Doing this will render the login links provided on the front page inactive.
+ </para>
+
+ </section>
+
+ <section>
+ <title>Migration from Enterprise Portal Platform 4.3</title>
+ <para>
+ Enterprise Portal Platform 5 is based upon an entirely new core architecture and is
not backwards compatible with Enterprise Portal Platform 4.3.
+ </para>
+ <para>
+ As a value added part of an enterprise subscription the JBoss Portal team is working
to develop a set of migration utilities (which may take the form of documentation, guides
and/or scripts) to assist customers in migration. We intend to release these utilities in
a future revision of JBoss Enterprise Portal Platform 5.x.
+ </para>
+ <para>
+ For customers seeking to begin a migration prior to the availability of any Red Hat
provided migration utilities, please contact Red Hat JBoss Support for migration advice.
Red Hat JBoss support will be the main communication channel for migration knowledge as it
is developed.
+ </para>
+ <para>
+ Red Hat JBoss Customer Support can be accessed <ulink type="http"
url="https://www.redhat.com/apps/support/">here</ulink>.
+ </para>
+ </section>
+
+ <section id="Tech-previews">
+ <title>Technology Previews</title>
+ <warning>
+ <title>Support</title>
+ <para>
+ Technology Preview features are not fully supported under Red Hat subscription
level agreements (SLAs), may not be functionally complete, and are not intended for
production use. However, these features provide early access to upcoming product
innovations, enabling customers to test functionality and provide feedback during the
development process. As Red Hat considers making future iterations of Technology Preview
features generally available, we will provide commercially reasonable efforts to resolve
any reported issues that customers experience when using these features.
+ </para>
+ </warning>
+ <section>
+ <title>Site Publisher</title>
+ <para>
+ &PRODUCT; 5.1 will include an optional web content authoring system add-on
called Site Publisher. A technical preview is available for download from the <ulink
type="http"
url="https://support.redhat.com/jbossnetwork/restricted/softwareDeta...
Hat Customer Support Portal</ulink>.
+ </para>
+ <para>
+ Site Publisher provides many additional features for organizations looking to enable
line of business resources to directly manage sites, pages and content within the context
of the portal versus through integration with an external web content management system.
+ </para>
+ </section>
+ </section>
+
+ <section id="sect-Release_Notes-_Documentation_">
+ <title> Documentation </title>
+ <para>
+ Visit <ulink type="http"
url="http://docs.redhat.com/docs/en-US/index.html">http://do...
for further documentation regarding &PRODUCT;.
+ </para>
+ <para>
+ This documentation includes:
+ </para>
+ <para>
+ <variablelist>
+ <varlistentry>
+ <term>Installation Guide</term>
+ <listitem>
+ <para>
+ This document explains how to install and verify the installation of &PRODUCT;
using different installation methods.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>User Guide</term>
+ <listitem>
+ <para>
+ This document provides an easy to follow guide to the functions and options
available in &PRODUCT;. It is intended to be accessible and useful to both experienced
and novice portal users.
+ </para>
+ </listitem>
+ </varlistentry>
+ <varlistentry>
+ <term>Reference Guide</term>
+ <listitem>
+ <para>
+ This is a high-level usage document. It deals with more advanced topics than the
Installation and User guides, adding new content or taking concepts discussed in the
earlier documents further. It aims to provide supporting documentation for advanced users
of &PRODUCT;. Its primary focus is on advanced use of the product and it assumes an
intermediate or advanced knowledge of the technology and terms.
+ </para>
+
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </para>
+ <para>
+ The online documentation will be updated as necessary so be sure to check the site
regularly, especially when a new version of &PRODUCT; is released.
+ </para>
+ </section>
+
+ <section
id="sect-Release_Notes-Product_Support_and_License_Website_Links">
+ <title> Product Support and License Website Links </title>
+ <formalpara>
+ <title>Red Hat JBoss Customer Support</title>
+ <para>
+ <ulink type="http"
url="https://access.redhat.com/home
"></ulink>
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>JBoss Customer Suport Portal Downloads</title>
+ <para>
+ <ulink type="http"
url="https://access.redhat.com/jbossnetwork/restricted/listSoftware....
+ </para>
+ </formalpara>
+ <formalpara>
+ <title>Support Processes</title>
+ <para>
+ <ulink
url="https://access.redhat.com/support/policy/support_process.html&q...
+ </para>
+ </formalpara>
+ <formalpara>
+ <title> Production Support Scope of Coverage </title>
+ <para>
+ <ulink
url="https://access.redhat.com/support/offerings/production/soc.html...
+ </para>
+ </formalpara>
+ <formalpara>
+ <title> Production Support Service Level Agreement </title>
+ <para>
+ <ulink
url="https://access.redhat.com/support/offerings/production/sla.html...
+ </para>
+ </formalpara>
+ <formalpara>
+ <title> Developer Support Scope of Coverage</title>
+ <para>
+ <ulink
url="https://access.redhat.com/support/offerings/developer/soc.html&...
+ </para>
+ </formalpara>
+ <formalpara>
+ <title> Developer Support Service Level Agreement</title>
+ <para>
+ <ulink
url="https://access.redhat.com/support/offerings/developer/sla.html&...
+ </para>
+ </formalpara>
+ <formalpara>
+ <title> Product Update and Support Policy</title>
+ <para>
+ <ulink
url="https://access.redhat.com/support/policy/updates/jboss_notes/&q...
+ </para>
+ </formalpara>
+ <formalpara>
+ <title> JBoss End User License Agreement</title>
+ <para>
+ <ulink
url="http://www.redhat.com/licenses/jboss_eula.html"></ul...
+ </para>
+ </formalpara>
+ </section>
+
+ <xi:include href="Revision_History.xml"
xmlns:xi="http://www.w3.org/2001/XInclude" />
+</article>
Modified: epp/docs/branches/EPP_5_0_Branch/Release_Notes/en-US/Revision_History.xml
===================================================================
--- epp/docs/branches/EPP_5_0_Branch/Release_Notes/en-US/Revision_History.xml 2010-10-12
05:16:11 UTC (rev 4627)
+++ epp/docs/branches/EPP_5_0_Branch/Release_Notes/en-US/Revision_History.xml 2010-10-12
05:40:34 UTC (rev 4628)
@@ -6,104 +6,6 @@
<simpara>
<revhistory>
<revision>
- <revnumber>1-1.7</revnumber>
- <date>Mon Oct 11 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Edit Product version number for publishing
restructure.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-1.6</revnumber>
- <date>Thu Sep 30 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Edit Product version number for publishing
restructure.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-1.5</revnumber>
- <date>Tues Sep 28 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Fix typo and increment for new build.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-1.4</revnumber>
- <date>Thu Sep 23 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Minor editorial changes.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-1.3</revnumber>
- <date>Wed Sep 22 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Refined JIRA descriptions and added new JIRA links.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-1.2</revnumber>
- <date>Mon Sep 20 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Refined JIRA descriptions and added new JIRA links.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
- <revnumber>1-1.1</revnumber>
- <date>Mon Sep 06 2010</date>
- <author>
- <firstname>Scott</firstname>
- <surname>Mumford</surname>
- <email>smumford(a)redhat.com</email>
- </author>
- <revdescription>
- <simplelist>
- <member>Updated help URLs and fixed incorrect JIRA link.</member>
- </simplelist>
- </revdescription>
- </revision>
- <revision>
<revnumber>1-1.0</revnumber>
<date>Fri Sep 03 2010</date>
<author>
@@ -123,7 +25,7 @@
</author> -->
<revdescription>
<simplelist>
- <member>Release Notes created for Enterprise Portal Platform 5.0.1
release.</member>
+ <member>Release Notes created for Enterprise Portal Platform 5.0.?
release.</member>
</simplelist>
</revdescription>
</revision>