[gatein-commits] gatein SVN: r8818 - in epp/docs/branches/5.2: Draft_CSP_Maps and 7 other directories.

Author: jaredmorgs Date: 2012-08-23 00:42:06 -0400 (Thu, 23 Aug 2012) New Revision: 8818 Added: epp/docs/branches/5.2/Draft_CSP_Maps/ epp/docs/branches/5.2/Draft_CSP_Maps/ReferenceGuide.contentspec Modified: epp/docs/branches/5.2/Reference_Guide/en-US/Book_Info.xml epp/docs/branches/5.2/Reference_Guide/en-US/Revision_History.xml epp/docs/branches/5.2/Reference_Guide/en-US/extras/PortalDevelopment_RTLFramework/default176.java epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/NavigationController.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortletDevelopment/Standard.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/WSRP.xml epp/docs/branches/5.2/Release_Notes/en-US/5.2.2_Release_Notes.ent epp/docs/branches/5.2/Release_Notes/en-US/5.2.2_Release_Notes.xml epp/docs/branches/5.2/Release_Notes/en-US/Author_Group.xml epp/docs/branches/5.2/Release_Notes/en-US/Book_Info.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_resolved.xml epp/docs/branches/5.2/Release_Notes/publican.cfg Log: Committing modifications to Release Notes and some minor reference guide changes. Also adding a CSP Maps folder to keep the maps under revision control until they are checked into the CCMS Added: epp/docs/branches/5.2/Draft_CSP_Maps/ReferenceGuide.contentspec =================================================================== --- epp/docs/branches/5.2/Draft_CSP_Maps/ReferenceGuide.contentspec (rev 0) +++ epp/docs/branches/5.2/Draft_CSP_Maps/ReferenceGuide.contentspec 2012-08-23 04:42:06 UTC (rev 8818) @@ -0,0 +1,329 @@ +Title = Reference Guide +Brand = JBoss +Product = JBoss Enterprise Portal Platform +Version = 6 +Edition = 6.0.0 +Subtitle = for use with JBoss Enterprise Portal Platform 6, and its patch releases. +Pubsnumber = 1 +DTD = Docbook 4.5 +Output Style = Narrative +Copyright Holder = Red Hat, Inc +Survey Links = OFF + +Part: Portal Development + + Chapter: Skinning the Portal + Overview [N, Concept] + Section: Skin components + Portal skin [N, Concept] + Window styles [N, Concept] + Portlet specification CSS classes [N, Concept] + Portlet skins [N, Concept] + Section: Skin selection + Skin selection through the user interface [N, Reference] + Setting the default skin within the configuration files [N, Task] + Skins in page markups [N, Concept] + The skin service [N, Concept] + Skin configuration [N, Task] + Resource request filter [N, Task] + Section: The default skin [N, Reference] + Process: Creating portal skins + Portal skin [X1, Concept] + Configuring a portal skin [N, Task] + Configuring a portal skin preview icon [N, Task] + Window style [N, Concept] + Configuring a window style [N, Task] + Configuring window style CSS [N, Task] + Configuring the default window style [N, Task] + Process: Creating portlet skins + Configure a portlet skin [N, Task] + Defining a custom CSS file [N, Task] + Configuing portlet icons [N, Task] + Configuring portlet specification CSS classes [N, Task] + Section: Tips and tricks + Easier CSS debugging [N, Task] + Section: Basic CSS techniques + Border pattern [N, Reference] + Left margin left pattern [N, Reference] + + Chapter: Portal life-cycle + Application Server start and stop [N, Concept] + The command servlet [N, Concept] + + Chapter: Default Portal + Default portal overview [N, Concept] + Default portal example [N, Reference] + + Chapter: Default permission configuration + Default permissions overview [N, Reference] + Overwriting default permissions [N, Task] + + Chapter: Navigation configuration + Portal navigation [N, Reference] + Group navigation [N, Reference] + User navigation [N, Reference] + + Chapter: Data import strategy + Import strategy overview [N, Reference] + Portal configuration object data [N, Reference] + Page object data [N, Reference] + Navigation object data [N, Reference] + Import mode [N, Reference] + + Chapter: Internationalization configuration + Internationalization overview [N, Concept] + Locales configuration [N, Reference] + ResourceBundleService [N, Reference] + Navigation resource bundles [N, Reference] + Adding Spanish translation to the portlet [N, Task] + Standard portlet resource keys [N, Reference] + + Chapter: Localization configuration + What is the pluggable locale policy [N, Concept] + LocalePolicy API [N, Concept] + Default LocalePolicy [N, Concept] + Custom LocalePolicy [N, Concept] + Configuring LocalePolicy [N, Concept] + Keeping non-bridged resources in sync with current locale [N, Concept] + + Chapter: XML resources bundles + Resource bundles overview [N, Concept] + Resource bundle XML format [N, Concept] + + + Chapter: Right To Left (RTL) Framework + RTL Groovy templates syntax [N, Reference] + RTL Stylesheet [N, Reference] + RTL Images [N, Reference] + RTL Client-side JavaScript [N, Reference] + + Chapter: JavaScript Inter Application Communication (IAC) + IAC overview [N, Concept] + IAC library [N, Reference] + IAC subscribe syntax [N, Reference] + IAC publish syntax [N, Reference] + IAC JavaScript events usage example [N, Reference] + + Chapter: Navigation Controller + Navigation controller [N, Concept] + Controller [N, Reference] + Building controller [N, Reference] + Section: controller.xml configuration + Route parameters [N, Reference] + Path parameters (regex support) [N, Reference] + Request parameter [N, Reference] + Route precedence [N, Reference] + Route nesting [N, Reference + Section: Integrate to JBoss Enterprise Portal Platform WebUI framework + Routing table parameters [N, Reference] + Section: WebUi Rendering components + PortalURL [N, Reference] + Obtaining a PortalURL [N, Reference] + NodeURL [N, Reference] + ComponentURL [N, Reference] + PortletURL [N, Reference] + WebUI URL builder [N, Reference] + WebUI Groovy templates [N, Reference] + +Part: Portlet Development + + Chapter: JSR-168 and JSR-286 + JSR overview [N, Concept] + Portal pages [N, Concept] + Rendering modes [N, Reference] + Window states [N, Reference] + Section: Deploying your first portlet + Compiling and packaging the application [N, Task] + Package structure [N, Reference] + Class structure [N, Reference] + Application descriptors [N, Reference] + Section: JavaServer pages portlet example + Example overview [N, Concept] + Compiling the example [N, Task] + Package structure [N, Reference] + Portlet class [N, Reference] + + Chapter: Shared portlet.xml + PortletFilter [N, Concept] + PortletFilter setup [N, Reference] + Global portlet.xml metadata elements + ApplicationMonitoringFilter filter [N, Reference] + + Chapter: Building JSF Portlets + JBoss Portlet Bridge (JBPB) [N, Concept] + How JSF works with portal [N, Concept] + Eventing [N, Concept] + Portlet-served resources [N, Concept] + Public render parameter [N, Concept] + Bridge frameworks and extensions [N, Concept] + Seam bridgelets [N, Concept] + + Process: Bridge Configuration + Configuring portlet.xml [N, Task] + Configuring faces-config.xml [N, Task] + Configuring facelets web.xml [N, Task] + Configuring JSP-only web.xml [N, Task] + + Process: RichFaces Setup and Configuration Options + Configuring RichFaces web.xml [N, Task] + Configure WSRP and PortletBridge [N, Task] + RichFaces local and remote portlet feature status [N, Reference] + + Process: Seam Setup and Configuration Options + ExceptionHandler [N, Concept] + Sending and receiving events [N, Task] + Public render parameters (PRPs)[N, Concept] + Configuring PRPs [N, Task] + Serving JSF resources in a portal [N, Reference] + + Chapter: Developing Portlets with the Bridge + Excluding attributes from the bridge request scope [N, Reference] + Supporting PortletMode changes [N, Reference] + Navigating to a mode's last viewId [N, Reference] + Using wildcards for session-scoped rule targets [N, Reference] + Clearing the view history when changing portlet modes [N, Reference] + General error handling [N, Reference] + Custom Ajax error handling [N, Reference] + Communication between portlets [N, Reference] + Storing components in PortletSession.APPLICATION_SCOPE [N, Reference] + Using PortletSession [N, Reference] + Linking to Portlet/JSF Pages Using h:outputlink [N, Reference] + Redirecting to an External Page or Resource [N, Reference] + Using Provided EL Variables [N, Reference] + +# check the EAP topics for related info for common info. +Part: Authentication and Authorization + + Chapter: Authentication + Authentication Overview [N, Reference] + Section: Login modules + WCILoginModule [N, Reference] + PortalLoginModule [N, Reference] + SharedStateLoginModule [N, Reference] + JbossLoginModule [N, Reference] + CustomMembershipLoginModule [N, Reference] + Login module source [N, Reference] + Section: Guidelines for creating a custom login module + Authentication on application server level [N, Reference] + Authentication on JBoss Enterprise Portal Platform level [N, Reference] + Authenticator and RolesExtractor [N, Reference] + Section: Authentication workflows + RememberMe authentication [N, Reference] +#the following section is from 17.2 Password Encryption + RememberMe password encryption [N, Task] + BASIC authentication [N, Reference] + Cluster login authentication [N, Reference] + SSO login authentication [N, Reference] + Section: Predefined user configuration + Overview [N, Reference] + OrganizationDatabaseInitializer plug-in [N, Reference] + MembershipType [N, Reference] + Groups [N, Reference] + Users [N, Reference] + NewUserEventListener plug-in [N, Reference] + Section: Authentication Token Configuration + The Token Service [N, Concept] + Implementing the Token Service API [N, Reference] + Configuring Token Services [N, Reference] + Section: PicketLink IDM integration + PicketLink IDM [N, Concept] + Overview [N, Reference] + Section: Organization API + exo.platform.services.organization [N, Reference] + Accessing User Profile [N, Reference + Section: Single Sign On (SSO) + Overview and Configuration Assumptions [N, Concept] + Process: SSO Valve + SSO Valve [N, Concept] + Implementing SSO Valve [N, Task] + Testing SSO Valve [N, Task] + Process: Enabling SSO with other web applications + Configuring SSO with other web application [N, Task] + Configuring SSO to authenticate from the public page using redirects [N, Task] + Section: Central Authentication Service (CAS) + Process: Implement CAS for portal user authentication + Installing CAS server and defining CAS_DIR [N, Task] + Modifying CAS server codebase [N, Task] + Setting up the CAS client [N, Task] + Redirecting user authentication to CAS [N, Task] + Section: Java Open Single Sign-On Project (JOSSO) + JOSSO [N, Concept] + Process: Implement OpenSSO for portal user authentication + Installing JOSSO server [N, Task] + Configuring JOSSO server [N, Task] + Configuring JOSSO client [N, Task] + Testing the JOSSO installation [N, Task] + Redirecting portal authentication to JOSSO [N, Task] + + Section: Open Single Sign-on (OpenSSO) + OpenSSO [N, Concept] + Process: Implement OpenSSO for portal user authetication + Installing OpenSSO [N, Task] + Modifying OpenSSO codebase [N, Task] + Configuring the gatein realm [N, Task] + Configuring the OpenSSO client [N, Task] + Redirecting portal authentication to OpenSSO [N, Task] +#Look for SPNEGO stuff in EAP 6 + Section: Simple and Protected GSSAPI Negotiation Mechanism (SPNEGO) + SPNEGO [N, Concept] + Process: Implement SPNEGO configuration for portal user authetication + Configuring kerberos [N, Task] + Configuring browser clients [N, Task] + Configure SPNEGO [N, Task] + Section: LDAP Integration + Lightweight Directory Access Protocol [N, Concept] + Process: LDAP in Read-only Mode + Configuring Red Hat Directory Server or OpenDS [N, Task] + Configuring Microsoft Active Directory [N, Task] + Configuring OpenLDAP + Configuring LDAP read-only mode [N, Task] + Process: LDAP as Default Store + Configuring Red Hat Directory Server or OpenDS [N, Task] + Configuring Microsoft Active Directory [N, Task] + Configuring OpenLDAP [N, Task] + Configuring OpenLDAP as the default store [N, Task] + LDAP configuration example [N, Reference] + Read-only groupTypeMappings example [N, Reference] + Default groupTypeMappings example [N, Reference] + Section: Create Users and Groups without Organization API + CoreOrganizationInitializer [N, Concept] + 17.10.1. Enable CoreOrganizationInitializer [N, Task] + 17.10.2. Operations [N, Reference] + 17.10.3. Using configuration directives [N, Concept] + Disabling launchAll at Startup [N, Task] + Disabling launchAll Job Scheduler [N, Task] + Altering the way JCR objects are created on-demand, at user login. [N, Task] + Triggering operations through the JMX console [N, Task] + REST Interface Example Commands [N, Reference] + + Chapter: Authorization + Authorization overview [N, Reference] + Servlet container authorization [N, Reference] + Portal level authorization [N, Reference] + +Part: Web Services for Remote Portlets (WSRP) +18.1. Introduction +18.2. Level of support in JBoss Enterprise Portal Platform +18.3. Deploying JBoss Enterprise Portal Platform's WSRP services +18.3.1. Considerations to use WSRP when running JBoss Enterprise Portal Platform on a non-default port or hostname +18.4. Securing WSRP +18.4.1. Considerations to use WSRP with SSL +18.4.2. WSRP and WS-Security +18.5. Making a portlet remotable +18.6. Consuming WSRP portlets from a remote Consumer +18.7. Consuming remote WSRP portlets in JBoss Enterprise Portal Platform +18.7.1. Overview +18.7.2. Configuring a remote producer using the configuration portlet +18.7.3. Configuring access to remote producers via XML +18.7.4. Adding remote portlets to categories +18.7.5. Adding remote portlets to pages +18.8. Consumers maintenance +18.8.1. Modifying a currently held registration +18.8.2. Consumer operations +18.8.3. Importing and exporting portlets +18.8.4. Erasing local registration data +18.9. Configuring JBoss Enterprise Portal Platform's WSRP Producer +18.9.1. Overview +18.9.2. Default configuration +18.9.3. Registration configuration +18.9.4. WSRP validation mode Modified: epp/docs/branches/5.2/Reference_Guide/en-US/Book_Info.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/Book_Info.xml 2012-08-19 22:43:22 UTC (rev 8817) +++ epp/docs/branches/5.2/Reference_Guide/en-US/Book_Info.xml 2012-08-23 04:42:06 UTC (rev 8818) @@ -9,7 +9,7 @@ <productname>JBoss Enterprise Portal Platform</productname> <productnumber>5.2</productnumber> <edition>5.2.2</edition> - <pubsnumber>9</pubsnumber> + <pubsnumber>11</pubsnumber> <abstract> <para> This Reference Guide is a high-level usage document. It deals with more advanced topics than the Installation and User Guides, adding new content or taking concepts discussed in the earlier documents further. It aims to provide supporting documentation for advanced users of the JBoss Enterprise Portal Platform product. Its primary focus is on advanced use of the product and it assumes an intermediate or advanced knowledge of the technology and terms. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/Revision_History.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/Revision_History.xml 2012-08-19 22:43:22 UTC (rev 8817) +++ epp/docs/branches/5.2/Reference_Guide/en-US/Revision_History.xml 2012-08-23 04:42:06 UTC (rev 8818) @@ -8,6 +8,34 @@ <simpara> <revhistory> <revision> + <revnumber>5.2.2-11</revnumber> + <date>Thu Aug 02 2012</date> + <author> + <firstname>Jared</firstname> + <surname>Morgan</surname> + <email/> + </author> + <revdescription> + <simplelist> + <member>BZ#839355 - Incorporated changes indentified by Matt Wringe to the Git repo into the enterprise docs.</member> + </simplelist> + </revdescription> + </revision> + <revision> + <revnumber>5.2.2-10</revnumber> + <date>Wed Jul 25 2012</date> + <author> + <firstname>Jared</firstname> + <surname>Morgan</surname> + <email/> + </author> + <revdescription> + <simplelist> + <member>BZ#812412 - Incorporated Docs QE feedback in Comment 16.</member> + </simplelist> + </revdescription> + </revision> + <revision> <revnumber>5.2.2-9</revnumber> <date>Wed Jul 11 2012</date> <author> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/extras/PortalDevelopment_RTLFramework/default176.java =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/extras/PortalDevelopment_RTLFramework/default176.java 2012-08-19 22:43:22 UTC (rev 8817) +++ epp/docs/branches/5.2/Reference_Guide/en-US/extras/PortalDevelopment_RTLFramework/default176.java 2012-08-23 04:42:06 UTC (rev 8818) @@ -1,4 +1,4 @@ color: white; line-height: 24px; padding: 0px 5px 0px 0px; /* orientation=lt */ -padding: 0px 0px 0px 5px; /* >orientation=rt */ +padding: 0px 0px 0px 5px; /* orientation=rt */ Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/NavigationController.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/NavigationController.xml 2012-08-19 22:43:22 UTC (rev 8817) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/NavigationController.xml 2012-08-23 04:42:06 UTC (rev 8818) @@ -84,8 +84,7 @@ JBoss Enterprise Portal Platform&apos;s extension project can define their own routing table, because of the extension mechanism. </para> <para> - The <filename>controller.xml</filename> can be changed and reloaded at runtime, this helps the testing of different configurations easily (configuration loading operations) and provide more insight into the routing engine (the <literal>findRoutes</literal> operation). see <emphasis role="bold">Rebuiding controller</emphasis> for more detail - </para> + The <filename>controller.xml</filename> can be changed and reloaded at runtime. This helps testing different configurations easily (configuration loading operations) and provides more insight into the routing engine (the <literal>findRoutes</literal> operation). </para> <para> The <application>WebAppController</application> is annotated with <code>@Managed</code> annotations and is bound under the <code>view=portal,service=controller</code> JMX name and under the &quot;portalcontroller&quot; REST name. </para> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortletDevelopment/Standard.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortletDevelopment/Standard.xml 2012-08-19 22:43:22 UTC (rev 8817) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortletDevelopment/Standard.xml 2012-08-23 04:42:06 UTC (rev 8818) @@ -517,62 +517,62 @@ </imageobject> </mediaobject> </section> - <section id="sect-Reference_Guide-JavaServer_Pages_Portlet_Example-JSF_example_using_the_JBoss_Portlet_Bridge"> - <title>JSF example using the JBoss Portlet Bridge</title> - <para> + </section> + <section id="sect-Reference_Guide-JavaServer_Pages_Portlet_Example-JSF_example_using_the_JBoss_Portlet_Bridge"> + <title>JSF example using the JBoss Portlet Bridge</title> + <para> In order to write a portlet using JSF a &apos;bridge&apos; is needed. This software allows developers to write a portlet application as if it was a JSF application. The bridge then negotiates the interactions between the two layers. </para> - <para> + <para> An example using the JBoss Portlet Bridge is available in the <filename>/jboss-epp-<replaceable>VERSION</replaceable>-src/portal/examples/portlets/</filename> directory of the JBoss Enterprise Portal Platform sources package. The configuration is slightly different from a JSP application. This example can be used as a base to configure instead of creating a new application. </para> - <para> + <para> As in any JSF application, the file <literal>faces-config.xml</literal> is required. It must contain the following information: </para> - <programlisting language="XML" role="XML"><xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../../extras/PortletDevelopment_Standard/default253.xml" parse="text"/></programlisting> - <para> + <programlisting language="XML" role="XML"><xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../../extras/PortletDevelopment_Standard/default253.xml" parse="text"/></programlisting> + <para> The portlet bridge libraries must be available and are usually bundled with the <literal>WEB-INF/lib</literal> directory of the web archive. </para> - <para> + <para> The other differences when compared to a regular portlet application are in the portlet descriptor. All the relevant details about this can be found in the JSR-329 specification that the JBoss Portlet Bridge implements. </para> - <programlistingco> - <areaspec> - <area coords="8 80" id="area-Reference_Guide-JavaServer_Pages_Portlet_Example-JSF_example_using_the_JBoss_Portlet_Bridge-portlet"/> - <area coords="21 80" id="area-Reference_Guide-JavaServer_Pages_Portlet_Example-JSF_example_using_the_JBoss_Portlet_Bridge-view"/> - <area coords="26 80" id="area-Reference_Guide-JavaServer_Pages_Portlet_Example-JSF_example_using_the_JBoss_Portlet_Bridge-edit"/> - <area coords="31 80" id="area-Reference_Guide-JavaServer_Pages_Portlet_Example-JSF_example_using_the_JBoss_Portlet_Bridge-help"/> - </areaspec> - <programlisting language="XML" role="XML"><xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../../extras/PortletDevelopment_Standard/default254.xml" parse="text"/></programlisting> - <calloutlist> - <callout arearefs="area-Reference_Guide-JavaServer_Pages_Portlet_Example-JSF_example_using_the_JBoss_Portlet_Bridge-portlet"> - <para> + <programlistingco> + <areaspec> + <area coords="8 80" id="area-Reference_Guide-JavaServer_Pages_Portlet_Example-JSF_example_using_the_JBoss_Portlet_Bridge-portlet"/> + <area coords="21 80" id="area-Reference_Guide-JavaServer_Pages_Portlet_Example-JSF_example_using_the_JBoss_Portlet_Bridge-view"/> + <area coords="26 80" id="area-Reference_Guide-JavaServer_Pages_Portlet_Example-JSF_example_using_the_JBoss_Portlet_Bridge-edit"/> + <area coords="31 80" id="area-Reference_Guide-JavaServer_Pages_Portlet_Example-JSF_example_using_the_JBoss_Portlet_Bridge-help"/> + </areaspec> + <programlisting language="XML" role="XML"><xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="../../extras/PortletDevelopment_Standard/default254.xml" parse="text"/></programlisting> + <calloutlist> + <callout arearefs="area-Reference_Guide-JavaServer_Pages_Portlet_Example-JSF_example_using_the_JBoss_Portlet_Bridge-portlet"> + <para> All JSF portlets define <literal>javax.portlet.faces.GenericFacesPortlet </literal> as portlet class. This class is part of the JBoss Portlet Bridge. </para> - </callout> - <callout arearefs="area-Reference_Guide-JavaServer_Pages_Portlet_Example-JSF_example_using_the_JBoss_Portlet_Bridge-view"> - <para> + </callout> + <callout arearefs="area-Reference_Guide-JavaServer_Pages_Portlet_Example-JSF_example_using_the_JBoss_Portlet_Bridge-view"> + <para> This is a mandatory parameter to define what&apos;s the default page to display. </para> - </callout> - <callout arearefs="area-Reference_Guide-JavaServer_Pages_Portlet_Example-JSF_example_using_the_JBoss_Portlet_Bridge-edit"> - <para> + </callout> + <callout arearefs="area-Reference_Guide-JavaServer_Pages_Portlet_Example-JSF_example_using_the_JBoss_Portlet_Bridge-edit"> + <para> This parameter defines which page to display on the &apos;edit&apos; mode. </para> - </callout> - <callout arearefs="area-Reference_Guide-JavaServer_Pages_Portlet_Example-JSF_example_using_the_JBoss_Portlet_Bridge-help"> - <para> + </callout> + <callout arearefs="area-Reference_Guide-JavaServer_Pages_Portlet_Example-JSF_example_using_the_JBoss_Portlet_Bridge-help"> + <para> This parameter defines which page to display on the &apos;help&apos; mode. </para> - </callout> - </calloutlist> - </programlistingco> - <note> - <title>JBoss Portlet Bridge</title> - <para> + </callout> + </calloutlist> + </programlistingco> + <note> + <title>JBoss Portlet Bridge</title> + <para> For more information about the JBoss Portlet Bridge, see the dedicated chapter which is part of this document. </para> - </note> - </section> + </note> </section> </section> </chapter> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/WSRP.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/WSRP.xml 2012-08-19 22:43:22 UTC (rev 8817) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/WSRP.xml 2012-08-23 04:42:06 UTC (rev 8818) @@ -70,14 +70,29 @@ </note> </section> <section> - <title>Deploying JBoss Enterprise Portal Platform&apos;s WSRP services</title> + <title><remark>BZ#839355</remark>Deploying JBoss Enterprise Portal Platform&apos;s WSRP services</title> <para> - JBoss Enterprise Portal Platform provides a complete support of WSRP 1.0 and 2.0 standard interfaces and offers both consumer and + JBoss Enterprise Portal Platform provides complete support for WSRP 1.0 and 2.0 standard interfaces, and offers both consumer and producer services. Starting with version 2.1.0-GA of the component, WSRP is packaged as a JBoss Enterprise Portal Platform - extension and is now self-contained in a package named + extension, and is self-contained in a package named <filename><replaceable>EPP_DIST</replaceable>/jboss-as/server/<replaceable>PROFILE</replaceable>/deploy/gatein-wsrp-integration.ear</filename> . - </para> +</para> + <para>The only files of interest from a user perspective +are located in the + <filename><replaceable>EPP_DIST</replaceable>/jboss-as/server/<replaceable>PROFILE</replaceable>/conf/gatein/</filename> +directory.</para> + <itemizedlist> + <listitem> + <para><filename>gatein-wsse-consumer.xml</filename>, which allows you to configure WS-Security support for the consumer.</para> + </listitem> + <listitem> + <para><filename>gatein-wsse-producer.xml</filename> which allows you to configure WS-Security support for + the producer.</para> + </listitem> + </itemizedlist> + <para> Refer to + <xref linkend="wss_configuration"/> section for configuration required in these files. </para> <para> The extension itself is composed of the following components: </para> @@ -85,11 +100,7 @@ <listitem> <para> <filename>META-INF</filename> - contains files necessary for EAR packaging. The only file that is of interest from a user perspective - is - <filename>gatein-wsse-consumer.xml</filename> - which allows you to configure WS-Security support for the consumer. Please see the - <xref linkend="wss_configuration"/> section for more details. + contains files necessary for EAR packaging. </para> </listitem> <listitem> @@ -130,10 +141,7 @@ <listitem> <para> The <filename>wsrp-producer-jb5wsss-&WSRP_VERSION;.war</filename>, which contains the producer-side - support for WS-Security. The only file of interest from a user perspective is - <filename>gatein-wsse-producer.xml</filename> which allows you to configure WS-Security support for - the producer. Please see the <xref linkend="wss_configuration"/> section. - for more details. + support for WS-Security. </para> </listitem> </itemizedlist> @@ -208,7 +216,7 @@ WSRP with WS-Security. </para> <section id="wss_configuration"> - <title>WS-Security Configuration</title> + <title><remark>BZ#839355</remark>WS-Security Configuration</title> <para>JBoss Enterprise Portal Platform uses JBossWS Native to handle ws-security. Please see the WS-Security section of the <ulink url="http://www.jboss.org/jbossas/docs/5-x">JBoss AS 5 Administration and Configuration Guide </ulink> for in-depth configuration options. Please note that since the consumer passes its credentials to the producer, the consumer will act as the wss client and the producer will act as the wss server. @@ -221,13 +229,13 @@ configuration file for the consumer. </para> <para> - <filename><replaceable>EPP_DIST</replaceable>/jboss-as/server/<replaceable>PROFILE/</replaceable>/gatein-wsrp-integration.ear/META-INF/gatein-wsse-consumer.xml</filename></para> + <filename><replaceable>EPP_DIST</replaceable>/jboss-as/server/<replaceable>PROFILE/</replaceable>conf/gatein/gatein-wsse-consumer.xml</filename></para> </listitem> <listitem> <para>JBossWS configuration file for the producer. </para> <para> - <filename><replaceable>EPP_DIST</replaceable>/jboss-as/server/<replaceable>PROFILE</replaceable>/gatein-wsrp-integration.ear/wsrp-producer-jb5wss.war/WEB-INF/conf/gatein-wsse-producer.xml </filename></para> + <filename><replaceable>EPP_DIST</replaceable>/jboss-as/server/<replaceable>PROFILE</replaceable>/conf/gatein/gatein-wsse-producer.xml </filename></para> </listitem> </itemizedlist> </section> @@ -239,51 +247,18 @@ </para> </section> <section> - <title>WS-Security Consumer Configuration</title> - <para>The consumer requires a few changes before it will function properly with WS-Security. The consumer - needs access to the current servlet request since this is used to retrieve the currently authenticated - user. In order for the consumer to access this information, it needs a special servlet-filter added to - the portal. + <title><remark>BZ#839355</remark>WS-Security Consumer Configuration</title> + <para>In the WSRP Configuration portlet <guilabel>Consumers Configuration</guilabel> options, check the &apos;Enable WS Security&apos; checkbox if you want credentials to be sent to the producer. </para> - <para>In <filename><replaceable>EPP_DIST</replaceable>/jboss-as/server/<replaceable>PROFILE</replaceable>/02portal.war/WEB-INF/web.xml</filename> add the following information: - </para> - <programlisting role="XML"><![CDATA[<!-- Filter to put request and response in ServletAccess --> - <filter> - <filter-name>ServletAccessFilter</filter-name> - <filter-class>org.gatein.wsrp.servlet.ServletAccessFilter</filter-class> - </filter> - <filter-mapping> - <filter-name>ServletAccessFilter</filter-name> - <url-pattern>/*</url-pattern> - </filter-mapping>]]> -</programlisting> - <para> - Finally, in the WSRP Configuration portlet, in the consumer configuration options, you will need to check the &apos;Enable WS Security&apos; checkbox: - </para> + <note> + <para>You do not need to enable this option if you want to use ws-security to encrypt the communication between the producer and consumer only, and not use it for identity propagation.</para> + </note> <mediaobject> <imageobject> <imagedata align="center" valign="middle" scalefit="1" fileref="images/WSRP/config_wss_selected.png" format="PNG"/> </imageobject> </mediaobject> </section> - <section> - <title>WS-Security Consumer Checklist</title> - <para> - In order for the consumer to handle ws-security, the following steps must be completed properly - </para> - <itemizedlist> - <listitem> - <para>The JBossWS configuration files must be configured.</para> - </listitem> - <listitem> - <para>The filter must be added to the portal&apos;s web.xml.</para> - </listitem> - <listitem> - <para>The enable wss feature must be check in the wsrp admin.</para> - </listitem> - </itemizedlist> - <para>The consumer will not properly handle ws-security unless all 3 are properly configured.</para> - </section> </section> </section> <section> Modified: epp/docs/branches/5.2/Release_Notes/en-US/5.2.2_Release_Notes.ent =================================================================== --- epp/docs/branches/5.2/Release_Notes/en-US/5.2.2_Release_Notes.ent 2012-08-19 22:43:22 UTC (rev 8817) +++ epp/docs/branches/5.2/Release_Notes/en-US/5.2.2_Release_Notes.ent 2012-08-23 04:42:06 UTC (rev 8818) @@ -11,4 +11,4 @@ <!-- Version Specifcs: --> <!ENTITY VX "5"> <!ENTITY VY "5.2"> -<!ENTITY VZ "5.2.1"> +<!ENTITY VZ "5.2.2"> 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/5.2.2_Release_Notes.xml 2012-08-19 22:43:22 UTC (rev 8817) +++ epp/docs/branches/5.2/Release_Notes/en-US/5.2.2_Release_Notes.xml 2012-08-23 04:42:06 UTC (rev 8818) @@ -1,9 +1,9 @@ <?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" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "5.2.1_Release_Notes.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "5.2.2_Release_Notes.ent"> %BOOK_ENTITIES; ]> -<book> +<book status="draft"> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Book_Info.xml"/> <part> <title>General Info</title> @@ -57,7 +57,7 @@ The JBoss Enterprise Portal Platform <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"/>. + The Installation Guide is available in multiple formats from <ulink url="http://access.redhat.com/knowledge/docs/JBoss_Enterprise_Portal... type="http"/>. </para> </chapter> <chapter id="Release_Notes-Component_Features"> @@ -85,19 +85,19 @@ </row> <row> <entry>eXo kernel</entry> - <entry>2.3.6-GA</entry> + <entry>2.3.8-GA</entry> </row> <row> <entry>eXo Core</entry> - <entry>2.4.6-GA</entry> + <entry>2.4.8-GA</entry> </row> <row> <entry>eXo WS</entry> - <entry>2.2.6-GA</entry> + <entry>2.2.8-GA</entry> </row> <row> <entry>eXo JCR</entry> - <entry>1.14.6-GA</entry> + <entry>1.14.8-GA</entry> </row> <row> <entry>Apache Shindig</entry> @@ -129,7 +129,7 @@ </row> <row> <entry>GateIn WSRP</entry> - <entry>2.1.5-EPP521-GA</entry> + <entry>2.1.7-EPP522-GA</entry> </row> <row> <entry>GateIn MOP</entry> @@ -141,7 +141,7 @@ </row> <row> <entry>PicketLink IDM</entry> - <entry>1.3.1.GA</entry> + <entry>1.3.2.CR01</entry> </row> <row> <entry>Chromattic</entry> @@ -149,7 +149,7 @@ </row> <row> <entry>Portlet Bridge</entry> - <entry>2.3.0.CP01.EPP521</entry> + <entry>2.3.1.CP01.EPP522</entry> </row> <row> <entry>Seam</entry> @@ -189,7 +189,7 @@ </row> <row> <entry>Gatein JON Plugin</entry> - <entry>1.0.0</entry> + <entry>1.0.1</entry> </row> </tbody> </tgroup> @@ -201,40 +201,40 @@ <title>New Components</title> <para>The following new components warrant special mention.</para> </formalpara> - <variablelist> - <varlistentry> - <term>Gatein JON Plugin</term> - <listitem> - <para>The Gatein JON plugin allows the portal to interact with JBoss Operations Network. The plugin captures portlet and site statistics.</para> - </listitem> - </varlistentry> - </variablelist> - <formalpara> + <remark>NEEDINFO: anything we need to mention here?</remark> +<!--<variablelist> + <varlistentry> + <term>Gatein JON Plugin</term> + <listitem> + <para>The Gatein JON plugin allows the portal to interact with JBoss Operations Network. The plugin captures portlet and site statistics.</para> + </listitem> + </varlistentry> +</variablelist>--> <formalpara> <title>Updated Components</title> <para>The following updated components warrant special mention.</para> </formalpara> - <variablelist> - <varlistentry> - <term>Java Content Repository</term> - <listitem> - <para>The JCR configuration has been corrected in the configuration.properties file. The previous configuration was incorrect. </para> - </listitem> - </varlistentry> - <varlistentry> - <term>Java Open Single Sign-on (JOSSO) </term> - <listitem> - <para>Packaging changes require different file paths for JOSSO. Refer to the Reference Guide &quot;Java Open Single Sign-On Project&quot; section for more information.</para> - </listitem> - </varlistentry> - </variablelist> - <note> + <remark>NEEDINFO: anything we need to mention here?</remark> +<!--<variablelist> + <varlistentry> + <term>Java Content Repository</term> + <listitem> + <para>The JCR configuration has been corrected in the configuration.properties file. The previous configuration was incorrect. </para> + </listitem> + </varlistentry> + <varlistentry> + <term>Java Open Single Sign-on (JOSSO) </term> + <listitem> + <para>Packaging changes require different file paths for JOSSO. Refer to the Reference Guide &quot;Java Open Single Sign-On Project&quot; section for more information.</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> </chapter> <chapter id="Release_Notes-Documentation"> <title>Documentation</title> <para> - An <citetitle>Installation Guide</citetitle> and a <citetitle>User Guide</citetitle> for JBoss Enterprise Portal Platform are available at <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platf... type="http"/>. JBoss Enterprise Portal Platform specific documentation is also available from this location, as is Site Publisher documentation. </para> + An <citetitle>Installation Guide</citetitle> and a <citetitle>User Guide</citetitle> for JBoss Enterprise Portal Platform are available at <ulink url="http://access.redhat.com/knowledge/docs/JBoss_Enterprise_Portal... type="http"/>. JBoss Enterprise Portal Platform specific documentation is also available from this location, as is Site Publisher documentation. </para> <para>In this release, the <citetitle>Installation Guide</citetitle> has undergone heavy rework and is now presented in a task-based narrative style. Any feedback you have regarding this new format would be greatly appreciated. You can provide feedback by following the instructions in the Feedback section located in the preface of the <citetitle>Installation Guide</citetitle>.</para> </chapter> <chapter id="Release_Notes-_Product_Support_and_License_Website_Links_"> @@ -261,7 +261,8 @@ </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="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> @@ -272,8 +273,9 @@ <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> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="resolved_issues_eXo.xml" encoding="XML"/> - </chapter> + <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/5.2/Release_Notes/en-US/Author_Group.xml =================================================================== --- epp/docs/branches/5.2/Release_Notes/en-US/Author_Group.xml 2012-08-19 22:43:22 UTC (rev 8817) +++ epp/docs/branches/5.2/Release_Notes/en-US/Author_Group.xml 2012-08-23 04:42:06 UTC (rev 8818) @@ -1,7 +1,5 @@ <?xml version='1.0' encoding='UTF-8'?> <!DOCTYPE authorgroup PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "5.2.0_Release_Notes.ent"> -%BOOK_ENTITIES; ]> <authorgroup> <author> Modified: epp/docs/branches/5.2/Release_Notes/en-US/Book_Info.xml =================================================================== --- epp/docs/branches/5.2/Release_Notes/en-US/Book_Info.xml 2012-08-19 22:43:22 UTC (rev 8817) +++ epp/docs/branches/5.2/Release_Notes/en-US/Book_Info.xml 2012-08-23 04:42:06 UTC (rev 8818) @@ -1,15 +1,12 @@ <?xml version='1.0' encoding='UTF-8'?> -<!DOCTYPE articleinfo PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "5.2.0_Release_Notes.ent"> -%BOOK_ENTITIES; +<!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.1 Release Notes</title> + <title>5.2.2 Release Notes</title> <subtitle>For use with JBoss Enterprise Portal Platform &VZ;, and the Site Publisher Plug-in.</subtitle> <productname>JBoss Enterprise Portal Platform</productname> <productnumber>5.2</productnumber> - <edition>5.2.1</edition> - <pubsnumber>52</pubsnumber> + <edition>5.2.2</edition> <abstract> <para> These release notes contain important information related to JBoss Enterprise Portal Platform &VZ;, and the Site Publisher plug-in that may not be currently available in the Product Manuals. You should read these Release Notes in their entirety before installing the product. Modified: epp/docs/branches/5.2/Release_Notes/en-US/Revision_History.xml =================================================================== --- epp/docs/branches/5.2/Release_Notes/en-US/Revision_History.xml 2012-08-19 22:43:22 UTC (rev 8817) +++ epp/docs/branches/5.2/Release_Notes/en-US/Revision_History.xml 2012-08-23 04:42:06 UTC (rev 8818) @@ -1,15 +1,13 @@ <?xml version='1.0' encoding='UTF-8'?> <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "5.2.0_Release_Notes.ent"> -%BOOK_ENTITIES; ]> <appendix id="appe-Release_Notes-Revision_History"> <title>Revision History</title> <simpara> <revhistory> <revision> - <revnumber>5.2.1-52</revnumber> - <date>Tue Apr 19 2012</date> + <revnumber>5.2.2-2</revnumber> + <date>Tue Aug 21 2012</date> <author> <firstname>Jared</firstname> <surname>Morgan</surname> @@ -17,13 +15,13 @@ </author> <revdescription> <simplelist> - <member>Final Draft Release Notes, updated with the bugs moved to their correct locations.</member> + <member>Release Notes draft with all issues currently flagged in BZ as requiring release notes.</member> </simplelist> </revdescription> </revision> <revision> - <revnumber>5.2.1-50</revnumber> - <date>Tue Apr 17 2012</date> + <revnumber>5.2.2-1</revnumber> + <date>Mon Aug 20 2012</date> <author> <firstname>Jared</firstname> <surname>Morgan</surname> @@ -31,11 +29,25 @@ </author> <revdescription> <simplelist> - <member>Final Draft Release Notes prepared for JBoss Enterprise Portal Platform 5.2.1 GA sign-off.</member> + <member>Release Notes First Draft.</member> </simplelist> </revdescription> </revision> <revision> + <revnumber>5.2.1-101</revnumber> + <date>Tue Apr 19 2012</date> + <author> + <firstname>Jared</firstname> + <surname>Morgan</surname> + <email/> + </author> + <revdescription> + <simplelist> + <member>Release Notes prepared for JBoss Enterprise Portal Platform 5.2.0 GA.</member> + </simplelist> + </revdescription> + </revision> + <revision> <revnumber>5.2.0-101</revnumber> <date>Thu Dec 14 2011</date> <author> Modified: epp/docs/branches/5.2/Release_Notes/en-US/known.xml =================================================================== --- epp/docs/branches/5.2/Release_Notes/en-US/known.xml 2012-08-19 22:43:22 UTC (rev 8817) +++ epp/docs/branches/5.2/Release_Notes/en-US/known.xml 2012-08-23 04:42:06 UTC (rev 8818) @@ -14,5 +14,25 @@ </remark> <variablelist> +<varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=795937"><... - Add SCP Documentation to Admin Guide for GateIn Management</term> + <listitem> + <remark>Status: ON_QA</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=803567"><... - Create Gatein/EPP JON Plugin Documentation</term> + <listitem> + <remark>Status: ON_QA</remark> + <para> + GateIn JON Plug-in information was missing from the documentation when the plug-in was initially released in v5.2.1. The content has been added in to a dedicated chapter in the Administration Guide in this release. Additionally, the Installation Guide has been updated with JBoss ON installation guidance. + </para> + </listitem> +</varlistentry> + </variablelist> </chapter> Modified: epp/docs/branches/5.2/Release_Notes/en-US/needinfo.xml =================================================================== --- epp/docs/branches/5.2/Release_Notes/en-US/needinfo.xml 2012-08-19 22:43:22 UTC (rev 8817) +++ epp/docs/branches/5.2/Release_Notes/en-US/needinfo.xml 2012-08-23 04:42:06 UTC (rev 8818) @@ -16,167 +16,40 @@ <variablelist> <varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=793425"><... - Creating user with username differing only in case-senstive case popups unknown error</term> - <listitem> - <para>The status is VERIFIED, assigned to mposolda(a)redhat.com.&lt;/para&gt; - <para> - CAUSE: When you are creating new user/group, UI layer is trying to look if user/group with same name already exists. If it exists, it shows message in UI and it won't try to create such user/group. - -OpenDS is not case-sensitive by default, but Picketlink IDM is doing case-sensitive comparison of user/group names. So when you try to search user "viLiam" and you already have "viliam", Picketlink IDM will return that user doesn't exist as it compares with respect to case-sensitivity by default. But when it tries to create user "viLiam", then it is failing because OpenDS is not case-sensitive and user "viliam" is already here. - -FIX: It's possible to fix it by configure Picketlink IDM to compare user/group names in case-insensitive way. This can be done by switch option "allowNotCaseSensitiveSearch" of LDAPIdentityStore in picketlink-idm-config.xml file to true. - -RESULT: So IDM is still case-sensitive by default. But customers have possibility to use the option and switch it to true to avoid exception. For now, it's documented here https://community.jboss.org/wiki/GateInIdentityAndSecurityFAQ in Q6/A6. - </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=794403"><... - Example skin looks scattered on the right side</term> - <listitem> - <para>The status is VERIFIED, assigned to ppalaga(a)redhat.com.&lt;/para&gt; - <para> - Cause: Width of for .UIWorkingWorkspace .UIPageBody set in the default skin was not suitable for SimpleSkin distributed with AS documentation. -Consequence: SimpleSkin looked scattered on the right side - the right border of #UIPageBody was shifted left and hidden under the JBoss EPP banner. -Fix: The width of the element in question was overriden by a more specific rule setting the width to auto. -Result: The border of #UIPageBody is 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"><... - Add SCP Documentation to Admin Guide for GateIn Management</term> - <listitem> - <para>The status is ON_QA, assigned to jmorgan(a)redhat.com.&lt;/para&gt; - <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"><... - Fix the sample portal datasource file.</term> - <listitem> - <para>The status is VERIFIED, assigned to ppalaga(a)redhat.com.&lt;/para&gt; - <para> - Cause: gatein-sample-portal-ds.xml file included in the documentation distributed with JBoss AS was out of sync with the gatein-ds.xml. -Consequence: Errors in the application server log when gatein-sample-portal-ds.xml was deployed together with gatein-sample-portal.ear -Fix: gatein-sample-portal-ds.xml file was brought in sync with gatein-ds.xml: (1) The order of datasources: IDM before JCR; (2) The Hypersonic data file location now under the gatein conf directory. (3) The IDM datastore was changed from local-tx-datasource to no-tx-datasource. -Result: Deployment of gatein-sample-portal-ds.xml with gatein-sample-portal.ear now finishes without errors and the sample portal can be visited under http://localhost:8080/sample-portal. - </para> - </listitem> -</varlistentry> - -<varlistentry> <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=801821"><... - Ensure that starter web application is always started last</term> <listitem> <para>The status is CLOSED, assigned to hfnukal(a)redhat.com.&lt;/para&gt; <para> - - </para> - </listitem> -</varlistentry> + NEEDINFO: What needs to be mentioned in the doc specifically? -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=803567"><... - Create Gatein/EPP JON Plugin Documentation</term> - <listitem> - <para>The status is ON_QA, assigned to jmorgan(a)redhat.com.&lt;/para&gt; - <para> - GateIn JON Plug-in information was missing from the documentation when the plug-in was initially released in v5.2.1. The content has been added in to a dedicated chapter in the Administration Guide in this release. Additionally, the Installation Guide has been updated with JBoss ON installation guidance. - </para> - </listitem> -</varlistentry> +CAUSE: -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=807012"><... - Remove possibly unused JARs from gatein.ear/lib</term> - <listitem> - <para>The status is VERIFIED, assigned to hfnukal(a)redhat.com.&lt;/para&gt; - <para> - Archive gatein.ear contains dupliucated jars. -Jars are removed. - </para> - </listitem> -</varlistentry> +CONSEQUENCE: -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=812657"><... - error when add new group the same with existing but different with lower and upper case on mysql</term> - <listitem> - <para>The status is VERIFIED, assigned to mposolda(a)redhat.com.&lt;/para&gt; - <para> - CAUSE: When you are creating new group, UI layer is trying to look if group with same name already exists. If it exists, it shows message in UI and it won't try to create such group. - -MySQL DB is not case-sensitive by default, but Picketlink IDM is doing case-sensitive comparison of group names. So when you try to search group "TEST_group" and you already have "test_group", Picketlink IDM will return that group doesn't exist as it compares with respect to case-sensitivity by default. But when it tries to create group "TEST_group", then it is failing because MySQL DB is not case-sensitive. - -FIX: It's possible to fix it by configure Picketlink IDM to compare group names in case-insensitive way. This can be done by switch option "allowNotCaseSensitiveSearch" of HibernateIdentityStore in picketlink-idm-config.xml file to true. - -RESULT: So IDM is still case-sensitive by default. But customers have possibility to use the option and switch it to true to avoid exception. For now, it's documented here https://community.jboss.org/wiki/GateInIdentityAndSecurityFAQ in Q6/A6. - </para> - </listitem> -</varlistentry> +FIX: -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=813729"><... - EPP configuration files use multiple version of kernel xsd definition</term> - <listitem> - <para>The status is VERIFIED, assigned to ppalaga(a)redhat.com.&lt;/para&gt; - <para> - Cause: Due to historical reasons several versions of kernel_1_*.xsd were referenced from XML configutation files. -Consequence: No harmful consequences known. XML configuration files seemed to be unconsistent. -Fix: All kernel_1_[^2].xsd references were replaced by kernel_1_2.xsd. -Result: XML configuration files look consistent. +RESULT: </para> </listitem> </varlistentry> <varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=813751"><... - Portlet Bridge - NPE when loading styles via <link> tag</term> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=813751"><... - Portlet Bridge - NPE when loading styles via link element</term> <listitem> <para>The status is VERIFIED, assigned to kfinniga(a)redhat.com.&lt;/para&gt; <para> - Documentation needs to be updated for Portlet Bridge to recommend following for including RichFaces scripts and stylesheets when using LoadStyleStrategy and LoadScriptStrategy of NONE: - - - <a4j:loadScript src="resource:////org/ajax4jsf/framework.pack.js" type="text/javascript" /> - <a4j:loadScript src="resource:////org/richfaces/ui.pack.js" type="text/javascript" /> - <a4j:loadStyle src="resource:////org/richfaces/skin.xcss" /> - </para> + Documentation quoted that the &lt;link&gt; element could be used to import Rich Faces XCSS scripts and stylesheets 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 stylesheets 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=824855"><... - Strange duplicated requests in gadget rendering</term> - <listitem> - <para>The status is VERIFIED, assigned to hfnukal(a)redhat.com.&lt;/para&gt; - <para> - C: Gadgets on dashboard sends more requests then necessary. -C: Performance impact on page loading. -R: Load only necessary data. -F: Each gadget is rendered individually. - </para> - </listitem> -</varlistentry> - -<varlistentry> - <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=824860"><... - Error while rendering doodle gadget when source is dead</term> - <listitem> - <para>The status is VERIFIED, assigned to hfnukal(a)redhat.com.&lt;/para&gt; - <para> - Cause: Loading gadget when source was down -Consequence: Gadget not loaded, broken UI -Fix: Handle error on background -Result: Show user friendly error - </para> - </listitem> -</varlistentry> - -<varlistentry> <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=824863"><... - groovy template should not print "null" string when variable is null</term> <listitem> <para>The status is ON_QA, assigned to hfnukal(a)redhat.com.&lt;/para&gt; <para> - C: GTMPL template prints null, when key was not definned -C: Non valid string shown on page -R: Use empty string -F: Returning empty string instead of null. + 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 "null" would be substituted for the value instead of the value parameter being present, but undefined. For example, &lt;input class="key" type="text" name="key" value="${key}"/&gt; resolved to &lt;input class="key" type="text" name="key" value="null"/&gt;, instead of &lt;input class="key" type="text" name="key" 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> @@ -186,7 +59,13 @@ <listitem> <para>The status is VERIFIED, assigned to claprun(a)redhat.com.&lt;/para&gt; <para> - + CAUSE: + +CONSEQUENCE: + +FIX: + +RESULT: </para> </listitem> </varlistentry> @@ -196,32 +75,15 @@ <listitem> <para>The status is CLOSED, assigned to mweiler(a)redhat.com.&lt;/para&gt; <para> - PATCH NAME: - 835375 -PRODUCT NAME: - JBoss Enterprise Portal Platform (EPP) -VERSION: - 5.2.1.GA -SHORT DESCRIPTION: - The getServiceDescription response of WSRP v2 is not including the optional supportedOptions element -LONG DESCRIPTION: - Using EPP 5.2.1 as WSRP v2 producer, the response to the getServiceDescription() request is not - including the supportedOptions element. -MANUAL INSTALL INSTRUCTIONS: - Replace the file $EPP_HOME/jboss-as/server/$CONFIG/deploy/gatein-wsrp-integration.ear - with the patched one. -COMPATIBILITY: - N/A -DEPENDENCIES: - N/A -SUPERSEDES: - BZ-832887 -SUPERSEDED BY: - EPP 5.2.2.GA -CREATOR: - Martin Weiler -DATE: - June 26, 2012 + Is a RN required for this issue? If so, please write CCFR. + +CAUSE: + +CONSEQUENCE: + +FIX: + +RESULT: </para> </listitem> </varlistentry> @@ -231,38 +93,18 @@ <listitem> <para>The status is VERIFIED, assigned to mposolda(a)redhat.com.&lt;/para&gt; <para> - CAUSE: Currently hibernate transaction needs to be started for every HTTP request of anonymous or logged user to EPP. This always needs obtain new DB connection from connection pool, which is quite expensive operation. - -FIX: There is fix available in underlying component Picketlink IDM, which added possibility to start Hibernate transaction lazily only for case when it's really needed. It's adding new option "lazyStartOfHibernateTransaction" into Picketlink IDM configuration file. Value true means that Hibernate transaction will be started lazily only when needed. Value false is starting transaction non-lazily during each request (current behaviour) - -RESULT: In configuration file gatein.ear/02portal.war/WEB-INF/conf/organization/picketlink-idm/picketlink-idm-config.xml is new option added: - <option> - <name>lazyStartOfHibernateTransaction</name> - <value>false</value> - </option> - -We can see that default value is false, so behaviour is same like before (because of backward compatibility and avoiding of risk). - -But for customers, who have problem with performance and DB connection is critical for them, it would be good to switch this option to "true". + 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, "lazyStartOfHibernateTransaction", 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=838973"><... - Dashboard pages with special characters</term> - <listitem> - <para>The status is CLOSED, assigned to mwringe(a)redhat.com.&lt;/para&gt; - <para> - CAUSE: Validation of dashboard page names changed. - -CONSEQUENCE: Dashboard page names with special characters are no longer considered an invalid page name. - -FIX: The portal can now properly handles dashboard page names with special characters. If a dashboard name contains an special character, it will be replaced with an underscore in the URL. - -RESULT: Special characters are now allowed in dashboard page names. - </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-08-19 22:43:22 UTC (rev 8817) +++ epp/docs/branches/5.2/Release_Notes/en-US/resolved.xml 2012-08-23 04:42:06 UTC (rev 8818) @@ -10,6 +10,46 @@ <variablelist> <varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=793425"><... - Creating user with username differing only in case-senstive case popups 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 "viLiam" were not distinguishable from the user name "viliam". 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 "allowNotCaseSensitiveSearch" 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"><... - 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=798801"><... - Fix the sample portal datasource 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 datasource file experienced issues when the file was deployed together with gatein-sample-portal.ear. Errors were 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 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=807012"><... - 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"><... - Support WSRP applications for Export/Import</term> <listitem> <remark>Status: VERIFIED</remark> @@ -31,5 +71,55 @@ </listitem> </varlistentry> +<varlistentry> + <term><ulink url="https://bugzilla.redhat.com/show_bug.cgi?id=812657"><... - 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 "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-insensitive way. In picketlink-idm-config.xml, change the HibernateIdentityStore option "allowNotCaseSensitiveSearch" 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=813729"><... - 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 configutation 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=824855"><... - 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"><... - 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=838973"><... - 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> </chapter> Modified: epp/docs/branches/5.2/Release_Notes/en-US/sp_known.xml =================================================================== --- epp/docs/branches/5.2/Release_Notes/en-US/sp_known.xml 2012-08-19 22:43:22 UTC (rev 8817) +++ epp/docs/branches/5.2/Release_Notes/en-US/sp_known.xml 2012-08-23 04:42:06 UTC (rev 8818) @@ -1,18 +1,11 @@ -<?xml version='1.0'?> +<?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 = "sp_known_issues"> - <title>Known Issues</title> - - <para> +<chapter id="sp_known_issues"> + <title>Known Issues</title> + <para> The following issues are known to exist in this release of the JBoss Enterprise Portal Platform Site Publisher Add-on, and will be fixed in a subsequent release. </para> - <remark> - Do some of these issues look more like <emphasis>Resolved Issues</emphasis>? If they do, its because the ticket has not been set to the correct - Resolved Issue status (VERIFIED, CLOSED). - </remark> - <variablelist> - - </variablelist> -</chapter> + <remark> Do some of these issues look more like <emphasis>Resolved Issues</emphasis>? If they do, its because the ticket has not been set to the correct Resolved Issue status (VERIFIED, CLOSED). </remark> + <remark>NEEDINFO: There are currently no Known Issues in BZ for Site Publisher according to the filters Is this correct? </remark> +<!--<variablelist/>--></chapter> Modified: epp/docs/branches/5.2/Release_Notes/en-US/sp_resolved.xml =================================================================== --- epp/docs/branches/5.2/Release_Notes/en-US/sp_resolved.xml 2012-08-19 22:43:22 UTC (rev 8817) +++ epp/docs/branches/5.2/Release_Notes/en-US/sp_resolved.xml 2012-08-23 04:42:06 UTC (rev 8818) @@ -1,13 +1,10 @@ -<?xml version='1.0'?> +<?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 = "sp_resolved"> - <title>Resolved Issues</title> - <para> +<chapter id="sp_resolved"> + <title>Resolved Issues</title> + <para> The following issues have been resolved in this release of the JBoss Enterprise Portal Platform Site Publisher Add-on. </para> - <variablelist> - - </variablelist> -</chapter> + <remark>NEEDINFO: There are currently no Resolved Issues in BZ for Site Publisher according to the filters Is this correct? </remark> +<!--<variablelist/>--></chapter> Modified: epp/docs/branches/5.2/Release_Notes/publican.cfg =================================================================== --- epp/docs/branches/5.2/Release_Notes/publican.cfg 2012-08-19 22:43:22 UTC (rev 8817) +++ epp/docs/branches/5.2/Release_Notes/publican.cfg 2012-08-23 04:42:06 UTC (rev 8818) @@ -1,5 +1,5 @@ xml_lang: en-US type: Book brand: JBoss -#show_remarks: 1 +show_remarks: 1 git_branch: docs-rhel-6