Author: jaredmorgs Date: 2012-01-24 17:41:45 -0500 (Tue, 24 Jan 2012) New Revision: 14039 Modified: docs/enterprise/trunk/Installation_Guide/en-US/Book_Info.xml docs/enterprise/trunk/Installation_Guide/en-US/Revision_History.xml docs/enterprise/trunk/PortletBridge/en-US/Book_Info.xml docs/enterprise/trunk/PortletBridge/en-US/Revision_History.xml docs/enterprise/trunk/Reference_Guide/en-US/Book_Info.xml docs/enterprise/trunk/Reference_Guide/en-US/Revision_History.xml docs/enterprise/trunk/Release_Notes/en-US/Book_Info.xml docs/enterprise/trunk/Release_Notes/en-US/CP07_Release_Notes.xml docs/enterprise/trunk/Release_Notes/en-US/Revision_History.xml docs/enterprise/trunk/Release_Notes/en-US/feature_requests.old docs/enterprise/trunk/Release_Notes/en-US/feature_requests.xml docs/enterprise/trunk/Release_Notes/en-US/known_issues.old docs/enterprise/trunk/Release_Notes/en-US/known_issues.xml docs/enterprise/trunk/Release_Notes/en-US/resolved_issues.old docs/enterprise/trunk/Release_Notes/en-US/resolved_issues.xml docs/enterprise/trunk/Release_Notes_Old/en-US/CP07_Release_Notes.xml docs/enterprise/trunk/Tuning_Guide/en-US/Book_Info.xml docs/enterprise/trunk/Tuning_Guide/en-US/Revision_History.xml docs/enterprise/trunk/User_Guide/en-US/Book_Info.xml docs/enterprise/trunk/User_Guide/en-US/Revision_History.xml Log: Eff it, lets release Modified: docs/enterprise/trunk/Installation_Guide/en-US/Book_Info.xml =================================================================== --- docs/enterprise/trunk/Installation_Guide/en-US/Book_Info.xml 2012-01-24 21:21:57 UTC (rev 14038) +++ docs/enterprise/trunk/Installation_Guide/en-US/Book_Info.xml 2012-01-24 22:41:45 UTC (rev 14039) @@ -4,11 +4,11 @@ <bookinfo id="Installation_Guide_JBoss_Enterprise_Portal_Platform"> <title>Installation Guide</title> - <subtitle>An Installation Guide for &PRODUCT;</subtitle> + <subtitle>For use with &PRODUCT;</subtitle> <productname>JBoss Enterprise Portal Platform</productname> <productnumber>4.3</productnumber> <edition>4.3.7</edition> - <pubsnumber>1</pubsnumber> + <pubsnumber>100</pubsnumber> <abstract><para>This Installation Guide documents relevant information regarding the installation of JBoss Enterprise Portal Platform</para> Modified: docs/enterprise/trunk/Installation_Guide/en-US/Revision_History.xml =================================================================== --- docs/enterprise/trunk/Installation_Guide/en-US/Revision_History.xml 2012-01-24 21:21:57 UTC (rev 14038) +++ docs/enterprise/trunk/Installation_Guide/en-US/Revision_History.xml 2012-01-24 22:41:45 UTC (rev 14039) @@ -6,6 +6,20 @@ <title>Revision History</title> <simpara> <revhistory> + <revision> + <revnumber>4.3.7-100</revnumber> + <date>Tue Jan 24 2011</date> + <author> + <firstname>Jared</firstname> + <surname>Morgan</surname> + <email>jmorgan [at] redhat [dot] com</email> + </author> + <revdescription> + <simplelist> + <member>Prepared for JBoss Enterprise Portal Platform 4.3.0 CP07 GA.</member> + </simplelist> + </revdescription> + </revision> <revision> <revnumber>1-1.4</revnumber> <date>Fri Jul 15 2011</date> Modified: docs/enterprise/trunk/PortletBridge/en-US/Book_Info.xml =================================================================== --- docs/enterprise/trunk/PortletBridge/en-US/Book_Info.xml 2012-01-24 21:21:57 UTC (rev 14038) +++ docs/enterprise/trunk/PortletBridge/en-US/Book_Info.xml 2012-01-24 22:41:45 UTC (rev 14039) @@ -7,7 +7,7 @@ <productname>JBoss Enterprise Portal Platform</productname> <productnumber>4.3</productnumber> <edition>4.3.7</edition> - <pubsnumber>1</pubsnumber> + <pubsnumber>100</pubsnumber> <abstract> <para> The JBoss Portlet Bridge is an implementation of the JSR-301 specification to support JSF within a portlet and with added enhancements to support other web frameworks. Currently the bridge supports any combination of JSF, Seam, and RichFaces to run inside a portlet. Modified: docs/enterprise/trunk/PortletBridge/en-US/Revision_History.xml =================================================================== --- docs/enterprise/trunk/PortletBridge/en-US/Revision_History.xml 2012-01-24 21:21:57 UTC (rev 14038) +++ docs/enterprise/trunk/PortletBridge/en-US/Revision_History.xml 2012-01-24 22:41:45 UTC (rev 14039) @@ -5,6 +5,20 @@ <title>Revision History</title> <simpara> <revhistory> + <revision> + <revnumber>4.3.7-100</revnumber> + <date>Tue Jan 24 2011</date> + <author> + <firstname>Jared</firstname> + <surname>Morgan</surname> + <email>jmorgan [at] redhat [dot] com</email> + </author> + <revdescription> + <simplelist> + <member>Prepared for JBoss Enterprise Portal Platform 4.3.0 CP07 GA.</member> + </simplelist> + </revdescription> + </revision> <revision> <revnumber>1-2.1</revnumber> <date>Fri Jul 15 2011</date> Modified: docs/enterprise/trunk/Reference_Guide/en-US/Book_Info.xml =================================================================== --- docs/enterprise/trunk/Reference_Guide/en-US/Book_Info.xml 2012-01-24 21:21:57 UTC (rev 14038) +++ docs/enterprise/trunk/Reference_Guide/en-US/Book_Info.xml 2012-01-24 22:41:45 UTC (rev 14039) @@ -3,11 +3,11 @@ ]> <bookinfo id="JBoss_Portal_Reference_Guide"> <title>Reference Guide</title> - <subtitle>A Reference Guide for Enterprise Portal Platform 4.3</subtitle> + <subtitle>For use with JBoss Enterprise Portal Platform 4.3</subtitle> <productname>JBoss Enterprise Portal Platform</productname> <productnumber>4.3</productnumber> <edition>4.3.7</edition> - <pubsnumber>1</pubsnumber> + <pubsnumber>100</pubsnumber> <abstract> <para>This book is the Enterprise Portal Platform Reference Guide.</para> </abstract> Modified: docs/enterprise/trunk/Reference_Guide/en-US/Revision_History.xml =================================================================== --- docs/enterprise/trunk/Reference_Guide/en-US/Revision_History.xml 2012-01-24 21:21:57 UTC (rev 14038) +++ docs/enterprise/trunk/Reference_Guide/en-US/Revision_History.xml 2012-01-24 22:41:45 UTC (rev 14039) @@ -6,6 +6,20 @@ <title>Revision History</title> <simpara> <revhistory> + <revision> + <revnumber>4.3.7-100</revnumber> + <date>Tue Jan 24 2011</date> + <author> + <firstname>Jared</firstname> + <surname>Morgan</surname> + <email>jmorgan [at] redhat [dot] com</email> + </author> + <revdescription> + <simplelist> + <member>Prepared for JBoss Enterprise Portal Platform 4.3.0 CP07 GA.</member> + </simplelist> + </revdescription> + </revision> <revision> <revnumber>1-1.10</revnumber> <date>Fri Jul 15 2011</date> Modified: docs/enterprise/trunk/Release_Notes/en-US/Book_Info.xml =================================================================== --- docs/enterprise/trunk/Release_Notes/en-US/Book_Info.xml 2012-01-24 21:21:57 UTC (rev 14038) +++ docs/enterprise/trunk/Release_Notes/en-US/Book_Info.xml 2012-01-24 22:41:45 UTC (rev 14039) @@ -9,7 +9,7 @@ <productname>JBoss Enterprise Portal Platform</productname> <productnumber>4.3</productnumber> <edition>4.3.7</edition> - <pubsnumber>1</pubsnumber> + <pubsnumber>50</pubsnumber> <abstract> <para> These release notes contain important information related to JBoss Enterprise Portal Platform &VZ; that may not be currently available in the Product Manuals. You should read these Release Notes in their entirety before installing the product. Modified: docs/enterprise/trunk/Release_Notes/en-US/CP07_Release_Notes.xml =================================================================== --- docs/enterprise/trunk/Release_Notes/en-US/CP07_Release_Notes.xml 2012-01-24 21:21:57 UTC (rev 14038) +++ docs/enterprise/trunk/Release_Notes/en-US/CP07_Release_Notes.xml 2012-01-24 22:41:45 UTC (rev 14039) @@ -1,6 +1,5 @@ <?xml version='1.0' encoding='UTF-8'?> -<!-- This document was created with Syntext Serna Free. --> -<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +<!-- This document was created with Syntext Serna Free. --><!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ <!ENTITY % BOOK_ENTITIES SYSTEM "CP07_Release_Notes.ent"> %BOOK_ENTITIES; ]> @@ -16,17 +15,16 @@ <chapter id="Release_Notes-Installation"> <title>Installation</title> <para> - The JBoss Enterprise Portal Platform <citetitle>Installation Guide</citetitle> contains detailed installation instructions as well as environment requirements. + The JBoss Enterprise Portal Platform &VZ; <citetitle>Installation Guide</citetitle> contains detailed installation instructions as well as environment requirements. </para> <para> The Installation Guide is available in multiple formats from <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platf... type="http"/>. </para> </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 13)</remark></para> + <title>Component versions<remark>Component versions</remark></title> <table frame="all" pgwide="1"> - <title>Component Versions</title> + <title>Component versions</title> <tgroup cols="2" colsep="1"> <colspec colnum="1"/> <colspec colnum="2"/> @@ -38,156 +36,36 @@ </thead> <tbody> <row> - <entry>EAP</entry> - <entry>5.1.1-GA</entry> + <entry>JBoss Enterprise Application Platform</entry> + <entry>4.3.0 CP10</entry> </row> <row> - <entry>eXo junit</entry> - <entry>1.2.1-GA</entry> + <entry>Identity Module</entry> + <entry>1.1.3</entry> </row> <row> - <entry>eXo kernel</entry> - <entry>2.3.3-GA</entry> + <entry>Portlet Module</entry> + <entry>2.0.9</entry> </row> <row> - <entry>eXo Core</entry> - <entry>2.4.3-GA</entry> + <entry>Web Module</entry> + <entry>1.2.4</entry> </row> <row> - <entry>eXo WS</entry> - <entry>2.2.3-GA</entry> + <entry>CMS Module</entry> + <entry>1.2.9</entry> </row> <row> - <entry>eXo JCR</entry> - <entry>1.14.3-GA</entry> + <entry>JBoss Portlet Bridge</entry> + <entry>2.0.1.FINAL.EPP43CP07</entry> </row> - <row> - <entry>Apache Shindig</entry> - <entry>2.0.2-CP01</entry> - </row> - <row> - <entry>Simple Captcha</entry> - <entry>1.1.1-GA-Patch01</entry> - </row> - <row> - <entry>GateIn Parent</entry> - <entry>1.1.0-GA</entry> - </row> - <row> - <entry>GateIn dep</entry> - <entry>1.1.0-GA</entry> - </row> - <row> - <entry>GateIn Common</entry> - <entry>2.0.4-GA</entry> - </row> - <row> - <entry>GateIn WCI</entry> - <entry>2.1.0-GA</entry> - </row> - <row> - <entry>GateIn PC</entry> - <entry>2.3.0-GA</entry> - </row> - <row> - <entry>GateIn WSRP</entry> - <entry>2.1.0-EPP520-GA</entry> - </row> - <row> - <entry>GateIn MOP</entry> - <entry>1.1.0-GA</entry> - </row> - <row> - <entry>GateIn SSO</entry> - <entry>1.1.0-GA</entry> - </row> - <row> - <entry>PicketLink IDM</entry> - <entry>1.3.0.GA</entry> - </row> - <row> - <entry>Chromattic</entry> - <entry>1.1.1</entry> - </row> - <row> - <entry>Portlet Bridge</entry> - <entry>2.2.0.GA.EPP520</entry> - </row> - <row> - <entry>Seam</entry> - <entry>2.2.4.EAP5</entry> - </row> - <row> - <entry>Richfaces</entry> - <entry>3.3.1.SP3</entry> - </row> - <row> - <entry>Groovy</entry> - <entry>1.7.6</entry> - </row> - <row> - <entry>Commons DBCP</entry> - <entry>1.4</entry> - </row> - <row> - <entry>Commons IO</entry> - <entry>1.4</entry> - </row> - <row> - <entry>Commons Lang</entry> - <entry>2.6</entry> - </row> - <row> - <entry>HSQLDB</entry> - <entry>2.0.0</entry> - </row> - <row> - <entry>JBoss Cache</entry> - <entry>3.2.7</entry> - </row> - <row> - <entry>GateIn Management</entry> - <entry>1.0.0-GA</entry> - </row> </tbody> </tgroup> </table> </chapter> <chapter> - <title>Upgraded Components</title> - <formalpara> - <title>New Components</title> - <para>The following new components warrant special mention.</para> - </formalpara> - <variablelist> - <varlistentry> - <term>Site Migration Utilities</term> - <listitem> - <para>This new functionality is designed to improve the experience of managing unique sites or groups of pages as they progress from the development to production life cycle. The Migration utility has multiple administrative interfaces to support the requirements of different enterprises.</para> - </listitem> - </varlistentry> - <varlistentry> - <term>Site Management Utilities</term> - <listitem> - <para>The new functionality is provided to assist administrators in performing routine tasks. This includes the release of IDM cache, gathering of performance metrics and other processes related to managing the portal server. </para> - </listitem> - </varlistentry> - </variablelist> - <formalpara> - <title>Updated Components</title> - <para>The following updated components warrant special mention.</para> - </formalpara> - <variablelist> - <varlistentry> - <term>Java Content Respostory</term> - <listitem> - <para>This updated release of the eXo Java Content Repository (JCR) has been updated to a newer version designed to improve the performance and scalability of large portal sites. </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> + <title>New and upgraded components<remark>New and upgraded components</remark></title> + <para>There are no new or upgrade components that require special mention in this release. Refer to <xref linkend="New_Features"/> for those components that received an update outside of the primary components specified in <xref linkend="Release_Notes-Component_Features"/></para> </chapter> <chapter id="Release_Notes-Documentation"> <title>Documentation</title> @@ -196,7 +74,7 @@ </para> </chapter> <chapter id="Release_Notes-_Product_Support_and_License_Website_Links_"> - <title> Product Support Links </title> + <title> Product support links </title> <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-Support_Processes"> <title>Product Update and Support Processes</title> <para> @@ -216,16 +94,16 @@ </para> </formalpara> </chapter> - <chapter> - <title>New Features</title> + <chapter id="New_Features"> + <title>New features</title> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="feature_requests.xml" encoding="XML"/> </chapter> <chapter id="Release_Notes-Known_Issues"> - <title>Known Issues </title> + <title>Known issues </title> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="known_issues.xml" encoding="XML"/> </chapter> <chapter id="Release_Notes-Issues_Resolved_In_Production"> - <title>Resolved Issues </title> + <title>Resolved issues </title> <para> The following issues were resolved in this release of JBoss Enterprise Portal Platform. </para> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="resolved_issues.xml"/> Modified: docs/enterprise/trunk/Release_Notes/en-US/Revision_History.xml =================================================================== --- docs/enterprise/trunk/Release_Notes/en-US/Revision_History.xml 2012-01-24 21:21:57 UTC (rev 14038) +++ docs/enterprise/trunk/Release_Notes/en-US/Revision_History.xml 2012-01-24 22:41:45 UTC (rev 14039) @@ -4,12 +4,12 @@ %BOOK_ENTITIES; ]> <appendix id="appe-Release_Notes-Revision_History"> - <title>Revision History</title> + <title>Revision history</title> <simpara> <revhistory> <revision> - <revnumber>5.2.0-101</revnumber> - <date>Thu Dec 14 2011</date> + <revnumber>4.3.7-100</revnumber> + <date>Wed Jan 25 2011</date> <author> <firstname>Jared</firstname> <surname>Morgan</surname> @@ -17,7 +17,7 @@ </author> <revdescription> <simplelist> - <member>Release Notes prepared for JBoss Enterprise Portal Platform 5.2.0 GA.</member> + <member>Release Notes prepared for JBoss Enterprise Portal Platform 4.3.0 CP07 GA.</member> </simplelist> </revdescription> </revision> Modified: docs/enterprise/trunk/Release_Notes/en-US/feature_requests.old =================================================================== --- docs/enterprise/trunk/Release_Notes/en-US/feature_requests.old 2012-01-24 21:21:57 UTC (rev 14038) +++ docs/enterprise/trunk/Release_Notes/en-US/feature_requests.old 2012-01-24 22:41:45 UTC (rev 14039) @@ -1,4 +1,333 @@ +<?xml version='1.0' encoding='UTF-8'?> +<!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> +<variablelist> +<!-- https://issues.jboss.org/browse/JBEPP-736 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-736">JBEPP-736<... + </term> + <listitem> + <remark>Assignee is: mposolda</remark> + <remark>JIRA is Closed</remark> + <para> + It is possible to switch portal clusters between UDP and TCP communication modes using a command-line parameter. The -Dgatein.default.jgroups.stack=[tcp | udp] parameter switches EPP clusters (JCR, IDM, MOPSessionManager, NavigationService, DescriptionService) between the two protocols. The functionality is implemented using an adapted, and mutually exclusive implementation of jboss.default.jgroups.stack. -<para> -There are no Feature Request in this release. -</para> +<note> + <para>This enhancement is based on, but deliberately independent of, the JBoss Enterprise Application Platform parameter. &quot;jboss.default.jgroups.stack&quot; which supports more values by default than Enterprise Portal Platform currently does. The decision to keep the two parameters separate was for upstream compatibility.</para> + </note> + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-932 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-932">JBEPP-932<... + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + URL handler support is available in this release. The WCM component uses this feature to support locales as part of the URL. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-933 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-933">JBEPP-933<... + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + Performance bottlenecks have been removed when a portal runs with hundreds of navigation nodes. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-934 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-934">JBEPP-934<... + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + In previous releases, navigation node translations had to be managed in language property files. This release allows Navigation nodes to be translated directly through the administration interface. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-937 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-937">JBEPP-937<... + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + It is now possible to define a portlet.xml that describes elements such as filters that need to be applied to all portlets. The file is located in jboss-as/server/[configuration]/conf/gatein/portlet.xml + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-938 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-938">JBEPP-938<... + </term> + <listitem> + <remark>Assignee is: mwringe</remark> + <remark>JIRA is Closed</remark> + <para> + This release upgrades Shindig to version 2.0.2. Shindig is used to embed OpenSocial gadgets. Refer to the Component Versions section for the definitive version featured in this release. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-939 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-939">JBEPP-939<... + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + Web service security between WSRP producers and consumers is available in this release. This enhancement allows for encrypted communication and access to authenticated user content over WSRP. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-940 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-940">JBEPP-940<... + </term> + <listitem> + <remark>Assignee is: bdaw</remark> + <remark>JIRA is Closed</remark> + <para> + This release makes it possible to configure several LDAP servers containing different users with GateIn. In a ReadOnly scenario, the user is searched in all configured sources. In a ReadWrite scenario, the user is created only in the first configured LDAP server, but obtained from all. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1008 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1008">JBEPP-1008&... + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + Application registry categories are now cached for better performance. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1015 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1015">JBEPP-1015&... + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + Each site can now have a site description, which can be accessed and used by the management applications. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1016 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1016">JBEPP-1016&... + </term> + <listitem> + <remark>Assignee is: mwringe</remark> + <remark>JIRA is Closed</remark> + <para> + Priority for the loading of skin css files can now be specified in gatein-resources.xml using the css-priority xml element. This allows the css elements to be loaded in a specific order, which can be useful for overriding existing css elements. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1045 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1045">JBEPP-1045&... + </term> + <listitem> + <remark>Assignee is: claprun</remark> + <remark>JIRA is Closed</remark> + <para> + WSRP was previously unavailable for portal extensions. The new WSRP component now properly initializes itself even when started from an extension (as opposed to the default portal container). + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1077 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1077">JBEPP-1077&... + </term> + <listitem> + <remark>This issue is unassigned!</remark> + <remark>JIRA is Closed</remark> + <para> + The datasource for JCR is now using managed transactions, and required a change in the datasource descriptor. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1078 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1078">JBEPP-1078&... + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + EPP is now partially available in Czech language. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1088 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1088">JBEPP-1088&... + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + When adding a page to a site, pages are displayed in a drop-down list instead of a free form text field. This makes adding pages more intuitive. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1098 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1098">JBEPP-1098&... + </term> + <listitem> + <remark>Assignee is: mwringe</remark> + <remark>JIRA is Closed</remark> + <para> + This release of JBoss Enterprise Portal Platform adds a configurable setting to control whether the &apos;info bar&apos; which surrounds new portlets is displayed by default. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1099 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1099">JBEPP-1099&... + </term> + <listitem> + <remark>Assignee is: mposolda</remark> + <remark>JIRA is Closed</remark> + <para> + In this release, the Single Sign On (SSO) component has been enhanced to support FORM authentication for instances where the user can not get access to SSO authentication sessions (such as a Kerberos ticket). Users can now authenticate manually with the portal-specific username and password as a fall-back. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1116 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1116">JBEPP-1116&... + </term> + <listitem> + <remark>Assignee is: claprun</remark> + <remark>JIRA is Closed</remark> + <para> + Configuring a page is no longer restricted to local portlets. It is now possible to define remote portlets (WSRP) in page descriptors to populate the base data for the page. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1140 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1140">JBEPP-1140&... + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + In previous releases, the portal did not indicate it had started clearly in the logs. Changes to core portal code now specifies the portal has started in the logs, and includes the portal version number for reference. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1149 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1149">JBEPP-1149&... + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + This release contains enhancements to Gadgets, which, like portlets, can now be integrated on a page definition through XML descriptors. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1158 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1158">JBEPP-1158&... + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + The HTML Document Object Module (DOM) has been optimized to achieve better performance when transmitting markup, and has been simplified for faster rendering on recent web browsers. Older browsers such as Internet Explorer will still work, however performance will be degraded. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1169 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1169">JBEPP-1169&... + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + The Apache Shindig configuration file has been made more accessible to be modified more easily. It is now part of eXoGadgetServer.war/containers/default/container.js + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1197 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1197">JBEPP-1197&... + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + An enhancement to the UserDashboardImpl object now allows dashboard instances to be reused. Dashboards now require less resources to operate correctly. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1210 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1210">JBEPP-1210&... + </term> + <listitem> + <remark>Assignee is: mposolda</remark> + <remark>JIRA is Closed</remark> + <para> + Cluster data transportation has been optimized to reduce the number of network connections and threads. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1250 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1250">JBEPP-1250&... + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + When defining navigation in an XML descriptor, it is now possible to define the strategy to apply during startup. It is possible to &quot;conserve&quot;, &quot;insert&quot;, &quot;merge&quot; or &quot;rewrite&quot; the content previously imported. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1332 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1332">JBEPP-1332&... + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + In this release the default JCR workspace name and system JCR workspace name can now be configured in the configuration.properties file. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1349 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1349">JBEPP-1349&... + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + There was no way to determine the Enterprise Portal Platform version, based on what was displayed when starting the portal. An enhancement to UIFooterPortlet.gtmpl has been implemented, which allows the user to see what portal version is used by mouse-hovering in the site footer. + </para> + </listitem> + </varlistentry> +</variablelist> Modified: docs/enterprise/trunk/Release_Notes/en-US/feature_requests.xml =================================================================== --- docs/enterprise/trunk/Release_Notes/en-US/feature_requests.xml 2012-01-24 21:21:57 UTC (rev 14038) +++ docs/enterprise/trunk/Release_Notes/en-US/feature_requests.xml 2012-01-24 22:41:45 UTC (rev 14039) @@ -1,333 +1,44 @@ -<?xml version='1.0' encoding='UTF-8'?> +<?xml version='1.0'?> <!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> + + <variablelist> -<!-- https://issues.jboss.org/browse/JBEPP-736 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-736">JBEPP-736<... - </term> - <listitem> - <remark>Assignee is: mposolda</remark> - <remark>JIRA is Closed</remark> - <para> - It is possible to switch portal clusters between UDP and TCP communication modes using a command-line parameter. The -Dgatein.default.jgroups.stack=[tcp | udp] parameter switches EPP clusters (JCR, IDM, MOPSessionManager, NavigationService, DescriptionService) between the two protocols. The functionality is implemented using an adapted, and mutually exclusive implementation of jboss.default.jgroups.stack. + + <!-- https://issues.jboss.org/browse/JBEPP-920 --> + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-920">JBEPP-920<... + <listitem> + + <remark>Assignee is: theute</remark> + + + <remark>JIRA is Closed</remark> + + + <para> + JackRabbit has been upgraded to version 1.6.4 in this release. + </para> + + </listitem> + </varlistentry> -<note> - <para>This enhancement is based on, but deliberately independent of, the JBoss Enterprise Application Platform parameter. &quot;jboss.default.jgroups.stack&quot; which supports more values by default than Enterprise Portal Platform currently does. The decision to keep the two parameters separate was for upstream compatibility.</para> - </note> + <!-- https://issues.jboss.org/browse/JBEPP-1457 --> + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1457">JBEPP-1457&... + <listitem> + + <remark>Assignee is: theute</remark> + + + <remark>JIRA is Closed</remark> + + + <para> + The Enterprise Application Platform base component has been upgraded to version 4.3.0 CP10 in this release. </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-932 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-932">JBEPP-932<... - </term> - <listitem> - <remark>Assignee is: theute</remark> - <remark>JIRA is Closed</remark> - <para> - URL handler support is available in this release. The WCM component uses this feature to support locales as part of the URL. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-933 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-933">JBEPP-933<... - </term> - <listitem> - <remark>Assignee is: theute</remark> - <remark>JIRA is Closed</remark> - <para> - Performance bottlenecks have been removed when a portal runs with hundreds of navigation nodes. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-934 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-934">JBEPP-934<... - </term> - <listitem> - <remark>Assignee is: theute</remark> - <remark>JIRA is Closed</remark> - <para> - In previous releases, navigation node translations had to be managed in language property files. This release allows Navigation nodes to be translated directly through the administration interface. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-937 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-937">JBEPP-937<... - </term> - <listitem> - <remark>Assignee is: theute</remark> - <remark>JIRA is Closed</remark> - <para> - It is now possible to define a portlet.xml that describes elements such as filters that need to be applied to all portlets. The file is located in jboss-as/server/[configuration]/conf/gatein/portlet.xml - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-938 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-938">JBEPP-938<... - </term> - <listitem> - <remark>Assignee is: mwringe</remark> - <remark>JIRA is Closed</remark> - <para> - This release upgrades Shindig to version 2.0.2. Shindig is used to embed OpenSocial gadgets. Refer to the Component Versions section for the definitive version featured in this release. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-939 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-939">JBEPP-939<... - </term> - <listitem> - <remark>Assignee is: hfnukal</remark> - <remark>JIRA is Closed</remark> - <para> - Web service security between WSRP producers and consumers is available in this release. This enhancement allows for encrypted communication and access to authenticated user content over WSRP. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-940 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-940">JBEPP-940<... - </term> - <listitem> - <remark>Assignee is: bdaw</remark> - <remark>JIRA is Closed</remark> - <para> - This release makes it possible to configure several LDAP servers containing different users with GateIn. In a ReadOnly scenario, the user is searched in all configured sources. In a ReadWrite scenario, the user is created only in the first configured LDAP server, but obtained from all. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-1008 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1008">JBEPP-1008&... - </term> - <listitem> - <remark>Assignee is: hfnukal</remark> - <remark>JIRA is Closed</remark> - <para> - Application registry categories are now cached for better performance. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-1015 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1015">JBEPP-1015&... - </term> - <listitem> - <remark>Assignee is: theute</remark> - <remark>JIRA is Closed</remark> - <para> - Each site can now have a site description, which can be accessed and used by the management applications. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-1016 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1016">JBEPP-1016&... - </term> - <listitem> - <remark>Assignee is: mwringe</remark> - <remark>JIRA is Closed</remark> - <para> - Priority for the loading of skin css files can now be specified in gatein-resources.xml using the css-priority xml element. This allows the css elements to be loaded in a specific order, which can be useful for overriding existing css elements. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-1045 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1045">JBEPP-1045&... - </term> - <listitem> - <remark>Assignee is: claprun</remark> - <remark>JIRA is Closed</remark> - <para> - WSRP was previously unavailable for portal extensions. The new WSRP component now properly initializes itself even when started from an extension (as opposed to the default portal container). - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-1077 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1077">JBEPP-1077&... - </term> - <listitem> - <remark>This issue is unassigned!</remark> - <remark>JIRA is Closed</remark> - <para> - The datasource for JCR is now using managed transactions, and required a change in the datasource descriptor. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-1078 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1078">JBEPP-1078&... - </term> - <listitem> - <remark>Assignee is: hfnukal</remark> - <remark>JIRA is Closed</remark> - <para> - EPP is now partially available in Czech language. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-1088 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1088">JBEPP-1088&... - </term> - <listitem> - <remark>Assignee is: theute</remark> - <remark>JIRA is Closed</remark> - <para> - When adding a page to a site, pages are displayed in a drop-down list instead of a free form text field. This makes adding pages more intuitive. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-1098 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1098">JBEPP-1098&... - </term> - <listitem> - <remark>Assignee is: mwringe</remark> - <remark>JIRA is Closed</remark> - <para> - This release of JBoss Enterprise Portal Platform adds a configurable setting to control whether the &apos;info bar&apos; which surrounds new portlets is displayed by default. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-1099 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1099">JBEPP-1099&... - </term> - <listitem> - <remark>Assignee is: mposolda</remark> - <remark>JIRA is Closed</remark> - <para> - In this release, the Single Sign On (SSO) component has been enhanced to support FORM authentication for instances where the user can not get access to SSO authentication sessions (such as a Kerberos ticket). Users can now authenticate manually with the portal-specific username and password as a fall-back. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-1116 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1116">JBEPP-1116&... - </term> - <listitem> - <remark>Assignee is: claprun</remark> - <remark>JIRA is Closed</remark> - <para> - Configuring a page is no longer restricted to local portlets. It is now possible to define remote portlets (WSRP) in page descriptors to populate the base data for the page. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-1140 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1140">JBEPP-1140&... - </term> - <listitem> - <remark>Assignee is: hfnukal</remark> - <remark>JIRA is Closed</remark> - <para> - In previous releases, the portal did not indicate it had started clearly in the logs. Changes to core portal code now specifies the portal has started in the logs, and includes the portal version number for reference. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-1149 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1149">JBEPP-1149&... - </term> - <listitem> - <remark>Assignee is: theute</remark> - <remark>JIRA is Closed</remark> - <para> - This release contains enhancements to Gadgets, which, like portlets, can now be integrated on a page definition through XML descriptors. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-1158 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1158">JBEPP-1158&... - </term> - <listitem> - <remark>Assignee is: theute</remark> - <remark>JIRA is Closed</remark> - <para> - The HTML Document Object Module (DOM) has been optimized to achieve better performance when transmitting markup, and has been simplified for faster rendering on recent web browsers. Older browsers such as Internet Explorer will still work, however performance will be degraded. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-1169 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1169">JBEPP-1169&... - </term> - <listitem> - <remark>Assignee is: theute</remark> - <remark>JIRA is Closed</remark> - <para> - The Apache Shindig configuration file has been made more accessible to be modified more easily. It is now part of eXoGadgetServer.war/containers/default/container.js - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-1197 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1197">JBEPP-1197&... - </term> - <listitem> - <remark>Assignee is: hfnukal</remark> - <remark>JIRA is Closed</remark> - <para> - An enhancement to the UserDashboardImpl object now allows dashboard instances to be reused. Dashboards now require less resources to operate correctly. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-1210 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1210">JBEPP-1210&... - </term> - <listitem> - <remark>Assignee is: mposolda</remark> - <remark>JIRA is Closed</remark> - <para> - Cluster data transportation has been optimized to reduce the number of network connections and threads. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-1250 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1250">JBEPP-1250&... - </term> - <listitem> - <remark>Assignee is: theute</remark> - <remark>JIRA is Closed</remark> - <para> - When defining navigation in an XML descriptor, it is now possible to define the strategy to apply during startup. It is possible to &quot;conserve&quot;, &quot;insert&quot;, &quot;merge&quot; or &quot;rewrite&quot; the content previously imported. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-1332 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1332">JBEPP-1332&... - </term> - <listitem> - <remark>Assignee is: theute</remark> - <remark>JIRA is Closed</remark> - <para> - In this release the default JCR workspace name and system JCR workspace name can now be configured in the configuration.properties file. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-1349 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1349">JBEPP-1349&... - </term> - <listitem> - <remark>Assignee is: hfnukal</remark> - <remark>JIRA is Closed</remark> - <para> - There was no way to determine the Enterprise Portal Platform version, based on what was displayed when starting the portal. An enhancement to UIFooterPortlet.gtmpl has been implemented, which allows the user to see what portal version is used by mouse-hovering in the site footer. - </para> - </listitem> - </varlistentry> + + </listitem> + </varlistentry> + </variablelist> Modified: docs/enterprise/trunk/Release_Notes/en-US/known_issues.old =================================================================== --- docs/enterprise/trunk/Release_Notes/en-US/known_issues.old 2012-01-24 21:21:57 UTC (rev 14038) +++ docs/enterprise/trunk/Release_Notes/en-US/known_issues.old 2012-01-24 22:41:45 UTC (rev 14039) @@ -1,4 +1,116 @@ +<?xml version='1.0'?> +<!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> -<para> -There are no known issues in this release. -</para> + +<variablelist> + + <!-- https://issues.jboss.org/browse/JBEPP-1376 --> + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1376">JBEPP-1376&... + <listitem> + + <remark>Assignee is: theute</remark> + + + <remark>JIRA is OPEN</remark> + + + <para> + When serving content from a portlet, resource encoding is being rewritten with the default encoding of the running JVM. To work around the issue, server the resource as a binary, or set the default system encoding to ISO-8859-1. + </para> + + </listitem> + </varlistentry> + + <!-- https://issues.jboss.org/browse/JBEPP-1396 --> + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1396">JBEPP-1396&... + <listitem> + + <remark>This issue is unassigned!</remark> + + + <remark>JIRA is OPEN</remark> + + + <para> + When a dashboard page is created and its title translated in various languages, switching languages will not update the dashboard page name on the user interface immediately. To work around the issue, log out and log back in to show the correct translation for the page name. + </para> + + </listitem> + </varlistentry> + + <!-- https://issues.jboss.org/browse/JBEPP-1399 --> + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1399">JBEPP-1399&... + <listitem> + + <remark>This issue is unassigned!</remark> + + + <remark>JIRA is OPEN</remark> + + + <para> + If you create a system subnode under a node in the Navigation Management, you are allowed the delete the parent node without the "Cannot delete a system node" message being shown. When trying to save the result, a message "Unknown error" is shown and the following NPE is thrown. A fix is being investigated for a future release. + </para> + + </listitem> + </varlistentry> + + <!-- https://issues.jboss.org/browse/JBEPP-1401 --> + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1401">JBEPP-1401&... + <listitem> + + <remark>Assignee is: theute</remark> + + + <remark>JIRA is OPEN</remark> + + + <para> + An issue with the No Result Found pop-up causes it to display after first searching for a non-existent user string, then searching for a string that is known to exist. There is no work around for this issue. + </para> + + </listitem> + </varlistentry> + + <!-- https://issues.jboss.org/browse/JBEPP-1402 --> + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1402">JBEPP-1402&... + <listitem> + + <remark>Assignee is: theute</remark> + + + <remark>JIRA is OPEN</remark> + + + <para> + An issue with node copy or clone behavior allows users to copy or clone a system node but not delete the node. This is caused by the node already being a system node, and therefore it can not be deleted based on it's context. There is no work around for this issue. + </para> + + </listitem> + </varlistentry> + + <!-- https://issues.jboss.org/browse/JBEPP-1411 --> + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1411">JBEPP-1411&... + <listitem> + + <remark>This issue is unassigned!</remark> + + + <remark>JIRA is OPEN</remark> + + + <para> + System child nodes can be deleted if the parent node is deleted. A system node should not be able to de be deleted, regardless of its position in a navigation tree. This behavior will be fixed in a future release. + </para> + + </listitem> + </varlistentry> + +</variablelist> Modified: docs/enterprise/trunk/Release_Notes/en-US/known_issues.xml =================================================================== --- docs/enterprise/trunk/Release_Notes/en-US/known_issues.xml 2012-01-24 21:21:57 UTC (rev 14038) +++ docs/enterprise/trunk/Release_Notes/en-US/known_issues.xml 2012-01-24 22:41:45 UTC (rev 14039) @@ -1,116 +1,4 @@ -<?xml version='1.0'?> -<!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -]> - -<variablelist> - - <!-- https://issues.jboss.org/browse/JBEPP-1376 --> - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1376">JBEPP-1376&... - <listitem> - - <remark>Assignee is: theute</remark> - - - <remark>JIRA is OPEN</remark> - - - <para> - When serving content from a portlet, resource encoding is being rewritten with the default encoding of the running JVM. To work around the issue, server the resource as a binary, or set the default system encoding to ISO-8859-1. - </para> - - </listitem> - </varlistentry> - - <!-- https://issues.jboss.org/browse/JBEPP-1396 --> - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1396">JBEPP-1396&... - <listitem> - - <remark>This issue is unassigned!</remark> - - - <remark>JIRA is OPEN</remark> - - - <para> - When a dashboard page is created and its title translated in various languages, switching languages will not update the dashboard page name on the user interface immediately. To work around the issue, log out and log back in to show the correct translation for the page name. - </para> - - </listitem> - </varlistentry> - - <!-- https://issues.jboss.org/browse/JBEPP-1399 --> - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1399">JBEPP-1399&... - <listitem> - - <remark>This issue is unassigned!</remark> - - - <remark>JIRA is OPEN</remark> - - - <para> - If you create a system subnode under a node in the Navigation Management, you are allowed the delete the parent node without the "Cannot delete a system node" message being shown. When trying to save the result, a message "Unknown error" is shown and the following NPE is thrown. A fix is being investigated for a future release. - </para> - - </listitem> - </varlistentry> - - <!-- https://issues.jboss.org/browse/JBEPP-1401 --> - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1401">JBEPP-1401&... - <listitem> - - <remark>Assignee is: theute</remark> - - - <remark>JIRA is OPEN</remark> - - - <para> - An issue with the No Result Found pop-up causes it to display after first searching for a non-existent user string, then searching for a string that is known to exist. There is no work around for this issue. - </para> - - </listitem> - </varlistentry> - - <!-- https://issues.jboss.org/browse/JBEPP-1402 --> - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1402">JBEPP-1402&... - <listitem> - - <remark>Assignee is: theute</remark> - - - <remark>JIRA is OPEN</remark> - - - <para> - An issue with node copy or clone behavior allows users to copy or clone a system node but not delete the node. This is caused by the node already being a system node, and therefore it can not be deleted based on it's context. There is no work around for this issue. - </para> - - </listitem> - </varlistentry> - - <!-- https://issues.jboss.org/browse/JBEPP-1411 --> - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1411">JBEPP-1411&... - <listitem> - - <remark>This issue is unassigned!</remark> - - - <remark>JIRA is OPEN</remark> - - - <para> - System child nodes can be deleted if the parent node is deleted. A system node should not be able to de be deleted, regardless of its position in a navigation tree. This behavior will be fixed in a future release. - </para> - - </listitem> - </varlistentry> - -</variablelist> +<para> +There are no known issues in this release. +</para> Modified: docs/enterprise/trunk/Release_Notes/en-US/resolved_issues.old =================================================================== --- docs/enterprise/trunk/Release_Notes/en-US/resolved_issues.old 2012-01-24 21:21:57 UTC (rev 14038) +++ docs/enterprise/trunk/Release_Notes/en-US/resolved_issues.old 2012-01-24 22:41:45 UTC (rev 14039) @@ -1,4 +1,457 @@ - -<para> -There are no resolved issues in this release. -</para> +<?xml version='1.0' encoding='UTF-8'?> +<!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> +<variablelist> +<!-- https://issues.jboss.org/browse/JBEPP-348 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-348">JBEPP-348<... + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + A Cross-site Scripting (XSS) vulnerability was discovered in the portlet description, which allowed Javascript to be specified in the portlet description through the application registry. The vulnerability has been fixed in this release. <ulink url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html&quo... + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-353 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-353">JBEPP-353<... + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + A Cross-site Scripting (XSS) vulnerability was discovered when adding a portlet to a category. The vulnerability has been fixed in this release. <ulink url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html&quo... + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-631 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-631">JBEPP-631<... + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + Remote Gadgets were not persisting data in category gadgets with more than five categories when the user switched between pages. User data entered in one screen was being lost when the user switched between pages. The fix implements changes to UIForm.js and UIFormCheckBoxInput.java which handles selected values reliably when the user switches between screens. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-699 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-699">JBEPP-699<... + </term> + <listitem> + <remark>This issue is unassigned!</remark> + <remark>JIRA is Closed</remark> + <para> + A bug in UIUserLanguageSelector caused a problem with dynamically updating the locale when a user selected a different language. The language state had to be saved using the Apply button. The fix introduces changes to locale handling in the affected module which fixes the issue. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-715 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-715">JBEPP-715<... + </term> + <listitem> + <remark>This issue is unassigned!</remark> + <remark>JIRA is Closed</remark> + <para> + The page URL conventions in previous versions of JBoss Enterprise Portal Platform did not allow for Portal pages to have the same name. In these instances, pages with identical names were allocated the same URL, with only one page available through it. A change to the way JBoss Enterprise Portal Platform constructs page URLs resolves this issue. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-763 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-763">JBEPP-763<... + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + The platform ships with a resource compressor (CSS and Javascript). Some javascript files were incorrectly compressed and would break unless the developer mode was enabled. Enabling the developer mode introduced performance side-effects. The Javascript compression engine has been replaced, and can be turned off if required, which fixes the issue. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-900 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-900">JBEPP-900<... + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + A bug in the Logo Portlet caused the processAction methods to be called once when the first, valid, processAction method was called to submit the value, and again when the page was rendered. This caused null values to be passed on the second submit. A fix to UILogoPortlet.gtmpl removes the second processAction call issue, which fixes the issue. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-901 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-901">JBEPP-901<... + </term> + <listitem> + <remark>Assignee is: bdaw</remark> + <remark>JIRA is Closed</remark> + <para> + When a &quot;root&quot; user (advanced administrative rights) logs onto the portal, part of the logon process calls a query that fetches all the groups from the database. This query was not optimized to handle databases containing very large numbers of groups. When testing with a large group database, the login process took an unacceptable amount of time. The fix implements performance improvements to the query, and provides enhanced caching for large group records. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-903 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-903">JBEPP-903<... + </term> + <listitem> + <remark>Assignee is: bdaw</remark> + <remark>JIRA is Closed</remark> + <para> + An issue was identified when the OrganizationManagementPortlet displayed many users from the IDM DB. This caused performance issues, specifically impacting load times for the portlet. The fix implements performance optimizations for specific database queries related to the process. Load time performance is improved for the portlet. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-908 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-908">JBEPP-908<... + </term> + <listitem> + <remark>Assignee is: bdaw</remark> + <remark>JIRA is Closed</remark> + <para> + A performance issue in a database query that checked for duplicate emails at user registration caused unacceptable wait times. The larger the user count was in the database, the more pronounced the issue. The fix implements performance optimization in the database query. User registration wait time is improved for portal instances with very large user databases. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-927 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-927">JBEPP-927<... + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + It is not possible to save notes in the TODO gadget when the gadget is placed anywhere except a dashboard. This behavior is expected. A workaround to this issue has been implemented in this version, which allows notes to be entered into this gadget only. Other gadgets still have this issue. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-950 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-950">JBEPP-950<... + </term> + <listitem> + <remark>Assignee is: mposolda</remark> + <remark>JIRA is Closed</remark> + <para> + An inefficiency in MOPSessionManager cache was causing unacceptable wait times when an user accessed the portal for the first time, when the portal was idle for an extended period, or when accessing pages that had not been previously cached. The fix implements performance improvements for cases where a portal instance has many pages and navigation nodes, improving overall response time. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-951 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-951">JBEPP-951<... + </term> + <listitem> + <remark>Assignee is: mposolda</remark> + <remark>JIRA is Closed</remark> + <para> + Performance issues were discovered in the portal when editing a navigation, or portal page that contained many sub-pages. In some cases, the save action was taking longer than one minute to complete. The fix implements changes to the queries used to retrieve navigation, or portal pages after saving, which improves load times significantly. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-983 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-983">JBEPP-983<... + </term> + <listitem> + <remark>Assignee is: claprun</remark> + <remark>JIRA is Closed</remark> + <para> + An inconsistency in how portlets are handled across different part of the administration interface resulted in an error when remote portlets were added to a category from the &quot;Portlet&quot; tab of the Application Registry. The inconsistency has now be resolved and it should be now possible to properly display remote portlets regardless of how they were added to categories. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-985 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-985">JBEPP-985<... + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + DateTimeValidator.java had an unnecessary check where the date input value needed to match the (not localized) DATETIME_REGEX. This superfluous requirement caused localized date input to fail. The fix removes the DATETIME_REGEX, which fixes the issue. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1032 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1032">JBEPP-1032&... + </term> + <listitem> + <remark>Assignee is: bdaw</remark> + <remark>JIRA is Closed</remark> + <para> + A bug was discovered where a transaction commit related to IDM database operations was not placed within a final() block. Any misconfiguration, or operation failure, could cause the database connection to remain open. The fix ensures the transaction commit related to IDM database operations is placed within a final() block, which fixes the issue. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1048 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1048">JBEPP-1048&... + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + A Cross-Site Scripting (XSS) vulnerability was discovered in the Edit Page &gt; Container Title field. The vulnerability is fixed in this release. <ulink url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html&quo... + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1049 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1049">JBEPP-1049&... + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + A Cross-site Scripting (XSS) vulnerability was discovered in the New Node label. The vulnerability has been removed in this release. <ulink url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html&quo... + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1050 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1050">JBEPP-1050&... + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + A Cross-site Scripting (XSS) vulnerability was discovered in the RSS reader gadget. The vulnerability has been fixed in this release. <ulink url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html&quo... + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1067 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1067">JBEPP-1067&... + </term> + <listitem> + <remark>Assignee is: bdaw</remark> + <remark>JIRA is Closed</remark> + <para> + Only users from the LDAP database were shown in organization management if LDAP did not support sorting. The fix changes the logging level to INFO in PicketLink IDM. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1082 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1082">JBEPP-1082&... + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + If gadget restrict access to specific group, it was accessible for not members in Dashboard and page editing. +Now users cannot add restricted gadget. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1148 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1148">JBEPP-1148&... + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + Activating JRMP configuration in JBoss EPP 5.1.x (or EPP based products) produced a large quantity of JMX/RMI logs in stdout/stderr. The JRMP agent had logging set to FINE, which resulted in verbose log information. The fix removes the embedded logger configuration, which results in the JBoss Enterprise Application Platform server log configuration being used for logging. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1150 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1150">JBEPP-1150&... + </term> + <listitem> + <remark>Assignee is: mputz</remark> + <remark>JIRA is Closed</remark> + <para> + An invisible navigation node was displayed in the Sitemap portlet when the parent node was expanded (not with Expand All button). The workaround described in the linked JIRA has been implemented in this release, which corrects the originally reported issue. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1167 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1167">JBEPP-1167&... + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + A problem with regard to the location of token keys prevented Gadgets from working in load-balanced clustered portal environments. Token keys have been moved to a location accessible by all load-balanced clustered portal instances. Gadgets can now be used as intended. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1196 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1196">JBEPP-1196&... + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + A problem with UploadService was causing the MIME type of .rtf files extracted from DiskFileItem in Apache as &quot;text/rtf&quot;. The value should have been extracted as &quot;application/rtf&quot;, which caused problems for applications dependent on correct MIME type information. The fix corrects the MIME type encoding, and ensures .rtf files are set with the MIME type &quot;application/rtf&quot;. + + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1221 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1221">JBEPP-1221&... + </term> + <listitem> + <remark>Assignee is: mwringe</remark> + <remark>JIRA is Closed</remark> + <para> + A problem with the GroupManagement.java isAdministrator method caused a NullPointerException when the Organization Portlet is placed on a page and an anonymous user tries to access it. The fix changes the behavior of isAdministrator for anonymous users, which fixes the issue. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1241 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1241">JBEPP-1241&... + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + A Cross-site Scripting (XSS) vulnerability was discovered in the UIFormDateTimeInput component. The vulnerability has been fixed in this release. <ulink url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html&quo... + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1243 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1243">JBEPP-1243&... + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + Group descriptions text entered by users was not properly protected from XSS attacks. It was possible to execute arbitrary Javascript if a user had permissions to enter a group description. The group description field has been protected to not execute any Javascript, which resolves the issue. <ulink url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html&quo... + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1293 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1293">JBEPP-1293&... + </term> + <listitem> + <remark>Assignee is: kenfinni</remark> + <remark>JIRA is Closed</remark> + <para> + org.jboss.portletbridge.seam.SeamPhaseListenerWrapper.afterPhase() did not correctly handle exceptions. Exceptions that typically occurred during during afterPhase() were truncated (for example StaleObjectStateException in Hibernate commit). The Seam exception handler was not notified of the truncated exceptions therefore the application moves to a next page instead of an error page. The fix ensures org.jboss.portletbridge.seam.SeamPhaseListenerWrapper.afterPhase() catches exceptions and passes them to Seam exception handler (for example, org.jboss.seam.jsf.SeamPhaseListener). Because exceptions are handled correctly, the Seam exception handler displays and error page given the appropriate conditions. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1310 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1310">JBEPP-1310&... + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + If the Opera browser is used to access the portal home page, a Javascript Uncaught exception is raised: &quot;TypeError: &apos;Browser.setOpacity&apos; is not a function&quot;. The fix incorporates a verified customer-submitted patch to Browser.js, which allows Opera browsers to access the portal home page. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1319 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1319">JBEPP-1319&... + </term> + <listitem> + <remark>Assignee is: claprun</remark> + <remark>JIRA is Closed</remark> + <para> + If the WSRP consumer was refreshed and activated, WSRP selfv2 prevented the server from starting when it was rebooted. The only way to work around this issue was to perform a force quit. The fix adds a &amp;lt;value-param&amp;gt; configuration option to the main WSRP configuration. consumersInitDelay provides a way to specify a delayed start (configurable, in seconds) of the ConsumerRegistry, which prevents a deadlock situation while the self consumers wait for the producer WSDL to be published. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1324 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1324">JBEPP-1324&... + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + It was found that the invoker servlets, deployed by default via +httpha-invoker, only performed access control on the HTTP GET and POST +methods, allowing remote attackers to make unauthenticated requests by +using different HTTP methods. Due to the second layer of authentication +provided by a security interceptor, this issue is not exploitable on +default installations unless an administrator has misconfigured the +security interceptor or disabled it. (CVE-2011-4085) + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1331 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1331">JBEPP-1331&... + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + When a portal host name contained the word &quot;portal&quot; in the name, gadgets were not displayed and a TemplateRuntimeException would occur. The fix adds functionality to several portal components which allows for the word &quot;portal&quot; in the host name. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1336 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1336">JBEPP-1336&... + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + It was found that the GateIn Portal contained verb-specific security constraints. As a result, authentication and authorization were only correctly applied to requests made using the GET and POST HTTP verbs. The GateIn Portal application does not allow a user to trigger any action using HTTP verbs other than POST and GET, so this issue did not expose an exploitable security flaw. As a defence-in-depth measure, the verb-specific security constraints have been removed. Authentication and authorization now correctly apply to requests made using all HTTP verbs. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1351 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1351">JBEPP-1351&... + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + The org.gatein.sso.agent.login.SSOLoginModule contains the common options &quot;portal&quot; and &quot;realmName&quot; as offered in other LoginModule classes. In the packaged gatein-jboss-beans.xml, this login module did not have these options. This caused problems when a customer wanted to implement SSO on a different portal container (for example in ecmdemo). The fix includes these common options in gatein-jboss-beans.xml, which resolves the issue. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1357 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1357">JBEPP-1357&... + </term> + <listitem> + <remark>Assignee is: claprun</remark> + <remark>JIRA is Closed</remark> + <para> + The Web Services for Remote Portlet (WSRP) configuration files for consumers and producer were previously only looked for in the WSRP extension archive. This resulted in extra configuration complexity for customers who wanted to edit the configuration directives for WSRP consumers and producer. The fix implements changes to the WSRP integration point that will now also look for WSRP configuration files in the conf/gatein directory of the active JBoss AS profile. + </para> + </listitem> + </varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1361 --> <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1361">JBEPP-1361&... + </term> + <listitem> + <remark>Assignee is: mposolda</remark> + <remark>JIRA is Closed</remark> + <para> + The JBoss Clustered Single Sign On (SSO) Valve must authenticate on all clustered nodes using the same password. The login process in Enterprise Portal Platform differed from normal authentication methods, and customers had to bypass standard authentication by enabling BASIC authentication, or patch login.jsp as described in the Reference Guide. The fix introduces PortalClusteredSSOSupportValve, which removes the patching and workarounds customers had to implement in earlier versions of the product, and increases overall platform security. + </para> + </listitem> + </varlistentry> +</variablelist> Modified: docs/enterprise/trunk/Release_Notes/en-US/resolved_issues.xml =================================================================== --- docs/enterprise/trunk/Release_Notes/en-US/resolved_issues.xml 2012-01-24 21:21:57 UTC (rev 14038) +++ docs/enterprise/trunk/Release_Notes/en-US/resolved_issues.xml 2012-01-24 22:41:45 UTC (rev 14039) @@ -2,456 +2,64 @@ <!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> <variablelist> -<!-- https://issues.jboss.org/browse/JBEPP-348 --> <varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-918 --> <varlistentry> <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-348">JBEPP-348<... + <ulink url="https://issues.jboss.org/browse/JBEPP-918">JBEPP-918<... </term> <listitem> - <remark>Assignee is: hfnukal</remark> - <remark>JIRA is Closed</remark> - <para> - A Cross-site Scripting (XSS) vulnerability was discovered in the portlet description, which allowed Javascript to be specified in the portlet description through the application registry. The vulnerability has been fixed in this release. <ulink url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html&quo... - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-353 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-353">JBEPP-353<... - </term> - <listitem> - <remark>Assignee is: hfnukal</remark> - <remark>JIRA is Closed</remark> - <para> - A Cross-site Scripting (XSS) vulnerability was discovered when adding a portlet to a category. The vulnerability has been fixed in this release. <ulink url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html&quo... - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-631 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-631">JBEPP-631<... - </term> - <listitem> - <remark>Assignee is: hfnukal</remark> - <remark>JIRA is Closed</remark> - <para> - Remote Gadgets were not persisting data in category gadgets with more than five categories when the user switched between pages. User data entered in one screen was being lost when the user switched between pages. The fix implements changes to UIForm.js and UIFormCheckBoxInput.java which handles selected values reliably when the user switches between screens. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-699 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-699">JBEPP-699<... - </term> - <listitem> - <remark>This issue is unassigned!</remark> - <remark>JIRA is Closed</remark> - <para> - A bug in UIUserLanguageSelector caused a problem with dynamically updating the locale when a user selected a different language. The language state had to be saved using the Apply button. The fix introduces changes to locale handling in the affected module which fixes the issue. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-715 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-715">JBEPP-715<... - </term> - <listitem> - <remark>This issue is unassigned!</remark> - <remark>JIRA is Closed</remark> - <para> - The page URL conventions in previous versions of JBoss Enterprise Portal Platform did not allow for Portal pages to have the same name. In these instances, pages with identical names were allocated the same URL, with only one page available through it. A change to the way JBoss Enterprise Portal Platform constructs page URLs resolves this issue. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-763 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-763">JBEPP-763<... - </term> - <listitem> - <remark>Assignee is: hfnukal</remark> - <remark>JIRA is Closed</remark> - <para> - The platform ships with a resource compressor (CSS and Javascript). Some javascript files were incorrectly compressed and would break unless the developer mode was enabled. Enabling the developer mode introduced performance side-effects. The Javascript compression engine has been replaced, and can be turned off if required, which fixes the issue. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-900 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-900">JBEPP-900<... - </term> - <listitem> - <remark>Assignee is: hfnukal</remark> - <remark>JIRA is Closed</remark> - <para> - A bug in the Logo Portlet caused the processAction methods to be called once when the first, valid, processAction method was called to submit the value, and again when the page was rendered. This caused null values to be passed on the second submit. A fix to UILogoPortlet.gtmpl removes the second processAction call issue, which fixes the issue. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-901 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-901">JBEPP-901<... - </term> - <listitem> - <remark>Assignee is: bdaw</remark> - <remark>JIRA is Closed</remark> - <para> - When a &quot;root&quot; user (advanced administrative rights) logs onto the portal, part of the logon process calls a query that fetches all the groups from the database. This query was not optimized to handle databases containing very large numbers of groups. When testing with a large group database, the login process took an unacceptable amount of time. The fix implements performance improvements to the query, and provides enhanced caching for large group records. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-903 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-903">JBEPP-903<... - </term> - <listitem> - <remark>Assignee is: bdaw</remark> - <remark>JIRA is Closed</remark> - <para> - An issue was identified when the OrganizationManagementPortlet displayed many users from the IDM DB. This caused performance issues, specifically impacting load times for the portlet. The fix implements performance optimizations for specific database queries related to the process. Load time performance is improved for the portlet. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-908 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-908">JBEPP-908<... - </term> - <listitem> - <remark>Assignee is: bdaw</remark> - <remark>JIRA is Closed</remark> - <para> - A performance issue in a database query that checked for duplicate emails at user registration caused unacceptable wait times. The larger the user count was in the database, the more pronounced the issue. The fix implements performance optimization in the database query. User registration wait time is improved for portal instances with very large user databases. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-927 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-927">JBEPP-927<... - </term> - <listitem> <remark>Assignee is: theute</remark> <remark>JIRA is Closed</remark> <para> - It is not possible to save notes in the TODO gadget when the gadget is placed anywhere except a dashboard. This behavior is expected. A workaround to this issue has been implemented in this version, which allows notes to be entered into this gadget only. Other gadgets still have this issue. + A bug in the org.jboss.portal.cms.security.AuthorizationProviderImpl#getCurrentRoles() call was incorrectly returning null. Users authenticated using LDAP were not seeing content that should have been available to them through the CMSPreviewServlet. The fix implements a fallback mechanism that uses the membershipModule to correctly authenticate users. </para> </listitem> </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-950 --> <varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-928 --> <varlistentry> <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-950">JBEPP-950<... + <ulink url="https://issues.jboss.org/browse/JBEPP-928">JBEPP-928<... </term> <listitem> - <remark>Assignee is: mposolda</remark> - <remark>JIRA is Closed</remark> - <para> - An inefficiency in MOPSessionManager cache was causing unacceptable wait times when an user accessed the portal for the first time, when the portal was idle for an extended period, or when accessing pages that had not been previously cached. The fix implements performance improvements for cases where a portal instance has many pages and navigation nodes, improving overall response time. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-951 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-951">JBEPP-951<... - </term> - <listitem> - <remark>Assignee is: mposolda</remark> - <remark>JIRA is Closed</remark> - <para> - Performance issues were discovered in the portal when editing a navigation, or portal page that contained many sub-pages. In some cases, the save action was taking longer than one minute to complete. The fix implements changes to the queries used to retrieve navigation, or portal pages after saving, which improves load times significantly. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-983 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-983">JBEPP-983<... - </term> - <listitem> - <remark>Assignee is: claprun</remark> - <remark>JIRA is Closed</remark> - <para> - An inconsistency in how portlets are handled across different part of the administration interface resulted in an error when remote portlets were added to a category from the &quot;Portlet&quot; tab of the Application Registry. The inconsistency has now be resolved and it should be now possible to properly display remote portlets regardless of how they were added to categories. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-985 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-985">JBEPP-985<... - </term> - <listitem> - <remark>Assignee is: hfnukal</remark> - <remark>JIRA is Closed</remark> - <para> - DateTimeValidator.java had an unnecessary check where the date input value needed to match the (not localized) DATETIME_REGEX. This superfluous requirement caused localized date input to fail. The fix removes the DATETIME_REGEX, which fixes the issue. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-1032 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1032">JBEPP-1032&... - </term> - <listitem> - <remark>Assignee is: bdaw</remark> - <remark>JIRA is Closed</remark> - <para> - A bug was discovered where a transaction commit related to IDM database operations was not placed within a final() block. Any misconfiguration, or operation failure, could cause the database connection to remain open. The fix ensures the transaction commit related to IDM database operations is placed within a final() block, which fixes the issue. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-1048 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1048">JBEPP-1048&... - </term> - <listitem> - <remark>Assignee is: hfnukal</remark> - <remark>JIRA is Closed</remark> - <para> - A Cross-Site Scripting (XSS) vulnerability was discovered in the Edit Page &gt; Container Title field. The vulnerability is fixed in this release. <ulink url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html&quo... - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-1049 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1049">JBEPP-1049&... - </term> - <listitem> <remark>Assignee is: theute</remark> <remark>JIRA is Closed</remark> <para> - A Cross-site Scripting (XSS) vulnerability was discovered in the New Node label. The vulnerability has been removed in this release. <ulink url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html&quo... - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-1050 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1050">JBEPP-1050&... - </term> - <listitem> - <remark>Assignee is: theute</remark> - <remark>JIRA is Closed</remark> - <para> - A Cross-site Scripting (XSS) vulnerability was discovered in the RSS reader gadget. The vulnerability has been fixed in this release. <ulink url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html&quo... - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-1067 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1067">JBEPP-1067&... - </term> - <listitem> - <remark>Assignee is: bdaw</remark> - <remark>JIRA is Closed</remark> - <para> - Only users from the LDAP database were shown in organization management if LDAP did not support sorting. The fix changes the logging level to INFO in PicketLink IDM. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-1082 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1082">JBEPP-1082&... - </term> - <listitem> - <remark>Assignee is: hfnukal</remark> - <remark>JIRA is Closed</remark> - <para> - If gadget restrict access to specific group, it was accessible for not members in Dashboard and page editing. -Now users cannot add restricted gadget. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-1148 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1148">JBEPP-1148&... - </term> - <listitem> - <remark>Assignee is: theute</remark> - <remark>JIRA is Closed</remark> - <para> - Activating JRMP configuration in JBoss EPP 5.1.x (or EPP based products) produced a large quantity of JMX/RMI logs in stdout/stderr. The JRMP agent had logging set to FINE, which resulted in verbose log information. The fix removes the embedded logger configuration, which results in the JBoss Enterprise Application Platform server log configuration being used for logging. + Removing the dashboard context from default-object.xml resulted in a Null Pointer Exception (NPE) when a user authenticated. The fix ensures that a proper null check is performed at the dashboardContext = portalObjectContainer.getContext(dashboardContextId) call, which fixes the issue. </para> </listitem> </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-1150 --> <varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-995 --> <varlistentry> <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1150">JBEPP-1150&... + <ulink url="https://issues.jboss.org/browse/JBEPP-995">JBEPP-995<... </term> <listitem> - <remark>Assignee is: mputz</remark> - <remark>JIRA is Closed</remark> - <para> - An invisible navigation node was displayed in the Sitemap portlet when the parent node was expanded (not with Expand All button). The workaround described in the linked JIRA has been implemented in this release, which corrects the originally reported issue. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-1167 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1167">JBEPP-1167&... - </term> - <listitem> <remark>Assignee is: theute</remark> <remark>JIRA is Closed</remark> <para> - A problem with regard to the location of token keys prevented Gadgets from working in load-balanced clustered portal environments. Token keys have been moved to a location accessible by all load-balanced clustered portal instances. Gadgets can now be used as intended. + IE 6 displayed &quot;This page contains both secure and nonsecure items&quot; on every page when users were authenticated using SSL. While IE6 was honoring the information it received in the header.jsp, this caused unnecessary modal dialog boxes to display every time a page with mixed content was opened. The fix implements changes to the header.jsp to correctly detect when a user is authenticated, and prevents the dialog boxes from opening. </para> </listitem> </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-1196 --> <varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1118 --> <varlistentry> <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1196">JBEPP-1196&... + <ulink url="https://issues.jboss.org/browse/JBEPP-1118">JBEPP-1118&... </term> <listitem> - <remark>Assignee is: hfnukal</remark> - <remark>JIRA is Closed</remark> - <para> - A problem with UploadService was causing the MIME type of .rtf files extracted from DiskFileItem in Apache as &quot;text/rtf&quot;. The value should have been extracted as &quot;application/rtf&quot;, which caused problems for applications dependent on correct MIME type information. The fix corrects the MIME type encoding, and ensures .rtf files are set with the MIME type &quot;application/rtf&quot;. - - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-1221 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1221">JBEPP-1221&... - </term> - <listitem> - <remark>Assignee is: mwringe</remark> - <remark>JIRA is Closed</remark> - <para> - A problem with the GroupManagement.java isAdministrator method caused a NullPointerException when the Organization Portlet is placed on a page and an anonymous user tries to access it. The fix changes the behavior of isAdministrator for anonymous users, which fixes the issue. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-1241 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1241">JBEPP-1241&... - </term> - <listitem> <remark>Assignee is: theute</remark> <remark>JIRA is Closed</remark> <para> - A Cross-site Scripting (XSS) vulnerability was discovered in the UIFormDateTimeInput component. The vulnerability has been fixed in this release. <ulink url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html&quo... - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-1243 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1243">JBEPP-1243&... - </term> - <listitem> - <remark>Assignee is: theute</remark> - <remark>JIRA is Closed</remark> - <para> - Group descriptions text entered by users was not properly protected from XSS attacks. It was possible to execute arbitrary Javascript if a user had permissions to enter a group description. The group description field has been protected to not execute any Javascript, which resolves the issue. <ulink url="https://www.redhat.com/security/data/cve/CVE-2011-4580.html&quo... - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-1293 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1293">JBEPP-1293&... - </term> - <listitem> - <remark>Assignee is: kenfinni</remark> - <remark>JIRA is Closed</remark> - <para> - org.jboss.portletbridge.seam.SeamPhaseListenerWrapper.afterPhase() did not correctly handle exceptions. Exceptions that typically occurred during during afterPhase() were truncated (for example StaleObjectStateException in Hibernate commit). The Seam exception handler was not notified of the truncated exceptions therefore the application moves to a next page instead of an error page. The fix ensures org.jboss.portletbridge.seam.SeamPhaseListenerWrapper.afterPhase() catches exceptions and passes them to Seam exception handler (for example, org.jboss.seam.jsf.SeamPhaseListener). Because exceptions are handled correctly, the Seam exception handler displays and error page given the appropriate conditions. + A bug in the HttpSession listener caused the ClusteredSession.invalidated() method to be called one during session validation, and again during the sessionDestroyed() call. Because the session was already invalidated, an exception is raised at the second invalidation attempt. The fix to HttpSession removes the unnecessary second call, which fixes the issue. </para> </listitem> </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-1310 --> <varlistentry> +<!-- https://issues.jboss.org/browse/JBEPP-1323 --> <varlistentry> <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1310">JBEPP-1310&... + <ulink url="https://issues.jboss.org/browse/JBEPP-1323">JBEPP-1323&... </term> <listitem> - <remark>Assignee is: hfnukal</remark> - <remark>JIRA is Closed</remark> - <para> - If the Opera browser is used to access the portal home page, a Javascript Uncaught exception is raised: &quot;TypeError: &apos;Browser.setOpacity&apos; is not a function&quot;. The fix incorporates a verified customer-submitted patch to Browser.js, which allows Opera browsers to access the portal home page. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-1319 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1319">JBEPP-1319&... - </term> - <listitem> - <remark>Assignee is: claprun</remark> - <remark>JIRA is Closed</remark> - <para> - If the WSRP consumer was refreshed and activated, WSRP selfv2 prevented the server from starting when it was rebooted. The only way to work around this issue was to perform a force quit. The fix adds a &amp;lt;value-param&amp;gt; configuration option to the main WSRP configuration. consumersInitDelay provides a way to specify a delayed start (configurable, in seconds) of the ConsumerRegistry, which prevents a deadlock situation while the self consumers wait for the producer WSDL to be published. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-1324 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1324">JBEPP-1324&... - </term> - <listitem> - <remark>Assignee is: hfnukal</remark> - <remark>JIRA is Closed</remark> - <para> - It was found that the invoker servlets, deployed by default via -httpha-invoker, only performed access control on the HTTP GET and POST -methods, allowing remote attackers to make unauthenticated requests by -using different HTTP methods. Due to the second layer of authentication -provided by a security interceptor, this issue is not exploitable on -default installations unless an administrator has misconfigured the -security interceptor or disabled it. (CVE-2011-4085) - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-1331 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1331">JBEPP-1331&... - </term> - <listitem> <remark>Assignee is: theute</remark> <remark>JIRA is Closed</remark> <para> - When a portal host name contained the word &quot;portal&quot; in the name, gadgets were not displayed and a TemplateRuntimeException would occur. The fix adds functionality to several portal components which allows for the word &quot;portal&quot; in the host name. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-1336 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1336">JBEPP-1336&... - </term> - <listitem> - <remark>Assignee is: theute</remark> - <remark>JIRA is Closed</remark> - <para> - It was found that the GateIn Portal contained verb-specific security constraints. As a result, authentication and authorization were only correctly applied to requests made using the GET and POST HTTP verbs. The GateIn Portal application does not allow a user to trigger any action using HTTP verbs other than POST and GET, so this issue did not expose an exploitable security flaw. As a defence-in-depth measure, the verb-specific security constraints have been removed. Authentication and authorization now correctly apply to requests made using all HTTP verbs. + It was found that the invoker servlets, deployed by default via httpha-invoker, only performed access control on the HTTP GET and POST methods, allowing remote attackers to make unauthenticated requests by using different HTTP methods. Due to the second layer of authentication provided by a security interceptor, this issue is not exploitable on default installations unless an administrator has misconfigured the security interceptor or disabled it. (CVE-2011-4085) </para> </listitem> </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-1351 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1351">JBEPP-1351&... - </term> - <listitem> - <remark>Assignee is: hfnukal</remark> - <remark>JIRA is Closed</remark> - <para> - The org.gatein.sso.agent.login.SSOLoginModule contains the common options &quot;portal&quot; and &quot;realmName&quot; as offered in other LoginModule classes. In the packaged gatein-jboss-beans.xml, this login module did not have these options. This caused problems when a customer wanted to implement SSO on a different portal container (for example in ecmdemo). The fix includes these common options in gatein-jboss-beans.xml, which resolves the issue. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-1357 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1357">JBEPP-1357&... - </term> - <listitem> - <remark>Assignee is: claprun</remark> - <remark>JIRA is Closed</remark> - <para> - The Web Services for Remote Portlet (WSRP) configuration files for consumers and producer were previously only looked for in the WSRP extension archive. This resulted in extra configuration complexity for customers who wanted to edit the configuration directives for WSRP consumers and producer. The fix implements changes to the WSRP integration point that will now also look for WSRP configuration files in the conf/gatein directory of the active JBoss AS profile. - </para> - </listitem> - </varlistentry> -<!-- https://issues.jboss.org/browse/JBEPP-1361 --> <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1361">JBEPP-1361&... - </term> - <listitem> - <remark>Assignee is: mposolda</remark> - <remark>JIRA is Closed</remark> - <para> - The JBoss Clustered Single Sign On (SSO) Valve must authenticate on all clustered nodes using the same password. The login process in Enterprise Portal Platform differed from normal authentication methods, and customers had to bypass standard authentication by enabling BASIC authentication, or patch login.jsp as described in the Reference Guide. The fix introduces PortalClusteredSSOSupportValve, which removes the patching and workarounds customers had to implement in earlier versions of the product, and increases overall platform security. - </para> - </listitem> - </varlistentry> </variablelist> Modified: docs/enterprise/trunk/Release_Notes_Old/en-US/CP07_Release_Notes.xml =================================================================== --- docs/enterprise/trunk/Release_Notes_Old/en-US/CP07_Release_Notes.xml 2012-01-24 21:21:57 UTC (rev 14038) +++ docs/enterprise/trunk/Release_Notes_Old/en-US/CP07_Release_Notes.xml 2012-01-24 22:41:45 UTC (rev 14039) @@ -1,6 +1,6 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Release_Notes.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "CP07_Release_Notes.ent"> %BOOK_ENTITIES; ]> <article> Modified: docs/enterprise/trunk/Tuning_Guide/en-US/Book_Info.xml =================================================================== --- docs/enterprise/trunk/Tuning_Guide/en-US/Book_Info.xml 2012-01-24 21:21:57 UTC (rev 14038) +++ docs/enterprise/trunk/Tuning_Guide/en-US/Book_Info.xml 2012-01-24 22:41:45 UTC (rev 14039) @@ -5,11 +5,11 @@ ]> <bookinfo id="book-Tuning_Guide-Tuning_Guide"> <title>Tuning Guide</title> - <subtitle>A guide to tuning the performance of JBoss Enterprise Portal Platform 4.3.</subtitle> + <subtitle>For use with JBoss Enterprise Portal Platform 4.3.</subtitle> <productname>JBoss Enterprise Portal Platform</productname> <productnumber>4.3</productnumber> <edition>4.3.7</edition> - <pubsnumber>1</pubsnumber> + <pubsnumber>100</pubsnumber> <abstract> <para> This Installation Guide documents tuning of JBoss Enterprise Portal Platform. Modified: docs/enterprise/trunk/Tuning_Guide/en-US/Revision_History.xml =================================================================== --- docs/enterprise/trunk/Tuning_Guide/en-US/Revision_History.xml 2012-01-24 21:21:57 UTC (rev 14038) +++ docs/enterprise/trunk/Tuning_Guide/en-US/Revision_History.xml 2012-01-24 22:41:45 UTC (rev 14039) @@ -7,6 +7,20 @@ <title>Revision History</title> <simpara> <revhistory> + <revision> + <revnumber>4.3.7-100</revnumber> + <date>Tue Jan 24 2011</date> + <author> + <firstname>Jared</firstname> + <surname>Morgan</surname> + <email>jmorgan [at] redhat [dot] com</email> + </author> + <revdescription> + <simplelist> + <member>Prepared for JBoss Enterprise Portal Platform 4.3.0 CP07 GA.</member> + </simplelist> + </revdescription> + </revision> <revision> <revnumber>1-1.5</revnumber> <date>Fri Jul 15 2011</date> Modified: docs/enterprise/trunk/User_Guide/en-US/Book_Info.xml =================================================================== --- docs/enterprise/trunk/User_Guide/en-US/Book_Info.xml 2012-01-24 21:21:57 UTC (rev 14038) +++ docs/enterprise/trunk/User_Guide/en-US/Book_Info.xml 2012-01-24 22:41:45 UTC (rev 14039) @@ -7,7 +7,7 @@ <productname>JBoss Enterprise Portal Platform</productname> <productnumber>4.3</productnumber> <edition>4.3.7</edition> - <pubsnumber>1</pubsnumber> + <pubsnumber>100</pubsnumber> <abstract> <para>This document is intended for those using JBoss Portal as End-Users. This is a &quot;Where do I Click?&quot; Guide.</para> <para> Modified: docs/enterprise/trunk/User_Guide/en-US/Revision_History.xml =================================================================== --- docs/enterprise/trunk/User_Guide/en-US/Revision_History.xml 2012-01-24 21:21:57 UTC (rev 14038) +++ docs/enterprise/trunk/User_Guide/en-US/Revision_History.xml 2012-01-24 22:41:45 UTC (rev 14039) @@ -7,6 +7,20 @@ <simpara> <revhistory> <revision> + <revnumber>4.3.7-100</revnumber> + <date>Tue Jan 24 2011</date> + <author> + <firstname>Jared</firstname> + <surname>Morgan</surname> + <email>jmorgan [at] redhat [dot] com</email> + </author> + <revdescription> + <simplelist> + <member>Prepared for JBoss Enterprise Portal Platform 4.3.0 CP07 GA.</member> + </simplelist> + </revdescription> + </revision> + <revision> <revnumber>1-1.10</revnumber> <date>Fri Jul 15 2011</date> <author>