From do-not-reply at jboss.org Wed Jun 1 01:31:35 2011
Content-Type: multipart/mixed; boundary="===============1004142927894867315=="
MIME-Version: 1.0
From: do-not-reply at jboss.org
To: gatein-commits at lists.jboss.org
Subject: [gatein-commits] gatein SVN: r6582 -
epp/docs/branches/5.1/Release_Notes/en-US.
Date: Wed, 01 Jun 2011 01:31:35 -0400
Message-ID: <201106010531.p515VZd9026239@svn01.web.mwc.hst.phx2.redhat.com>
--===============1004142927894867315==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Author: smumford
Date: 2011-06-01 01:31:35 -0400 (Wed, 01 Jun 2011)
New Revision: 6582
Modified:
epp/docs/branches/5.1/Release_Notes/en-US/5.1.1_Release_Notes.ent
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
Log:
Updated for 5.1.1 Release
Modified: epp/docs/branches/5.1/Release_Notes/en-US/5.1.1_Release_Notes.ent
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- epp/docs/branches/5.1/Release_Notes/en-US/5.1.1_Release_Notes.ent 2011-=
05-31 15:12:57 UTC (rev 6581)
+++ epp/docs/branches/5.1/Release_Notes/en-US/5.1.1_Release_Notes.ent 2011-=
06-01 05:31:35 UTC (rev 6582)
@@ -7,3 +7,8 @@
+
+
+
+
+
\ No newline at end of file
Modified: epp/docs/branches/5.1/Release_Notes/en-US/5.1.1_Release_Notes.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- epp/docs/branches/5.1/Release_Notes/en-US/5.1.1_Release_Notes.xml 2011-=
05-31 15:12:57 UTC (rev 6581)
+++ epp/docs/branches/5.1/Release_Notes/en-US/5.1.1_Release_Notes.xml 2011-=
06-01 05:31:35 UTC (rev 6582)
@@ -369,7 +369,7 @@
Known Issues
- There are no known issues in this release of JBoss Enterprise Portal Pl=
atform
+ There are no known issues in this release of JBoss Enterprise Portal Pl=
atform.
=
-
+
+ Plain Text Passwords
+
+
+ JBoss Enterprise Portal Platform administrators shoul=
d be aware that passwords saved by users who chose the Remember M=
e option when logging in are stored in the underlying JCR in pla=
in text. This creates a possible security risk as user passwords could be o=
btained with an SQL query.
+
+
+ While this is the default behavior of JBoss Enterp=
rise Portal Platform, administrators can negate this risk by either disabli=
ng the Remember Me option or encrypting the passwords =
stored in the JCR. =
+
+
+ Instructions for implementing both of these soluti=
ons are included in section 14.1 of the JBoss Enterprise Portal Platform Re=
ference Guide which is available at .
+
+
+
+
+
+ =
+
- =
+ =
Migration
@@ -399,9 +420,7 @@
=
- Site Publisher
-
- DOCS NOTE: Do we still want this here?
+ Site Publisher
Site Publisher provides many additional features for organizations look=
ing to enable line of business resources to directly manage sites, pages an=
d content within the context of the portal versus through integration with =
an external web content management system.
Modified: epp/docs/branches/5.1/Release_Notes/en-US/Book_Info.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- epp/docs/branches/5.1/Release_Notes/en-US/Book_Info.xml 2011-05-31 15:1=
2:57 UTC (rev 6581)
+++ epp/docs/branches/5.1/Release_Notes/en-US/Book_Info.xml 2011-06-01 05:3=
1:35 UTC (rev 6582)
@@ -6,10 +6,10 @@
5.1.1 Release Notes
For use with JBoss Enterprise Portal Platform 5.1.1
- 1
- 1.1
JBoss Enterprise Portal Platform
5.1
+ 1
+ 1.2
These release notes contain important information related to JBoss Ente=
rprise Portal Platform 5.1.1 that may not be currently available in the Pro=
duct 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
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- epp/docs/branches/5.1/Release_Notes/en-US/Revision_History.xml 2011-05-=
31 15:12:57 UTC (rev 6581)
+++ epp/docs/branches/5.1/Release_Notes/en-US/Revision_History.xml 2011-06-=
01 05:31:35 UTC (rev 6582)
@@ -8,6 +8,20 @@
+ 1-1.2
+ Mon May 23 2011
+
+ Scott
+ Mumford
+ smumford(a)redhat.com
+
+
+
+ Added "Recommended Practices" section.
+
+
+
+
1-1.1
Wed May 4 2011
Modified: epp/docs/branches/5.1/Release_Notes/en-US/resolved_issues.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- epp/docs/branches/5.1/Release_Notes/en-US/resolved_issues.xml 2011-05-3=
1 15:12:57 UTC (rev 6581)
+++ epp/docs/branches/5.1/Release_Notes/en-US/resolved_issues.xml 2011-06-0=
1 05:31:35 UTC (rev 6582)
@@ -1,159 +1,139 @@
-
+
-%BOOK_ENTITIES;
]>
-
-
-
-
-
- Warning messages were found in the server log when starting JBoss Ente=
rprise Portal Platform 5 without an active internet connection. This was be=
cause the Java EE Webservices Metadata Handler 2.0 schema was requested via=
the network at start up. The schema is now bundled with the WSRP which all=
ows JBoss Enterprise Portal Platform to start without producing error messa=
ges if there is no internet connection.
-
+
=
-
=
-
-
-
-
-
- A thread safety issue in the breadcrumb portlet could lead to NullPoin=
terException under load.The issue has been fixed.
-
+
+ =
+
+
+
+
+
+ Warning messages were found in the server log when starting JBoss=
Enterprise Portal Platform 5 without an active internet connection. This w=
as because the Java EE Webservices Metadata Handler 2.0 schema was requeste=
d via the network at start up. The schema is now bundled with the WSRP whic=
h allows JBoss Enterprise Portal Platform to start without producing error =
messages if there is no internet connection.
+
+
+
=
-
+
+
+
+
+
+ A thread safety issue in the breadcrumb portlet could lead to Nul=
lPointerException under load. The issue has been fixed. =
+
+
+
=
-
-
-
-
-
- The name of a dashboard page entered by user was not properly encoded =
before being returned on the web browser. This allowed javascript snippets =
to be executed when creating a new page through the Portal Dashboard. The n=
ame of the page is now properly HTML encoded before being returned and java=
script is no longer invoked when entered into page fields.
-
+
+
+
+
+
+ The name of a dashboard page entered by user was not properly enc=
oded before being returned on the web browser. This allowed javascript snip=
pets to be executed when creating a new page through the Portal Dashboard. =
The name of the page is now properly HTML encoded before being returned and=
javascript is no longer invoked when entered into page fields.
+
+
+
=
-
+
+
+
+
+
+ A bug cause the JBoss Enterprise Portal Platform upload service t=
o not work properly with Internet Explorer 7. As a result, any application =
using the upload service (such as Site Publisher) would not behave correctl=
y with this web browser unless a name was provided. The bug has been fixed =
and the upload service now works as expected in all browsers (including IE7=
).
+
+
+
=
-
-
-
-
-
- Previous versions of JBoss Enterprise Portal Platform wrote saved pass=
words to the JCR database in plain text. This created a possible security r=
isk as user passwords could be obtained with an SQL query. Passwords are no=
w encrypted when written to the database, negating the security risk.
-
+
+
+
+
+
+ A bug prevented the 'Preferences' tab from appearing in some port=
lets. The tab would only appear in portlets that were customized during the=
first deployment through the portal.xml descriptor. Non-customized portlet=
s would not show a 'Preferences' tab. The UIFormInputSet.java and UIPortlet=
Form.java files have been patched to fix the issue and now the tab now appe=
ars in all portlets that have configurable preferences.
+
+
+
=
-
+
+
+
+
+
+ The two JBoss Cache instances created by PicketLink were calling =
on the same configuration file in idm-configuration.xml and, as a result, w=
ere using the same cluster names. This could lead to conflicts as the same =
JBoss Cache instance could join the same channel twice. Separate configurat=
ion files were added to the distribution package and the Portal configurati=
on was customized to call on the different files. JBoss Cache instances can=
now run simultaneously without conflict.
+
+
+
=
-
-
-
-
-
- A bug cause the JBoss Enterprise Portal Platform upload service to not=
work properly with Internet Explorer 7. As a result, any application using=
the upload service (such as Site Publisher) would not behave correctly wit=
h this web browser unless a name was provided. The bug has been fixed and t=
he upload service now works as expected in all browsers (including IE7).
-
+
+
+
+
+
+ When adding resources (js, css, etc) to the Head of the HTML resp=
onse with the doHeaders method a bug was encountered which caused those res=
ources to be added twice. A patch has been applied to fix the bug and new r=
esources are now only linked once.
+
+
+
=
-
+
+
+
+
+
+ A bug in data caching prevented some changes to Portal navigation=
from reloading in real time. When changing a group navigation priority, th=
e reordering of the groups was only happening after a log-out. The UIPageNa=
vigationForm.java has been patched to correct this and navigation changes n=
ow update immediately, without the user needing to log-out. =
+
+
+
=
-
-
-
-
-
- A bug prevented the 'Preferences' tab from appearing in some portlets.=
The tab would only appear in portlets that were customized during the firs=
t deployment through the portal.xml descriptor. Non-customized portlets wou=
ld 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 i=
n all portlets that have configurable preferences.
-
+
+
+
+
+
+ WSRP Strict mode was previously set only via listeners, which wer=
e not triggered at startup since they don't yet exist at that time. This me=
ant that WSRP Strict Mode was not properly restored when JBoss Enterprise P=
ortal 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 sta=
rtup.
+
+
+
=
-
+
+
+
+
+
+ Exceptions thrown by the handleFaceletNotFound method (when a fac=
elet file was not found) were being obscured by FaceletViewHandler as the r=
esponse object was not a subtype of HttpServletResponse (it is a instance o=
f PortletResponse). FaceletPortletViewHandler.java has been updated to hand=
le instances of both HttpServletResponse and PortletResponse response objec=
ts.
+
+
+
=
-
-
-
-
-
- The two JBoss Cache instances created by PicketLink were calling on th=
e same configuration file in idm-configuration.xml and, as a result, were u=
sing the same cluster names. This could lead to conflicts as the same JBoss=
Cache instance could join the same channel twice. Separate configuration f=
iles were added to the distribution package and the Portal configuration wa=
s customized to call on the different files. JBoss Cache instances can now =
run simultaneously without conflict.
-
+
+
+
+
+
+ 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 w=
as enabled) the values could be garbled on output. An upgrade of the SSO co=
mponent to version 1.0.2-epp-GA (which includes a patch to the AbstractLogo=
utFilter code) resolves this issue and Non-UTF-8 characters are now specifi=
ed correctly.
+
+
+
=
-
+
+
+
+
+
+ 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 desc=
riptors. The transaction has now been split so that not all page definition=
s are held in memory prior to being written and the Out Of Memory error is =
no longer encountered.
+
+
+
=
-
-
-
-
-
- When adding resources (js, css, etc) to the Head of the HTML response =
with the doHeaders method a bug was encountered which caused those resource=
s to be added twice. A patch has been applied to fix the bug and new resour=
ces are now only linked once.
-
+
+
+
+
+
+ JBoss Enterprise Portal Platform doesn't set content-type on css-=
files added via gatein-resources.xml. This causes Internet Explorer 9 to ig=
nore these css-files due to new security policy (a console message states: =
SEC7113: CSS was ignored due to mime type mismatch). The ResourceRequestFil=
ter.java file has been modified to set the content type so that content-typ=
es will be set and Internet Explorer 9 will render the Portal as expected.
+
+
+
=
-
-
-
-
-
-
-
- A bug in data caching prevented some changes to Portal navigation from=
reloading in real time. When changing a group navigation priority, the reo=
rdering of the groups was only happening after a log-out. The UIPageNavigat=
ionForm.java has been patched to correct this and navigation changes now up=
date immediately, without the user needing to log-out.
-
-
-
-
-
-
-
-
-
- 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 t=
hat 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.
-
-
-
-
-
-
-
-
-
- Exceptions thrown by the handleFaceletNotFound method (when a facelet =
file was not found) were being obscured by FaceletViewHandler as the respon=
se object was not a subtype of HttpServletResponse (it is a instance of Por=
tletResponse). FaceletPortletViewHandler.java has been updated to handle in=
stances of both HttpServletResponse and PortletResponse response objects.
-
-
-
-
-
-
-
-
-
- The Single Sign On (SSO) AbstractLogoutFilter in JBoss Enterprise Port=
al Platform would read request parameters before setting the character enco=
ding. When a form was submitted with non-UTF-8 characters (while SSO was en=
abled) the values could be garbled on output. An upgrade of the SSO compone=
nt to version 1.0.2-epp-GA (which includes a patch to the AbstractLogoutFil=
ter code) resolves this issue and Non-UTF-8 characters are now specified co=
rrectly.
-
-
-
-
-
-
-
-
-
- MOPPortalStructuralAccess was improperly closing the POMSession that w=
as under control of another Portal component, leaving that component unable=
to properly access JCR state. An NPE was thrown when other components trie=
d to access the closed POMSession. MOPPortalStructureAccess now simply save=
s the session instead of saving *and* closing it. Since MOPPortalStructural=
Access doesn't close the POMSession anymore, it can still be used by compon=
ents upstream without issue.
-
-
-
-
-
-
-
-
-
- In previous Portal versions, page definitions were held in system memo=
ry before being written when starting the Portal. This could cause an Out O=
f Memory error if a large number of pages were defined in the XML descripto=
rs. 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 lo=
nger encountered.
-
-
-
-
-
-
-
-
-
- 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: SEC71=
13: CSS was ignored due to mime type mismatch). The ResourceRequestFilter.j=
ava file has been modified to set the content type so that content-types wi=
ll be set and Internet Explorer 9 will render the Portal as expected.
-
-
-
-
-
-
-
--===============1004142927894867315==--