Author: jaredmorgs Date: 2012-03-16 00:28:51 -0400 (Fri, 16 Mar 2012) New Revision: 8613 Added: epp/docs/branches/5.2/Release_Notes/en-US/needinfo.xml Modified: epp/docs/branches/5.2/Release_Notes/en-US/5.2.1_Release_Notes.xml epp/docs/branches/5.2/Release_Notes/en-US/known.xml epp/docs/branches/5.2/Release_Notes/en-US/resolved.xml epp/docs/branches/5.2/Release_Notes/publican.cfg Log: Version 1 of the EPP 5.2.1 release notes as generated by the BZ release note script Modified: epp/docs/branches/5.2/Release_Notes/en-US/5.2.1_Release_Notes.xml =================================================================== --- epp/docs/branches/5.2/Release_Notes/en-US/5.2.1_Release_Notes.xml 2012-03-15 21:53:32 UTC (rev 8612) +++ epp/docs/branches/5.2/Release_Notes/en-US/5.2.1_Release_Notes.xml 2012-03-16 04:28:51 UTC (rev 8613) @@ -3,7 +3,7 @@ <!ENTITY % BOOK_ENTITIES SYSTEM "5.2.1_Release_Notes.ent"> %BOOK_ENTITIES; ]> -<book> +<book status="draft"> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Book_Info.xml"/> <chapter id="Release_Notes-Introduction"> <title>Introduction</title> @@ -230,6 +230,7 @@ </para> </formalpara> </chapter> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="needinfo.xml" encoding="XML"/> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="known.xml" encoding="XML"/> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="resolved.xml"/> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/> Modified: epp/docs/branches/5.2/Release_Notes/en-US/known.xml =================================================================== --- epp/docs/branches/5.2/Release_Notes/en-US/known.xml 2012-03-15 21:53:32 UTC (rev 8612) +++ epp/docs/branches/5.2/Release_Notes/en-US/known.xml 2012-03-16 04:28:51 UTC (rev 8613) @@ -6,8 +6,12 @@ <title>Known Issues</title> <para> - The following issues are known to exist in this version of the JBoss Enterprise Portal Platform and will be fixed in a subsequent release. + The following issues are known to exist in JBoss Enterprise Portal Platform, and will be fixed in a subsequent release. </para> + <remark> + Do some of these issues look more like Resolved Issues? If they do, its because the ticket has not been set to the correct + resolution status (VERIFIED, CLOSED). + </remark> <variablelist> <varlistentry> @@ -16,11 +20,35 @@ <para> An issue was found in the Site Publisher Installation Guide regarding the requirement for Site Publisher to have a separate database to Enterprise Portal Platform. A customer identified an issue with the clarity of this information when they encountered a problem with database provisioning for the platform. The Site Publisher Installation Guide has been merged with the Installation Guide. The Database Configuration section has been extensively reworked to specify Site Publisher must have its own IDM and JCR database configured, and matching database connector JNDI name directives specified in gatein-ds.xml </para> + </listitem> +</varlistentry> + +<varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794386" /></term> + <listitem> <para> - This behavior persists in JBoss Enterprise Portal Platform 5.2.1 and will be resolved in a future release. + It was discovered that there was insufficient information in the Installation Guide regarding how to replace the default Hypersonic Database (HSQLDB) with a certified database that Red Hat supports. Detailed steps have been added to the Database Configuration section of the guide, which explain how to replace HSQLDB, and the requirements JBoss Enterprise Portal Platform has regarding separate databases for JCR and IDM. </para> </listitem> </varlistentry> +<varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794440" /></term> + <listitem> + <para> + Gadgets require HTTPS to be configured correctly in order to operate. This requirement was not clearly documented in the Installation Guide, which caused configuration issues for customers. Instructions from a KBase article have been incorporated into the Installation Guide, with clarifying links to other JBoss Middleware product documentation for background info on keystore and truststore configuration. + </para> + </listitem> +</varlistentry> + +<varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=793259" /></term> + <listitem> + <para> + A problem affecting Microsoft Internet Explorer 6 caused portal javascript module messages to remain in the window status area after the module had successfully loaded. This caused confusion if a customer was not aware a module had loaded, and saw the error message. The fix corrects the issue by clearing the window.status message after a javascript module is loaded. + </para> + </listitem> +</varlistentry> + </variablelist> </chapter> Added: epp/docs/branches/5.2/Release_Notes/en-US/needinfo.xml =================================================================== --- epp/docs/branches/5.2/Release_Notes/en-US/needinfo.xml (rev 0) +++ epp/docs/branches/5.2/Release_Notes/en-US/needinfo.xml 2012-03-16 04:28:51 UTC (rev 8613) @@ -0,0 +1,73 @@ +<?xml version='1.0'?> +<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> + +<chapter id = "needinfo_issues"> + <title>NEEDINFO</title> + + <para> + The following issues require more information from developers, or need to be processed by the lead writer before they can be approved for Release Note inclusion. + </para> + <remark> + These tickets will not be included in Release Notes as they currently stand. + This could be because the tickets have not been docs Ack'd (still at release_note?) + or the tickets have not been set to the correct resolution status (VERIFIED, CLOSED). + </remark> + <variablelist> + +<varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=793639" /></term> + <listitem> + <para> + If a user manually added users or groups into a Java Content Repository or LDAP, the required objects were not created because some necessary listeners were not called as they would be if the Organization API was used. This could result in exceptions in some situations, because the required JCR objects for a particular user or group were not correctly initialized. The fix introduces the CoreOrganizationInitializer plugin (exo.portal.component.initializer), which monitors the JCR and LDAP for changes and initiates the listeners when required. The plugin is disabled by default, but can be enabled by a portal administrator by uncommenting the block in JBOSS_HOME/server/[PROFILE]/deploy/gatein.ear/02portal.war/WEB-INF/conf/configuration.xml, which imports the static configuration stored in the initializer-configuration.xml file . + </para> + </listitem> +</varlistentry> + +<varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=793804" /></term> + <listitem> + <para> + CAUSE: when memberships of some user are changed (For example user root will remove user john from group /platform/users group), then user john won't see updates immediately. He needs to logout and login to see it. Example: +1) Start browser1, Go to http://localhost:8080/portal and login as john. User john is in group /platform/administrators by default, so he can see "Administrators" link in group menu, +2) Start browser2, Go to http://localhost:8080/portal and login as root. Go to OrganizationManagement and remove user john from /platform/administrators +3) Return to browser1 and refresh page. User john can still see "administrators" pages, which is a bug. +4) Logout and login again as john. Now "Administrators" are not longer visible. Bad is that john needs to logout and login, otherwise permissions for pages are not reflected. + +FIX: I added new listener "MembershipUpdateListener" into organization-configuration.xml file. This listener will update all memberships of logged user in ConversationRegistry, so that changes are immediately reflected in UI. + +RESULT: Changes are immediately reflected in UI. In previous example, user john won't see "Administrators" page in step 3, which is correct. + </para> + </listitem> +</varlistentry> + +<varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794235" /></term> + <listitem> + <para> + CAUSE: When user login, he can see his fullname in right top corner. This is his fullName according to format "firstName lastName" and it's hardcoded so that users can't use different format. It is also quite bad for some languages like Japanese, where is common to use opposite order as fullName. + +FIX: There is new field "Display Name" in UI in all screens where is possible to create or edit user. So user is able to fill his displayName and this displayName will be used in right top corner instead of fullName. DisplayName is not mandatory and when user is not using it, it fallback to fullName (old behaviour). This also ensure backward compatibility with older versions of EPP. Name of new attribute in Picketlink IDM database is "displayName" but as said before, attribute is not mandatory. + </para> + </listitem> +</varlistentry> + +<varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=793838" /></term> + <listitem> + <para> + Release notes docs status: Not Yet Documented + +Release notes: CAUSE: Previously it was possible to integrate EPP only with JOSSO 1.8.1 + +FIX: It's fixed in EPP SSO component, which has been updated in EPP to have the fix available. Now it's still possible to integrate with JOSSO 1.8.1 but also with newer versions like 1.8.2, 1.8.3, 1.8.4 and 1.8.5. + +There is changed JOSSO agent API between JOSSO versions 1.8.1 and 1.8.2, which means that we need to have slightly different packaging for JOSSO 1.8.1 and for JOSSO 1.8.2 and newer. + +It also affects documentation and related Docs issue is https://bugzilla.redhat.com/show_bug.cgi?id=794433 + </para> + </listitem> +</varlistentry> + + </variablelist> +</chapter> Modified: epp/docs/branches/5.2/Release_Notes/en-US/resolved.xml =================================================================== --- epp/docs/branches/5.2/Release_Notes/en-US/resolved.xml 2012-03-15 21:53:32 UTC (rev 8612) +++ epp/docs/branches/5.2/Release_Notes/en-US/resolved.xml 2012-03-16 04:28:51 UTC (rev 8613) @@ -5,9 +5,32 @@ <chapter id = "resolved"> <title>Resolved Issues</title> <para> - The following issues have been resolved in JBoss Enterprise Portal Platform 5.2.1. + The following issues have been resolved in JBoss Enterprise Portal Platform . </para> <variablelist> +<varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=793956" /></term> + <listitem> + <para> + Picketlink IDM did not support system property substitution in the configuration files. + +The fix implements parameters that allow system property substitution. Substitution is supported for every String element in the Picketlink IDM configuration file. The substitution operates in the same way as JBoss Enterprise Application Platform substitution. Usage examples follow. + +<itemizedlist> + <listitem> + <para>${property1} - Substitutes the system property &quot;property1&quot;.</para> + </listitem> + <listitem> + <para>${property1:defaultValue} - Substitutes the system property &quot;property1&quot;, and passes the &quot;defaultValue&quot; value if the system property is not set.</para> + </listitem> + <listitem> + <para>${property1,property2:defaultValue} - Substitutes the system property &quot;property1&quot;, then attempts to set the &quot;property2&quot; system property. If &quot;property1&quot; and &quot;property2&quot; are not set, fallback to &quot;defaultValue&quot;.</para> + </listitem> +</itemizedlist> + </para> + </listitem> +</varlistentry> + </variablelist> </chapter> Modified: epp/docs/branches/5.2/Release_Notes/publican.cfg =================================================================== --- epp/docs/branches/5.2/Release_Notes/publican.cfg 2012-03-15 21:53:32 UTC (rev 8612) +++ epp/docs/branches/5.2/Release_Notes/publican.cfg 2012-03-16 04:28:51 UTC (rev 8613) @@ -4,7 +4,5 @@ xml_lang: en-US type: Book brand: JBoss -#show_remarks: 1 -cvs_branch: DOCS-RHEL-6 -cvs_root: :ext:cvs.devel.redhat.com:/cvs/dist -cvs_pkg: JBoss_Enterprise_Portal_Platform-5.2.0_Release_Notes-5.2-web-__LANG__ +show_remarks: 1 +git_branch: docs-rhel-6