From do-not-reply at jboss.org Thu Aug 30 19:18:34 2012 Content-Type: multipart/mixed; boundary="===============1376988670308266981==" MIME-Version: 1.0 From: do-not-reply at jboss.org To: gatein-commits at lists.jboss.org Subject: [gatein-commits] gatein SVN: r8837 - epp/docs/branches/5.2/Release_Notes/en-US. Date: Thu, 30 Aug 2012 19:18:34 -0400 Message-ID: <201208302318.q7UNIYjt011872@svn01.web.mwc.hst.phx2.redhat.com> --===============1376988670308266981== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Author: jaredmorgs Date: 2012-08-30 19:18:33 -0400 (Thu, 30 Aug 2012) New Revision: 8837 Modified: epp/docs/branches/5.2/Release_Notes/en-US/5.2.2_Release_Notes.xml epp/docs/branches/5.2/Release_Notes/en-US/Revision_History.xml epp/docs/branches/5.2/Release_Notes/en-US/known.xml epp/docs/branches/5.2/Release_Notes/en-US/needinfo.xml epp/docs/branches/5.2/Release_Notes/en-US/resolved.xml epp/docs/branches/5.2/Release_Notes/en-US/sp_known.xml epp/docs/branches/5.2/Release_Notes/en-US/sp_needinfo.xml epp/docs/branches/5.2/Release_Notes/en-US/sp_resolved.xml Log: Final draft before release push Modified: epp/docs/branches/5.2/Release_Notes/en-US/5.2.2_Release_Notes.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- epp/docs/branches/5.2/Release_Notes/en-US/5.2.2_Release_Notes.xml 2012-= 08-30 12:52:33 UTC (rev 8836) +++ epp/docs/branches/5.2/Release_Notes/en-US/5.2.2_Release_Notes.xml 2012-= 08-30 23:18:33 UTC (rev 8837) @@ -62,7 +62,8 @@ Component Versions - Updated table from https://docspace.corp.redhat.com/do= cs/DOC-68705 (version 27) + Updated table from https://docspace.corp.redhat.com/docs/DOC= -68705 (version 33) + 20120831 - Just checking that REVISION 33 of the docspace ab= ove is the FINAL version. I note it still contains CR versions of component= s. Component Versions @@ -195,43 +196,44 @@
- - Upgraded Components - - New Components - The following new components warrant special mention. - - NEEDINFO: anything we need to mention here? - - Updated Components - The following updated components warrant special mention. - - NEEDINFO: anything we need to mention here? - - For detailed information about component versions included i= n this release, refer to - - - + Documentation An Installation Guide and a Use= r Guide for JBoss Enterprise Portal Platform are available at <= ulink url=3D"http://access.redhat.com/knowledge/docs/JBoss_Enterprise_Porta= l_Platform/" type=3D"http"/>. JBoss Enterprise Portal Platform specific doc= umentation is also available from this location, as is Site Publisher docum= entation. @@ -261,21 +263,20 @@ Enterprise Portal Platform - - + Site Publisher Plug-in - - Issues Resolved Upstream<remark>Issues Resolved Upstream</rem= ark> - This release contains Site Publisher issues resolved upstream= by eXo Platform. The following major issues fixed by eXo Platform have bee= n verified by the JBoss Enterprise Portal Platform Engineering team and inc= luded as part of this release. - 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. - An issue with my extraction script from eXo JIRA is preventi= ng me from pulling out the following issues: https://jira.exoplatform.org/s= ecure/IssueNavigator.jspa?requestId=3D14125&mode=3Dhide - The script is abandonware, and I have no other way of doing = extraction. - - + Modified: epp/docs/branches/5.2/Release_Notes/en-US/Revision_History.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- epp/docs/branches/5.2/Release_Notes/en-US/Revision_History.xml 2012-08-= 30 12:52:33 UTC (rev 8836) +++ epp/docs/branches/5.2/Release_Notes/en-US/Revision_History.xml 2012-08-= 30 23:18:33 UTC (rev 8837) @@ -6,6 +6,34 @@ + 5.2.2-4 + Fri Aug 31 2012 + + Jared + Morgan + + + + + Release Notes FINAL draft with all comments and feedba= ck incorporated. + + + + + 5.2.2-3 + Tue Aug 28 2012 + + Jared + Morgan + + + + + Release Notes draft with all issues currently flagged = in BZ as requiring release notes as of the date in this revision entry. + + + + 5.2.2-2 Tue Aug 21 2012 Modified: epp/docs/branches/5.2/Release_Notes/en-US/known.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- epp/docs/branches/5.2/Release_Notes/en-US/known.xml 2012-08-30 12:52:33= UTC (rev 8836) +++ epp/docs/branches/5.2/Release_Notes/en-US/known.xml 2012-08-30 23:18:33= UTC (rev 8837) @@ -1,38 +1,33 @@ - + - - - Known Issues - = - + + Known Issues + The following issues are known to exist in this release of JBoss= Enterprise Portal Platform, and will be fixed in a subsequent release. - - Do some of these issues look more like Resolved Issues<= /emphasis>? If they do, its because the ticket has not been set to the corr= ect = - Resolved Issue status (VERIFIED, CLOSED). - - - - - BZ#795937 - Add SCP Documentation to Admi= n Guide for GateIn Management - - Status: ON_QA - - Secure Copy documentation was missing from the Administration Gui= de. The SCP information is now present in the Administration Guide for Mana= gement Extensions and Command Line Interface chapters. + BZ#801821 removed from document at the request of theute. + + + + BZ#838973 + - Dashboard pages with special characters + + Status: CLOSED + + A change to how dashboard page names were validated in another is= sue 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 w= ill be added to the Dashboard Portlet section of the User Guide in a future= release. - - - - + + + Modified: epp/docs/branches/5.2/Release_Notes/en-US/needinfo.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- epp/docs/branches/5.2/Release_Notes/en-US/needinfo.xml 2012-08-30 12:52= :33 UTC (rev 8836) +++ epp/docs/branches/5.2/Release_Notes/en-US/needinfo.xml 2012-08-30 23:18= :33 UTC (rev 8837) @@ -1,110 +1,10 @@ - + - - - NEEDINFO - = - + + NEEDINFO + The following issues require more information from developers, o= r need to be processed by the lead writer before they can be approved for R= elease Note inclusion. - - These tickets will not be included in Release Notes as they curre= ntly 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). - - - - - BZ#801821 - Ensure that starter web appli= cation is always started last - - The status is CLOSED, assigned to hfnukal(a)redhat.com. - - NEEDINFO: What needs to be mentioned in the doc specifically? - -CAUSE: - -CONSEQUENCE: - -FIX: - -RESULT: - - - - - - BZ#813751 - Portlet Bridge - NPE when loa= ding styles via link element - - The status is VERIFIED, assigned to kfinniga(a)redhat.com. - - Documentation quoted that the <link> element could be used = to import Rich Faces XCSS scripts and stylesheets using the following synta= x:<link type=3D"text/css" rel=3D"s= tylesheet" href=3D"/richFacesPortlet/faces/rfRes/org/richfaces/sk= in.xcss"/>This syntax is no longer correct, = and results in a NPE. To correct the issue, use a4j:loadstyle to import the= scripts and stylesheets when using LoadStyleStrategy and LoadScriptStrateg= y of NONE:<a4j:loadScript src=3D"resource://= //org/ajax4jsf/framework.pack.js" type=3D"text/javascript"/&= gt; - <a4j:loadScript src=3D"resource:////org/richfaces/ui.pack.js&q= uot; type=3D"text/javascript"/> - <a4j:loadStyle src=3D"resource:////org/richfaces/skin.xcss&quo= t;/> - - - - - BZ#824863 - groovy template should not pr= int "null" string when variable is null - - The status is ON_QA, assigned to hfnukal(a)redhat.com. - - If a GateIn Template file (*.gtmpl) contained an <input> di= rective that declared a variable as a value, and that variable resolved to = null, the word "null" would be substituted for the value instead of the val= ue parameter being present, but undefined. For example, <input class=3D"= key" type=3D"text" name=3D"key" value=3D"${key}"/> resolved to <input= class=3D"key" type=3D"text" name=3D"key" value=3D"null"/>, instead of &= lt;input class=3D"key" type=3D"text" name=3D"key" value/>. The fix corr= ects the way null values are handled, and now prints undefined parameters, = instead of printing null as the parameter value. - - - - - - BZ#835369 - WSRP: The supportedOptions el= ement in the producers response to a getServiceDescription request is missi= ng the supported features - - The status is VERIFIED, assigned to claprun(a)redhat.com. - - CAUSE: - -CONSEQUENCE: - -FIX: - -RESULT: - - - - - - BZ#835375 - Patch to enhance WSRP produce= rs response to a getServiceDescription request - - The status is CLOSED, assigned to mweiler(a)redhat.com. - - Is a RN required for this issue? If so, please write CCFR. - -CAUSE: - -CONSEQUENCE: - -FIX: - -RESULT: - - - - - - BZ#835578 - Open an "Identity Transaction= " only when it is necessary - - The status is VERIFIED, assigned to mposolda(a)redhat.com. - - Hibernate transactions had to be started for each HTTP request fr= om an anonymous or authenticated user, which in turn required a new databas= e connection from the connection pool (an expensive operation if it is not = required for the request). The fix enables a new option, "lazyStartOfHibern= ateTransaction", which is set in gatein.ear/02portal.war/WEB-INF/conf/organ= ization/picketlink-idm/picketlink-idm-config.xml. = - - -<option> - <name>lazyStartOfHibernateTransaction</name> - <value>false</value> - </option> - -If the value is set to true, the Hibernate transaction is started on= ly when required, and not for every request. The default value is false for= backwards-compatibility. - - - - - + These tickets will not be included in Release Notes as they cur= rently 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). Modified: epp/docs/branches/5.2/Release_Notes/en-US/resolved.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- epp/docs/branches/5.2/Release_Notes/en-US/resolved.xml 2012-08-30 12:52= :33 UTC (rev 8836) +++ epp/docs/branches/5.2/Release_Notes/en-US/resolved.xml 2012-08-30 23:18= :33 UTC (rev 8837) @@ -1,125 +1,303 @@ - + - - - Resolved Issues - + + Resolved Issues + The following issues have been resolved in this release of JBoss Ent= erprise Portal Platform. = - - - - BZ#793425 - Creating user with username d= iffering only in case-senstive case popups unknown error - - Status: VERIFIED - - Picketlink IDM was performing case-sensitive comparison of user a= nd group names with information stored in OpenDS. Because OpenDS does not r= ecord user and group names in a case-sensitive manner by default, cased use= r names such as "viLiam" were not distinguishable from the user name "vilia= m". This issue affected search retrieval, as well as user and group creatio= n. 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, chang= e the LDAPIdentityStore option "allowNotCaseSensitiveSearch" to true. Setti= ng this option will prevent any Picketlink IDM exceptions relating to case = insensitivity. + + + + BZ#793425 + - Creating user with username differing only in case-sens= tive case popups unknown error + + Status: VERIFIED + + Picketlink IDM was performing case-sensitive comparison of user a= nd group names with information stored in OpenDS. Because OpenDS does not r= ecord user and group names in a case-sensitive manner by default, cased use= r names such as "viLiam" were not distinguishable from the user n= ame "viliam". This issue affected search retrieval, as well as us= er 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-i= dm-config.xml, change the LDAPIdentityStore option "allowNotCaseSensit= iveSearch" to true. Setting this option will prevent any Picketlink ID= M exceptions relating to case insensitivity. - - - - - BZ#794403 - Example skin looks scattered = on the right side - - Status: VERIFIED - + + + + + BZ#794403 + - Example skin looks scattered on the right side + + Status: VERIFIED + An issue with the width of .UIWorkingWorkspace .UIPageBody set in= the default skin was not suitable for SimpleSkin distributed with the Appl= ication Server. The incompatibility caused the right border of #UIPageBody = to shift left and be hidden under the JBoss Enterprise Portal Platform bann= er. 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 a= bove it. - - - - - BZ#798801 - Fix the sample portal datasou= rce file. - - Status: VERIFIED - - It was discovered that the gatein-sample-portal-ds.xml file shipp= ed with the application server was out of sync with the gatein-ds.xml file.= Customers that used the sample portal datasource file experienced issues w= hen the file was deployed together with gatein-sample-portal.ear. Errors we= re logged to the application server's log, and the sample portal would not = correctly start. The fix rebases gatein-sample-portal-ds.xml in line with g= atein-ds.xml with the following fixes: The IDM database configuration is de= clared 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 deploy= ed with gatein-sample-portal.ear, the sample portal starts, and can be visi= ted using http://localhost:8080/sample-portal. + + + + + BZ#795937 + - Add SCP Documentation to Admin Guide for GateIn Managem= ent + + Status: VERIFIED + + Secure Copy documentation was missing from the Administration Gui= de. The SCP information is now present in the Administration Guide for Mana= gement Extensions and Command Line Interface chapters. - - - - - BZ#807012 - Remove possibly unused JARs f= rom gatein.ear/lib - - Status: VERIFIED - + + + + + BZ#798801 + - Fix the sample portal datasource file. + + Status: VERIFIED + + It was discovered that the gatein-sample-portal-ds.xml file shipp= ed with the application server was out of sync with the gatein-ds.xml file.= Customers that used the sample portal datasource file experienced issues w= hen the file was deployed together with gatein-sample-portal.ear. Errors we= re logged to the application server's log, and the sample portal would= not correctly start. The fix rebases gatein-sample-portal-ds.xml in line w= ith 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 loc= al-tx-datasource to no-tx-datasource. When gatein-sample-portal-ds.xml is d= eployed with gatein-sample-portal.ear, the sample portal starts, and can be= visited using http://localhost:8080/sample-portal. + + + + + + BZ#803776 + - Disable exposure of jmx stats for anonymous caches + + Status: VERIFIED + + It was discovered that exposing information for anonymous caches = using JMX resulted in too much information being exposed. The configuratio= n has been changed to ensure JMX stats for anonymous caches display the cor= rect information. + + + + + + BZ#807012 + - Remove possibly unused JARs from gatein.ear/lib + + Status: VERIFIED + It was discovered that the gatein.ear archive contained JAR files= that were not required in the enterprise version of the product. The fix r= emoves the unnecessary JAR files. JAR files applicable to both community an= d enterprise builds are retained for platform stability. - - - - - BZ#807279 - Support WSRP applications for= Export/Import - - Status: VERIFIED - + + + + + BZ#807279 + - Support WSRP applications for Export/Import + + Status: VERIFIED + When WSRP is added to a page, and a user attempts to export the p= age using the portal management functions, an exception displays stating WS= RP 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. - - - - - BZ#809141 - Sample extension datasource u= ses local-tx-datasource type - - Status: VERIFIED - - It was discovered that the sample datasource file for portal exte= nsions -jboss-as/docs/examples/portal/gatein-sample-portal-ds.xml specifies the incorrect datasource type for IDM. It should be no-tx-da= tasource for IDM and + + + + + BZ#809141 + - Sample extension datasource uses local-tx-datasource ty= pe + + Status: VERIFIED + + It was discovered that the sample datasource file for portal exte= nsions +jboss-as/docs/examples/portal/gatein-sample-portal-ds.xml specifies the incorrect datasource type for IDM. It should be no-tx-da= tasource for IDM and local-tx-datasource for JCR, instead of local-tx-datasource for both direc= tive blocks. To work around the issue, define the datasource type manually,= following the guidelines in this Release Note. - - - - - BZ#812657 - error when add new group the = same with existing but different with lower and upper case on mysql - - Status: VERIFIED - - 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 "TEST_group" were not distinguishable from the group name "test_group". = 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-i= nsensitive way. In picketlink-idm-config.xml, change the HibernateIdentityS= tore option "allowNotCaseSensitiveSearch" to true. Setting this option will= prevent any Picketlink IDM exceptions relating to case insensitivity. + + + + + BZ#809777 + - Improvement for the error handling of JCR index build e= rror or node corruption + + Status: VERIFIED + + It was discovered that if the JCR index is broken, JCR stops. Thi= s 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 p= ortal to start correctly and log the data corruption, rather instead of fai= ling to start. - - - - - BZ#813729 - EPP configuration files use m= ultiple version of kernel xsd definition - - Status: VERIFIED - + + + + + BZ#812657 + - error when add new group the same with existing but dif= ferent with lower and upper case on mysql + + Status: VERIFIED + + 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 "TEST_group" were not distinguishable from the group name &quo= t;test_group". This issue affected search retrieval, as well as group = creation. The issue can be fixed by configuring Picketlink IDM to compare g= roup names in case-insensitive way. In picketlink-idm-config.xml, change th= e HibernateIdentityStore option "allowNotCaseSensitiveSearch" to = true. Setting this option will prevent any Picketlink IDM exceptions relati= ng to case insensitivity. + + + + + + BZ#813388 + - Special characters in a text file content is not correc= tly encoded after uploading. + + Status: VERIFIED + + 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 "=C3=A1=C3=A1=C3=A1=C3=A1=C3=A1 =C3=A3 =C3= =A3 =C3=A3 =C3=B3=C3=B3=C3=B3=C3=B3", displaying the text file content= in ContentExplorer would reveal the following: "áá&aacu= te;áá ã ã ã óóó&oac= ute;". The issue was not present in the ContentExplorer WYSIWYG editor= . The fix introduces improvements to ContentExplorer that removes the doubl= e-encoding, which results in special characters being displayed correctly. + + + + + + BZ#813729 + - EPP configuration files use multiple version of kernel = xsd definition + + Status: VERIFIED + It was discovered that several versions of kernel_1_*.xsd were re= ferenced in XML configutation files. While no harmful consequences existed = by having these obsolete templates declared, it made the XML files appear i= nconsistent. The fix removes all kernel_1_[^2].xsd, and replaces these refe= rences with kernel_1_2.xsd which makes the XML configuration files consist= ent. - - - - - BZ#824855 - Strange duplicated requests i= n gadget rendering - - Status: VERIFIED - + + + + + BZ#813751 + - Portlet Bridge - NPE when loading styles via link eleme= nt + + Status: VERIFIED + + Documentation quoted that the <link> element could be used = to import Rich Faces XCSS scripts and stylesheets using the following synta= x: + <link type=3D"text/css" rel=3D"s= tylesheet" href=3D"/richFacesPortlet/faces/rfRes/org/richfaces/sk= in.xcss"/> + This syntax is no longer correct, and results in a NPE. To c= orrect the issue, use a4j:loadstyle to import the scripts and stylesheets w= hen using LoadStyleStrategy and LoadScriptStrategy of NONE: + <a4j:loadScript src=3D"resource:////org/aj= ax4jsf/framework.pack.js" type=3D"text/javascript"/> + <a4j:loadScript src=3D"resource:////org/richfaces/ui.pack.js&q= uot; type=3D"text/javascript"/> + <a4j:loadStyle src=3D"resource:////org/richfaces/skin.xcss&quo= t;/> + + + + + BZ#818565 + - Portal container name is hardcoded in the LocalizationF= ilter + + Status: VERIFIED + + A hard-coded portal container name in the LocalizationFilter caus= ed 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 Lo= calizationFilter, which corrects the issue. + + + + + + BZ#824855 + - Strange duplicated requests in gadget rendering + + Status: VERIFIED + It was discovered that certain gadgets on the dashboard were send= ing more requests then necessary. The unnecessary requests caused a perform= ance impact on page loading times. The fix implements changes to how gadget= s are rendered. Each gadget is rendered individually, and only loads necess= ary data which fixes the performance issue. - - - - - BZ#824860 - Error while rendering doodle = gadget when source is dead - - Status: VERIFIED - + + + + + BZ#824860 + - Error while rendering doodle gadget when source is dead= + + Status: VERIFIED + When the Doodle gadget was added to a dashboard, and the source w= ebsite supplying the gadget metadata was unavailable, the gadget was not lo= aded, and a user interface error occurred. The fix introduces a more inform= ative error message to all gadgets that require external sources, which dis= plays in the user interface at the time the error occurs. This helps the us= er diagnose the problem easier, and fixes the issue. - - - - - BZ#838973 - Dashboard pages with special = characters - - Status: CLOSED - - A change to how dashboard page names were validated in another is= sue 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 w= ill be added to the Dashboard Portlet section of the User Guide in a future= release. + + + + + BZ#824863 + - groovy template should not print "null" strin= g when variable is null + + Status: VERIFIED + + If a GateIn Template file (*.gtmpl) contained an <input> di= rective that declared a variable as a value, and that variable resolved to = null, the word "null" would be substituted for the value instead = of the value parameter being present, but undefined. For example, <input= class=3D"key" type=3D"text" name=3D"key" val= ue=3D"${key}"/> resolved to <input class=3D"key" = type=3D"text" name=3D"key" value=3D"null"/>= ;, instead of <input class=3D"key" type=3D"text" nam= e=3D"key" value/>. The fix corrects the way null values are h= andled, and now prints undefined parameters, instead of printing null as th= e parameter value. - - - - + + + + + BZ#824907 + - Add ability to deactivate URL rewriting on WSRP produce= r + + Status: VERIFIED + + 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 th= ese circumstances, it was desirable to disable URL rewriting, however no su= ch mechanism existed. The fix includes enhancements to the WSRP, with the a= ddition of the "org.gatein.wsrp.producer.deactivateURLRewriting".= If the parameter is set to true, URL rewriting is disabled. + + + + + + BZ#829885 + - X.509 token in ws-security support in WSRP + + Status: VERIFIED + + It was discovered that JBossWS supports X.509 token with WSSE, ho= wever the functionality only partially worked. It was not possible to encry= pt the entire message. The fix introduces improvements to this aspect of JB= ossWS in WSRP, and corrects the issue. + + + + + + BZ#831445 + - WSRP is failing when including OASIS WSRP WSDL + + Status: VERIFIED + + OASIS changed the way HTTP WSRP WSDL requests were redirected. Th= e requests redirected to a HTTP 302 response that included an XML document = with a public ID, but no system ID. This caused an exception "SAXParse= Exception: White spaces are required between publicId and systemId" 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 t= he OASIS website. +This corrects the issue, and restores expected functionality to Netunity v= 1 & v2. + + + + + + BZ#832089 + - WSRP: getPortletProperties doesn't behave properly= when en empty set of property names is passed + + Status: VERIFIED + + A problem detected with reading preferences from WLP 10.0.1 throu= gh a WSRP V1 endpoint caused the portlet properties to raise a NPE as a res= ult of the interaction. This issue has been fixed in the affected WSRP comp= onent, and the component updated for this release. Reading the portlet prop= erties via WSRP V1 now works as expected. + + + + + + BZ#835369 + - WSRP: The supportedOptions element in the producers res= ponse to a getServiceDescription request is missing the supported features<= /term> + + Status: VERIFIED + + The WSRP Producer was ignoring several optional elements when ret= urning a service description response to the consumer, including the suppor= tedOptions element. WSRP Consumers that were relying on these optional elem= ents to tailor their communication with the producer could behave improperl= y based on wrong assumptions due to missing (though optional) information. = The WSRP Producer now properly emits the supportedOptions element in its s= ervice description response, which allows Consumers to properly tailor thei= r behavior, and results in improved interoperability with third-party consu= mers. + + + + + + BZ#835375 + - Patch to enhance WSRP producers response to a getServic= eDescription request + + Status: CLOSED + + A number of issues were discovered: 1) WSRP: getPortletProperties= doesn'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 tho= ugh it's optional according to XSD. This caused the requests to be rej= ected by the server with an IllegalArgumentException: 'Property requir= es a non-null, non-empty language'. The fix applies a patch to the aff= ected files which corrects the issue. + + + + + + BZ#835578 + - Open an "Identity Transaction" only when it i= s necessary + + Status: VERIFIED + + Hibernate transactions had to be started for each HTTP request fr= om an anonymous or authenticated user, which in turn required a new databas= e connection from the connection pool (an expensive operation if it is not = required for the request). The fix enables a new option, "lazyStartOfH= ibernateTransaction", which is set in gatein.ear/02portal.war/WEB-INF/= conf/organization/picketlink-idm/picketlink-idm-config.xml. = + + +<option> + <name>lazyStartOfHibernateTransaction</name> + <value>false</value> + </option> + + If the value is set to true, the Hibernate transaction is st= arted only when required, and not for every request. The default value is f= alse for backwards-compatibility. + + + + + + BZ#837029 + - Change of JBC configuration - LRU algorithm + separate = configuration for portal-system workspace + + Status: VERIFIED + + A change made to the JBoss Cache cache algorithm caused performan= ce issues for some configuration scenarios. The fix introduces configuratio= n with an improved algorithm. The new algorithm references a new configurat= ion file, which now loads correctly. This corrects the performance issues. + + + + Modified: epp/docs/branches/5.2/Release_Notes/en-US/sp_known.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- epp/docs/branches/5.2/Release_Notes/en-US/sp_known.xml 2012-08-30 12:52= :33 UTC (rev 8836) +++ epp/docs/branches/5.2/Release_Notes/en-US/sp_known.xml 2012-08-30 23:18= :33 UTC (rev 8837) @@ -3,9 +3,38 @@ ]> Known Issues - - The following issues are known to exist in this release of the J= Boss Enterprise Portal Platform Site Publisher Add-on, and will be fixed in= a subsequent release. + The following issues are known to exist in this release of the JBo= ss Enterprise Portal Platform Site Publisher Add-on, and will be fixed in a= subsequent release. + 20120831 - Depending on the response from Martin to Thomas'= email about the following upgrade binaries I can include the following sen= tence and remove the upgrade binaries instruction set. If this is not the c= orrect way to proceed, I have added Thomas' guidance about getting cus= tomers to remove the libraries after server first-run (step 4 in that proce= dure. + There are no known issues for the Site Publisher plug-in in this r= elease. + And I would remove this release note if Martin will be providing= this to customers using KB. + + + + BZ#846276 + - Include upgrade binaries in SP package + + Status: ASSIGNED + + During the migration from EPP-SP 5.1.x to EPP-SP 5.2.x the templa= tes stored in the JCR database were not updated to the latest version. The = issue was discovered too late in the release cycle. - Do some of these issues look more like Resolved Issue= s? If they do, its because the ticket has not been set to the co= rrect Resolved Issue status (VERIFIED, CLOSED). - NEEDINFO: There are currently no Known Issues in BZ for Site Pub= lisher according to the filters Is this correct? - + To work around this issue, the binaries containing the Upgra= dePlugins have been added to the EPP-SP package, so customers who migrate f= rom an older EPP-SP release can add them to their installation manually. Fo= llow these steps: + = + + + + Download Site Publisher binary from the Customer Portal.= + + + Extract jars from the archive to = EPP_HOME/jboss-as/server/PROFILE/l= ib folder. + + + Start the server. + + + Remove the jar libraries from the server after starting = Site Publisher for the first time. + + + + + + Modified: epp/docs/branches/5.2/Release_Notes/en-US/sp_needinfo.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- epp/docs/branches/5.2/Release_Notes/en-US/sp_needinfo.xml 2012-08-30 12= :52:33 UTC (rev 8836) +++ epp/docs/branches/5.2/Release_Notes/en-US/sp_needinfo.xml 2012-08-30 23= :18:33 UTC (rev 8837) @@ -4,17 +4,13 @@ = NEEDINFO - = - - The following issues require more information from developers, o= r need to be processed by the lead writer before they can be approved for R= elease Note inclusion. - - + The following issues require more information from developers, or= need to be processed by the lead writer before they can be approved for Re= lease Note inclusion. + These tickets will not be included in Release Notes as they curre= ntly 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). - + = -#846276 ASSIGNED - hfnukal(a)redhat.com - Include upgrade binaries in SP p= ackage Modified: epp/docs/branches/5.2/Release_Notes/en-US/sp_resolved.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- epp/docs/branches/5.2/Release_Notes/en-US/sp_resolved.xml 2012-08-30 12= :52:33 UTC (rev 8836) +++ epp/docs/branches/5.2/Release_Notes/en-US/sp_resolved.xml 2012-08-30 23= :18:33 UTC (rev 8837) @@ -6,5 +6,31 @@ The following issues have been resolved in this release of the JBoss= Enterprise Portal Platform Site Publisher Add-on. = - NEEDINFO: There are currently no Resolved Issues in BZ for Site = Publisher according to the filters Is this correct? - + 20120831 - Because we don't have any BZ captured Site Publi= sher issues marked as resolved for this release, I propose the following wo= rding. + There are no resolved issues for the Site Publisher plug-in in thi= s release. + 20120831 - but because this may not be a good message to send to= customers, how about this as a compromise. + Site Publisher issues affecting this release were fixed upstream i= n eXo Platform for this release. + --===============1376988670308266981==--