Author: jaredmorgs Date: 2012-09-07 00:41:40 -0400 (Fri, 07 Sep 2012) New Revision: 8845 Modified: epp/docs/branches/6.0/Release_Notes/en-US/5.2.2_Release_Notes.xml epp/docs/branches/6.0/Release_Notes/en-US/Book_Info.xml epp/docs/branches/6.0/Release_Notes/en-US/known.xml epp/docs/branches/6.0/Release_Notes/en-US/needinfo.xml epp/docs/branches/6.0/Release_Notes/en-US/resolved.xml Log: Updated RN to meet new BZ format requirements Modified: epp/docs/branches/6.0/Release_Notes/en-US/5.2.2_Release_Notes.xml =================================================================== --- epp/docs/branches/6.0/Release_Notes/en-US/5.2.2_Release_Notes.xml 2012-09-06 03:02:30 UTC (rev 8844) +++ epp/docs/branches/6.0/Release_Notes/en-US/5.2.2_Release_Notes.xml 2012-09-07 04:41:40 UTC (rev 8845) @@ -14,44 +14,43 @@ <para>By integrating open source frameworks such as JBoss Seam, Hibernate, Tomcat, and JBoss Cache, JBoss Enterprise Portal Platform takes advantage of innovations in the open source community. </para> <para>JBoss Enterprise Portal Platform &VZ; is fully tested and supported by Red Hat, and is certified to work on many leading enterprise hardware and software products.</para> </chapter> - <chapter id="Site_Publisher_Introduction"> - <title>What is Site Publisher</title> - <para> +<!--<chapter id="Site_Publisher_Introduction"> + <title>What is Site Publisher</title> + <para> JBoss Site Publisher (powered by eXo) is an add-on component for JBoss Enterprise Portal Platform. Site Publisher enables users to create, edit and publish rich web content within the context of their portal installation. </para> - <note> - <title>Subscription</title> - <para> + <note> + <title>Subscription</title> + <para> Subscriptions to JBoss Site Publisher are available at an additional fee over and above JBoss Enterprise Portal Platform subscriptions. </para> - </note> - <para> + </note> + <para> JBoss Site Publisher simplifies the authoring and management for every website an organization needs to deploy. It includes the ability to administer sites, manage navigation, and publish content. Site Publisher delivers powerful functionality to everyone responsible for maintaining web content: </para> - <itemizedlist> - <listitem> - <para> + <itemizedlist> + <listitem> + <para> Webmasters can easily administer multiple websites. </para> - </listitem> - <listitem> - <para> + </listitem> + <listitem> + <para> Website administrators can set permission policies according to user roles to better control website changes. </para> - </listitem> - <listitem> - <para> + </listitem> + <listitem> + <para> Content providers can use JBoss Enterprise Portal Platform’s tools to create content and then choose how to publish it using blogs, RSS feeds, social networks and more. </para> - </listitem> - <listitem> - <para> + </listitem> + <listitem> + <para> Web developers can introduce other forms of rich media content to create truly professional websites easily and efficiently. </para> - </listitem> - </itemizedlist> - </chapter> - <chapter id="Release_Notes-Installation"> + </listitem> + </itemizedlist> +</chapter>--> <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. @@ -260,22 +259,20 @@ </formalpara> </chapter> </part> - <part> - <title>Enterprise Portal Platform</title> -<!--<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"/> - </part> - <part> - <title>Site Publisher plug-in</title> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="sp_known.xml" encoding="XML"/> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="sp_resolved.xml" encoding="XML"/> -<!--<chapter id="Release_Notes-Issues_Resolved_Upstream"> - <title>Issues Resolved Upstream<remark>Issues Resolved Upstream</remark></title> - <para>This release contains Site Publisher issues resolved upstream by eXo Platform. The following major issues fixed by eXo Platform have been verified by the JBoss Enterprise Portal Platform Engineering team and included as part of this release. </para> - <para><remark>These issues have been pulled out of eXo Platform&apos;s JIRA instance using a modified version of JOT. The issues included here are CRITICAL and BLOCKER issues only. </remark></para> - <remark>An issue with my extraction script from eXo JIRA is preventing me from pulling out the following issues: https://jira.exoplatform.org/secure/IssueNavigator.jspa?requestId=14125&a... </remark> - <remark>The script is abandonware, and I have no other way of doing extraction.</remark> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="resolved_issues_eXo.xml" encoding="XML"/> -</chapter>--> </part> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.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="enhancement.xml" encoding="XML"/> +<!--<part> + <title>Site Publisher plug-in</title> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="sp_known.xml" encoding="XML"/> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="sp_resolved.xml" encoding="XML"/> + <chapter id="Release_Notes-Issues_Resolved_Upstream"> + <title>Issues Resolved Upstream<remark>Issues Resolved Upstream</remark></title> + <para>This release contains Site Publisher issues resolved upstream by eXo Platform. The following major issues fixed by eXo Platform have been verified by the JBoss Enterprise Portal Platform Engineering team and included as part of this release. </para> + <para><remark>These issues have been pulled out of eXo Platform&apos;s JIRA instance using a modified version of JOT. The issues included here are CRITICAL and BLOCKER issues only. </remark></para> + <remark>An issue with my extraction script from eXo JIRA is preventing me from pulling out the following issues: https://jira.exoplatform.org/secure/IssueNavigator.jspa?requestId=14125&a... </remark> + <remark>The script is abandonware, and I have no other way of doing extraction.</remark> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="resolved_issues_eXo.xml" encoding="XML"/> + </chapter> +</part>--> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/> </book> Modified: epp/docs/branches/6.0/Release_Notes/en-US/Book_Info.xml =================================================================== --- epp/docs/branches/6.0/Release_Notes/en-US/Book_Info.xml 2012-09-06 03:02:30 UTC (rev 8844) +++ epp/docs/branches/6.0/Release_Notes/en-US/Book_Info.xml 2012-09-07 04:41:40 UTC (rev 8845) @@ -2,8 +2,8 @@ <!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> <bookinfo id="arti-Release_Notes-Release_Notes"> - <title>5.2.2 Release Notes</title> - <subtitle>For use with JBoss Enterprise Portal Platform &VZ;, and the Site Publisher plug-in.</subtitle> + <title>6.0 Release Notes</title> + <subtitle>For use with JBoss Enterprise Portal Platform &VZ;.</subtitle> <productname>JBoss Enterprise Portal Platform</productname> <productnumber>5.2</productnumber> <edition>5.2.2</edition> Modified: epp/docs/branches/6.0/Release_Notes/en-US/known.xml =================================================================== --- epp/docs/branches/6.0/Release_Notes/en-US/known.xml 2012-09-06 03:02:30 UTC (rev 8844) +++ epp/docs/branches/6.0/Release_Notes/en-US/known.xml 2012-09-07 04:41:40 UTC (rev 8845) @@ -1,29 +1,6 @@ -<?xml version='1.0' encoding='UTF-8'?> -<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -]> -<chapter id="known_issues"> - <title>Known issues</title> - <para> - The following issues are known to exist in this release of JBoss Enterprise Portal Platform, and will be fixed in a subsequent release. - </para> - <variablelist> -<!--<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=801821"> - <citetitle>BZ#801821</citetitle> - </ulink> - Ensure that starter web application is always started last</term> - <listitem> - <remark>Status: CLOSED</remark> - <para> - If portal extension project is named with lowercase letter, it is possible that it starts later then necessary services, and throws java.lang.IllegalStateException. To workaround this issue, always use an uppercase first letter. This current functionality will be improved in a future release. - </para> - </listitem> -</varlistentry>--> <varlistentry> - <term> - <ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=793816">BZ#... - </term> - <listitem> - <para>The platform did not support JTA in previous releases. There were some problems related to it, particularly the fact that without JTA support, there was a need to obtain DB connection for IDM database for each HTTP request of logged user. In some environments, this requirement may cause problems related to a lack of DB connections and introduce performance issues. To work around the issue, it is possible to configure the platform for JTA support. Configuring JTA support may reduce the number of DB connections opened against an IDM database. JTA is disabled by default. To enable JTA support, follow the procedure in <ulink url="https://community.jboss.org/wiki/JTAIntegrationWithGateIn"...;, while observing the following caveats to the procedure: replace &quot;gatein-idm&quot; and &quot;gatein-jcr&quot; with &quot;jdbcidm&quot; and &quot;jdbcjcr&quot; respectively; step 2 (JCR configuration of DataSourceProvider) is not needed because it is enabled by default in t! he platform.</para> - </listitem> - </varlistentry> - </variablelist> +<?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="known"> +<title>Known Issues</title> +<para>There are no Known issues in this release.</para> </chapter> Modified: epp/docs/branches/6.0/Release_Notes/en-US/needinfo.xml =================================================================== --- epp/docs/branches/6.0/Release_Notes/en-US/needinfo.xml 2012-09-06 03:02:30 UTC (rev 8844) +++ epp/docs/branches/6.0/Release_Notes/en-US/needinfo.xml 2012-09-07 04:41:40 UTC (rev 8845) @@ -1,10 +1,19 @@ -<?xml version='1.0' encoding='UTF-8'?> +<?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> + +<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&apos;d (still at release_note?) or the tickets have not been set to the correct resolution status (VERIFIED, CLOSED). </remark> + <remark> + These tickets will not be included in Release Notes as they currently stand. + This could be because the tickets have not been processed by the docs lead (still at required_doc_text?), + or the tickets have not been set to the correct resolution status (VERIFIED, CLOSED). + </remark> + <variablelist> + + </variablelist> </chapter> Modified: epp/docs/branches/6.0/Release_Notes/en-US/resolved.xml =================================================================== --- epp/docs/branches/6.0/Release_Notes/en-US/resolved.xml 2012-09-06 03:02:30 UTC (rev 8844) +++ epp/docs/branches/6.0/Release_Notes/en-US/resolved.xml 2012-09-07 04:41:40 UTC (rev 8845) @@ -1,314 +1,6 @@ -<?xml version='1.0' encoding='UTF-8'?> -<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -]> +<?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="resolved"> - <title>Resolved issues</title> - <para> - The following issues have been resolved in this release of JBoss Enterprise Portal Platform. - </para> - <variablelist> - <varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=793425"> - <citetitle>BZ#793425</citetitle> - </ulink> - Creating user with user name differing only in case-sensitive case pop-ups unknown error</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> - Picketlink IDM was performing case-sensitive comparison of user and group names with information stored in OpenDS. Because OpenDS does not record user and group names in a case-sensitive manner by default, cased user names such as &quot;viLiam&quot; were not distinguishable from the user name &quot;viliam&quot;. This issue affected search retrieval, as well as user and group creation. The issue can be fixed by configuring Picketlink IDM to compare user and group names in a case-insensitive way. In picketlink-idm-config.xml, change the LDAPIdentityStore option &quot;allowNotCaseSensitiveSearch&quot; to true. Setting this option will prevent any Picketlink IDM exceptions relating to case insensitivity. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794403"> - <citetitle>BZ#794403</citetitle> - </ulink> - Example skin looks scattered on the right side</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> - An issue with the width of .UIWorkingWorkspace .UIPageBody set in the default skin was not suitable for SimpleSkin distributed with the Application Server. The incompatibility caused the right border of #UIPageBody to shift left and be hidden under the JBoss Enterprise Portal Platform banner. The fix introduces an override to the element causing the border shift, with a specific alignment rule that sets the width to auto. The border of #UIPageBody is now rendered properly, aligned with the breadcrumbs panel above it. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=795937"> - <citetitle>BZ#795937</citetitle> - </ulink> - Add SCP Documentation to Administration Guide for GateIn Management</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> - Secure Copy documentation was missing from the Administration Guide. The SCP information is now present in the Administration Guide for Management Extensions and Command Line Interface chapters. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=798801"> - <citetitle>BZ#798801</citetitle> - </ulink> - Fix the sample portal data-source file.</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> - It was discovered that the gatein-sample-portal-ds.xml file shipped with the application server was out of sync with the gatein-ds.xml file. Customers that used the sample portal data-source file experienced issues when the file was deployed together with gatein-sample-portal.ear. Errors were logged to the application server&apos;s log, and the sample portal would not correctly start. The fix re-bases gatein-sample-portal-ds.xml in line with gatein-ds.xml with the following fixes: The IDM database configuration is declared before JCR; The Hypersonic data file location is now specified under the gatein /conf directory; and the IDM datastore was changed from local-tx-datasource to no-tx-datasource. When gatein-sample-portal-ds.xml is deployed with gatein-sample-portal.ear, the sample portal starts, and can be visited using http://localhost:8080/sample-portal. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=803776"> - <citetitle>BZ#803776</citetitle> - </ulink> - Disable exposure of JMX stats for anonymous caches</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> - It was discovered that exposing information for anonymous caches using JMX resulted in too much information being exposed. The configuration has been changed to ensure JMX stats for anonymous caches display the correct information. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=807012"> - <citetitle>BZ#807012</citetitle> - </ulink> - Remove possibly unused JARs from gatein.ear/lib</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> - It was discovered that the gatein.ear archive contained JAR files that were not required in the enterprise version of the product. The fix removes the unnecessary JAR files. JAR files applicable to both community and enterprise builds are retained for platform stability. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=807279"> - <citetitle>BZ#807279</citetitle> - </ulink> - Support WSRP applications for Export/Import</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> - When WSRP is added to a page, and a user attempts to export the page using the portal management functions, an exception displays stating WSRP is not supported. This issue is being investigated, and will be included in a future release of the portal. There is no workaround to this issue. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=809141"> - <citetitle>BZ#809141</citetitle> - </ulink> - Sample extension datasource uses local-tx-datasource type</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> - It was discovered that the sample datasource file for portal extensions -<filename>jboss-as/docs/examples/portal/gatein-sample-portal-ds.xml</filename> specifies the incorrect datasource type for IDM. It should be no-tx-datasource for IDM and -local-tx-datasource for JCR, instead of local-tx-datasource for both directive blocks. To work around the issue, define the datasource type manually, following the guidelines in this Release Note. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=809777"> - <citetitle>BZ#809777</citetitle> - </ulink> - Improvement for the error handling of JCR index build error or node corruption</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> - It was discovered that if the JCR index is broken, JCR stops. This caused a JCR index build error or node corruption during portal and Site Publisher start-up. The fix includes upgrades to the JCR which allows the portal to start correctly and log the data corruption, rather instead of failing to start. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=812657"> - <citetitle>BZ#812657</citetitle> - </ulink> - error when add new group the same with existing but different with lower and upper case on MySQL</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> - Picketlink IDM was performing case-sensitive comparison of group names with information stored in MySQL DB. Because MySQL DB does not record group names in a case-sensitive manner by default, cased group names such as &quot;TEST_group&quot; were not distinguishable from the group name &quot;test_group&quot;. This issue affected search retrieval, as well as group creation. The issue can be fixed by configuring Picketlink IDM to compare group names in case-insensitive way. In picketlink-idm-config.xml, change the HibernateIdentityStore option &quot;allowNotCaseSensitiveSearch&quot; to true. Setting this option will prevent any Picketlink IDM exceptions relating to case insensitivity. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=813388"> - <citetitle>BZ#813388</citetitle> - </ulink> - Special characters in a text file content is not correctly encoded after uploading.</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> - An issue with the view template for text files was not displaying special characters correctly in files that were uploaded. After uploading a text file which contained &quot;ááááá ã ã ã óóóó&quot;, displaying the text file content in ContentExplorer would reveal the following: &quot;&aacute;&aacute;&aacute;&aacute;&aacute; &atilde; &atilde; &atilde; &oacute;&oacute;&oacute;&oacute;&quot;. The issue was not present in the ContentExplorer WYSIWYG editor. The fix introduces improvements to ContentExplorer that removes the double-encoding, which results in special characters being displayed correctly. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=813729"> - <citetitle>BZ#813729</citetitle> - </ulink> - EPP configuration files use multiple version of kernel XSD definition</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> - It was discovered that several versions of kernel_1_*.xsd were referenced in XML configuration files. While no harmful consequences existed by having these obsolete templates declared, it made the XML files appear inconsistent. The fix removes all kernel_1_[^2].xsd, and replaces these references with kernel_1_2.xsd which makes the XML configuration files consistent. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=813751"> - <citetitle>BZ#813751</citetitle> - </ulink> - Portlet Bridge - NPE when loading styles via link element</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> - Documentation quoted that the &lt;link&gt; element could be used to import Rich Faces XCSS scripts and style-sheets using the following syntax:</para> - <programlisting>&lt;link type=&quot;text/css&quot; rel=&quot;stylesheet&quot; href=&quot;/richFacesPortlet/faces/rfRes/org/richfaces/skin.xcss&quot;/&gt;</programlisting> - <para>This syntax is no longer correct, and results in a NPE. To correct the issue, use a4j:loadstyle to import the scripts and style-sheets when using LoadStyleStrategy and LoadScriptStrategy of NONE:</para> - <programlisting>&lt;a4j:loadScript src=&quot;resource:////org/ajax4jsf/framework.pack.js&quot; type=&quot;text/javascript&quot;/&gt; - &lt;a4j:loadScript src=&quot;resource:////org/richfaces/ui.pack.js&quot; type=&quot;text/javascript&quot;/&gt; - &lt;a4j:loadStyle src=&quot;resource:////org/richfaces/skin.xcss&quot;/&gt;</programlisting> - </listitem> - </varlistentry> - <varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=818565"> - <citetitle>BZ#818565</citetitle> - </ulink> - Portal container name is hard-coded in the LocalizationFilter</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> - A hard-coded portal container name in the LocalizationFilter caused a NPE (NULL container) if the default context path was changed. The fix introduces changes to the way the portal container name is parsed by the LocalizationFilter, which corrects the issue. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=824855"> - <citetitle>BZ#824855</citetitle> - </ulink> - Strange duplicated requests in gadget rendering</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> - It was discovered that certain gadgets on the dashboard were sending more requests then necessary. The unnecessary requests caused a performance impact on page loading times. The fix implements changes to how gadgets are rendered. Each gadget is rendered individually, and only loads necessary data which fixes the performance issue. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=824860"> - <citetitle>BZ#824860</citetitle> - </ulink> - Error while rendering doodle gadget when source is dead</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> - When the Doodle gadget was added to a dashboard, and the source website supplying the gadget metadata was unavailable, the gadget was not loaded, and a user interface error occurred. The fix introduces a more informative error message to all gadgets that require external sources, which displays in the user interface at the time the error occurs. This helps the user diagnose the problem easier, and fixes the issue. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=824863"> - <citetitle>BZ#824863</citetitle> - </ulink> - groovy template should not print &quot;null&quot; string when variable is null</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> - If a GateIn Template file (*.gtmpl) contained an &lt;input&gt; directive that declared a variable as a value, and that variable resolved to null, the word &quot;null&quot; would be substituted for the value instead of the value parameter being present, but undefined. For example, &lt;input class=&quot;key&quot; type=&quot;text&quot; name=&quot;key&quot; value=&quot;${key}&quot;/&gt; resolved to &lt;input class=&quot;key&quot; type=&quot;text&quot; name=&quot;key&quot; value=&quot;null&quot;/&gt;, instead of &lt;input class=&quot;key&quot; type=&quot;text&quot; name=&quot;key&quot; value/&gt;. The fix corrects the way null values are handled, and now prints undefined parameters, instead of printing null as the parameter value. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=824907"> - <citetitle>BZ#824907</citetitle> - </ulink> - Add ability to deactivate URL rewriting on WSRP producer</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> - In the current WSRP implementation, the producer URL is rewritten at consumer side so it can be accessed remotely. -If users have static content at both the producer and consumer sides, they do not expect those resources to be accessed from a remote producer. In these circumstances, it was desirable to disable URL rewriting, however no such mechanism existed. The fix includes enhancements to the WSRP, with the addition of the &quot;org.gatein.wsrp.producer.deactivateURLRewriting&quot;. If the parameter is set to true, URL rewriting is disabled. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=829885"> - <citetitle>BZ#829885</citetitle> - </ulink> - X.509 token in ws-security support in WSRP</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> - It was discovered that JBossWS supports X.509 token with WSSE, however the functionality only partially worked. It was not possible to encrypt the entire message. The fix introduces improvements to this aspect of JBossWS in WSRP, and corrects the issue. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=831445"> - <citetitle>BZ#831445</citetitle> - </ulink> - WSRP is failing when including OASIS WSRP WSDL</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> - OASIS changed the way HTTP WSRP WSDL requests were redirected. The requests redirected to a HTTP 302 response that included an XML document with a public ID, but no system ID. This caused an exception &quot;SAXParseException: White spaces are required between publicId and systemId&quot; to be raised. -The fix introduces changes to the JBossWS entity resolver, which now uses the WSDLs and XSDs placed in the unzipped folder instead of the ones from the OASIS website. -This corrects the issue, and restores expected functionality to Netunity v1 &amp; v2. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=832089"> - <citetitle>BZ#832089</citetitle> - </ulink> - WSRP: getPortletProperties doesn&apos;t behave properly when en empty set of property names is passed</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> - A problem detected with reading preferences from WLP 10.0.1 through a WSRP V1 endpoint caused the portlet properties to raise a NPE as a result of the interaction. This issue has been fixed in the affected WSRP component, and the component updated for this release. Reading the portlet properties via WSRP V1 now works as expected. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=835369"> - <citetitle>BZ#835369</citetitle> - </ulink> - WSRP: The supportedOptions element in the producers response to a getServiceDescription request is missing the supported features</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> - The WSRP Producer was ignoring several optional elements when returning a service description response to the consumer, including the supportedOptions element. WSRP Consumers that were relying on these optional elements to tailor their communication with the producer could behave improperly based on wrong assumptions due to missing (though optional) information. The WSRP Producer now properly emits the supportedOptions element in its service description response, which allows Consumers to properly tailor their behavior, and results in improved interoperability with third-party consumers. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=835375"> - <citetitle>BZ#835375</citetitle> - </ulink> - Patch to enhance WSRP producers response to a getServiceDescription request</term> - <listitem> - <remark>Status: CLOSED</remark> - <para> - A number of issues were discovered: 1) WSRP: getPortletProperties doesn&apos;t behave properly when en empty set of property names is passed; 2) WSRP type factories require a lang value to create a Property even though it&apos;s optional according to XSD. This caused the requests to be rejected by the server with an IllegalArgumentException: &apos;Property requires a non-null, non-empty language. The fix applies a patch to the affected files which corrects the issue. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=835578"> - <citetitle>BZ#835578</citetitle> - </ulink> - Open an &quot;Identity Transaction&quot; only when it is necessary</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> - Hibernate transactions had to be started for each HTTP request from an anonymous or authenticated user, which in turn required a new database connection from the connection pool (an expensive operation if it is not required for the request). The fix enables a new option, &quot;lazyStartOfHibernateTransaction&quot;, which is set in gatein.ear/02portal.war/WEB-INF/conf/organization/picketlink-idm/picketlink-idm-config.xml. -</para> - <programlisting> -&lt;option&gt; - &lt;name&gt;lazyStartOfHibernateTransaction&lt;/name&gt; - &lt;value&gt;false&lt;/value&gt; - &lt;/option&gt; -</programlisting> - <para>If the value is set to true, the Hibernate transaction is started only when required, and not for every request. The default value is false for backwards-compatibility. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=837029"> - <citetitle>BZ#837029</citetitle> - </ulink> - Change of JBC configuration - LRU algorithm + separate configuration for portal-system workspace</term> - <listitem> - <remark>Status: VERIFIED</remark> - <para> - A change made to the JBoss Cache cache algorithm caused performance issues for some configuration scenarios. The fix introduces configuration with an improved algorithm. The new algorithm references a new configuration file, which now loads correctly. This corrects the performance issues. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=838973"> - <citetitle>BZ#838973</citetitle> - </ulink> - Dashboard pages with special characters</term> - <listitem> - <remark>Status: CLOSED</remark> - <para> - A change to how dashboard page names were validated in another issue caused dashboard page names containing special characters to no longer be considered as invalid. If a dashboard name contains a special character, it is now replaced with an underscore in the URL. This new functionality will be added to the Dashboard Portlet section of the User Guide in a future release. - </para> - </listitem> - </varlistentry> - </variablelist> +<title>Resolved Issues</title> +<para>There are no Resolved Issues in this release.</para> </chapter>