December 2011 - gatein-commits - Jboss List Archives

gatein SVN: r8199 - epp/docs/branches/5.2/Admin_Guide/en-US.

by do-not-reply＠jboss.org

Author: smumford Date: 2011-12-06 18:40:13 -0500 (Tue, 06 Dec 2011) New Revision: 8199 Modified: epp/docs/branches/5.2/Admin_Guide/en-US/Book_Info.xml epp/docs/branches/5.2/Admin_Guide/en-US/Revision_History.xml epp/docs/branches/5.2/Admin_Guide/en-US/chapter-4-Management_Extensions.xml Log: Updated with 'xml-escaping during export' problem fix. Modified: epp/docs/branches/5.2/Admin_Guide/en-US/Book_Info.xml =================================================================== --- epp/docs/branches/5.2/Admin_Guide/en-US/Book_Info.xml 2011-12-06 23:20:56 UTC (rev 8198) +++ epp/docs/branches/5.2/Admin_Guide/en-US/Book_Info.xml 2011-12-06 23:40:13 UTC (rev 8199) @@ -9,7 +9,7 @@ <productname>JBoss Enterprise Portal Platform</productname> <productnumber>5.2</productnumber> <edition>5.2.0</edition> - <pubsnumber>4</pubsnumber> + <pubsnumber>5</pubsnumber> <abstract> <para> This document is a guide to administering an implementation of JBoss Enterprise Portal Platform. It is intended for System Administrators and assumes a high level of technical knowledge. Modified: epp/docs/branches/5.2/Admin_Guide/en-US/Revision_History.xml =================================================================== --- epp/docs/branches/5.2/Admin_Guide/en-US/Revision_History.xml 2011-12-06 23:20:56 UTC (rev 8198) +++ epp/docs/branches/5.2/Admin_Guide/en-US/Revision_History.xml 2011-12-06 23:40:13 UTC (rev 8199) @@ -8,6 +8,20 @@ <simpara> <revhistory> <revision> + <revnumber>5.2.0-5</revnumber> + <date>Wed Dec 7 2011</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email></email> + </author> + <revdescription> + <simplelist> + <member>Updated with 'xml-escaping during export' problem fix.</member> + </simplelist> + </revdescription> + </revision> + <revision> <revnumber>5.2.0-4</revnumber> <date>Tue Nov 15 2011</date> <author> Modified: epp/docs/branches/5.2/Admin_Guide/en-US/chapter-4-Management_Extensions.xml =================================================================== --- epp/docs/branches/5.2/Admin_Guide/en-US/chapter-4-Management_Extensions.xml 2011-12-06 23:20:56 UTC (rev 8198) +++ epp/docs/branches/5.2/Admin_Guide/en-US/chapter-4-Management_Extensions.xml 2011-12-06 23:40:13 UTC (rev 8199) @@ -16,9 +16,6 @@ <section id="sid-8094332_GateInManagement-Operationsxx"> <title>Operations</title> - <para> - - </para> <section id="sid-8094332_GateInManagement-readconfigasxml"> <title>config-as-xml</title> @@ -27,7 +24,7 @@ <code>read-config-as-xml</code> operation can only be executed on the site layout, pages, and navigation managed resources. The xml format returned is that of which is defined in by the <ulink url="http://www.gatein.org/xml/ns/">gatein-objects</ulink> - xsd. This means that these resources are exposed in the same format as that which a portal extension would accept for importing data into the portal. + xsd. This means that these resources are exposed in the same format as what a portal extension would accept for importing data into the portal. </para> </section> <section id="sid-8094332_GateInManagement-exportresource"> @@ -235,8 +232,6 @@ <programlisting>HTTP/1.1 200 OK</programlisting> </example> </section> - - </section> <section id="sid-8094332_GateInManagement-SiteLayoutResource"> <title>Site Layout Resource</title> @@ -300,7 +295,6 @@ </example> </section> </section> - <section id="sid-8094332_GateInManagement-PagesResource"> <title>Pages Resource</title> @@ -384,7 +378,6 @@ </example> </section> </section> - <section id="sid-8094332_GateInManagement-NavigationResource"> <title>Navigation Resource</title> @@ -497,6 +490,7 @@ <title>Export all site types but user and group</title> <programlisting>GET /mop.zip?filter=site-type:!user,group</programlisting> </example> + </section> </section> <section id="sid-8094332_GateInManagement-CommandLineInterfacex">

13 years

1
0
0 / 0

gatein SVN: r8198 - epp/docs/branches/5.2/Migration_Guide/en-US.

by do-not-reply＠jboss.org

Author: smumford Date: 2011-12-06 18:20:56 -0500 (Tue, 06 Dec 2011) New Revision: 8198 Modified: epp/docs/branches/5.2/Migration_Guide/en-US/Book_Info.xml epp/docs/branches/5.2/Migration_Guide/en-US/Revision_History.xml epp/docs/branches/5.2/Migration_Guide/en-US/chapter-2-Portal_Containers.xml epp/docs/branches/5.2/Migration_Guide/en-US/chapter-3-Portal_URLs.xml epp/docs/branches/5.2/Migration_Guide/en-US/chapter-5-User_interface.xml Log: JBEPP-1441: Documented changes to <filename>web.xml</filename>. Modified: epp/docs/branches/5.2/Migration_Guide/en-US/Book_Info.xml =================================================================== --- epp/docs/branches/5.2/Migration_Guide/en-US/Book_Info.xml 2011-12-05 23:53:15 UTC (rev 8197) +++ epp/docs/branches/5.2/Migration_Guide/en-US/Book_Info.xml 2011-12-06 23:20:56 UTC (rev 8198) @@ -6,7 +6,7 @@ <productname>JBoss Enterprise Portal Platform</productname> <productnumber>5.2</productnumber> <edition>5.2.0</edition> - <pubsnumber>2</pubsnumber> + <pubsnumber>3</pubsnumber> <abstract> <para> This guide will assist Portal administrators to migrate from an installation of JBoss Enterprise Portal Platform 5.1 to the 5.2 version. Modified: epp/docs/branches/5.2/Migration_Guide/en-US/Revision_History.xml =================================================================== --- epp/docs/branches/5.2/Migration_Guide/en-US/Revision_History.xml 2011-12-05 23:53:15 UTC (rev 8197) +++ epp/docs/branches/5.2/Migration_Guide/en-US/Revision_History.xml 2011-12-06 23:20:56 UTC (rev 8198) @@ -5,6 +5,20 @@ <simpara> <revhistory> <revision> + <revnumber>5.2.0-3</revnumber> + <date>Wed Dec 7 2011</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email></email> + </author> + <revdescription> + <simplelist> + <member>JBEPP-1441: Documented changes to <filename>web.xml</filename>.</member> + </simplelist> + </revdescription> + </revision> + <revision> <revnumber>5.2.0-2</revnumber> <date>Fri Nov 25 2011</date> <author> Modified: epp/docs/branches/5.2/Migration_Guide/en-US/chapter-2-Portal_Containers.xml =================================================================== --- epp/docs/branches/5.2/Migration_Guide/en-US/chapter-2-Portal_Containers.xml 2011-12-05 23:53:15 UTC (rev 8197) +++ epp/docs/branches/5.2/Migration_Guide/en-US/chapter-2-Portal_Containers.xml 2011-12-06 23:20:56 UTC (rev 8198) @@ -3,13 +3,13 @@ <chapter id="sid-13467783"> <title>Portal Containers</title> - <para>If a customized portal container was used in JBoss Enterprise Portal Platform 5.1, its login module list should be adapted, in the file gatein-jboss-beans.xml the following would need to be added on top of the other login module definitions.</para> - <para>If this isn't done, it will not be possible to log into the portal.</para> + <para>If a customized portal container was used in JBoss Enterprise Portal Platform 5.1, its login module list should be adapted. The following would need to be added on top of the other login module definitions in the file gatein-jboss-beans.xml:</para> + <para>If this is not done, it will not be possible to log into the portal.</para> <example> - <title>Example</title> -<programlisting><login-module code="org.gatein.wci.security.WCILoginModule" flag="optional"> - <module-option name="portalContainerName">ecmdemo</module-option> - <module-option name="realmName">gatein-domain-ecmdemo</module-option> -</login-module></programlisting> + <title>Example</title> + <programlisting> <login-module code="org.gatein.wci.security.WCILoginModule" flag="optional"> + <module-option name="portalContainerName">ecmdemo</module-option> + <module-option name="realmName">gatein-domain-ecmdemo</module-option> + </login-module></programlisting> </example> </chapter> Modified: epp/docs/branches/5.2/Migration_Guide/en-US/chapter-3-Portal_URLs.xml =================================================================== --- epp/docs/branches/5.2/Migration_Guide/en-US/chapter-3-Portal_URLs.xml 2011-12-05 23:53:15 UTC (rev 8197) +++ epp/docs/branches/5.2/Migration_Guide/en-US/chapter-3-Portal_URLs.xml 2011-12-06 23:20:56 UTC (rev 8198) @@ -166,7 +166,7 @@ The private redirection performs first an authentication before doing the redirection. In that case the <emphasis role="italics">/private/classic/administration/registry</emphasis> path will resolve be redirected to the - <emphasis role="italics">/portal/groups/:platform:administrators/administration/registry</emphasis> + <emphasis role="italics">/portal/g/:platform:administrators/administration/registry</emphasis> page if the user has the sufficient security rights. </para> </listitem> @@ -222,7 +222,7 @@ <URL-pattern>/dologin</URL-pattern> </servlet-mapping></programlisting> </example> - <para>Declare portal servlet as default Servlet</para> + <para>Delare portal servlet as default Servlet</para> <example> <title>Example</title> <programlisting><servlet-mapping> @@ -258,6 +258,27 @@ <welcome-file>/index.jsp</welcome-file> </welcome-file-list></programlisting> </example> + <para> + We need to change the location of + <code>PortalLoginController</code> + : + </para> + <para>In 5.1, web.xml contained this:</para> + <example> + <title>Example</title> + <programlisting><servlet> + <servlet-name>PortalLoginController</servlet-name> + <servlet-class>org.exoplatform.web.login.PortalLoginController</servlet-class> +</servlet></programlisting> + </example> + <para>In 5.2 it should be:</para> + <example> + <title>Example</title> + <programlisting><servlet> + <servlet-name>PortalLoginController</servlet-name> + <servlet-class>org.exoplatform.web.security.PortalLoginController</servlet-class> +</servlet></programlisting> + </example> </section> <section id="sid-13467785_PortalURLs-Dashboardchanges"> Modified: epp/docs/branches/5.2/Migration_Guide/en-US/chapter-5-User_interface.xml =================================================================== --- epp/docs/branches/5.2/Migration_Guide/en-US/chapter-5-User_interface.xml 2011-12-05 23:53:15 UTC (rev 8197) +++ epp/docs/branches/5.2/Migration_Guide/en-US/chapter-5-User_interface.xml 2011-12-06 23:20:56 UTC (rev 8198) @@ -7,7 +7,7 @@ <section id="sid-13467777_Userinterface-Cleanthewebbrowsercache"> <title>Clean the web browser cache</title> - <para>This has not been changed and, while performing the migration, your web browser may still have the content of previous portal in cache. You will need to empty your web browser cache if you see that the UI is malformed or if overlay menus are not appearing. With most browsers you can refresh the cache by clicking on Ctrl+F5 while being on the problematic page.</para> + <para>This has not been changed and, while performing the migration, your web browser may still have the content of previous portal in cache. You will need to empty your web browser cache if you see that the UI is malfored or if overlay menus are not appearing. With most browsers you can refresh the cache by clicking on Ctrl+F5 while being on the problematic page.</para> </section> <section id="sid-13467777_Userinterface-Cleanthecookies">

13 years

1
0
0 / 0

gatein SVN: r8197 - epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr.

by do-not-reply＠jboss.org

Author: smumford Date: 2011-12-05 18:53:15 -0500 (Mon, 05 Dec 2011) New Revision: 8197 Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/statistics.xml Log: Actioning QE feedback Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/statistics.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/statistics.xml 2011-12-05 23:48:30 UTC (rev 8196) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/statistics.xml 2011-12-05 23:53:15 UTC (rev 8197) @@ -248,7 +248,6 @@ </section> -  + </section> <section id="sect-Reference_Guide-eXo_JCR_statistics-Statistics_Manager"> <title>Statistics Manager</title>

13 years

1
0
0 / 0

gatein SVN: r8196 - epp/docs/branches/5.2/Migration_Guide/en-US.

by do-not-reply＠jboss.org

Author: smumford Date: 2011-12-05 18:48:30 -0500 (Mon, 05 Dec 2011) New Revision: 8196 Modified: epp/docs/branches/5.2/Migration_Guide/en-US/chapter-5-User_interface.xml Log: Actioning QE feedback Modified: epp/docs/branches/5.2/Migration_Guide/en-US/chapter-5-User_interface.xml =================================================================== --- epp/docs/branches/5.2/Migration_Guide/en-US/chapter-5-User_interface.xml 2011-12-05 22:43:29 UTC (rev 8195) +++ epp/docs/branches/5.2/Migration_Guide/en-US/chapter-5-User_interface.xml 2011-12-05 23:48:30 UTC (rev 8196) @@ -3,7 +3,7 @@ <chapter id="sid-13467777"> <title>User interface</title> - <para>For performance reasons, part of the Javascript and CSS have changed. With Change 'EPP' to full name. 5.2 only some levels of navigation nodes are loaded and the others are loaded on demand, also the markup produced by the portal has been drastically simplified. Simplifying the markup helped a lot decreasing the size of what transits over the network but also speed up its rendering on web browsers.</para> + <para>For performance reasons, part of the Javascript and CSS have changed. With 5.2 only some levels of navigation nodes are loaded and the others are loaded on demand, also the markup produced by the portal has been drastically simplified. Simplifying the markup helped a lot decreasing the size of what transits over the network but also speed up its rendering on web browsers.</para> <section id="sid-13467777_Userinterface-Cleanthewebbrowsercache"> <title>Clean the web browser cache</title>

13 years

1
0
0 / 0

gatein SVN: r8195 - epp/docs/branches/5.2/Migration_Guide/en-US.

by do-not-reply＠jboss.org

Author: smumford Date: 2011-12-05 17:43:29 -0500 (Mon, 05 Dec 2011) New Revision: 8195 Modified: epp/docs/branches/5.2/Migration_Guide/en-US/chapter-2-Portal_Containers.xml epp/docs/branches/5.2/Migration_Guide/en-US/chapter-5-User_interface.xml Log: Actioning QE feedback Modified: epp/docs/branches/5.2/Migration_Guide/en-US/chapter-2-Portal_Containers.xml =================================================================== --- epp/docs/branches/5.2/Migration_Guide/en-US/chapter-2-Portal_Containers.xml 2011-12-05 22:27:07 UTC (rev 8194) +++ epp/docs/branches/5.2/Migration_Guide/en-US/chapter-2-Portal_Containers.xml 2011-12-05 22:43:29 UTC (rev 8195) @@ -5,10 +5,11 @@ <title>Portal Containers</title> <para>If a customized portal container was used in JBoss Enterprise Portal Platform 5.1, its login module list should be adapted, in the file gatein-jboss-beans.xml the following would need to be added on top of the other login module definitions.</para> <para>If this isn't done, it will not be possible to log into the portal.</para> - <informalexample> + <example> + <title>Example</title> <programlisting><login-module code="org.gatein.wci.security.WCILoginModule" flag="optional"> <module-option name="portalContainerName">ecmdemo</module-option> <module-option name="realmName">gatein-domain-ecmdemo</module-option> </login-module></programlisting> - </informalexample> + </example> </chapter> Modified: epp/docs/branches/5.2/Migration_Guide/en-US/chapter-5-User_interface.xml =================================================================== --- epp/docs/branches/5.2/Migration_Guide/en-US/chapter-5-User_interface.xml 2011-12-05 22:27:07 UTC (rev 8194) +++ epp/docs/branches/5.2/Migration_Guide/en-US/chapter-5-User_interface.xml 2011-12-05 22:43:29 UTC (rev 8195) @@ -12,7 +12,7 @@ <section id="sid-13467777_Userinterface-Cleanthecookies"> <title>Clean the cookies</title> - <para>On some rare occasions after using JBoss Enterprise Portal Platform 5.1 and 5.2 alternatively during migration phase, the portal may not answer and during login errors such as:</para> + <para>On some rare occasions after using JBoss Enterprise Portal Platform 5.1 and 5.2 alternatively during migration phase, the portal may not answer and, during login, errors such as the folowing may appear:</para> <para>11:33:07,011 ERROR [SetCurrentIdentityFilter] Not found identity in IdentityRegistry for user root, check Login Module.</para> <example> <title>Example</title>

13 years

1
0
0 / 0

gatein SVN: r8194 - epp/docs/branches/5.2/Admin_Guide/en-US.

by do-not-reply＠jboss.org

Author: smumford Date: 2011-12-05 17:27:07 -0500 (Mon, 05 Dec 2011) New Revision: 8194 Added: epp/docs/branches/5.2/Admin_Guide/en-US/Administration_Guide.ent epp/docs/branches/5.2/Admin_Guide/en-US/Administration_Guide.xml Removed: epp/docs/branches/5.2/Admin_Guide/en-US/Admin_Guide.ent epp/docs/branches/5.2/Admin_Guide/en-US/Admin_Guide.xml Log: Updated toplevel filenames to Administration (from Admin) Deleted: epp/docs/branches/5.2/Admin_Guide/en-US/Admin_Guide.ent =================================================================== --- epp/docs/branches/5.2/Admin_Guide/en-US/Admin_Guide.ent 2011-12-05 21:10:57 UTC (rev 8193) +++ epp/docs/branches/5.2/Admin_Guide/en-US/Admin_Guide.ent 2011-12-05 22:27:07 UTC (rev 8194) @@ -1,19 +0,0 @@ - -<!ENTITY PRODUCT "JBoss Enterprise Portal Platform"> - - -<!ENTITY BOOKID "Admin Guide"> - - -<!ENTITY BZPRODUCT "JBoss Enterprise Portal Platform 5"> -<!ENTITY BZCOMPONENT "docs-Admin_Guide"> -<!ENTITY BZURL "<ulink url='https://bugzilla.redhat.com/enter_bug.cgi?product=JBoss&percnt;20Enterpri...'>http://bugzilla.redhat.com/</ulink>"> - - -<!ENTITY YEAR "2011"> -<!ENTITY HOLDER "Red Hat, Inc"> - - -<!ENTITY VX "5"> -<!ENTITY VY "5.2"> -<!ENTITY VZ "5.2.0"> \ No newline at end of file Deleted: epp/docs/branches/5.2/Admin_Guide/en-US/Admin_Guide.xml =================================================================== --- epp/docs/branches/5.2/Admin_Guide/en-US/Admin_Guide.xml 2011-12-05 21:10:57 UTC (rev 8193) +++ epp/docs/branches/5.2/Admin_Guide/en-US/Admin_Guide.xml 2011-12-05 22:27:07 UTC (rev 8194) @@ -1,15 +0,0 @@ -<?xml version='1.0' encoding='utf-8' ?> -<!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 "Admin_Guide.ent"> -%BOOK_ENTITIES; -]> -<book> - <xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="chapter-1-Introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="chapter-2-REST.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="chapter-3-Command_Line_Interface.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="chapter-4-Management_Extensions.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -</book> - Added: epp/docs/branches/5.2/Admin_Guide/en-US/Administration_Guide.ent =================================================================== --- epp/docs/branches/5.2/Admin_Guide/en-US/Administration_Guide.ent (rev 0) +++ epp/docs/branches/5.2/Admin_Guide/en-US/Administration_Guide.ent 2011-12-05 22:27:07 UTC (rev 8194) @@ -0,0 +1,19 @@ + +<!ENTITY PRODUCT "JBoss Enterprise Portal Platform"> + + +<!ENTITY BOOKID "Admin Guide"> + + +<!ENTITY BZPRODUCT "JBoss Enterprise Portal Platform 5"> +<!ENTITY BZCOMPONENT "docs-Admin_Guide"> +<!ENTITY BZURL "<ulink url='https://bugzilla.redhat.com/enter_bug.cgi?product=JBoss&percnt;20Enterpri...'>http://bugzilla.redhat.com/</ulink>"> + + +<!ENTITY YEAR "2011"> +<!ENTITY HOLDER "Red Hat, Inc"> + + +<!ENTITY VX "5"> +<!ENTITY VY "5.2"> +<!ENTITY VZ "5.2.0"> \ No newline at end of file Property changes on: epp/docs/branches/5.2/Admin_Guide/en-US/Administration_Guide.ent ___________________________________________________________________ Added: svn:executable + * Added: epp/docs/branches/5.2/Admin_Guide/en-US/Administration_Guide.xml =================================================================== --- epp/docs/branches/5.2/Admin_Guide/en-US/Administration_Guide.xml (rev 0) +++ epp/docs/branches/5.2/Admin_Guide/en-US/Administration_Guide.xml 2011-12-05 22:27:07 UTC (rev 8194) @@ -0,0 +1,15 @@ +<?xml version='1.0' encoding='utf-8' ?> +<!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 "Admin_Guide.ent"> +%BOOK_ENTITIES; +]> +<book> + <xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="chapter-1-Introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="chapter-2-REST.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="chapter-3-Command_Line_Interface.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="chapter-4-Management_Extensions.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> +</book> +

13 years

1
0
0 / 0

gatein SVN: r8193 - epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US.

by do-not-reply＠jboss.org

Author: smumford Date: 2011-12-05 16:10:57 -0500 (Mon, 05 Dec 2011) New Revision: 8193 Removed: epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Create_A_Site.xml Modified: epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Site_Publisher_Installation_Guide.xml Log: JBEPP-846: Removing unecessary Create_A_Site content Deleted: epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Create_A_Site.xml =================================================================== --- epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Create_A_Site.xml 2011-12-05 04:34:52 UTC (rev 8192) +++ epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Create_A_Site.xml 2011-12-05 21:10:57 UTC (rev 8193) @@ -1,1272 +0,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" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Site_Publisher_Installation_Guide.ent"> -%BOOK_ENTITIES; -]> -<chapter id="chap-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo"> - <title>Create a Site Using The Demo</title> - <para> - It is possible to use the source files of the <literal>ecmdemo</literal> example site as a basis for a new site within your portal deployment. - </para> - <para> - <remark>Does it have to be the sources that get modified to do this? Can the changes be made in the <filename>ecmdemo</filename>.ear that is part of the SP download?</remark> - - </para> - <section id="sect-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-Pre_requisites"> - <title>Pre-requisites</title> - <para> - In order to use the demonstration portal to create a new site, you will need the following tools: - </para> - <itemizedlist> - <listitem> - <para> - The <application>Subversion</application> version management tool. - </para> - - </listitem> - <listitem> - <para> - The <application>Maven</application> build tool. - </para> - - </listitem> - <listitem> - <para> - A subscription to JBoss Enterprise Portal Platform Site Publisher and the <filename>jboss-eppsp-<version>-exo-<version>-GA.zip</filename> package available from the JBoss Customer Service Portal. - </para> - - </listitem> - - </itemizedlist> - - </section> - - <section id="sect-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-Get_Started"> - <title>Get Started</title> - <procedure> - <title></title> - <step id="step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-Execution-Get_Started-step_1"> - <title>Get the sources</title> - <para> - Obtain the <literal>ecmdemo</literal> source files with the following command: - </para> - -<programlisting>svn export http://svn.exoplatform.org/projects/ecms/tags/2.1.4/packaging/ecmdemo/ EXT_NAME</programlisting> - <para> - (In this instance, and throughout the rest of this guide, EXT_NAME will be used to denote the name of your new site.) - </para> - <note> - <title>SVN Export</title> - <para> - Using the <command>svn export</command> command allows you to check out the source files without creating a local working copy of the repository. - </para> - - </note> - - </step> - - </procedure> - - - </section> - - <section id="sect-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-Customize_the_extension"> - <title>Customize the extension</title> - <para> - The <literal>ecmdemo</literal> project uses the extension mechanism to create a new portal container. This portal container is separate from the default deployment; it uses its own IDM implementation, JCR datasources and URL context. All services required by the new site area configured independently, meaning the default portal instance in not affected in any way. - </para> - <para> - The <literal>ecmdemo</literal> portal container includes two portals; <emphasis role="bold">Classic</emphasis> and <emphasis role="bold">Acme</emphasis>. The <emphasis role="bold">Classic</emphasis> portal is a presentation of the JBoss Enterprise Portal Platform product while the <emphasis role="bold">Acme</emphasis> site serves as a demonstration of Site Publisher's features. - </para> - <para> - The following procedures will guide you through renaming the extension to whatever you intend to call your new portal. - </para> - <procedure id="proc-Site_Publisher_Installation_Guide-Customize_the_extension-Renaming_In_POM_Files"> - <title>Renaming In POM Files</title> - <step id="step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-step_1"> - <para> - Files to be modified in this section: - </para> - <programlistingco> - <areaspec> - <area coords="1 20" id="area-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-EXT_NAME" /> - <area coords="2 20" id="area-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-pom" /> - <area coords="3 20" id="area-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-config" /> - <area coords="5 20" id="area-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-webapp" /> - <area coords="7 20" id="area-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-rest" /> - <area coords="9 20" id="area-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-ear" /> - - </areaspec> - -<programlisting><replaceable>EXT_NAME</replaceable> -├── pom.xml -├── config -│ └── pom.xml -├── webapp -│ └── pom.xml -├── rest-webapp -│ └── pom.xml -└── ear - └── pom.xml -</programlisting> - <calloutlist> - <callout arearefs="area-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-EXT_NAME"> - <para> - The parent project. - </para> - - </callout> - <callout arearefs="area-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-pom"> - <para> - The extension's <filename>pom</filename> file. - </para> - <para> - Refer to <xref linkend="step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-step_2" /> for information on how to edit the <filename>pom.xml</filename>. - </para> - - </callout> - <callout arearefs="area-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-config"> - <para> - The configuration JAR. <remark>This is a normal directory in my copy (not a JAR)</remark> - - </para> - <para> - Refer to <xref linkend="step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-step_3" /> for information on how to edit the <filename>pom.xml</filename>. - </para> - - </callout> - <callout arearefs="area-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-webapp"> - <para> - The configuration WAR. <remark>This is a normal directory in my copy (not a WAR)</remark> - - </para> - <para> - Refer to <xref linkend="step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-step_4" /> for information on how to edit the <filename>pom.xml</filename>. - </para> - - </callout> - <callout arearefs="area-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-rest"> - <para> - The REST configuration WAR. <remark>This is a normal directory in my copy (not a WAR)</remark> - - </para> - <para> - Refer to <xref linkend="step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-step_5" /> for information on how to edit the <filename>pom.xml</filename>. - </para> - - </callout> - <callout arearefs="area-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-ear"> - <para> - The deployable EAR archive. <remark>This is a normal directory in my copy (not an EAR)</remark> - - </para> - <para> - Refer to <xref linkend="step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-step_6" /> for information on how to edit the <filename>pom.xml</filename>. - </para> - - </callout> - - </calloutlist> - - </programlistingco> - - - </step> - <step id="step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-step_2"> - <para> - Remove references to the original project from the extension's <filename>pom.xml</filename> file. - </para> - -<programlisting language="XML" role="XML">... - <groupId>org.myorg</groupId> - <artifactId>EXT_NAME</artifactId> - <version>1.0.0</version> - <packaging>pom</packaging> - <name>EXT NAME</name> - <description/> -...</programlisting> - - </step> - <step id="step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-step_3"> - <para> - Remove references to the original project from the <filename>config/pom.xml</filename> file. - </para> - -<programlisting language="XML" role="XML">... - <parent> - <groupId>org.myorg</groupId> - <artifactId>EXT_NAME</artifactId> - <version>1.0.0</version> - </parent> - <artifactId>EXT_NAME-config</artifactId> - <name>EXT NAME configuration jar</name> -...</programlisting> - <para> - (You may also remove the <literal>src/main/java</literal> resource folder definition because the <literal>EXT_NAME-config</literal> project only contains one configuration file which is located in the <filename>src/main/resources</filename> folder.) - </para> - - </step> - <step id="step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-step_4"> - <para> - Remove references to the original project from the <filename>webapp/pom.xml</filename> file. - </para> - -<programlisting language="XML" role="XML">... - <parent> - <groupId>org.myorg</groupId> - <artifactId>EXT_NAME</artifactId> - <version>1.0.0</version> - </parent> - <artifactId>EXT_NAME-webapp</artifactId> - <packaging>war</packaging> - <name>EXT_NAME configuration war</name> - ...</programlisting> - - </step> - <step id="step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-step_5"> - <para> - Remove references to the original project from the <filename>rest-webapp/pom.xml</filename> file. - </para> - -<programlisting language="XML" role="XML">... -<parent> - <groupId>org.myorg</groupId> - <artifactId>EXT_NAME</artifactId> - <version>1.0.0</version> -</parent> -<artifactId>EXT_NAME-rest-webapp</artifactId> -<packaging>war</packaging> -<name>EXT NAME Portal REST war</name> -...</programlisting> - <para> - Remove or comment-out the <parameter>finalName</parameter> tag from the build definition. - </para> - - </step> - <step id="step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-step-Site_Publisher_Installation_Guide-Execution-Rename_project_in_the_POM_files-step_6"> - <para> - Remove references to the original project from the <filename>ear/pom.xml</filename> file. - </para> - -<programlisting language="XML" role="XML">... -<parent> - <groupId>org.myorg</groupId> - <artifactId>EXT_NAME</artifactId> - <version>1.0.0</version> -</parent> -<artifactId>EXT_NAME-ear</artifactId> -<packaging>ear</packaging> -<name>EXT_NAME EAR for GateIn</name> -...</programlisting> - <para> - Rename the <parameter>dependencies</parameter> to match the renamed projects. - </para> - -<programlisting language="XML" role="XML">... -<dependencies> -<dependency> - <groupId>org.myorg</groupId> - <artifactId>EXT_NAME-config</artifactId> - <version>${project.version}</version> -</dependency> -...</programlisting> - <para> - Rename the artifacts in <parameter>maven-ear-plugin</parameter> configuration. - </para> - -<programlisting language="XML" role="XML">... -<configuration> - <displayName>EXT_NAME</displayName> - <defaultLibBundleDir>lib</defaultLibBundleDir> - <modules> - <jarModule> - <groupId>org.myorg</groupId> - <artifactId>EXT_NAME-config</artifactId> - <includeInApplicationXml>true</includeInApplicationXml> - </jarModule> - <webModule> - <groupId>org.myorg</groupId> - <artifactId>EXT_NAME-webapp</artifactId> - <contextRoot>EXT_NAME</contextRoot> - <bundleFileName>EXT_NAME.war</bundleFileName> - </webModule> - <webModule> - <groupId>org.myorg</groupId> - <artifactId>EXT_NAME-rest-webapp</artifactId> - <contextRoot>rest-EXT_NAME</contextRoot> - <bundleFileName>rest-EXT_NAME.war</bundleFileName> - </webModule> - </modules> -</configuration> -... -</programlisting> - <para> - Add the <parameter>finalName</parameter> tag to the build element so the result EAR will be <filename>EXT_NAME.ear</filename>. - </para> - -<programlisting language="XML" role="XML">... -<build> - <finalName>EXT_NAME</finalName> - ...</programlisting> - - </step> - - </procedure> - - - </section> - - <section id="sect-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-Renaming_Configuration_Files"> - <title>Renaming Configuration Files</title> - <para> - The <literal>ecmdemo</literal> string is present in the following configuration files within the project: - </para> - -<screen>EXT_NAME/ -├── pom.xml -├── config -│ └── src -│ └── main -│ └── resources -│ └── conf -│ └── configuration.xml -├── webapp -│ └── src -│ └── main -│ └── webapp -│ └── WEB-INF -│ ├── conf -│ │ └── sample-portal -│ │ ├── portal -│ │ │ └── portal -│ │ │ └── acme -│ │ │ └── pages.xml -│ │ └── wcm -│ │ ├── artifacts -│ │ │ └── site-resources -│ │ │ └── newsletter -│ │ │ └── newsletterBasicTemplate.xml -│ │ └── friendly-configuration.xml -│ ├── jboss-web.xml -│ └── web.xml -├── rest-webapp -│ └── src -│ └── main -│ └── webapp -│ └── WEB-INF -│ ├── jboss-web.xml -│ └── web.xml -└── ear - └── src - └── main - └── application - ├── ecmdemo.xml - └── META-INF - └── gatein-jboss-beans.xml -</screen> - <para> - To completely rename the extension project all occurences of the <literal>ecmdemo</literal> string must be replaced with your <replaceable>EXT_NAME</replaceable>. - </para> - <para> - Additionally, the <filename>ecmdemo.xml</filename> file must be renamed <filename><replaceable>EXT_NAME</replaceable>.xml</filename>. - </para> - - </section> - - <section id="sect-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-Deploy_the_application"> - <title>Deploy the application</title> - <para> - After the project is completely renamed, you must build it and deploy it00 into JBoss Enterprise Portal Platform portal. - </para> - <procedure> - <step> - <para> - Build the application with the following commands: - </para> - <substeps> - <step> - <para> - <command>cd <replaceable>EXT_NAME</replaceable>/</command> - </para> - - </step> - <step> - <para> - <command>mvn clean install</command> - </para> - - </step> - - </substeps> - <para> - The above commands will create an <filename><replaceable>EXT_NAME</replaceable>.ear</filename> file in a new <filename>ear/target/</filename> directory. - </para> - - </step> - <step> - <para> - Copy the <filename><replaceable>EXT_NAME</replaceable>.ear</filename> to the <filename>deploy</filename> directory of your JBoss Enterprise Portal Platform profile: - </para> - -<programlisting><command>cp ear/target/<filename><replaceable>EXT_NAME</replaceable>.ear</filename> <replaceable>JBOSS_HOME</replaceable>/jboss-as/server/<<replaceable>PROFILE</replaceable>>/deploy/</command></programlisting> - - </step> - <step> - <para> - As the extension also creates a new portal container, a separate datasource config file must be deployed as well. - </para> - <substeps> - <step> - <para> - Copy the <filename>gatein-ds.xml</filename> file from the <filename>jboss-eppsp-<version>-exo-<version>-GA.zip</filename> distribution package. - </para> - - </step> - <step> - <para> - Edit the file to replace instances of the <emphasis>portal</emphasis> JNDI name with your <replaceable>EXT_NAME</replaceable>. - </para> - -<programlisting language="XML" role="XML"><datasources> -<no-tx-datasource> - <jndi-name>gatein-idm_spdemo</jndi-name> - <connection-url>jdbc:hsqldb:${jboss.server.data.dir}${/}gatein${/}hypersonic${/}gatein-idm_spdemo-localDB</connection-url> - ... -</programlisting> - <para> - - </para> - - </step> - - </substeps> - - </step> - <step> - <para> - Ensure you have also deployed at least the <filename>gatein-wcm-extension-<replaceable><version></replaceable>-GA.ear</filename> and <filename>gatein-ds.xml</filename> artifacts from the Site Publisher disribution package. - </para> - <para> - - </para> - <para> - Refer to the <emphasis role="bold">Installation</emphasis> chapter of the Site Publisher Installation Guide for more information about the other files in the distribution and their deployment. - </para> - - </step> - <step> - <para> - Start the server using the configuration profile you deployed your new portal to. - </para> - <itemizedlist> - <listitem> - <para> - For Linux (or other Unix-based) systems: - </para> - -<programlisting><command>sh <replaceable>JBOSS_HOME</replaceable>/jboss-as/bin/run.sh -c <replaceable>EXT_NAME</replaceable></command></programlisting> - - </listitem> - <listitem> - <para> - For Microsoft Windows systems: - </para> - -<programlisting><command><replaceable>JBOSS_HOME</replaceable>/jboss-as/bin/run.bat -c <replaceable>EXT_NAME</replaceable></command></programlisting> - - </listitem> - - </itemizedlist> - <para> - (The commands above assume that you have created a profile with the same name as the portal you are creating) - </para> - - </step> - <step> - <para> - Access the new portal at <ulink type="http" url="http://localhost:8080/EXT_NAME" /> - </para> - - </step> - - </procedure> - - <note> - <title>Portal Content</title> - <para> - At this point the new portal container will have the same content as the original <literal>ecmdemo</literal>. As a result, much of the web content (stylesheets, links, etc.) will still use the <ulink type="http" url="/ecmdemo" /> context and may not be displayed properly (unless the original site is deployed as well). - </para> - <para> - Also, as the the portals in <literal>ecmdemo</literal> use separate <literal>SingleContentViewer</literal> portlets to display the <guilabel>Login</guilabel>, <guilabel>Register</guilabel> and <guilabel>Language</guilabel> links and not the <literal>BannerPortlet</literal> (as they do in the default <ulink type="http" url="/portal" /> container URL context), the links will not work in your new portal context. - </para> - - </note> - - </section> - - <section id="sect-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-Add_a_new_portalwebsite"> - <title>Add a new portal/website</title> - <para> - Within the <filename>webapp/WEB-INF/CONF</filename> directory is the main configuration entry point for the portal container; <filename>configuration.xml</filename>. This file imports all the required configurations from the <filename>sample-portal</filename> subdirectory. - </para> - -<screen>EXT_NAME/ -└── webapp - └── src - └── main - └── webapp - └── WEB-INF - └── conf - ├── configuration.xml - └── sample-portal - ├── portal - │ └── portal-configuration.xml - └── wcm - └── ... -</screen> - <para> - The <filename>configuration.xml</filename> file defines all the portals and websites in the portal container with the <literal>UserPortalConfigService</literal>. - </para> - <para> - To add a new portal/website to the container follow the steps below: - </para> - <procedure id="proc-Site_Publisher_Installation_Guide-Add_a_new_portalwebsite-Create_a_new_portal"> - <title>Create a new portal</title> - <step> - <para> - Register the new site in the <filename>portal-configuration.xml</filename> file: - </para> - <para> - In this example the new site will be called <emphasis role="bold">demo</emphasis>. - </para> - -<programlisting language="XML" role="XML"><object-param> - <name>portal.configuration</name> - <description>description</description> - <object type="org.exoplatform.portal.config.NewPortalConfig"> - <field name="predefinedOwner"> - <collection type="java.util.HashSet"> - <value> - <string>demo</string> - </value> - <value> - <string>classic</string> - </value> - <value> - <string>acme</string> - </value> - </collection> - </field> - ... -</object-param></programlisting> - - </step> - <step> - <para> - Set the <emphasis role="bold">demo</emphasis> portal as the default. JBoss Enterprise Portal Platform will then redirect to this portal when users access the <ulink type="http" url="EXT_NAME/" /> URL context. - </para> - -<programlisting language="XML" role="XML"><value-param> - <name>default.portal</name> - <description>The default portal for checking db is empty or not</description> - <value>demo</value> -</value-param></programlisting> - - </step> - <step> - <para> - Add the configuration of the portal layout, navigation and pages. These configurations are set in <filename>portal.xml</filename>, <filename>navigation.xml</filename> and <filename>pages.xml</filename>, respectively. - </para> - -<screen>EXT_NAME/ -└── webapp - └── src - └── main - └── webapp - └── WEB-INF - └── conf - └── sample-portal - └── portal - └── portal - ├── acme - │ ├── navigation.xml - │ ├── pages.xml - │ └── portal.xml - ├── classic - │ ├── navigation.xml - │ ├── pages.xml - │ └── portal.xml - └── template - └── acme - ├── navigation.xml - ├── pages.xml - └── portal.xml - -</screen> - - </step> - - </procedure> - - <para> - The most effective way to create a new portal configuration is to copy an existing portal configuration (from the <emphasis role="bold">Classic</emphasis> portal, for example) and modify it to create a new empty portal. - </para> - <para> - This process is explained in more detail in the next section. - </para> - - </section> - - <section id="sect-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-Define_portal_layout"> - <title>Define portal layout</title> - <procedure id="proc-Site_Publisher_Installation_Guide-Define_portal_layout-Define_portal_layout"> - <title>Define portal layout</title> - <step> - <para> - Create folder <emphasis role="bold">demo</emphasis> in the <filename>sample-portal/portal/portal/</filename> directory and copy the <filename>portal.xml</filename> file from the <emphasis role="bold">classic</emphasis> configuration. - </para> - - </step> - <step> - <para> - Edit the <filename>portal.xml</filename> file and change the portal name in the <parameter>portal-name</parameter> element to <emphasis role="bold">demo</emphasis> then replace the contents of the <parameter>portal-layout</parameter> element with the following code: - </para> - -<programlisting language="XML" role="XML"><portal-layout> - - <portlet-application> - <portlet> - <application-ref>web</application-ref> - <portlet-ref>BannerPortlet</portlet-ref> - <preferences> - <preference> - <name>template</name> - <value>par:/groovy/groovy/webui/component/UIBannerPortlet.gtmpl</value> - <read-only>false</read-only> - </preference> - </preferences> - </portlet> - <access-permissions>Everyone</access-permissions> - <show-info-bar>false</show-info-bar> - </portlet-application> - - <portlet-application> - <portlet> - <application-ref>web</application-ref> - <portlet-ref>NavigationPortlet</portlet-ref> - </portlet> - <access-permissions>Everyone</access-permissions> - <show-info-bar>false</show-info-bar> - </portlet-application> - - <container id="MainColumn" template="system:/groovy/portal/webui/container/UITableColumnContainer.gtmpl"> - <container id="PageColumn" template="system:/groovy/portal/webui/container/UIContainer.gtmpl"> - <access-permissions>Everyone</access-permissions> - <page-body/> - </container> - <container id="SideColumn" template="system:/groovy/portal/webui/container/UIContainer.gtmpl"> - <access-permissions>Everyone</access-permissions> - </container> - </container> - - <portlet-application> - <portlet> - <application-ref>web</application-ref> - <portlet-ref>FooterPortlet</portlet-ref> - <preferences> - <preference> - <name>template</name> - <value>par:/groovy/groovy/webui/component/UIFooterPortlet.gtmpl</value> - <read-only>false</read-only> - </preference> - </preferences> - </portlet> - <access-permissions>Everyone</access-permissions> - <show-info-bar>false</show-info-bar> - </portlet-application> - -</portal-layout></programlisting> - <para> - This will create a layout that contains: - </para> - <variablelist> - <title></title> - <varlistentry> - <term>BannerPortlet</term> - <listitem> - <para> - The <literal>BannerPortlet</literal> is a default portlet which is used to display the website's banner and also the Login, Register and Language quick-links on the front page. - </para> - <para> - This portlet's stylesheet can be overridden and customized to better suit your website's design. - </para> - - </listitem> - - </varlistentry> - <varlistentry> - <term>NavigationPortlet</term> - <listitem> - <para> - The <literal>NavigationPortlet</literal> controls portal navigation. - </para> - - </listitem> - - </varlistentry> - <varlistentry> - <term>MainColumn</term> - <listitem> - <para> - The <literal>MainColumn</literal> container is generated by <filename>UITableColumnContainer.gtmpl</filename> template. - </para> - <para> - This template also contains: - </para> - <variablelist> - <title></title> - <varlistentry> - <term>PageColumn</term> - <listitem> - <para> - This container holds the <emphasis role="bold">page-body</emphasis> element. During runtime this element is replaced by the currently selected selected portal page. - </para> - - </listitem> - - </varlistentry> - <varlistentry> - <term>SideColumn</term> - <listitem> - <para> - This container displays the <guilabel>Searchbox</guilabel> and other content elements required on every portal page. - </para> - - </listitem> - - </varlistentry> - - </variablelist> - - </listitem> - - </varlistentry> - <varlistentry> - <term>FooterPortlet</term> - <listitem> - <para> - The <literal>FooterPortlet</literal> is a default JBoss Enterprise Portal Platform portlet. It can be replaced with a custom <literal>SingleContentViewer</literal> portlet. - </para> - - </listitem> - - </varlistentry> - - </variablelist> - - </step> - - </procedure> - - - </section> - - <section id="sect-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-Define_portal_navigation_and_pages"> - <title>Define portal navigation and pages</title> - <para> - It is recommended that portal creators use the <filename>navigation.xml</filename> and <filename>pages.xml</filename> files from the <literal>Classic</literal> portal as templates. - </para> -<programlistingco> - <areaspec> - <area coords="21" id="area-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-Define_portal_navigation_and_pages-nav" /> - <area coords="22" id="area-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-Define_portal_navigation_and_pages-page" /> - </areaspec> -<programlisting>EXT_NAME/ -└── webapp - └── src - └── main - └── webapp - └── WEB-INF - └── conf - └── sample-portal - └── portal - ├── portal - │ ├── acme - │ ├── navigation.xml - │ ├── pages.xml - │ └── portal.xml - ├── classic - │ ├── navigation.xml - │ ├── pages.xml - │ └── portal.xml - └── template - └── acme - ├── navigation.xml - ├── pages.xml - └── portal.xml -</programlisting> - <calloutlist> -  - <callout arearefs="area-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-Define_portal_navigation_and_pages-nav"> - <para> - Edit the <filename>navigation.xml</filename> file and customize the navigational structure of your website. - </para> - <itemizedlist> - <listitem> - <para> - Change page labels from <parameter>#{portal.classic.*}</parameter> to <parameter>#{portal.demo.*}</parameter> - </para> - <para> - The <parameter>#{...}</parameter> notation means the portal will look for a localized label rather than a hardcoded string. - </para> - </listitem> - <listitem> - <para> - Change all page references from <parameter>portal::classic::*</parameter> to <parameter>portal::demo::*</parameter>. - </para> - </listitem> - <listitem> - <para> - Add two new nodes: <literal>docs</literal> and <literal>news</literal>. Other nodes remain as they are. - </para> - </listitem> - </itemizedlist> -<programlisting language="XML" role="XML"><![CDATA[<node-navigation ...> - <priority>1</priority> - <page-nodes> - <node> - <uri>home</uri> - <name>home</name> - <label>#{portal.demo.home}</label> - <visibility>DISPLAYED</visibility> - <page-reference>portal::demo::homepage</page-reference> - </node> - <node> - <uri>docs</uri> - <name>docs</name> - <label>#{portal.demo.docs}</label> - <visibility>DISPLAYED</visibility> - <page-reference>portal::demo::docs</page-reference> - </node> - <node> - <uri>news</uri> - <name>news</name> - <label>#{portal.demo.news}</label> - <visibility>DISPLAYED</visibility> - <page-reference>portal::demo::news</page-reference> - </node> - <node> - ... - </node> - ... - </page-nodes> -</node-navigation>]]></programlisting> - </callout> -  - <callout arearefs="area-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-Define_portal_navigation_and_pages-page"> - <para> - Edit the <filename>pages.xml</filename> file to customize the layout and content of particular pages. - </para> - <itemizedlist> - <listitem> - <para> - Remove the content configured for the classic website's homepage by deleting the container <parameter>ClassicBody</parameter> from the homepage definition in the page-set. - </para> - </listitem> - <listitem> - <para> - Add empty pages <literal>docs</literal> and <literal>news</literal>. Other nodes remain as they are. - </para> - </listitem> - </itemizedlist> - <programlisting language="XML" role="XML"><![CDATA[<page-set ...> - <page> - <name>homepage</name> - <title>Home Page</title> - <access-permissions>Everyone</access-permissions> - <edit-permission>*:/platform/administrators</edit-permission> - -  - - </page> - <page> - <name>docs</name> - <title>Documentation</title> - <access-permissions>Everyone</access-permissions> - <edit-permission>*:/platform/administrators</edit-permission> - - </page> - <page> - <name>news</name> - <title>News</title> - <access-permissions>Everyone</access-permissions> - <edit-permission>*:/platform/administrators</edit-permission> - - </page> - <page> ... </page> - ... - </page-set>]]></programlisting> - </callout> - </calloutlist> -</programlistingco> - - <para> - This will provide a working portal configuration for the new <replaceable>demo</replaceable> portal. It defines a simple portal layout and a basic navigation. The pages will be empty, however, until some webcontent is added to the portal's JCR repository. - </para> - <para> - Later chapters in this guide will discuss how to deploy content. - </para> - </section> - - <section id="sect-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-Localize_the_navigation"> - <title>Localize the navigation</title> - <para> - To localize navigation nodes; - </para> - <procedure> - <step> - <para> - Browse to the <filename>classes/locale/navigation/portal/</filename> folder and create an XML file called <filename>demo_<replaceable><locale></replaceable>.xml</filename> (where <replaceable><locale></replaceable> is the desired localization, <filename>demo_en.xml</filename> for example). - </para> - </step> - <step> - <para> - Populate the file with: - </para> -<programlisting language="XML" role="XML"><![CDATA[<bundle> - <portal> - <demo> - <home>Home</home> - <news>News</news> - <docs>Documentation</docs> - ... - </demo> - </portal> -</bundle>]]></programlisting> - </step> - <step> - <para> - Register your localization in the <filename>conf/sample-portlet/portal/resource-bundle-configuration.xml</filename> file by adding the <parameter>locale.navigation.portal.demo</parameter> to the <parameter>init.resources</parameter> and <parameter>portal.resources.names</parameter> parameters. - </para> - </step> - </procedure> - </section> - - <section id="sect-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-Deploy_custom_content"> - <title>Deploy custom content</title> - <para> - All content managed by Site Publisher is stored in the portal JCR repository. For more information, refer to the <emphasis role="bold">JCR</emphasis> chapter of the JBoss Enterprise Portal Platform Reference Guide at <ulink type="http" url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/index...."></ulink>. - </para> - <para> - Each node can be exported from the repository into an XML file and imported back to an arbitrary location. The export/import functionality can be used via the <application>ContentExplorer portlet</application> which is an integral part of Site Publisher's User Interface. - </para> - <para> - The content can also be imported by the <application>WCMContentInitializerServices</application> which is used to initialize content for the websites in the <emphasis role="bold">ecmodemo</emphasis> project. - </para> - <para> - The <application>TaxonomyPlugin</application> can be used to deploy a custom taxonomy. - </para> - <para> - Site Publisher enables customization of website stylesheets. To customize the styles you can put the CSS files into the <filename>css</filename> directory of the appropriate website's JCR repository. - </para> - <section> - <title>Various web content</title> - <para> - Use the following files and locations in the following procedure to deploy web content: - </para> -<programlisting>EXT_NAME/ -└── webapp - ├── pom.xml - └── src - └── main - └── webapp - └── WEB-INF - └── conf - ├── configuration.xml - └── sample-portal - └── wcm - ├── artifacts - │ └── site-resources - │ └── demo - │ ├── Logo.xml - │ └── ... - └── deployment - └── demo-deployment-configuration.xml -</programlisting> - <procedure id="proc-Site_Publisher_Installation_Guide-Deploy_custom_content-Various_web_content"> - <title>Various web content</title> - <step> - <para> - Build and deploy your application, then start the server. Refer to <xref linkend="sect-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-Deploy_the_application"/> for information on how to do this. - </para> - </step> - <step> - <para> - Access the custom portal container at <ulink type="http" url="http://localhost:8080/EXT_NAME"></ulink>. - </para> - <itemizedlist> - <listitem> - <para> - The container will also contain the <replaceable>EXT_NAME</replaceable> portal project. - </para> - </listitem> - <listitem> - <para> - You will automatically be redirected to <ulink type="http" url="http://localhost:8080/EXT_NAME/public/demo"></ulink>. - </para> - </listitem> - </itemizedlist> - </step> - <step> - <para> - Create, edit or upload content items using the <application>ContentExplorer portlet</application>. - </para> - <itemizedlist> - <listitem> - <para> - The portlet can be accessed via <menuchoice><guimenu>Group</guimenu><guimenuitem>Content Explorer</guimenuitem></menuchoice>. - </para> - </listitem> - <listitem> - <para> - To add content to your portal repository, browse to Sites Management / demo - </para> - </listitem> - <listitem> - <para> - Previously exported content call also be imported via <menuchoice><guimenu>System</guimenu><guimenuitem>Import Node</guimenuitem></menuchoice>. - </para> - </listitem> - </itemizedlist> - </step> - <step> - <para> - Use the <application>ContentExplorer</application> portlet to export the content into XML files - </para> - <itemizedlist> - <listitem> - <para> - Browse to, and open, the the item you wish to export and use the <menuchoice><guimenu>System</guimenu><guimenuitem>Export Node</guimenuitem></menuchoice>. - </para> - </listitem> - <listitem> - <para> - Both singular items and whole directories can be exported. - </para> - </listitem> - <listitem> - <para> - Version history is not required in the export as the <application>WCMContentInitializerService</application> cannot import version information. - </para> - </listitem> - </itemizedlist> - </step> - <step> - <para> - Place the exported XML files into a <emphasis role="bold">demo</emphasis> directory in <filename>webapp/WEB-INF/conf/sample-portal/wcm/artifacts/site-resources/</filename> - </para> - </step> - <step> - <para> - Configure the <application>WCMContentInitializerService</application> to feploy the content to appropriate locations in the JCR. - </para> - <substeps> - <step> - <para> - Navigate to the <filename>/sample-portal/wcm/deployment/</filename> directory. - </para> - </step> - <step> - <para> - Create a configuration file called <filename>demo-deployment-configuration.xml</filename> by making a copy of the <filename>classic-deployment-configuration.xml</filename>. - </para> - </step> - <step> - <para> - Create an entry to import the <filename>demo-deployment-configuration.xml</filename> file in the main configuration <filename>WEB-INF/conf/configuration.xml</filename>file - </para> - </step> - <step> - <para> - Edit the <filename>demo-deployment-configuration.xml</filename> to configure <application>WCMContentInitializer</application> and <application>XMLDeploymentPlugin</application> to deploy your content items to particular locations in your new portal's JCR repository. - </para> - <para> - The <filename>demo-deployment-configuration.xml</filename> contains a configuration of the <application>XMLDeploymentPlugin</application> which has several <application>DeploymentDescriptor</application> object init-params. Each deployment descriptor represents a deployment of a single XML file to a particular JCR location. - </para> - <para> - The <application>DeploymentDescriptor</application> param has the following fields: - </para> - <itemizedlist> - <listitem> - <para> - The <parameter>target</parameter> determines the location in the JCR repository to which the content will be imported. - </para> - </listitem> - <listitem> - <para> - The <parameter>sourcePath</parameter> is the path to the XML file to import. In this case the file is in the application as per <emphasis role="bold">Step 5</emphasis> above. - </para> - </listitem> - <listitem> - <para> - The <parameter>cleanupPublication</parameter> parameter is used as a workaround for a known issue with webcontent that has <emphasis>Publication State</emphasis> data not being successfully imported. - </para> - </listitem> - </itemizedlist> - </step> - </substeps> -<programlisting language="XML" role="XML"><![CDATA[... -<external-component-plugins> - <target-component>org.exoplatform.services.deployment.WCMContentInitializerService</target-component> - <component-plugin> - ... - <type>org.exoplatform.services.deployment.plugins.XMLDeploymentPlugin</type> - <init-params> - <object-param> - <name>Logo</name> - ... - <object type="org.exoplatform.services.deployment.DeploymentDescriptor"> - <field name="target">  - <object type="org.exoplatform.services.deployment.DeploymentDescriptor$Target"> - <field name="repository"><string>repository</string></field> - <field name="workspace"><string>collaboration</string></field> - <field name="nodePath"><string>/sites content/live/demo/medias/images</string></field> - </object> - </field> - <field name="sourcePath"> - <string>war:/conf/sample-portal/wcm/artifacts/site-resources/demo/Logo.xml</string>  - </field> - <field name="cleanupPublication"> - <boolean>true</boolean> - </field> - </object> - </object-param> - <object-param> - ... - </object-param> - ...]]></programlisting> - </step> - <step> - <para> - Edit <filename>/sample-portal/wcm/deployment/template-deployment-configuration.xml</filename> file to disable deployment of template contents into the <emphasis role="bold">demo</emphasis> portal by adding value <literal>demo</literal> to the <parameter>ignored.portals</parameter> list: - </para> -<programlisting language="XML" role="XML"><![CDATA[<component> - <key>org.exoplatform.services.wcm.portal.artifacts.CreatePortalArtifactsService</key> - <type>org.exoplatform.services.wcm.portal.artifacts.CreatePortalArtifactsServiceImpl</type> - <init-params> - <values-param> - <name>ignored.portals</name> - <value>demo</value> - ...]]></programlisting> - </step> - </procedure> - </section> - </section> - - <section id="sect-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-Taxonomies"> - <title>Taxonomies</title> - <para> - - </para> - <procedure> - <step> - <para> - - </para> - - </step> - - </procedure> - - - </section> - - <section id="sect-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-Custom_website_stylesheet"> - <title>Custom website stylesheet</title> - <para> - - </para> - <procedure> - <step> - <para> - - </para> - - </step> - - </procedure> - - - </section> - - <section id="sect-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-Searchbox_stylesheet"> - <title>Searchbox stylesheet</title> - <para> - - </para> - <procedure> - <step> - <para> - - </para> - - </step> - - </procedure> - - - </section> - - <section id="sect-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-Configure_content_presentation_portlets"> - <title>Configure content presentation portlets</title> - <procedure id="proc-Site_Publisher_Installation_Guide-Configure_content_presentation_portlets-SingleContentViewer_portlet_preferences"> - <title>SingleContentViewer portlet preferences</title> - <step> - <para> - - </para> - - </step> - - </procedure> - - - </section> - - <section id="sect-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-ContentListViewer_portlet_preferences"> - <title>ContentListViewer portlet preferences</title> - <para> - - </para> - <procedure> - <step> - <para> - - </para> - - </step> - - </procedure> - - - </section> - - <section id="sect-Site_Publisher_Installation_Guide-Create_a_Site_Using_The_Demo-Other_configurations"> - <title>Other configurations</title> - <procedure id="proc-Site_Publisher_Installation_Guide-Other_configurations-Newsletter_configuration"> - <title>Newsletter configuration</title> - <step> - <para> - - </para> - - </step> - - </procedure> - - - </section> - - -</chapter> - Modified: epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Site_Publisher_Installation_Guide.xml =================================================================== --- epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Site_Publisher_Installation_Guide.xml 2011-12-05 04:34:52 UTC (rev 8192) +++ epp/docs/branches/5.2/Site_Publisher/Installation_Guide/en-US/Site_Publisher_Installation_Guide.xml 2011-12-05 21:10:57 UTC (rev 8193) @@ -4,12 +4,11 @@ %BOOK_ENTITIES; ]> <book> - <xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Create_A_Site.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <index /> + <xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="Introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="Installation.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <index /> </book>

13 years

1
0
0 / 0

gatein SVN: r8192 - in portal/trunk/docs/reference-guide/en-US/modules: AuthenticationAndIdentity and 1 other directory.

by do-not-reply＠jboss.org

Author: smumford Date: 2011-12-04 23:34:52 -0500 (Sun, 04 Dec 2011) New Revision: 8192 Modified: portal/trunk/docs/reference-guide/en-US/modules/AuthenticationAndIdentity/SSO.xml portal/trunk/docs/reference-guide/en-US/modules/WSRP.xml Log: JBEPP-1431: Actioning QE feedback Modified: portal/trunk/docs/reference-guide/en-US/modules/AuthenticationAndIdentity/SSO.xml =================================================================== --- portal/trunk/docs/reference-guide/en-US/modules/AuthenticationAndIdentity/SSO.xml 2011-12-05 04:33:56 UTC (rev 8191) +++ portal/trunk/docs/reference-guide/en-US/modules/AuthenticationAndIdentity/SSO.xml 2011-12-05 04:34:52 UTC (rev 8192) @@ -336,7 +336,7 @@ <section id="sect-Reference_Guide-CAS_Central_Authentication_Service-CAS_server"> <title>CAS server</title> <para> - First, set up the server to authenticate against the portal login module. In this example, the CAS server is installed on Tomcat. + First, set up the server to authenticate against the portal login module. In this example, the CAS server is installed on Tomcat. </para> <section id="sect-Reference_Guide-CAS_server-Obtaining_CAS"> <title>Obtaining CAS</title> @@ -352,7 +352,7 @@ <section id="sect-Reference_Guide-CAS_server-Modifying_CAS_server"> <title>Modifying the CAS server</title> <para> - To configure the web archive as desired, the simplest way is to make the necessary changes directly in the CAS codebase. + To configure the web archive as desired, the simplest way is to make the necessary changes directly in the CAS codebase. </para> <note> <para> @@ -361,10 +361,10 @@ </para> </note> <para> - First, change the default authentication handler with the one provided by &PRODUCT;. + First, change the default authentication handler with the one provided by &PRODUCT;. </para> <para> - The CAS Server Plugin makes secure authentication callbacks to a RESTful service installed on the remote &PRODUCT; server to authenticate a user. + The CAS Server Plugin makes secure authentication callbacks to a RESTful service installed on the remote &PRODUCT; server to authenticate a user. </para> <para> In order for the plugin to function correctly, it needs to be properly configured to connect to this service. This configuration is done via the <filename>cas.war/WEB-INF/deployerConfigContext.xml </filename> file. @@ -457,7 +457,7 @@ Change the default port to avoid a conflict with the default &PRODUCT; (for testing purposes). Edit <filename>TOMCAT_HOME/conf/server.xml</filename> and replace the 8080 port to 8888. <note> <para> - If &PRODUCT; is running on the same machine as Tomcat, other ports need to be changed in addition to 8080 to avoid port conflicts. + If &PRODUCT; is running on the same machine as Tomcat, other ports need to be changed in addition to 8080 to avoid port conflicts. They can be changed to any free port. For example, you can change admin port from 8005 to 8805, and AJP port from 8009 to 8809. </para> </note> @@ -513,7 +513,7 @@ <itemizedlist> <listitem> <para> - In JBoss AS, edit <filename>gatein.ear/META-INF/gatein-jboss-beans.xml</filename> and uncomment on this section: + In JBoss AS, edit <filename>gatein.ear/META-INF/gatein-jboss-beans.xml</filename> and uncomment on this section: </para> <programlisting> <![CDATA[ @@ -533,7 +533,7 @@ </listitem> <listitem> <para> - In Tomcat, edit <filename>GATEIN_HOME/conf/jaas.conf</filename>, uncomment on this section and comment other parts: + In Tomcat, edit <filename>GATEIN_HOME/conf/jaas.conf</filename>, uncomment on this section and comment other parts: </para> <programlisting>org.gatein.sso.agent.login.SSOLoginModule required; org.exoplatform.services.security.j2ee.TomcatLoginModule required @@ -687,18 +687,18 @@ <section id="sect-Reference_Guide-Single_Sign_On-JOSSO"> <title>JOSSO</title> <para> - This Single-Sign-On plugin enables the seamless integration between &PRODUCT; and the JOSSO Single-Sign-On Framework. Details about JOSSO can be found <ulink url="http://www.josso.org">here</ulink>. + This Single-Sign-On plugin enables the seamless integration between &PRODUCT; and the JOSSO Single-Sign-On Framework. Details about JOSSO can be found <ulink url="http://www.josso.org">here</ulink>. </para> <para> - Setting up this integration consists of two steps: installing/configuring a JOSSO server, and setting up the portal to use the JOSSO server. + Setting up this integration consists of two steps: installing/configuring a JOSSO server, and setting up the portal to use the JOSSO server. </para> <section id="sect-Reference_Guide-JOSSO-JOSSO_server"> <title>JOSSO server</title> <para> - This section describes how to set up the JOSSO server to authenticate against the &PRODUCT; login module. + This section describes how to set up the JOSSO server to authenticate against the &PRODUCT; login module. </para> <para> - In this example, the JOSSO server will be installed on Tomcat. + In this example, the JOSSO server will be installed on Tomcat. </para> <section id="sect-Reference_Guide-JOSSO_server-Obtaining_JOSSO"> <title>Obtaining JOSSO</title> @@ -981,7 +981,7 @@ </section> <section id="sect-Reference_Guide-OpenSSO_server-Modifying_OpenSSO_server"> - <title>Modifying the OpenSSO server</title> + <title>Modifying the OpenSSO server</title> <para> To configure the web server as desired, it is simpler to directly modify the sources. </para> @@ -989,7 +989,7 @@ The first step is to add the &PRODUCT; Authentication Plugin: </para> <para> - The plugin makes secure authentication callbacks to a RESTful service installed on the remote &PRODUCT; server to authenticate a user. + The plugin makes secure authentication callbacks to a RESTful service installed on the remote &PRODUCT; server to authenticate a user. </para> <para> In order for the plugin to function correctly, it needs to be properly configured to connect to this service. This configuration is done via the <filename>opensso.war/config/auth/default/AuthenticationPlugin.xml</filename> file. @@ -1002,7 +1002,7 @@ </step> <step> <para> - Change the default port to avoid a conflict with the default &PRODUCT; port (for testing purposes) by editing <filename>TOMCAT_HOME/conf/server.xml</filename> and replacing the 8080 port with 8888. + Change the default port to avoid a conflict with the default &PRODUCT; port (for testing purposes) by editing <filename>TOMCAT_HOME/conf/server.xml</filename> and replacing the 8080 port with 8888. <note> <para> If &PRODUCT; is running on the same machine as Tomcat, other ports need to be changed in addition to 8080 to avoid port conflicts. @@ -1140,7 +1140,7 @@ </listitem> <listitem> <para> - If you are running &PRODUCT; in Tomcat, edit $GATEIN_HOME/conf/jaas.conf, uncomment on this section and comment other parts: + If you are running &PRODUCT; in Tomcat, edit $GATEIN_HOME/conf/jaas.conf, uncomment on this section and comment other parts: </para> <programlisting>org.gatein.sso.agent.login.SSOLoginModule required; org.exoplatform.services.security.j2ee.TomcatLoginModule required @@ -1572,7 +1572,7 @@ adding the 'SPNEGO' authenticators property. </para> -<programlisting language="xml"> +<programlisting language="XML"> <![CDATA[<deployment xmlns="urn:jboss:bean-deployer:2.0"> <property name="authenticators"> <map class="java.util.Properties" keyClass="java.lang.String" valueClass="java.lang.String"> @@ -1625,7 +1625,7 @@ Modify the <emphasis role="bold">JBOSS_HOME/server/defaut/deploy/gatein.ear/META-INF/gatein-jboss-beans.xml</emphasis> file as below: </para> - <programlisting language="xml"><![CDATA[ + <programlisting language="XML"><![CDATA[ <deployment xmlns="urn:jboss:bean-deployer:2.0"> <application-policy xmlns="urn:jboss:security-beans:1.0" name="gatein-form-auth-domain"> @@ -1691,7 +1691,7 @@ <para> Modify <emphasis role="bold">JBOSS_HOME/server/default/deploy/gatein.ear/02portal.war/WEB-INF/web.xml</emphasis> as below.</para> - <programlisting language="xml"><![CDATA[ + <programlisting language="XML"><![CDATA[ <!-- <login-config> <auth-method>FORM</auth-method> <realm-name>gatein-domain</realm-name> Modified: portal/trunk/docs/reference-guide/en-US/modules/WSRP.xml =================================================================== --- portal/trunk/docs/reference-guide/en-US/modules/WSRP.xml 2011-12-05 04:33:56 UTC (rev 8191) +++ portal/trunk/docs/reference-guide/en-US/modules/WSRP.xml 2011-12-05 04:34:52 UTC (rev 8192) @@ -171,7 +171,7 @@ for more details. </para> <para> - Of course, if you have modified you have modified the host name and port on which your server runs, you will + Of course, if you have modified the host name and port on which your server runs, you will need to update the configuration for the consumer used to consume &PRODUCT_NAME;'s 'self' producer. Please refer to the @@ -233,7 +233,7 @@ <para>&PRODUCT_NAME; 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 indepth configuration options. Please note that since the consumer passes its credentials - to the producer, the consumer will act at the wss client and the producer will act as the wss server. + to the producer, the consumer will act as the wss client and the producer will act as the wss server. </para> <para> The following are the JBossWS Native configuration files which need to be configure for WSRP: </para> @@ -294,16 +294,16 @@ </para> <itemizedlist> <listitem> - <para>The JBossWS configuration files must be configured</para> + <para>The JBossWS configuration files must be configured.</para> </listitem> <listitem> - <para>The filter must be added to the portal's web.xml</para> + <para>The filter must be added to the portal's web.xml.</para> </listitem> <listitem> - <para>the enable wss feature must be check in the wsrp admin</para> + <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> + <para>The consumer will not properly handle ws-security unless all 3 are properly configured.</para> </note> </sect2> </sect1> @@ -356,9 +356,7 @@ <para> It is also possible to specify that all the portlets declared within a given portlet application to be remotable by default. This is done by specifying the - <code> - container-runtime-option - </code> + <code>container-runtime-option</code> at the <code>portlet-app</code> element level. Individual portlets can override that value to not be remotely exposed. Let's look at an @@ -415,11 +413,11 @@ <varname>RemotelyExposedPortlet</varname> inherits the remotable status defined at the <code>portlet-app</code> - level since it does not specify a value for the<code>org.gatein.pc.remotable container-runtime-option</code>. + level since it does not specify a value for the <code>org.gatein.pc.remotable container-runtime-option</code>. The<varname>NotRemotelyExposedPortlet</varname>, however, overrides the default behavior and is not remotely exposed. Note that in the absence of a top-level <code>org.gatein.pc.remotable container-runtime-option</code> - value set to<code>true</code>, portlets are NOT remotely exposed. + value set to <code>true</code>, portlets are NOT remotely exposed. </para> </sect1> @@ -481,7 +479,7 @@ <para> &PRODUCT_NAME; provides a portlet to configure access (among other functions) to remote WSRP Producers - grahically. Starting with &PRODUCT_VERSION;, the WSRP configuration portlet is installed by default. You + graphically. Starting with &PRODUCT_VERSION;, the WSRP configuration portlet is installed by default. You can find it at <ulink url="http://localhost:8080/portal/login?initialURI=%2Fportal%2Fprivate%2Fclass..."> @@ -592,7 +590,7 @@ properties, as is the case for the <literal>selfv2</literal> consumer (the consumer that accesses the portlets made remotely available by &PRODUCT_NAME;'s producer via - WSRP 2), we'd have seen something similar to, after pressing the "Refresh & Save" button: + WSRP 2), we'd have seen something similar to the screenshot below, after pressing the "Refresh & Save" button: <mediaobject> <imageobject> <imagedata fileref="images/WSRP/config_refresh.png" format="PNG" align="center" valign="middle"

13 years

1
0
0 / 0

gatein SVN: r8191 - in epp/docs/branches/5.2/Reference_Guide/en-US: extras/PortalDevelopment_DefaultPortalPermissionConfiguration and 10 other directories.

by do-not-reply＠jboss.org

Author: smumford Date: 2011-12-04 23:33:56 -0500 (Sun, 04 Dec 2011) New Revision: 8191 Modified: epp/docs/branches/5.2/Reference_Guide/en-US/extras/PortalDevelopment_DefaultPortalNavigationConfiguration/gadgets.xml epp/docs/branches/5.2/Reference_Guide/en-US/extras/PortalDevelopment_DefaultPortalPermissionConfiguration/default145.xml epp/docs/branches/5.2/Reference_Guide/en-US/icons/icon.svg epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Configuring_Services.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalConfiguration.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalNavigationConfiguration.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/NavigationController.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/PortalLifecycle.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/WSRP.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/backup/exojcr-backup-service.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/nodetype-registration.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/jbosscache-configuration-templates.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/other/jcr-resources.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/protocols/ftp.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/query-handler-config.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/statistics.xml Log: JBEPP-1431: Actioning QE feedback Modified: epp/docs/branches/5.2/Reference_Guide/en-US/extras/PortalDevelopment_DefaultPortalNavigationConfiguration/gadgets.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/extras/PortalDevelopment_DefaultPortalNavigationConfiguration/gadgets.xml 2011-12-05 03:51:59 UTC (rev 8190) +++ epp/docs/branches/5.2/Reference_Guide/en-US/extras/PortalDevelopment_DefaultPortalNavigationConfiguration/gadgets.xml 2011-12-05 04:33:56 UTC (rev 8191) @@ -7,15 +7,15 @@ <gadget name="Todo"> <path>/gadgets/Todo/Todo.xml</path> </gadget> - + <gadget name="Calendar"> <path>/gadgets/Calendar/Calendar.xml</path> </gadget> - + <gadget name="Calculator"> <path>/gadgets/Calculator/Calculator.xml</path> </gadget> - + <gadget name="rssAggregator"> <path>/gadgets/rssAggregator/rssAggregator.xml</path> </gadget> @@ -23,4 +23,8 @@ <gadget name="Currency"> <url>http://www.donalobrien.net/apps/google/currency.xml</url> </gadget> + + <gadget name="ServiceMangement"> + <path>/gadgets/ServiceManagement/ServiceManagement.xml</path> + </gadget> </gadgets> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/extras/PortalDevelopment_DefaultPortalPermissionConfiguration/default145.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/extras/PortalDevelopment_DefaultPortalPermissionConfiguration/default145.xml 2011-12-05 03:51:59 UTC (rev 8190) +++ epp/docs/branches/5.2/Reference_Guide/en-US/extras/PortalDevelopment_DefaultPortalPermissionConfiguration/default145.xml 2011-12-05 04:33:56 UTC (rev 8191) @@ -25,16 +25,16 @@ <value>/platform/guests</value> </value-param> <values-param> - <name>mandatory.groups</name> - <description>Groups that can not be deleted.</description> - <value>/platform/administrators</value> - <value>/platform/users</value> - <value>/platform/guests</value> - </values-param> - <values-param> - <name>mandatory.mstypes</name> - <description>Membership type that can not be deleted.</description> - <value>member</value> - </values-param> + <name>mandatory.groups</name> + <description>Groups that can not be deleted.</description> + <value>/platform/administrators</value> + <value>/platform/users</value> + <value>/platform/guests</value> + </values-param> + <values-param> + <name>mandatory.mstypes</name> + <description>Membership type that can not be deleted.</description> + <value>member</value> + </values-param> </init-params> -</component> +</component> \ No newline at end of file Modified: epp/docs/branches/5.2/Reference_Guide/en-US/icons/icon.svg =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/icons/icon.svg 2011-12-05 03:51:59 UTC (rev 8190) +++ epp/docs/branches/5.2/Reference_Guide/en-US/icons/icon.svg 2011-12-05 04:33:56 UTC (rev 8191) @@ -1,3936 +1,19 @@ <?xml version="1.0" encoding="UTF-8" standalone="no"?> - -<svg - xmlns:ns="http://ns.adobe.com/AdobeSVGViewerExtensions/3/" - xmlns:a="http://ns.adobe.com/AdobeSVGViewerExtensions/3.0/" - xmlns:dc="http://purl.org/dc/elements/1.1/" - xmlns:cc="http://web.resource.org/cc/" - xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" - xmlns:svg="http://www.w3.org/2000/svg" - xmlns="http://www.w3.org/2000/svg" - xmlns:xlink="http://www.w3.org/1999/xlink" - xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd" - xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape" - version="1.0" - width="32" - height="32" - id="svg3017" - sodipodi:version="0.32" - inkscape:version="0.44+devel" - sodipodi:docname="book.svg" - sodipodi:docbase="/home/andy/Desktop"> - <metadata - id="metadata489"> - <rdf:RDF> - <cc:Work - rdf:about=""> - <dc:format>image/svg+xml</dc:format> - <dc:type - rdf:resource="http://purl.org/dc/dcmitype/StillImage" /> - </cc:Work> - </rdf:RDF> - </metadata> - <sodipodi:namedview - inkscape:window-height="480" - inkscape:window-width="858" - inkscape:pageshadow="0" - inkscape:pageopacity="0.0" - guidetolerance="10.0" - gridtolerance="10.0" - objecttolerance="10.0" - borderopacity="1.0" - bordercolor="#666666" - pagecolor="#ffffff" - id="base" - inkscape:zoom="1" - inkscape:cx="16" - inkscape:cy="15.944056" - inkscape:window-x="0" - inkscape:window-y="33" - inkscape:current-layer="svg3017" /> - <defs - id="defs3019"> - <linearGradient - id="linearGradient2381"> - <stop - style="stop-color:white;stop-opacity:1" - offset="0" - id="stop2383" /> - <stop - style="stop-color:white;stop-opacity:0" - offset="1" - id="stop2385" /> +<svg xmlns:svg="http://www.w3.org/2000/svg" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" version="1.0" width="32" height="32" id="svg3017"> + <defs id="defs3019"> + <linearGradient id="linearGradient2381"> + <stop id="stop2383" style="stop-color:#ffffff;stop-opacity:1" offset="0"/> + <stop id="stop2385" style="stop-color:#ffffff;stop-opacity:0" offset="1"/> </linearGradient> - <linearGradient - x1="415.73831" - y1="11.854" - x2="418.13361" - y2="18.8104" - id="XMLID_1758_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.8362,0.5206,-1.1904,0.992,147.62,-30.9374)"> - <stop - style="stop-color:#ccc;stop-opacity:1" - offset="0" - id="stop3903" /> - <stop - style="stop-color:#f2f2f2;stop-opacity:1" - offset="1" - id="stop3905" /> - <a:midPointStop - style="stop-color:#CCCCCC" - offset="0" /> - <a:midPointStop - style="stop-color:#CCCCCC" - offset="0.5" /> - <a:midPointStop - style="stop-color:#F2F2F2" - offset="1" /> - </linearGradient> - <linearGradient - x1="500.70749" - y1="-13.2441" - x2="513.46442" - y2="-2.1547" - id="XMLID_1757_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)"> - <stop - style="stop-color:#5387ba;stop-opacity:1" - offset="0" - id="stop3890" /> - <stop - style="stop-color:#96bad6;stop-opacity:1" - offset="1" - id="stop3892" /> - <a:midPointStop - style="stop-color:#5387BA" - offset="0" /> - <a:midPointStop - style="stop-color:#5387BA" - offset="0.5" /> - <a:midPointStop - style="stop-color:#96BAD6" - offset="1" /> - </linearGradient> - <clipPath - id="XMLID_1755_"> - <use - id="use3874" - x="0" - y="0" - width="744.09448" - height="600" - xlink:href="#XMLID_343_" /> - </clipPath> - <linearGradient - x1="505.62939" - y1="-14.9526" - x2="527.49402" - y2="-0.7536" - id="XMLID_1756_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)"> - <stop - style="stop-color:#b4daea;stop-opacity:1" - offset="0" - id="stop3877" /> - <stop - style="stop-color:#b4daea;stop-opacity:1" - offset="0.51120001" - id="stop3879" /> - <stop - style="stop-color:#5387ba;stop-opacity:1" - offset="0.64609998" - id="stop3881" /> - <stop - style="stop-color:#16336e;stop-opacity:1" - offset="1" - id="stop3883" /> - <a:midPointStop - style="stop-color:#B4DAEA" - offset="0" /> - <a:midPointStop - style="stop-color:#B4DAEA" - offset="0.5" /> - <a:midPointStop - style="stop-color:#B4DAEA" - offset="0.5112" /> - <a:midPointStop - style="stop-color:#B4DAEA" - offset="0.5" /> - <a:midPointStop - style="stop-color:#5387BA" - offset="0.6461" /> - <a:midPointStop - style="stop-color:#5387BA" - offset="0.5" /> - <a:midPointStop - style="stop-color:#16336E" - offset="1" /> - </linearGradient> - <linearGradient - x1="471.0806" - y1="201.07761" - x2="481.91711" - y2="210.4977" - id="XMLID_1754_" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:#6498c1;stop-opacity:1" - offset="0.005618" - id="stop3863" /> - <stop - style="stop-color:#79a9cc;stop-opacity:1" - offset="0.2332" - id="stop3865" /> - <stop - style="stop-color:#a4cde2;stop-opacity:1" - offset="0.74049997" - id="stop3867" /> - <stop - style="stop-color:#b4daea;stop-opacity:1" - offset="1" - id="stop3869" /> - <a:midPointStop - style="stop-color:#6498C1" - offset="5.618000e-003" /> - <a:midPointStop - style="stop-color:#6498C1" - offset="0.4438" /> - <a:midPointStop - style="stop-color:#B4DAEA" - offset="1" /> - </linearGradient> - <linearGradient - x1="516.57672" - y1="-15.769" - x2="516.57672" - y2="0.84280002" - id="XMLID_1753_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)"> - <stop - style="stop-color:#b2b2b2;stop-opacity:1" - offset="0" - id="stop3851" /> - <stop - style="stop-color:#f2f2f2;stop-opacity:1" - offset="1" - id="stop3853" /> - <a:midPointStop - style="stop-color:#B2B2B2" - offset="0" /> - <a:midPointStop - style="stop-color:#B2B2B2" - offset="0.5" /> - <a:midPointStop - style="stop-color:#F2F2F2" - offset="1" /> - </linearGradient> - <clipPath - id="XMLID_1751_"> - <use - id="use3837" - x="0" - y="0" - width="744.09448" - height="600" - xlink:href="#XMLID_338_" /> - </clipPath> - <linearGradient - x1="506.09909" - y1="-11.5137" - x2="527.99609" - y2="2.7063999" - id="XMLID_1752_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)"> - <stop - style="stop-color:#b4daea;stop-opacity:1" - offset="0" - id="stop3840" /> - <stop - style="stop-color:#b4daea;stop-opacity:1" - offset="0.51120001" - id="stop3842" /> - <stop - style="stop-color:#5387ba;stop-opacity:1" - offset="0.64609998" - id="stop3844" /> - <stop - style="stop-color:#16336e;stop-opacity:1" - offset="1" - id="stop3846" /> - <a:midPointStop - style="stop-color:#B4DAEA" - offset="0" /> - <a:midPointStop - style="stop-color:#B4DAEA" - offset="0.5" /> - <a:midPointStop - style="stop-color:#B4DAEA" - offset="0.5112" /> - <a:midPointStop - style="stop-color:#B4DAEA" - offset="0.5" /> - <a:midPointStop - style="stop-color:#5387BA" - offset="0.6461" /> - <a:midPointStop - style="stop-color:#5387BA" - offset="0.5" /> - <a:midPointStop - style="stop-color:#16336E" - offset="1" /> - </linearGradient> - <linearGradient - x1="468.2915" - y1="204.7612" - x2="479.39871" - y2="214.4166" - id="XMLID_1750_" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:#5387ba;stop-opacity:1" - offset="0" - id="stop3830" /> - <stop - style="stop-color:#96bad6;stop-opacity:1" - offset="1" - id="stop3832" /> - <a:midPointStop - style="stop-color:#5387BA" - offset="0" /> - <a:midPointStop - style="stop-color:#5387BA" - offset="0.5" /> - <a:midPointStop - style="stop-color:#96BAD6" - offset="1" /> - </linearGradient> - <linearGradient - x1="502.70749" - y1="115.3013" - x2="516.39001" - y2="127.1953" - id="XMLID_1749_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.9703,0.2419,-0.2419,0.9703,11.0227,-35.6159)"> - <stop - style="stop-color:#5387ba;stop-opacity:1" - offset="0" - id="stop3818" /> - <stop - style="stop-color:#96bad6;stop-opacity:1" - offset="1" - id="stop3820" /> - <a:midPointStop - style="stop-color:#5387BA" - offset="0" /> - <a:midPointStop - style="stop-color:#5387BA" - offset="0.5" /> - <a:midPointStop - style="stop-color:#96BAD6" - offset="1" /> - </linearGradient> - <linearGradient - x1="501.0903" - y1="-19.2544" - x2="531.85413" - y2="0.72390002" - id="XMLID_1748_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)"> - <stop - style="stop-color:#b4daea;stop-opacity:1" - offset="0" - id="stop3803" /> - <stop - style="stop-color:#b4daea;stop-opacity:1" - offset="0.51120001" - id="stop3805" /> - <stop - style="stop-color:#5387ba;stop-opacity:1" - offset="0.64609998" - id="stop3807" /> - <stop - style="stop-color:#16336e;stop-opacity:1" - offset="1" - id="stop3809" /> - <a:midPointStop - style="stop-color:#B4DAEA" - offset="0" /> - <a:midPointStop - style="stop-color:#B4DAEA" - offset="0.5" /> - <a:midPointStop - style="stop-color:#B4DAEA" - offset="0.5112" /> - <a:midPointStop - style="stop-color:#B4DAEA" - offset="0.5" /> - <a:midPointStop - style="stop-color:#5387BA" - offset="0.6461" /> - <a:midPointStop - style="stop-color:#5387BA" - offset="0.5" /> - <a:midPointStop - style="stop-color:#16336E" - offset="1" /> - </linearGradient> - <linearGradient - x1="481.23969" - y1="212.5742" - x2="472.92981" - y2="207.4967" - id="XMLID_2275_" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:#f3403f;stop-opacity:1" - offset="0" - id="stop9947" /> - <stop - style="stop-color:#d02a28;stop-opacity:1" - offset="0.37889999" - id="stop9949" /> - <stop - style="stop-color:#b21714;stop-opacity:1" - offset="0.77649999" - id="stop9951" /> - <stop - style="stop-color:#a6100c;stop-opacity:1" - offset="1" - id="stop9953" /> - <a:midPointStop - style="stop-color:#F3403F" - offset="0" /> - <a:midPointStop - style="stop-color:#F3403F" - offset="0.4213" /> - <a:midPointStop - style="stop-color:#A6100C" - offset="1" /> - </linearGradient> - <clipPath - id="XMLID_2273_"> - <use - id="use9933" - x="0" - y="0" - width="744.09448" - height="600" - xlink:href="#XMLID_960_" /> - </clipPath> - <linearGradient - x1="473.7681" - y1="209.17529" - x2="486.98099" - y2="213.2001" - id="XMLID_2274_" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:#f3403f;stop-opacity:1" - offset="0" - id="stop9936" /> - <stop - style="stop-color:#d02a28;stop-opacity:1" - offset="0.37889999" - id="stop9938" /> - <stop - style="stop-color:#b21714;stop-opacity:1" - offset="0.77649999" - id="stop9940" /> - <stop - style="stop-color:#a6100c;stop-opacity:1" - offset="1" - id="stop9942" /> - <a:midPointStop - style="stop-color:#F3403F" - offset="0" /> - <a:midPointStop - style="stop-color:#F3403F" - offset="0.4213" /> - <a:midPointStop - style="stop-color:#A6100C" - offset="1" /> - </linearGradient> - <linearGradient - x1="478.21341" - y1="-131.9297" - x2="469.85818" - y2="-140.28481" - id="XMLID_2272_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.5592,0.829,-0.829,0.5592,101.3357,-104.791)"> - <stop - style="stop-color:#f3403f;stop-opacity:1" - offset="0" - id="stop9917" /> - <stop - style="stop-color:#d02a28;stop-opacity:1" - offset="0.37889999" - id="stop9919" /> - <stop - style="stop-color:#b21714;stop-opacity:1" - offset="0.77649999" - id="stop9921" /> - <stop - style="stop-color:#a6100c;stop-opacity:1" - offset="1" - id="stop9923" /> - <a:midPointStop - style="stop-color:#F3403F" - offset="0" /> - <a:midPointStop - style="stop-color:#F3403F" - offset="0.4213" /> - <a:midPointStop - style="stop-color:#A6100C" - offset="1" /> - </linearGradient> - <marker - refX="0" - refY="0" - orient="auto" - style="overflow:visible" - id="TriangleInM"> - <path - d="M 5.77,0 L -2.88,5 L -2.88,-5 L 5.77,0 z " - transform="scale(-0.4,-0.4)" - style="fill:#5c5c4f" - id="path3197" /> - </marker> - <linearGradient - x1="200.7363" - y1="100.4028" - x2="211.99519" - y2="89.143997" - id="XMLID_3298_" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:#bfbfbf;stop-opacity:1" - offset="0" - id="stop20103" /> - <stop - style="stop-color:#f2f2f2;stop-opacity:1" - offset="1" - id="stop20105" /> - <a:midPointStop - offset="0" - style="stop-color:#BFBFBF" /> - <a:midPointStop - offset="0.5" - style="stop-color:#BFBFBF" /> - <a:midPointStop - offset="1" - style="stop-color:#F2F2F2" /> - </linearGradient> - <linearGradient - x1="200.7363" - y1="100.4028" - x2="211.99519" - y2="89.143997" - id="linearGradient36592" - xlink:href="#XMLID_3298_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1.029078,0,0,1,-183.2624,-79.44655)" /> - <linearGradient - x1="181.2925" - y1="110.8481" - x2="192.6369" - y2="99.5037" - id="XMLID_3297_" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:#e5e5e5;stop-opacity:1" - offset="0" - id="stop20096" /> - <stop - style="stop-color:#ccc;stop-opacity:1" - offset="1" - id="stop20098" /> - <a:midPointStop - offset="0" - style="stop-color:#E5E5E5" /> - <a:midPointStop - offset="0.5" - style="stop-color:#E5E5E5" /> - <a:midPointStop - offset="1" - style="stop-color:#CCCCCC" /> - </linearGradient> - <linearGradient - x1="181.2925" - y1="110.8481" - x2="192.6369" - y2="99.5037" - id="linearGradient36595" - xlink:href="#XMLID_3297_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1.029078,0,0,1,-183.2624,-79.44655)" /> - <linearGradient - x1="211.77589" - y1="105.7749" - x2="212.6619" - y2="108.2092" - id="XMLID_3296_" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:#0f6124;stop-opacity:1" - offset="0" - id="stop20087" /> - <stop - style="stop-color:#219630;stop-opacity:1" - offset="1" - id="stop20089" /> - <a:midPointStop - offset="0" - style="stop-color:#0F6124" /> - <a:midPointStop - offset="0.5" - style="stop-color:#0F6124" /> - <a:midPointStop - offset="1" - style="stop-color:#219630" /> - </linearGradient> - <linearGradient - x1="211.77589" - y1="105.7749" - x2="212.6619" - y2="108.2092" - id="linearGradient36677" - xlink:href="#XMLID_3296_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1.029078,0,0,1,-183.2624,-79.44655)" /> - <linearGradient - x1="208.9834" - y1="116.8296" - x2="200.0811" - y2="96.834602" - id="XMLID_3295_" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:#b2b2b2;stop-opacity:1" - offset="0" - id="stop20076" /> - <stop - style="stop-color:#e5e5e5;stop-opacity:1" - offset="0.5" - id="stop20078" /> - <stop - style="stop-color:white;stop-opacity:1" - offset="1" - id="stop20080" /> - <a:midPointStop - offset="0" - style="stop-color:#B2B2B2" /> - <a:midPointStop - offset="0.5" - style="stop-color:#B2B2B2" /> - <a:midPointStop - offset="0.5" - style="stop-color:#E5E5E5" /> - <a:midPointStop - offset="0.5" - style="stop-color:#E5E5E5" /> - <a:midPointStop - offset="1" - style="stop-color:#FFFFFF" /> - </linearGradient> - <linearGradient - x1="208.9834" - y1="116.8296" - x2="200.0811" - y2="96.834602" - id="linearGradient36604" - xlink:href="#XMLID_3295_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1.029078,0,0,1,-183.2624,-79.44655)" /> - <linearGradient - x1="195.5264" - y1="97.911102" - x2="213.5213" - y2="115.9061" - id="XMLID_3294_" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:#ccc;stop-opacity:1" - offset="0" - id="stop20069" /> - <stop - style="stop-color:white;stop-opacity:1" - offset="1" - id="stop20071" /> - <a:midPointStop - offset="0" - style="stop-color:#CCCCCC" /> - <a:midPointStop - offset="0.5" - style="stop-color:#CCCCCC" /> - <a:midPointStop - offset="1" - style="stop-color:#FFFFFF" /> - </linearGradient> - <linearGradient - x1="195.5264" - y1="97.911102" - x2="213.5213" - y2="115.9061" - id="linearGradient36607" - xlink:href="#XMLID_3294_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1.029078,0,0,1,-183.2624,-79.44655)" /> - <linearGradient - x1="186.1938" - y1="109.1343" - x2="206.6881" - y2="88.639999" - id="XMLID_3293_" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:#b2b2b2;stop-opacity:1" - offset="0" - id="stop20056" /> - <stop - style="stop-color:#e5e5e5;stop-opacity:1" - offset="0.16850001" - id="stop20058" /> - <stop - style="stop-color:white;stop-opacity:1" - offset="0.23029999" - id="stop20060" /> - <stop - style="stop-color:#e5e5e5;stop-opacity:1" - offset="0.2809" - id="stop20062" /> - <stop - style="stop-color:#c2c2c2;stop-opacity:1" - offset="0.5" - id="stop20064" /> - <a:midPointStop - offset="0" - style="stop-color:#B2B2B2" /> - <a:midPointStop - offset="0.5" - style="stop-color:#B2B2B2" /> - <a:midPointStop - offset="0.1685" - style="stop-color:#E5E5E5" /> - <a:midPointStop - offset="0.5" - style="stop-color:#E5E5E5" /> - <a:midPointStop - offset="0.2303" - style="stop-color:#FFFFFF" /> - <a:midPointStop - offset="0.5" - style="stop-color:#FFFFFF" /> - <a:midPointStop - offset="0.2809" - style="stop-color:#E5E5E5" /> - <a:midPointStop - offset="0.5" - style="stop-color:#E5E5E5" /> - <a:midPointStop - offset="0.5" - style="stop-color:#C2C2C2" /> - </linearGradient> - <linearGradient - x1="186.1938" - y1="109.1343" - x2="206.6881" - y2="88.639999" - id="linearGradient36610" - xlink:href="#XMLID_3293_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1.029078,0,0,1,-183.2624,-79.44655)" /> - <linearGradient - x1="184.8569" - y1="112.2676" - x2="211.94099" - y2="89.541397" - id="XMLID_3292_" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:#b2b2b2;stop-opacity:1" - offset="0" - id="stop20043" /> - <stop - style="stop-color:#e5e5e5;stop-opacity:1" - offset="0.16850001" - id="stop20045" /> - <stop - style="stop-color:white;stop-opacity:1" - offset="0.23029999" - id="stop20047" /> - <stop - style="stop-color:#e5e5e5;stop-opacity:1" - offset="0.2809" - id="stop20049" /> - <stop - style="stop-color:#ccc;stop-opacity:1" - offset="1" - id="stop20051" /> - <a:midPointStop - offset="0" - style="stop-color:#B2B2B2" /> - <a:midPointStop - offset="0.5" - style="stop-color:#B2B2B2" /> - <a:midPointStop - offset="0.1685" - style="stop-color:#E5E5E5" /> - <a:midPointStop - offset="0.5" - style="stop-color:#E5E5E5" /> - <a:midPointStop - offset="0.2303" - style="stop-color:#FFFFFF" /> - <a:midPointStop - offset="0.5" - style="stop-color:#FFFFFF" /> - <a:midPointStop - offset="0.2809" - style="stop-color:#E5E5E5" /> - <a:midPointStop - offset="0.5" - style="stop-color:#E5E5E5" /> - <a:midPointStop - offset="1" - style="stop-color:#CCCCCC" /> - </linearGradient> - <linearGradient - x1="184.8569" - y1="112.2676" - x2="211.94099" - y2="89.541397" - id="linearGradient36613" - xlink:href="#XMLID_3292_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1.029078,0,0,1,-183.2624,-79.44655)" /> - <marker - refX="0" - refY="0" - orient="auto" - style="overflow:visible" - id="TriangleOutM"> - <path - d="M 5.77,0 L -2.88,5 L -2.88,-5 L 5.77,0 z " - transform="scale(0.4,0.4)" - style="fill:#5c5c4f;fill-rule:evenodd;stroke-width:1pt;marker-start:none" - id="path3238" /> - </marker> - <linearGradient - x1="165.3" - y1="99.5" - x2="165.3" - y2="115.9" - id="XMLID_3457_" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:#999;stop-opacity:1" - offset="0" - id="stop8309" /> - <stop - style="stop-color:#b2b2b2;stop-opacity:1" - offset="0.30000001" - id="stop8311" /> - <stop - style="stop-color:#b2b2b2;stop-opacity:1" - offset="1" - id="stop8313" /> - <a:midPointstop - offset="0" - style="stop-color:#999999" /> - <a:midPointstop - offset="0.5" - style="stop-color:#999999" /> - <a:midPointstop - offset="0.3" - style="stop-color:#B2B2B2" /> - <a:midPointstop - offset="0.5" - style="stop-color:#B2B2B2" /> - <a:midPointstop - offset="1" - style="stop-color:#B2B2B2" /> - </linearGradient> - <linearGradient - x1="165.3" - y1="99.5" - x2="165.3" - y2="115.9" - id="lg1997" - xlink:href="#XMLID_3457_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1.2,0,0,1.2,-175.9,-114.6)" /> - <linearGradient - x1="175" - y1="99.800003" - x2="175" - y2="112.5" - id="XMLID_3456_" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:#737373;stop-opacity:1" - offset="0" - id="stop8300" /> - <stop - style="stop-color:#191919;stop-opacity:1" - offset="0.60000002" - id="stop8302" /> - <stop - style="stop-color:#191919;stop-opacity:1" - offset="1" - id="stop8304" /> - <a:midPointstop - offset="0" - style="stop-color:#737373" /> - <a:midPointstop - offset="0.5" - style="stop-color:#737373" /> - <a:midPointstop - offset="0.6" - style="stop-color:#191919" /> - <a:midPointstop - offset="0.5" - style="stop-color:#191919" /> - <a:midPointstop - offset="1" - style="stop-color:#191919" /> - </linearGradient> - <linearGradient - x1="175" - y1="99.800003" - x2="175" - y2="112.5" - id="lg2000" - xlink:href="#XMLID_3456_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1.2,0,0,1.2,-175.9,-114.6)" /> - <linearGradient - x1="168.8" - y1="107.1" - x2="164.5" - y2="110" - id="XMLID_3455_" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:#666;stop-opacity:1" - offset="0" - id="stop8291" /> - <stop - style="stop-color:#191919;stop-opacity:1" - offset="0.69999999" - id="stop8293" /> - <stop - style="stop-color:#191919;stop-opacity:1" - offset="1" - id="stop8295" /> - <a:midPointstop - offset="0" - style="stop-color:#666666" /> - <a:midPointstop - offset="0.5" - style="stop-color:#666666" /> - <a:midPointstop - offset="0.7" - style="stop-color:#191919" /> - <a:midPointstop - offset="0.5" - style="stop-color:#191919" /> - <a:midPointstop - offset="1" - style="stop-color:#191919" /> - </linearGradient> - <linearGradient - x1="168.8" - y1="107.1" - x2="164.5" - y2="110" - id="lg2003" - xlink:href="#XMLID_3455_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1.2,0,0,1.2,-175.9,-114.6)" /> - <linearGradient - id="lg63694"> - <stop - style="stop-color:white;stop-opacity:1" - offset="0" - id="stop63696" /> - <stop - style="stop-color:white;stop-opacity:0" - offset="1" - id="stop63698" /> - </linearGradient> - <linearGradient - x1="458" - y1="483" - x2="465.20001" - y2="271.39999" - id="lg2006" - xlink:href="#lg63694" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(6.3e-2,0,0,6.3e-2,-1.3,-9.8)" /> - <linearGradient - x1="176.3" - y1="110.1" - x2="158.7" - y2="105" - id="XMLID_3453_" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:#666;stop-opacity:1" - offset="0" - id="stop8271" /> - <stop - style="stop-color:#737373;stop-opacity:1" - offset="0.2" - id="stop8273" /> - <stop - style="stop-color:white;stop-opacity:1" - offset="1" - id="stop8275" /> - <a:midPointstop - offset="0" - style="stop-color:#666666" /> - <a:midPointstop - offset="0.5" - style="stop-color:#666666" /> - <a:midPointstop - offset="0.2" - style="stop-color:#737373" /> - <a:midPointstop - offset="0.5" - style="stop-color:#737373" /> - <a:midPointstop - offset="1" - style="stop-color:#FFFFFF" /> - </linearGradient> - <linearGradient - x1="176.3" - y1="110.1" - x2="158.7" - y2="105" - id="lg2009" - xlink:href="#XMLID_3453_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1.2,0,0,1.2,-175.9,-114.6)" /> - <linearGradient - x1="173.60001" - y1="118.9" - x2="172.8" - y2="128.2" - id="XMLID_3449_" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:#ecb300;stop-opacity:1" - offset="0" - id="stop8232" /> - <stop - style="stop-color:#fff95e;stop-opacity:1" - offset="0.60000002" - id="stop8234" /> - <stop - style="stop-color:#ecd600;stop-opacity:1" - offset="1" - id="stop8236" /> - <a:midPointstop - offset="0" - style="stop-color:#ECB300" /> - <a:midPointstop - offset="0.5" - style="stop-color:#ECB300" /> - <a:midPointstop - offset="0.6" - style="stop-color:#FFF95E" /> - <a:midPointstop - offset="0.5" - style="stop-color:#FFF95E" /> - <a:midPointstop - offset="1" - style="stop-color:#ECD600" /> - </linearGradient> - <linearGradient - x1="173.60001" - y1="118.9" - x2="172.8" - y2="128.2" - id="lg2016" - xlink:href="#XMLID_3449_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1.2,0,0,1.2,-175.9,-114.6)" /> - <radialGradient - cx="284.60001" - cy="172.60001" - r="6.5" - fx="284.60001" - fy="172.60001" - id="XMLID_3448_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1.4,0,0,1.4,-237.3,-126.8)"> - <stop - style="stop-color:#ecb300;stop-opacity:1" - offset="0" - id="stop8219" /> - <stop - style="stop-color:#ecb300;stop-opacity:1" - offset="0.30000001" - id="stop8221" /> - <stop - style="stop-color:#c96b00;stop-opacity:1" - offset="0.89999998" - id="stop8223" /> - <stop - style="stop-color:#9a5500;stop-opacity:1" - offset="1" - id="stop8225" /> - <a:midPointstop - offset="0" - style="stop-color:#ECB300" /> - <a:midPointstop - offset="0.5" - style="stop-color:#ECB300" /> - <a:midPointstop - offset="0.3" - style="stop-color:#ECB300" /> - <a:midPointstop - offset="0.5" - style="stop-color:#ECB300" /> - <a:midPointstop - offset="0.9" - style="stop-color:#C96B00" /> - <a:midPointstop - offset="0.5" - style="stop-color:#C96B00" /> - <a:midPointstop - offset="1" - style="stop-color:#9A5500" /> - </radialGradient> - <radialGradient - cx="284.60001" - cy="172.60001" - r="6.5" - fx="284.60001" - fy="172.60001" - id="rg2020" - xlink:href="#XMLID_3448_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(2.513992,0,0,2.347576,-689.1621,-378.5717)" /> - <linearGradient - x1="158.10001" - y1="123" - x2="164.2" - y2="126.6" - id="XMLID_3447_" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:#ecd600;stop-opacity:1" - offset="0" - id="stop8204" /> - <stop - style="stop-color:#ffffb3;stop-opacity:1" - offset="0.30000001" - id="stop8206" /> - <stop - style="stop-color:white;stop-opacity:1" - offset="1" - id="stop8208" /> - <a:midPointstop - offset="0" - style="stop-color:#ECD600" /> - <a:midPointstop - offset="0.5" - style="stop-color:#ECD600" /> - <a:midPointstop - offset="0.3" - style="stop-color:#FFFFB3" /> - <a:midPointstop - offset="0.5" - style="stop-color:#FFFFB3" /> - <a:midPointstop - offset="1" - style="stop-color:#FFFFFF" /> - </linearGradient> - <linearGradient - x1="158.10001" - y1="123" - x2="164.2" - y2="126.6" - id="lg2026" - xlink:href="#XMLID_3447_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1.2,0,0,1.2,-175.9,-114.6)" /> - <radialGradient - cx="280.89999" - cy="163.7" - r="10.1" - fx="280.89999" - fy="163.7" - id="XMLID_3446_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1.4,0,0,1.4,-237.3,-126.8)"> - <stop - style="stop-color:white;stop-opacity:1" - offset="0" - id="stop8197" /> - <stop - style="stop-color:#fff95e;stop-opacity:1" - offset="1" - id="stop8199" /> - <a:midPointstop - offset="0" - style="stop-color:#FFFFFF" /> - <a:midPointstop - offset="0.5" - style="stop-color:#FFFFFF" /> - <a:midPointstop - offset="1" - style="stop-color:#FFF95E" /> - </radialGradient> - <radialGradient - cx="280.89999" - cy="163.7" - r="10.1" - fx="280.89999" - fy="163.7" - id="rg2029" - xlink:href="#XMLID_3446_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1.7,0,0,1.7,-457.5,-266.8)" /> - <linearGradient - x1="156.5" - y1="122.7" - x2="180.10001" - y2="122.7" - id="XMLID_3445_" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:#ecb300;stop-opacity:1" - offset="0" - id="stop8184" /> - <stop - style="stop-color:#ffe900;stop-opacity:1" - offset="0.2" - id="stop8186" /> - <stop - style="stop-color:#ffffb3;stop-opacity:1" - offset="0.30000001" - id="stop8188" /> - <stop - style="stop-color:#ffe900;stop-opacity:1" - offset="0.40000001" - id="stop8190" /> - <stop - style="stop-color:#d68100;stop-opacity:1" - offset="1" - id="stop8192" /> - <a:midPointstop - offset="0" - style="stop-color:#ECB300" /> - <a:midPointstop - offset="0.5" - style="stop-color:#ECB300" /> - <a:midPointstop - offset="0.2" - style="stop-color:#FFE900" /> - <a:midPointstop - offset="0.5" - style="stop-color:#FFE900" /> - <a:midPointstop - offset="0.3" - style="stop-color:#FFFFB3" /> - <a:midPointstop - offset="0.5" - style="stop-color:#FFFFB3" /> - <a:midPointstop - offset="0.4" - style="stop-color:#FFE900" /> - <a:midPointstop - offset="0.5" - style="stop-color:#FFE900" /> - <a:midPointstop - offset="1" - style="stop-color:#D68100" /> - </linearGradient> - <linearGradient - x1="156.5" - y1="122.7" - x2="180.10001" - y2="122.7" - id="lg2032" - xlink:href="#XMLID_3445_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1.2,0,0,1.2,-175.9,-114.6)" /> - <linearGradient - x1="156.39999" - y1="115.4" - x2="180.10001" - y2="115.4" - id="XMLID_3444_" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:#ecb300;stop-opacity:1" - offset="0" - id="stop8171" /> - <stop - style="stop-color:#ffe900;stop-opacity:1" - offset="0.2" - id="stop8173" /> - <stop - style="stop-color:#ffffb3;stop-opacity:1" - offset="0.30000001" - id="stop8175" /> - <stop - style="stop-color:#ffe900;stop-opacity:1" - offset="0.40000001" - id="stop8177" /> - <stop - style="stop-color:#d68100;stop-opacity:1" - offset="1" - id="stop8179" /> - <a:midPointstop - offset="0" - style="stop-color:#ECB300" /> - <a:midPointstop - offset="0.5" - style="stop-color:#ECB300" /> - <a:midPointstop - offset="0.2" - style="stop-color:#FFE900" /> - <a:midPointstop - offset="0.5" - style="stop-color:#FFE900" /> - <a:midPointstop - offset="0.3" - style="stop-color:#FFFFB3" /> - <a:midPointstop - offset="0.5" - style="stop-color:#FFFFB3" /> - <a:midPointstop - offset="0.4" - style="stop-color:#FFE900" /> - <a:midPointstop - offset="0.5" - style="stop-color:#FFE900" /> - <a:midPointstop - offset="1" - style="stop-color:#D68100" /> - </linearGradient> - <linearGradient - x1="156.39999" - y1="115.4" - x2="180.10001" - y2="115.4" - id="lg2035" - xlink:href="#XMLID_3444_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1.2,0,0,1.2,-175.9,-114.6)" /> - <linearGradient - x1="379.70001" - y1="167.89999" - x2="383.89999" - y2="172.89999" - id="lg4286_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.8,0.2,-0.2,0.8,78.8,38.1)"> - <stop - style="stop-color:white;stop-opacity:1" - offset="0" - id="s16159" /> - <stop - style="stop-color:white;stop-opacity:1" - offset="0.1" - id="s16161" /> - <stop - style="stop-color:#737373;stop-opacity:1" - offset="1" - id="s16163" /> - <ns:midPointStop - style="stop-color:#FFFFFF" - offset="0" /> - <ns:midPointStop - style="stop-color:#FFFFFF" - offset="0.5" /> - <ns:midPointStop - style="stop-color:#FFFFFF" - offset="0.1" /> - <ns:midPointStop - style="stop-color:#FFFFFF" - offset="0.5" /> - <ns:midPointStop - style="stop-color:#737373" - offset="1" /> - </linearGradient> - <linearGradient - x1="379.60001" - y1="167.8" - x2="383.79999" - y2="172" - id="lg6416" - xlink:href="#lg4286_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(2.622156,0.623859,-0.623859,2.62182,-882.9706,-673.7921)" /> - <linearGradient - x1="384.20001" - y1="169.8" - x2="384.79999" - y2="170.39999" - id="lg4285_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.8,0.2,-0.2,0.8,78.8,38.1)"> - <stop - style="stop-color:#737373;stop-opacity:1" - offset="0" - id="s16152" /> - <stop - style="stop-color:#d9d9d9;stop-opacity:1" - offset="1" - id="s16154" /> - <ns:midPointStop - style="stop-color:#737373" - offset="0" /> - <ns:midPointStop - style="stop-color:#737373" - offset="0.5" /> - <ns:midPointStop - style="stop-color:#D9D9D9" - offset="1" /> - </linearGradient> - <linearGradient - x1="384.20001" - y1="169.8" - x2="384.79999" - y2="170.39999" - id="lg6453" - xlink:href="#lg4285_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(2.6,0.6,-0.6,2.6,-883,-673.8)" /> - <linearGradient - x1="380.5" - y1="172.60001" - x2="382.79999" - y2="173.7" - id="lg4284_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.8,0.2,-0.2,0.8,78.8,38.1)"> - <stop - style="stop-color:gray;stop-opacity:1" - offset="0" - id="s16145" /> - <stop - style="stop-color:#e5e5e5;stop-opacity:1" - offset="1" - id="s16147" /> - <ns:midPointStop - style="stop-color:#808080" - offset="0" /> - <ns:midPointStop - style="stop-color:#808080" - offset="0.5" /> - <ns:midPointStop - style="stop-color:#E5E5E5" - offset="1" /> - </linearGradient> - <linearGradient - x1="380.5" - y1="172.60001" - x2="382.79999" - y2="173.7" - id="lg6456" - xlink:href="#lg4284_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(2.6,0.6,-0.6,2.6,-883,-673.8)" /> - <radialGradient - cx="347.29999" - cy="244.5" - r="5.1999998" - fx="347.29999" - fy="244.5" - id="lg4282_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(3.4,0,0,3.4,-1148,-802)"> - <stop - style="stop-color:#333;stop-opacity:1" - offset="0" - id="s16135" /> - <stop - style="stop-color:#999;stop-opacity:1" - offset="1" - id="s16137" /> - <ns:midPointStop - style="stop-color:#333333" - offset="0" /> - <ns:midPointStop - style="stop-color:#333333" - offset="0.5" /> - <ns:midPointStop - style="stop-color:#999999" - offset="1" /> - </radialGradient> - <linearGradient - x1="310.39999" - y1="397.70001" - x2="310.89999" - y2="399.5" - id="lg4280_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.7,-0.7,0.7,0.7,-153.4,180.6)"> - <stop - style="stop-color:#ffcd00;stop-opacity:1" - offset="0" - id="s16111" /> - <stop - style="stop-color:#ffffb3;stop-opacity:1" - offset="0.60000002" - id="s16113" /> - <stop - style="stop-color:#ffffb3;stop-opacity:1" - offset="1" - id="s16115" /> - <ns:midPointStop - style="stop-color:#FFCD00" - offset="0" /> - <ns:midPointStop - style="stop-color:#FFCD00" - offset="0.5" /> - <ns:midPointStop - style="stop-color:#FFFFB3" - offset="0.6" /> - <ns:midPointStop - style="stop-color:#FFFFB3" - offset="0.5" /> - <ns:midPointStop - style="stop-color:#FFFFB3" - offset="1" /> - </linearGradient> - <linearGradient - x1="310.39999" - y1="397.70001" - x2="310.89999" - y2="399.5" - id="lg6467" - xlink:href="#lg4280_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(2.4,-2.4,2.4,2.4,-1663.6,-195)" /> - <linearGradient - x1="310.89999" - y1="395.79999" - x2="313.29999" - y2="403.10001" - id="lg4279_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.7,-0.7,0.7,0.7,-153.4,180.6)"> - <stop - style="stop-color:#ffffb3;stop-opacity:1" - offset="0" - id="s16100" /> - <stop - style="stop-color:#ffffb3;stop-opacity:1" - offset="0.40000001" - id="s16102" /> - <stop - style="stop-color:#ffcd00;stop-opacity:1" - offset="0.89999998" - id="s16104" /> - <stop - style="stop-color:#ffcd00;stop-opacity:1" - offset="1" - id="s16106" /> - <ns:midPointStop - style="stop-color:#FFFFB3" - offset="0" /> - <ns:midPointStop - style="stop-color:#FFFFB3" - offset="0.5" /> - <ns:midPointStop - style="stop-color:#FFFFB3" - offset="0.4" /> - <ns:midPointStop - style="stop-color:#FFFFB3" - offset="0.5" /> - <ns:midPointStop - style="stop-color:#FFCD00" - offset="0.9" /> - <ns:midPointStop - style="stop-color:#FFCD00" - offset="0.5" /> - <ns:midPointStop - style="stop-color:#FFCD00" - offset="1" /> - </linearGradient> - <linearGradient - x1="310.89999" - y1="395.79999" - x2="313.29999" - y2="403.10001" - id="lg6465" - xlink:href="#lg4279_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(2.4,-2.4,2.4,2.4,-1663.6,-195)" /> - <linearGradient - x1="307.79999" - y1="395.20001" - x2="313.79999" - y2="413.60001" - id="lg4278_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.7,-0.7,0.7,0.7,-153.4,180.6)"> - <stop - style="stop-color:#ffffb3;stop-opacity:1" - offset="0" - id="s16091" /> - <stop - style="stop-color:#fcd72f;stop-opacity:1" - offset="0.40000001" - id="s16093" /> - <stop - style="stop-color:#ffcd00;stop-opacity:1" - offset="1" - id="s16095" /> - <ns:midPointStop - style="stop-color:#FFFFB3" - offset="0" /> - <ns:midPointStop - style="stop-color:#FFFFB3" - offset="0.5" /> - <ns:midPointStop - style="stop-color:#FCD72F" - offset="0.4" /> - <ns:midPointStop - style="stop-color:#FCD72F" - offset="0.5" /> - <ns:midPointStop - style="stop-color:#FFCD00" - offset="1" /> - </linearGradient> - <linearGradient - x1="306.5" - y1="393" - x2="309" - y2="404" - id="lg6400" - xlink:href="#lg4278_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(2.4,-2.4,2.4,2.4,-1663.6,-195)" /> - <linearGradient - x1="352.10001" - y1="253.60001" - x2="348.5" - y2="237.8" - id="lg4276_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(3.4,0,0,3.4,-1148,-802)"> - <stop - style="stop-color:#ffff87;stop-opacity:1" - offset="0" - id="s16077" /> - <stop - style="stop-color:#ffad00;stop-opacity:1" - offset="1" - id="s16079" /> - <ns:midPointStop - style="stop-color:#FFFF87" - offset="0" /> - <ns:midPointStop - style="stop-color:#FFFF87" - offset="0.5" /> - <ns:midPointStop - style="stop-color:#FFAD00" - offset="1" /> - </linearGradient> - <linearGradient - x1="335.60001" - y1="354.79999" - x2="337.89999" - y2="354.79999" - id="lg4275_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.9,-0.5,0.5,0.9,-121.7,105.1)"> - <stop - style="stop-color:#d9d9d9;stop-opacity:1" - offset="0" - id="s16057" /> - <stop - style="stop-color:white;stop-opacity:1" - offset="0.80000001" - id="s16059" /> - <stop - style="stop-color:white;stop-opacity:1" - offset="1" - id="s16061" /> - <ns:midPointStop - style="stop-color:#D9D9D9" - offset="0" /> - <ns:midPointStop - style="stop-color:#D9D9D9" - offset="0.5" /> - <ns:midPointStop - style="stop-color:#FFFFFF" - offset="0.8" /> - <ns:midPointStop - style="stop-color:#FFFFFF" - offset="0.5" /> - <ns:midPointStop - style="stop-color:#FFFFFF" - offset="1" /> - </linearGradient> - <linearGradient - x1="335.60001" - y1="354.79999" - x2="337.89999" - y2="354.79999" - id="lg6463" - xlink:href="#lg4275_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(2.9,-1.7,1.7,2.9,-1557,-448.7)" /> - <linearGradient - x1="337.39999" - y1="353.10001" - x2="339.39999" - y2="357.10001" - id="lg4274_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.9,-0.5,0.5,0.9,-121.7,105.1)"> - <stop - style="stop-color:white;stop-opacity:1" - offset="0" - id="s16048" /> - <stop - style="stop-color:white;stop-opacity:1" - offset="0.1" - id="s16050" /> - <stop - style="stop-color:#ccc;stop-opacity:1" - offset="1" - id="s16052" /> - <ns:midPointStop - style="stop-color:#FFFFFF" - offset="0" /> - <ns:midPointStop - style="stop-color:#FFFFFF" - offset="0.5" /> - <ns:midPointStop - style="stop-color:#FFFFFF" - offset="0.1" /> - <ns:midPointStop - style="stop-color:#FFFFFF" - offset="0.5" /> - <ns:midPointStop - style="stop-color:#CCCCCC" - offset="1" /> - </linearGradient> - <linearGradient - x1="337.39999" - y1="353.10001" - x2="339.39999" - y2="357.10001" - id="lg6461" - xlink:href="#lg4274_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(2.9,-1.7,1.7,2.9,-1557,-448.7)" /> - <linearGradient - x1="334.39999" - y1="355.5" - x2="335.5" - y2="356.79999" - id="lg4273_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.9,-0.5,0.5,0.9,-121.7,105.1)"> - <stop - style="stop-color:white;stop-opacity:1" - offset="0" - id="s16041" /> - <stop - style="stop-color:#ccc;stop-opacity:1" - offset="1" - id="s16043" /> - <ns:midPointStop - style="stop-color:#FFFFFF" - offset="5.6e-003" /> - <ns:midPointStop - style="stop-color:#FFFFFF" - offset="0.5" /> - <ns:midPointStop - style="stop-color:#CCCCCC" - offset="1" /> - </linearGradient> - <linearGradient - x1="334.39999" - y1="355.5" - x2="335.5" - y2="356.79999" - id="lg6381" - xlink:href="#lg4273_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(2.9,-1.7,1.7,2.9,-1557,-448.7)" /> - <linearGradient - x1="348.39999" - y1="247.39999" - x2="354.10001" - y2="242" - id="lg4271_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(3.4,0,0,3.4,-1148,-802)"> - <stop - style="stop-color:#f2f2f2;stop-opacity:1" - offset="0" - id="s16025" /> - <stop - style="stop-color:#9e9e9e;stop-opacity:1" - offset="0.40000001" - id="s16027" /> - <stop - style="stop-color:black;stop-opacity:1" - offset="1" - id="s16029" /> - <ns:midPointStop - style="stop-color:#F2F2F2" - offset="0" /> - <ns:midPointStop - style="stop-color:#F2F2F2" - offset="0.5" /> - <ns:midPointStop - style="stop-color:#000000" - offset="1" /> - </linearGradient> - <linearGradient - x1="351.29999" - y1="257.29999" - x2="346.29999" - y2="235.5" - id="lg4270_" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:#ffff87;stop-opacity:1" - offset="0" - id="s16007" /> - <stop - style="stop-color:#ffad00;stop-opacity:1" - offset="1" - id="s16009" /> - <ns:midPointStop - style="stop-color:#FFFF87" - offset="0" /> - <ns:midPointStop - style="stop-color:#FFFF87" - offset="0.5" /> - <ns:midPointStop - style="stop-color:#FFAD00" - offset="1" /> - </linearGradient> - <linearGradient - x1="351.29999" - y1="257.29999" - x2="346.29999" - y2="235.5" - id="lg6459" - xlink:href="#lg4270_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(3.4,0,0,3.4,-1148,-802)" /> - <linearGradient - x1="43.799999" - y1="32.5" - x2="63.299999" - y2="66.400002" - id="XMLID_2708_" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:white;stop-opacity:1" - offset="0" - id="stop75318" /> - <stop - style="stop-color:#fffcea;stop-opacity:1" - offset="1" - id="stop75320" /> - <a:midPointStop - style="stop-color:#FFFFFF" - offset="0" /> - <a:midPointStop - style="stop-color:#FFFFFF" - offset="0.5" /> - <a:midPointStop - style="stop-color:#FFFCEA" - offset="1" /> - </linearGradient> - <linearGradient - x1="43.799999" - y1="32.5" - x2="63.299999" - y2="66.400002" - id="lg1907" - xlink:href="#XMLID_2708_" - gradientUnits="userSpaceOnUse" - gradientTransform="translate(-29,-22.6)" /> - <linearGradient - x1="52.5" - y1="40.400002" - x2="58.200001" - y2="64" - id="XMLID_2707_" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:#ffdea0;stop-opacity:1" - offset="0" - id="stop75305" /> - <stop - style="stop-color:#ffd89e;stop-opacity:1" - offset="0.30000001" - id="stop75307" /> - <stop - style="stop-color:#ffd79e;stop-opacity:1" - offset="0.30000001" - id="stop75309" /> - <stop - style="stop-color:#dbaf6d;stop-opacity:1" - offset="0.69999999" - id="stop75311" /> - <stop - style="stop-color:#6f4c24;stop-opacity:1" - offset="1" - id="stop75313" /> - <a:midPointStop - style="stop-color:#FFDEA0" - offset="0" /> - <a:midPointStop - style="stop-color:#FFDEA0" - offset="0.6" /> - <a:midPointStop - style="stop-color:#FFD79E" - offset="0.3" /> - <a:midPointStop - style="stop-color:#FFD79E" - offset="0.5" /> - <a:midPointStop - style="stop-color:#DBAF6D" - offset="0.7" /> - <a:midPointStop - style="stop-color:#DBAF6D" - offset="0.5" /> - <a:midPointStop - style="stop-color:#6F4C24" - offset="1" /> - </linearGradient> - <linearGradient - x1="52.5" - y1="40.400002" - x2="58.200001" - y2="64" - id="lg1910" - xlink:href="#XMLID_2707_" - gradientUnits="userSpaceOnUse" - gradientTransform="translate(-29,-22.6)" /> - <linearGradient - x1="58" - y1="73.199997" - x2="44.5" - y2="19" - id="XMLID_2704_" - gradientUnits="userSpaceOnUse" - gradientTransform="translate(-29,-22.6)"> - <stop - style="stop-color:#d4a96c;stop-opacity:1" - offset="0.5" - id="stop75284" /> - <stop - style="stop-color:#dcb273;stop-opacity:1" - offset="0.60000002" - id="stop75286" /> - <stop - style="stop-color:#f0ca87;stop-opacity:1" - offset="0.80000001" - id="stop75288" /> - <stop - style="stop-color:#ffdc96;stop-opacity:1" - offset="0.69999999" - id="stop75290" /> - <stop - style="stop-color:#c18a42;stop-opacity:1" - offset="1" - id="stop75292" /> - <a:midPointStop - style="stop-color:#D4A96C" - offset="0.5" /> - <a:midPointStop - style="stop-color:#D4A96C" - offset="0.6" /> - <a:midPointStop - style="stop-color:#FFDC96" - offset="0.7" /> - <a:midPointStop - style="stop-color:#FFDC96" - offset="0.5" /> - <a:midPointStop - style="stop-color:#C18A42" - offset="1" /> - </linearGradient> - <linearGradient - x1="53.700001" - y1="32" - x2="53.700001" - y2="64.599998" - id="XMLID_2703_" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:#e5c9b0;stop-opacity:1" - offset="0" - id="stop75268" /> - <stop - style="stop-color:#e5c9b0;stop-opacity:1" - offset="0.40000001" - id="stop75270" /> - <stop - style="stop-color:#c0aa94;stop-opacity:1" - offset="1" - id="stop75272" /> - <a:midPointStop - style="stop-color:#E5C9B0" - offset="0" /> - <a:midPointStop - style="stop-color:#E5C9B0" - offset="0.5" /> - <a:midPointStop - style="stop-color:#E5C9B0" - offset="0.4" /> - <a:midPointStop - style="stop-color:#E5C9B0" - offset="0.5" /> - <a:midPointStop - style="stop-color:#C0AA94" - offset="1" /> - </linearGradient> - <linearGradient - x1="53.700001" - y1="32" - x2="53.700001" - y2="64.599998" - id="lg1916" - xlink:href="#XMLID_2703_" - gradientUnits="userSpaceOnUse" - gradientTransform="translate(-29,-22.6)" /> - <linearGradient - x1="224.31" - y1="19.450001" - x2="214.33" - y2="11.46" - id="XMLID_419_" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:#404040;stop-opacity:1" - offset="0" - id="s1903" /> - <stop - style="stop-color:#6d6d6d;stop-opacity:1" - offset="0.33000001" - id="s1905" /> - <stop - style="stop-color:#e9e9e9;stop-opacity:1" - offset="1" - id="s1907" /> - <a:midPointStop - offset="0" - style="stop-color:#404040" /> - <a:midPointStop - offset="0.5" - style="stop-color:#404040" /> - <a:midPointStop - offset="0.33" - style="stop-color:#6D6D6D" /> - <a:midPointStop - offset="0.5" - style="stop-color:#6D6D6D" /> - <a:midPointStop - offset="1" - style="stop-color:#E9E9E9" /> - </linearGradient> - <linearGradient - x1="221.84" - y1="32.779999" - x2="212.2" - y2="20.27" - id="lg1988" - xlink:href="#XMLID_419_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1.33,0,0,1.31,-274.2,-5.2)" /> - <linearGradient - x1="228.35001" - y1="33.279999" - x2="215.42999" - y2="33.279999" - id="lg1900" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:white;stop-opacity:1" - offset="0" - id="s1902" /> - <stop - style="stop-color:white;stop-opacity:0" - offset="1" - id="s1906" /> - <a:midPointStop - style="stop-color:#575757" - offset="0" /> - <a:midPointStop - style="stop-color:#575757" - offset="0.5" /> - <a:midPointStop - style="stop-color:#6D6D6D" - offset="0.33" /> - <a:midPointStop - style="stop-color:#6D6D6D" - offset="0.5" /> - <a:midPointStop - style="stop-color:#D3D3D3" - offset="1" /> - </linearGradient> - <linearGradient - x1="234.81" - y1="33.279999" - x2="228.27" - y2="33.279999" - id="lg1908" - xlink:href="#lg1900" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1.33,0,0,1.31,-274.2,-5.2)" /> - <linearGradient - x1="228.35001" - y1="33.279999" - x2="215.42999" - y2="33.279999" - id="XMLID_416_" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:#575757;stop-opacity:1" - offset="0" - id="s1874" /> - <stop - style="stop-color:#6d6d6d;stop-opacity:1" - offset="0.33000001" - id="s1876" /> - <stop - style="stop-color:#d3d3d3;stop-opacity:1" - offset="1" - id="s1878" /> - <a:midPointStop - offset="0" - style="stop-color:#575757" /> - <a:midPointStop - offset="0.5" - style="stop-color:#575757" /> - <a:midPointStop - offset="0.33" - style="stop-color:#6D6D6D" /> - <a:midPointStop - offset="0.5" - style="stop-color:#6D6D6D" /> - <a:midPointStop - offset="1" - style="stop-color:#D3D3D3" /> - </linearGradient> - <linearGradient - x1="228.35001" - y1="33.279999" - x2="215.42999" - y2="33.279999" - id="lg1991" - xlink:href="#XMLID_416_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1.33,0,0,1.31,-274.2,-5.2)" /> - <radialGradient - cx="603.19" - cy="230.77" - r="1.67" - fx="603.19" - fy="230.77" - id="x5010_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1.1,0,0,1.1,-54.33,-75.4)"> - <stop - style="stop-color:#c9ffc9;stop-opacity:1" - offset="0" - id="stop29201" /> - <stop - style="stop-color:#23a11f;stop-opacity:1" - offset="1" - id="stop29203" /> - <a:midPointStop - offset="0" - style="stop-color:#C9FFC9" /> - <a:midPointStop - offset="0.5" - style="stop-color:#C9FFC9" /> - <a:midPointStop - offset="1" - style="stop-color:#23A11F" /> - </radialGradient> - <radialGradient - cx="603.19" - cy="230.77" - r="1.67" - fx="603.19" - fy="230.77" - id="radialGradient5711" - xlink:href="#x5010_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1.23,0,0,1.23,-709.93,-245.02)" /> - <linearGradient - x1="592.31" - y1="162.60001" - x2="609.32001" - y2="145.59" - id="lg5722" - xlink:href="#x5003_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)" /> - <linearGradient - x1="601.48999" - y1="170.16" - x2="613.84003" - y2="170.16" - id="x5002_" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:#d9d9d9;stop-opacity:1" - offset="0" - id="stop29134" /> - <stop - style="stop-color:white;stop-opacity:1" - offset="0.2" - id="stop29136" /> - <stop - style="stop-color:#999;stop-opacity:1" - offset="1" - id="stop29138" /> - <a:midPointStop - offset="0" - style="stop-color:#D9D9D9" /> - <a:midPointStop - offset="0.5" - style="stop-color:#D9D9D9" /> - <a:midPointStop - offset="0.20" - style="stop-color:#FFFFFF" /> - <a:midPointStop - offset="0.5" - style="stop-color:#FFFFFF" /> - <a:midPointStop - offset="1" - style="stop-color:#999999" /> - </linearGradient> - <linearGradient - x1="601.48999" - y1="170.16" - x2="613.84003" - y2="170.16" - id="lg5725" - xlink:href="#x5002_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)" /> - <linearGradient - x1="592.20001" - y1="156.45" - x2="609.98999" - y2="174.23" - id="x5004_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)"> - <stop - style="stop-color:#d9d9d9;stop-opacity:1" - offset="0" - id="stop29157" /> - <stop - style="stop-color:white;stop-opacity:1" - offset="1" - id="stop29159" /> - <a:midPointStop - offset="0" - style="stop-color:#D9D9D9" /> - <a:midPointStop - offset="0.5" - style="stop-color:#D9D9D9" /> - <a:midPointStop - offset="1" - style="stop-color:#FFFFFF" /> - </linearGradient> - <linearGradient - x1="592.20001" - y1="156.45" - x2="609.98999" - y2="174.23" - id="lg5728" - xlink:href="#x5004_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)" /> - <linearGradient - x1="592.31" - y1="162.60001" - x2="609.32001" - y2="145.59" - id="x5003_" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:#f2f2f2;stop-opacity:1" - offset="0" - id="stop29143" /> - <stop - style="stop-color:#e5e5e5;stop-opacity:1" - offset="1" - id="stop29145" /> - <a:midPointStop - offset="0" - style="stop-color:#F2F2F2" /> - <a:midPointStop - offset="0.5" - style="stop-color:#F2F2F2" /> - <a:midPointStop - offset="1" - style="stop-color:#E5E5E5" /> - </linearGradient> - <linearGradient - x1="592.31" - y1="162.60001" - x2="609.32001" - y2="145.59" - id="lg5732" - xlink:href="#x5003_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)" /> - <linearGradient - x1="592.20001" - y1="156.45" - x2="609.98999" - y2="174.24001" - id="x5000_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)"> - <stop - style="stop-color:#d9d9d9;stop-opacity:1" - offset="0" - id="stop29124" /> - <stop - style="stop-color:white;stop-opacity:1" - offset="1" - id="stop29126" /> - <a:midPointStop - offset="0" - style="stop-color:#D9D9D9" /> - <a:midPointStop - offset="0.5" - style="stop-color:#D9D9D9" /> - <a:midPointStop - offset="1" - style="stop-color:#FFFFFF" /> - </linearGradient> - <linearGradient - x1="592.20001" - y1="156.45" - x2="609.98999" - y2="174.24001" - id="lg5735" - xlink:href="#x5000_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)" /> - <linearGradient - x1="308.54999" - y1="149.89999" - x2="299.72" - y2="148.83" - id="XMLID_2433_" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:#d6d6d6;stop-opacity:1" - offset="0" - id="71615" /> - <stop - style="stop-color:#a5a5a5;stop-opacity:1" - offset="1" - id="71617" /> - <a:midPointStop - offset="0" - style="stop-color:#D6D6D6" /> - <a:midPointStop - offset="0.5" - style="stop-color:#D6D6D6" /> - <a:midPointStop - offset="1" - style="stop-color:#A5A5A5" /> - </linearGradient> - <linearGradient - x1="308.54999" - y1="149.89999" - x2="299.72" - y2="148.83" - id="lg1952" - xlink:href="#XMLID_2433_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1.03,0,0,1.03,-279.57,-124.36)" /> - <radialGradient - cx="307.39999" - cy="121" - r="23.35" - fx="307.39999" - fy="121" - id="XMLID_2432_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.98,0,0,0.98,2.88,2.75)"> - <stop - style="stop-color:#d2d2d2;stop-opacity:1" - offset="0.19" - id="71592" /> - <stop - style="stop-color:#cfcfcf;stop-opacity:1" - offset="0.44999999" - id="71594" /> - <stop - style="stop-color:#c7c7c7;stop-opacity:1" - offset="0.60000002" - id="71596" /> - <stop - style="stop-color:#b9b9b9;stop-opacity:1" - offset="0.74000001" - id="71598" /> - <stop - style="stop-color:#a4a4a4;stop-opacity:1" - offset="0.86000001" - id="71600" /> - <stop - style="stop-color:#8a8a8a;stop-opacity:1" - offset="0.95999998" - id="71602" /> - <stop - style="stop-color:gray;stop-opacity:1" - offset="1" - id="71604" /> - <a:midPointStop - offset="0.19" - style="stop-color:#D2D2D2" /> - <a:midPointStop - offset="0.8" - style="stop-color:#D2D2D2" /> - <a:midPointStop - offset="1" - style="stop-color:#808080" /> - </radialGradient> - <radialGradient - cx="307.39999" - cy="121" - r="23.35" - fx="307.39999" - fy="121" - id="radialGradient2331" - xlink:href="#XMLID_2432_" - gradientUnits="userSpaceOnUse" - gradientTransform="translate(-276.62,-121.54)" /> - <linearGradient - x1="294.13" - y1="127.07" - x2="294.13" - y2="142.2" - id="XMLID_2430_" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:#b5d8ff;stop-opacity:1" - offset="0" - id="71582" /> - <stop - style="stop-color:black;stop-opacity:1" - offset="1" - id="71584" /> - <a:midPointStop - offset="0" - style="stop-color:#B5D8FF" /> - <a:midPointStop - offset="0.5" - style="stop-color:#B5D8FF" /> - <a:midPointStop - offset="1" - style="stop-color:#000000" /> - </linearGradient> - <linearGradient - x1="294.13" - y1="127.07" - x2="294.13" - y2="142.2" - id="lg2820" - xlink:href="#XMLID_2430_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1.03,0,0,1.03,-279.57,-124.36)" /> - <linearGradient - x1="279.10999" - y1="148.03" - x2="309.16" - y2="148.03" - id="XMLID_2429_" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:#e1e1e1;stop-opacity:1" - offset="0" - id="71564" /> - <stop - style="stop-color:#e1e1e1;stop-opacity:1" - offset="0.25" - id="71566" /> - <stop - style="stop-color:#a5a5a5;stop-opacity:1" - offset="0.44" - id="71568" /> - <stop - style="stop-color:#a5a5a5;stop-opacity:1" - offset="1" - id="71570" /> - <a:midPointStop - offset="0" - style="stop-color:#E1E1E1" /> - <a:midPointStop - offset="0.5" - style="stop-color:#E1E1E1" /> - <a:midPointStop - offset="0.25" - style="stop-color:#E1E1E1" /> - <a:midPointStop - offset="0.5" - style="stop-color:#E1E1E1" /> - <a:midPointStop - offset="0.44" - style="stop-color:#A5A5A5" /> - <a:midPointStop - offset="0.5" - style="stop-color:#A5A5A5" /> - <a:midPointStop - offset="1" - style="stop-color:#A5A5A5" /> - </linearGradient> - <linearGradient - x1="279.10999" - y1="148.03" - x2="309.16" - y2="148.03" - id="lg2818" - xlink:href="#XMLID_2429_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1.03,0,0,1.03,-279.57,-124.36)" /> - <radialGradient - cx="622.34302" - cy="14.449" - r="26.496" - fx="622.34302" - fy="14.449" - id="lg3499_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.851,0,0,0.849,69.297,51.658)"> - <stop - style="stop-color:#23468e;stop-opacity:1" - offset="0" - id="stop10972" /> - <stop - style="stop-color:#012859;stop-opacity:1" - offset="1" - id="stop10974" /> - <a:midPointStop - offset="0" - style="stop-color:#23468E" /> - <a:midPointStop - offset="0.5" - style="stop-color:#23468E" /> - <a:midPointStop - offset="1" - style="stop-color:#012859" /> - </radialGradient> - <radialGradient - cx="622.34302" - cy="14.449" - r="26.496" - fx="622.34302" - fy="14.449" - id="rg5791" - xlink:href="#lg3499_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.858,0,0,0.857,-511.7,9.02)" /> - <linearGradient - x1="616.112" - y1="76.247002" - x2="588.14099" - y2="60.742001" - id="lg3497_" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:#01326e;stop-opacity:1" - offset="0" - id="stop10962" /> - <stop - style="stop-color:#012859;stop-opacity:1" - offset="1" - id="stop10964" /> - <a:midPointStop - offset="0" - style="stop-color:#01326E" /> - <a:midPointStop - offset="0.5" - style="stop-color:#01326E" /> - <a:midPointStop - offset="1" - style="stop-color:#012859" /> - </linearGradient> - <linearGradient - x1="617.698" - y1="82.445999" - x2="585.95203" - y2="54.848999" - id="lg3496_" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:#e5e5e5;stop-opacity:1" - offset="0" - id="stop10950" /> - <stop - style="stop-color:#ccc;stop-opacity:1" - offset="1" - id="stop10952" /> - <a:midPointStop - offset="0" - style="stop-color:#E5E5E5" /> - <a:midPointStop - offset="0.5" - style="stop-color:#E5E5E5" /> - <a:midPointStop - offset="1" - style="stop-color:#CCCCCC" /> - </linearGradient> - <linearGradient - x1="617.698" - y1="82.445999" - x2="585.95203" - y2="54.848999" - id="lg5794" - xlink:href="#lg3496_" - gradientUnits="userSpaceOnUse" /> - <linearGradient - x1="601.39001" - y1="55.341" - x2="588.29199" - y2="71.515999" - id="lg3495_" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:#d9d9d9;stop-opacity:1" - offset="0" - id="stop10941" /> - <stop - style="stop-color:#f2f2f2;stop-opacity:1" - offset="0.52200001" - id="stop10943" /> - <stop - style="stop-color:#ccc;stop-opacity:1" - offset="1" - id="stop10945" /> - <a:midPointStop - offset="0" - style="stop-color:#D9D9D9" /> - <a:midPointStop - offset="0.5" - style="stop-color:#D9D9D9" /> - <a:midPointStop - offset="0.522" - style="stop-color:#F2F2F2" /> - <a:midPointStop - offset="0.5" - style="stop-color:#F2F2F2" /> - <a:midPointStop - offset="1" - style="stop-color:#CCCCCC" /> - </linearGradient> - <linearGradient - x1="601.39001" - y1="55.341" - x2="588.29199" - y2="71.515999" - id="lg5771" - xlink:href="#lg3495_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1.009,0,0,1.009,-581.615,-43.098)" /> - <linearGradient - x1="611.34601" - y1="55.279999" - x2="590.39001" - y2="81.157997" - id="lg3494_" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:#d9d9d9;stop-opacity:1" - offset="0" - id="stop10932" /> - <stop - style="stop-color:#f2f2f2;stop-opacity:1" - offset="0.52200001" - id="stop10934" /> - <stop - style="stop-color:#ccc;stop-opacity:1" - offset="1" - id="stop10936" /> - <a:midPointStop - offset="0" - style="stop-color:#D9D9D9" /> - <a:midPointStop - offset="0.5" - style="stop-color:#D9D9D9" /> - <a:midPointStop - offset="0.522" - style="stop-color:#F2F2F2" /> - <a:midPointStop - offset="0.5" - style="stop-color:#F2F2F2" /> - <a:midPointStop - offset="1" - style="stop-color:#CCCCCC" /> - </linearGradient> - <linearGradient - x1="611.34601" - y1="55.279999" - x2="590.39001" - y2="81.157997" - id="lg5774" - xlink:href="#lg3494_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1.009,0,0,1.009,-581.616,-43.098)" /> - <linearGradient - x1="798.72998" - y1="69.839996" - x2="799.04999" - y2="70.709999" - id="g3302_" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:#005e00;stop-opacity:1" - offset="0" - id="s6504" /> - <stop - style="stop-color:#23a11f;stop-opacity:1" - offset="1" - id="s6506" /> - <a:midPointstop - style="stop-color:#005E00" - offset="0" /> - <a:midPointstop - style="stop-color:#005E00" - offset="0.5" /> - <a:midPointstop - style="stop-color:#23A11F" - offset="1" /> - </linearGradient> - <linearGradient - x1="798.72998" - y1="69.839996" - x2="799.04999" - y2="70.709999" - id="lg5851" - xlink:href="#g3302_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1.204,0,0,1.263,-926.036,-60.001)" /> - <linearGradient - x1="779.19" - y1="122.73" - x2="811.69" - y2="149.74001" - id="g3301_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1,-0.25,0,1,0,129.19)"> - <stop - style="stop-color:#f2f2f2;stop-opacity:1" - offset="0" - id="s6483" /> - <stop - style="stop-color:#eee;stop-opacity:1" - offset="0.17" - id="s6485" /> - <stop - style="stop-color:#e3e3e3;stop-opacity:1" - offset="0.34" - id="s6487" /> - <stop - style="stop-color:#cfcfcf;stop-opacity:1" - offset="0.50999999" - id="s6489" /> - <stop - style="stop-color:#b4b4b4;stop-opacity:1" - offset="0.67000002" - id="s6491" /> - <stop - style="stop-color:#919191;stop-opacity:1" - offset="0.83999997" - id="s6493" /> - <stop - style="stop-color:#666;stop-opacity:1" - offset="1" - id="s6495" /> - <a:midPointstop - style="stop-color:#F2F2F2" - offset="0" /> - <a:midPointstop - style="stop-color:#F2F2F2" - offset="0.71" /> - <a:midPointstop - style="stop-color:#666666" - offset="1" /> - </linearGradient> - <linearGradient - x1="779.19" - y1="122.73" - x2="811.69" - y2="149.74001" - id="lg5855" - xlink:href="#g3301_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1.204,-0.316,0,1.263,-926.036,103.123)" /> - <clipPath - id="g3299_"> - <use - id="use6469" - x="0" - y="0" - width="1005.92" - height="376.97" - xlink:href="#g101_" /> - </clipPath> - <radialGradient - cx="1189.9301" - cy="100.05" - r="40.400002" - fx="1189.9301" - fy="100.05" - id="g3300_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.34,-8.46e-2,0,0.34,394.16,137.13)"> - <stop - style="stop-color:white;stop-opacity:1" - offset="0" - id="s6472" /> - <stop - style="stop-color:white;stop-opacity:0" - offset="1" - id="s6474" /> - <a:midPointstop - style="stop-color:#FFFFFF" - offset="0" /> - <a:midPointstop - style="stop-color:#FFFFFF" - offset="0.5" /> - <a:midPointstop - style="stop-color:#000000" - offset="1" /> - </radialGradient> - <radialGradient - cx="1199.74" - cy="97.150002" - r="40.400002" - fx="1199.74" - fy="97.150002" - id="rg5860" - xlink:href="#g3300_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.409,-0.107,0,0.429,-451.489,113.149)" /> - <linearGradient - x1="796.38" - y1="67.580002" - x2="781.28003" - y2="58.549999" - id="g3298_" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:#4c8bca;stop-opacity:1" - offset="0" - id="s6462" /> - <stop - style="stop-color:#b7e9ff;stop-opacity:1" - offset="1" - id="s6464" /> - <a:midPointstop - style="stop-color:#4C8BCA" - offset="0" /> - <a:midPointstop - style="stop-color:#4C8BCA" - offset="0.5" /> - <a:midPointstop - style="stop-color:#B7E9FF" - offset="1" /> - </linearGradient> - <linearGradient - x1="800.97998" - y1="140.72" - x2="777.71997" - y2="121.76" - id="g3297_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1,-0.25,0,1,0,129.19)"> - <stop - style="stop-color:#e5e5e5;stop-opacity:1" - offset="0" - id="s6448" /> - <stop - style="stop-color:#ccc;stop-opacity:1" - offset="1" - id="s6450" /> - <a:midPointstop - style="stop-color:#E5E5E5" - offset="0" /> - <a:midPointstop - style="stop-color:#E5E5E5" - offset="0.5" /> - <a:midPointstop - style="stop-color:#CCCCCC" - offset="1" /> - </linearGradient> - <linearGradient - x1="800.97998" - y1="140.72" - x2="777.71997" - y2="121.76" - id="lg5890" - xlink:href="#g3297_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1,-0.25,0,1,0,129.19)" /> - <linearGradient - x1="790.03998" - y1="-16.33" - x2="779.84003" - y2="-3.73" - id="g3296_" - gradientUnits="userSpaceOnUse" - gradientTransform="translate(0,70.17)"> - <stop - style="stop-color:#d9d9d9;stop-opacity:1" - offset="0" - id="s6439" /> - <stop - style="stop-color:#f2f2f2;stop-opacity:1" - offset="0.51999998" - id="s6441" /> - <stop - style="stop-color:#ccc;stop-opacity:1" - offset="1" - id="s6443" /> - <a:midPointstop - style="stop-color:#D9D9D9" - offset="0" /> - <a:midPointstop - style="stop-color:#D9D9D9" - offset="0.5" /> - <a:midPointstop - style="stop-color:#F2F2F2" - offset="0.52" /> - <a:midPointstop - style="stop-color:#F2F2F2" - offset="0.5" /> - <a:midPointstop - style="stop-color:#CCCCCC" - offset="1" /> - </linearGradient> - <linearGradient - x1="790.03998" - y1="-16.33" - x2="779.84003" - y2="-3.73" - id="lg5866" - xlink:href="#g3296_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1.204,0,0,1.263,-926.036,28.6)" /> - <linearGradient - x1="785.84003" - y1="72.989998" - x2="785.26001" - y2="76.279999" - id="g3293_" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:white;stop-opacity:1" - offset="0" - id="s6412" /> - <stop - style="stop-color:#737373;stop-opacity:1" - offset="1" - id="s6414" /> - <a:midPointstop - style="stop-color:#FFFFFF" - offset="0" /> - <a:midPointstop - style="stop-color:#FFFFFF" - offset="0.5" /> - <a:midPointstop - style="stop-color:#737373" - offset="1" /> - </linearGradient> - <linearGradient - x1="785.84003" - y1="72.989998" - x2="785.26001" - y2="76.279999" - id="lg5871" - xlink:href="#g3293_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1.204,0,0,1.263,-926.036,-60.001)" /> - <linearGradient - x1="789.37" - y1="69.879997" - x2="791.03998" - y2="77.120003" - id="g3292_" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:#999;stop-opacity:1" - offset="0" - id="s6403" /> - <stop - style="stop-color:#f2f2f2;stop-opacity:1" - offset="0.28" - id="s6405" /> - <stop - style="stop-color:#666;stop-opacity:1" - offset="1" - id="s6407" /> - <a:midPointstop - style="stop-color:#999999" - offset="0" /> - <a:midPointstop - style="stop-color:#999999" - offset="0.5" /> - <a:midPointstop - style="stop-color:#F2F2F2" - offset="0.28" /> - <a:midPointstop - style="stop-color:#F2F2F2" - offset="0.5" /> - <a:midPointstop - style="stop-color:#666666" - offset="1" /> - </linearGradient> - <linearGradient - x1="789.37" - y1="69.879997" - x2="791.03998" - y2="77.120003" - id="lg5874" - xlink:href="#g3292_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1.204,0,0,1.263,-926.036,-60.001)" /> - <linearGradient - x1="786.65997" - y1="136.12" - x2="786.71002" - y2="134.33" - id="g3290_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1,-0.25,0,1,0,137.29)"> - <stop - style="stop-color:#d9d9d9;stop-opacity:1" - offset="0" - id="s6380" /> - <stop - style="stop-color:#b2b2b2;stop-opacity:1" - offset="1" - id="s6382" /> - <a:midPointstop - style="stop-color:#D9D9D9" - offset="0" /> - <a:midPointstop - style="stop-color:#D9D9D9" - offset="0.5" /> - <a:midPointstop - style="stop-color:#B2B2B2" - offset="1" /> - </linearGradient> - <linearGradient - x1="786.65997" - y1="136.12" - x2="786.71002" - y2="134.33" - id="lg5878" - xlink:href="#g3290_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(1.204,-0.316,0,1.263,-926.036,113.351)" /> - <radialGradient - cx="1458.77" - cy="-5.0999999" - r="35.130001" - fx="1458.77" - fy="-5.0999999" - id="g3289_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.42,0,0,0.42,167.09,79.84)"> - <stop - style="stop-color:white;stop-opacity:1" - offset="0" - id="s6371" /> - <stop - style="stop-color:#999;stop-opacity:1" - offset="1" - id="s6373" /> - <a:midPointstop - style="stop-color:#FFFFFF" - offset="0" /> - <a:midPointstop - style="stop-color:#FFFFFF" - offset="0.5" /> - <a:midPointstop - style="stop-color:#999999" - offset="1" /> - </radialGradient> - <radialGradient - cx="1458.77" - cy="-5.0999999" - r="35.130001" - fx="1458.77" - fy="-5.0999999" - id="rg5881" - xlink:href="#g3289_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.505,0,0,0.53,-724.957,40.636)" /> - <radialGradient - cx="1612.98" - cy="-4.4699998" - r="36.580002" - fx="1612.98" - fy="-4.4699998" - id="g3288_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.34,0,0,0.36,238.56,86.87)"> - <stop - style="stop-color:#e5e5e5;stop-opacity:1" - offset="0" - id="s6362" /> - <stop - style="stop-color:#b2b2b2;stop-opacity:1" - offset="0.63999999" - id="s6364" /> - <stop - style="stop-color:#737373;stop-opacity:1" - offset="1" - id="s6366" /> - <a:midPointstop - style="stop-color:#E5E5E5" - offset="0" /> - <a:midPointstop - style="stop-color:#E5E5E5" - offset="0.5" /> - <a:midPointstop - style="stop-color:#B2B2B2" - offset="0.64" /> - <a:midPointstop - style="stop-color:#B2B2B2" - offset="0.5" /> - <a:midPointstop - style="stop-color:#737373" - offset="1" /> - </radialGradient> - <radialGradient - cx="1612.98" - cy="-4.4699998" - r="36.580002" - fx="1612.98" - fy="-4.4699998" - id="rg5884" - xlink:href="#g3288_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.408,0,0,0.448,-638.943,49.495)" /> - <radialGradient - cx="1470.5" - cy="-10.21" - r="33.290001" - fx="1470.5" - fy="-10.21" - id="g3287_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.42,0,0,0.42,167.09,79.84)"> - <stop - style="stop-color:#e5e5e5;stop-opacity:1" - offset="0" - id="s6347" /> - <stop - style="stop-color:#b2b2b2;stop-opacity:1" - offset="0.38999999" - id="s6349" /> - <stop - style="stop-color:#b1b1b1;stop-opacity:1" - offset="0.75" - id="s6351" /> - <stop - style="stop-color:#aaa;stop-opacity:1" - offset="0.88" - id="s6353" /> - <stop - style="stop-color:#9e9e9e;stop-opacity:1" - offset="0.97000003" - id="s6355" /> - <stop - style="stop-color:#999;stop-opacity:1" - offset="1" - id="s6357" /> - <a:midPointstop - style="stop-color:#E5E5E5" - offset="0" /> - <a:midPointstop - style="stop-color:#E5E5E5" - offset="0.5" /> - <a:midPointstop - style="stop-color:#B2B2B2" - offset="0.39" /> - <a:midPointstop - style="stop-color:#B2B2B2" - offset="0.87" /> - <a:midPointstop - style="stop-color:#999999" - offset="1" /> - </radialGradient> - <radialGradient - cx="1470.5" - cy="-10.21" - r="33.290001" - fx="1470.5" - fy="-10.21" - id="rg5887" - xlink:href="#g3287_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.505,0,0,0.53,-724.957,40.636)" /> - <pattern - patternTransform="matrix(0.592927,0,0,0.592927,78,462)" - id="cream-spots" - height="32" - width="32" - patternUnits="userSpaceOnUse"> - <g - transform="translate(-365.3146,-513.505)" - id="g3047"> - id="path2858" /> - <path - inkscape:label="#path2854" - sodipodi:nodetypes="czzzz" - style="fill:#e3dcc0" - id="path3060" - d="M 390.31462,529.50504 C 390.31462,534.47304 386.28262,538.50504 381.31462,538.50504 C 376.34662,538.50504 372.31462,534.47304 372.31462,529.50504 C 372.31462,524.53704 376.34662,520.50504 381.31462,520.50504 C 386.28262,520.50504 390.31462,524.53704 390.31462,529.50504 z " /> -</g> - </pattern> - <pattern - patternTransform="matrix(0.733751,0,0,0.733751,67,367)" - id="dark-cream-spots" - height="32" - width="32" - patternUnits="userSpaceOnUse"> - <g - transform="translate(-408.0946,-513.505)" - id="dark-cream-spot" - inkscape:label="#g3043"> - <path - sodipodi:nodetypes="czzzz" - style="fill:#c8c5ac" - d="M 433.09458,529.50504 C 433.09458,534.47304 429.06258,538.50504 424.09458,538.50504 C 419.12658,538.50504 415.09458,534.47304 415.09458,529.50504 C 415.09458,524.53704 419.12658,520.50504 424.09458,520.50504 C 429.06258,520.50504 433.09458,524.53704 433.09458,529.50504 z " - id="path2953" /> - </g> - </pattern> - <pattern - patternTransform="matrix(0.375,0,0,0.375,379,400)" - id="white-spots" - height="32" - width="32" - patternUnits="userSpaceOnUse"> - <g - transform="translate(-484.3997,-513.505)" - id="white-spot" - inkscape:label="#g3035"> - <path - style="opacity:0.25;fill:white" - id="path3033" - d="M 509.39967,529.50504 C 509.39967,534.47304 505.36767,538.50504 500.39967,538.50504 C 495.43167,538.50504 491.39967,534.47304 491.39967,529.50504 C 491.39967,524.53704 495.43167,520.50504 500.39967,520.50504 C 505.36767,520.50504 509.39967,524.53704 509.39967,529.50504 z " - sodipodi:nodetypes="czzzz" /> - </g> - </pattern> - <pattern - patternTransform="matrix(0.455007,0,0,0.455007,-5e-5,1.9e-5)" - id="black-spots" - height="32" - width="32" - patternUnits="userSpaceOnUse"> - <g - transform="translate(-448.3997,-513.505)" - id="black-spot" - inkscape:label="#g3039"> - <path - sodipodi:nodetypes="czzzz" - d="M 473.39967,529.50504 C 473.39967,534.47304 469.36767,538.50504 464.39967,538.50504 C 459.43167,538.50504 455.39967,534.47304 455.39967,529.50504 C 455.39967,524.53704 459.43167,520.50504 464.39967,520.50504 C 469.36767,520.50504 473.39967,524.53704 473.39967,529.50504 z " - id="path2961" - style="opacity:0.25;fill:black" /> - </g> - </pattern> - <linearGradient - x1="501.0903" - y1="-19.2544" - x2="531.85413" - y2="0.72390002" - id="linearGradient17334" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)"> - <stop - style="stop-color:#b4daea;stop-opacity:1" - offset="0" - id="stop17336" /> - <stop - style="stop-color:#b4daea;stop-opacity:1" - offset="0.51120001" - id="stop17338" /> - <stop - style="stop-color:#5387ba;stop-opacity:1" - offset="0.64609998" - id="stop17340" /> - <stop - style="stop-color:#16336e;stop-opacity:1" - offset="1" - id="stop17342" /> - <a:midPointStop - offset="0" - style="stop-color:#B4DAEA" /> - <a:midPointStop - offset="0.5" - style="stop-color:#B4DAEA" /> - <a:midPointStop - offset="0.5112" - style="stop-color:#B4DAEA" /> - <a:midPointStop - offset="0.5" - style="stop-color:#B4DAEA" /> - <a:midPointStop - offset="0.6461" - style="stop-color:#5387BA" /> - <a:midPointStop - offset="0.5" - style="stop-color:#5387BA" /> - <a:midPointStop - offset="1" - style="stop-color:#16336E" /> - </linearGradient> - <linearGradient - x1="415.73831" - y1="11.854" - x2="418.13361" - y2="18.8104" - id="linearGradient17426" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.8362,0.5206,-1.1904,0.992,147.62,-30.9374)"> - <stop - style="stop-color:#ccc;stop-opacity:1" - offset="0" - id="stop17428" /> - <stop - style="stop-color:#f2f2f2;stop-opacity:1" - offset="1" - id="stop17430" /> - <a:midPointStop - offset="0" - style="stop-color:#CCCCCC" /> - <a:midPointStop - offset="0.5" - style="stop-color:#CCCCCC" /> - <a:midPointStop - offset="1" - style="stop-color:#F2F2F2" /> - </linearGradient> - <linearGradient - x1="478.21341" - y1="-131.9297" - x2="469.85818" - y2="-140.28481" - id="linearGradient17434" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.5592,0.829,-0.829,0.5592,101.3357,-104.791)"> - <stop - style="stop-color:#f3403f;stop-opacity:1" - offset="0" - id="stop17436" /> - <stop - style="stop-color:#d02a28;stop-opacity:1" - offset="0.37889999" - id="stop17438" /> - <stop - style="stop-color:#b21714;stop-opacity:1" - offset="0.77649999" - id="stop17440" /> - <stop - style="stop-color:#a6100c;stop-opacity:1" - offset="1" - id="stop17442" /> - <a:midPointStop - offset="0" - style="stop-color:#F3403F" /> - <a:midPointStop - offset="0.4213" - style="stop-color:#F3403F" /> - <a:midPointStop - offset="1" - style="stop-color:#A6100C" /> - </linearGradient> - <linearGradient - x1="502.70749" - y1="115.3013" - x2="516.39001" - y2="127.1953" - id="linearGradient17709" - xlink:href="#XMLID_1749_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.9703,0.2419,-0.2419,0.9703,11.0227,-35.6159)" /> - <linearGradient - x1="506.09909" - y1="-11.5137" - x2="527.99609" - y2="2.7063999" - id="linearGradient17711" - xlink:href="#XMLID_1752_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" /> - <linearGradient - x1="516.57672" - y1="-15.769" - x2="516.57672" - y2="0.84280002" - id="linearGradient17713" - xlink:href="#XMLID_1753_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" /> - <linearGradient - x1="505.62939" - y1="-14.9526" - x2="527.49402" - y2="-0.7536" - id="linearGradient17715" - xlink:href="#XMLID_1756_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" /> - <linearGradient - x1="500.70749" - y1="-13.2441" - x2="513.46442" - y2="-2.1547" - id="linearGradient17717" - xlink:href="#XMLID_1757_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" /> - <linearGradient - x1="473.7681" - y1="209.17529" - x2="486.98099" - y2="213.2001" - id="linearGradient17721" - xlink:href="#XMLID_2274_" - gradientUnits="userSpaceOnUse" /> - <linearGradient - x1="481.23969" - y1="212.5742" - x2="472.92981" - y2="207.4967" - id="linearGradient17723" - xlink:href="#XMLID_2275_" - gradientUnits="userSpaceOnUse" /> - <linearGradient - x1="500.70749" - y1="-13.2441" - x2="513.46442" - y2="-2.1547" - id="linearGradient17416" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)"> - <stop - style="stop-color:#5387ba;stop-opacity:1" - offset="0" - id="stop17418" /> - <stop - style="stop-color:#96bad6;stop-opacity:1" - offset="1" - id="stop17420" /> - <a:midPointStop - style="stop-color:#5387BA" - offset="0" /> - <a:midPointStop - style="stop-color:#5387BA" - offset="0.5" /> - <a:midPointStop - style="stop-color:#96BAD6" - offset="1" /> - </linearGradient> - <defs - id="defs9929"> - <path - d="M 489.21,209.35 L 485.35,203.63 C 483.63,204.25 473.47,208.93 471.5,210.18 C 470.57,210.77 470.17,211.16 469.72,212.48 C 470.93,212.31 471.72,212.49 473.42,213.04 C 473.26,214.77 473.24,215.74 473.57,218.2 C 474.01,216.88 474.41,216.49 475.34,215.9 C 477.33,214.65 487.49,209.97 489.21,209.35 z " - id="XMLID_960_" /> - </defs> - <clipPath - id="clipPath17448"> - <use - id="use17450" - x="0" - y="0" - width="744.09448" - height="600" - xlink:href="#XMLID_960_" /> - </clipPath> - <linearGradient - x1="473.7681" - y1="209.17529" - x2="486.98099" - y2="213.2001" - id="linearGradient17452" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:#f3403f;stop-opacity:1" - offset="0" - id="stop17454" /> - <stop - style="stop-color:#d02a28;stop-opacity:1" - offset="0.37889999" - id="stop17456" /> - <stop - style="stop-color:#b21714;stop-opacity:1" - offset="0.77649999" - id="stop17458" /> - <stop - style="stop-color:#a6100c;stop-opacity:1" - offset="1" - id="stop17460" /> - <a:midPointStop - style="stop-color:#F3403F" - offset="0" /> - <a:midPointStop - style="stop-color:#F3403F" - offset="0.4213" /> - <a:midPointStop - style="stop-color:#A6100C" - offset="1" /> - </linearGradient> - <linearGradient - x1="481.23969" - y1="212.5742" - x2="472.92981" - y2="207.4967" - id="linearGradient17463" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:#f3403f;stop-opacity:1" - offset="0" - id="stop17465" /> - <stop - style="stop-color:#d02a28;stop-opacity:1" - offset="0.37889999" - id="stop17467" /> - <stop - style="stop-color:#b21714;stop-opacity:1" - offset="0.77649999" - id="stop17469" /> - <stop - style="stop-color:#a6100c;stop-opacity:1" - offset="1" - id="stop17471" /> - <a:midPointStop - style="stop-color:#F3403F" - offset="0" /> - <a:midPointStop - style="stop-color:#F3403F" - offset="0.4213" /> - <a:midPointStop - style="stop-color:#A6100C" - offset="1" /> - </linearGradient> - <linearGradient - x1="481.23969" - y1="212.5742" - x2="472.92981" - y2="207.4967" - id="linearGradient17807" - xlink:href="#XMLID_2275_" - gradientUnits="userSpaceOnUse" - gradientTransform="translate(-177.1654,35.43307)" /> - <linearGradient - x1="473.7681" - y1="209.17529" - x2="486.98099" - y2="213.2001" - id="linearGradient17810" - xlink:href="#XMLID_2274_" - gradientUnits="userSpaceOnUse" - gradientTransform="translate(-177.1654,35.43307)" /> - <linearGradient - x1="502.70749" - y1="115.3013" - x2="516.39001" - y2="127.1953" - id="linearGradient17812" - xlink:href="#XMLID_1749_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.9703,0.2419,-0.2419,0.9703,11.0227,-35.6159)" /> - <linearGradient - x1="506.09909" - y1="-11.5137" - x2="527.99609" - y2="2.7063999" - id="linearGradient17814" - xlink:href="#XMLID_1752_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" /> - <linearGradient - x1="516.57672" - y1="-15.769" - x2="516.57672" - y2="0.84280002" - id="linearGradient17816" - xlink:href="#XMLID_1753_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" /> - <linearGradient - x1="505.62939" - y1="-14.9526" - x2="527.49402" - y2="-0.7536" - id="linearGradient17818" - xlink:href="#XMLID_1756_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" /> - <linearGradient - x1="502.70749" - y1="115.3013" - x2="516.39001" - y2="127.1953" - id="linearGradient17347" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.9703,0.2419,-0.2419,0.9703,11.0227,-35.6159)"> - <stop - style="stop-color:#5387ba;stop-opacity:1" - offset="0" - id="stop17349" /> - <stop - style="stop-color:#96bad6;stop-opacity:1" - offset="1" - id="stop17351" /> - <a:midPointStop - offset="0" - style="stop-color:#5387BA" /> - <a:midPointStop - offset="0.5" - style="stop-color:#5387BA" /> - <a:midPointStop - offset="1" - style="stop-color:#96BAD6" /> - </linearGradient> - <linearGradient - x1="516.57672" - y1="-15.769" - x2="516.57672" - y2="0.84280002" - id="linearGradient17379" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)"> - <stop - style="stop-color:#b2b2b2;stop-opacity:1" - offset="0" - id="stop17381" /> - <stop - style="stop-color:#f2f2f2;stop-opacity:1" - offset="1" - id="stop17383" /> - <a:midPointStop - offset="0" - style="stop-color:#B2B2B2" /> - <a:midPointStop - offset="0.5" - style="stop-color:#B2B2B2" /> - <a:midPointStop - offset="1" - style="stop-color:#F2F2F2" /> - </linearGradient> - <linearGradient - x1="502.70749" - y1="115.3013" - x2="516.39001" - y2="127.1953" - id="linearGradient17862" - xlink:href="#XMLID_1749_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.9703,0.2419,-0.2419,0.9703,-166.1427,-0.18283)" /> - <linearGradient - x1="505.62939" - y1="-14.9526" - x2="527.49402" - y2="-0.7536" - id="linearGradient17864" - xlink:href="#XMLID_1756_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" /> - <defs - id="defs3859"> - <polygon - points="465.54,213.52 481.94,217.46 482.74,216.71 487.46,198.05 471.08,194.07 470.26,194.83 465.54,213.52 " - id="XMLID_343_" /> - </defs> - <linearGradient - x1="471.0806" - y1="201.07761" - x2="481.91711" - y2="210.4977" - id="linearGradient17389" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:#6498c1;stop-opacity:1" - offset="0.005618" - id="stop17391" /> - <stop - style="stop-color:#79a9cc;stop-opacity:1" - offset="0.2332" - id="stop17393" /> - <stop - style="stop-color:#a4cde2;stop-opacity:1" - offset="0.74049997" - id="stop17395" /> - <stop - style="stop-color:#b4daea;stop-opacity:1" - offset="1" - id="stop17397" /> - <a:midPointStop - style="stop-color:#6498C1" - offset="5.618000e-003" /> - <a:midPointStop - style="stop-color:#6498C1" - offset="0.4438" /> - <a:midPointStop - style="stop-color:#B4DAEA" - offset="1" /> - </linearGradient> - <clipPath - id="clipPath17400"> - <use - id="use17402" - x="0" - y="0" - width="744.09448" - height="600" - xlink:href="#XMLID_343_" /> - </clipPath> - <linearGradient - x1="505.62939" - y1="-14.9526" - x2="527.49402" - y2="-0.7536" - id="linearGradient17404" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)"> - <stop - style="stop-color:#b4daea;stop-opacity:1" - offset="0" - id="stop17406" /> - <stop - style="stop-color:#b4daea;stop-opacity:1" - offset="0.51120001" - id="stop17408" /> - <stop - style="stop-color:#5387ba;stop-opacity:1" - offset="0.64609998" - id="stop17410" /> - <stop - style="stop-color:#16336e;stop-opacity:1" - offset="1" - id="stop17412" /> - <a:midPointStop - style="stop-color:#B4DAEA" - offset="0" /> - <a:midPointStop - style="stop-color:#B4DAEA" - offset="0.5" /> - <a:midPointStop - style="stop-color:#B4DAEA" - offset="0.5112" /> - <a:midPointStop - style="stop-color:#B4DAEA" - offset="0.5" /> - <a:midPointStop - style="stop-color:#5387BA" - offset="0.6461" /> - <a:midPointStop - style="stop-color:#5387BA" - offset="0.5" /> - <a:midPointStop - style="stop-color:#16336E" - offset="1" /> - </linearGradient> - <linearGradient - x1="506.09909" - y1="-11.5137" - x2="527.99609" - y2="2.7063999" - id="linearGradient17882" - xlink:href="#XMLID_1752_" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" /> - <defs - id="defs3826"> - <polygon - points="463.52,216.14 480.56,220.24 481.36,219.5 483.03,202.04 469.05,196.69 468.24,197.45 463.52,216.14 " - id="XMLID_338_" /> - </defs> - <linearGradient - x1="468.2915" - y1="204.7612" - x2="479.39871" - y2="214.4166" - id="linearGradient17357" - gradientUnits="userSpaceOnUse"> - <stop - style="stop-color:#5387ba;stop-opacity:1" - offset="0" - id="stop17359" /> - <stop - style="stop-color:#96bad6;stop-opacity:1" - offset="1" - id="stop17361" /> - <a:midPointStop - style="stop-color:#5387BA" - offset="0" /> - <a:midPointStop - style="stop-color:#5387BA" - offset="0.5" /> - <a:midPointStop - style="stop-color:#96BAD6" - offset="1" /> - </linearGradient> - <clipPath - id="clipPath17364"> - <use - id="use17366" - x="0" - y="0" - width="744.09448" - height="600" - xlink:href="#XMLID_338_" /> - </clipPath> - <linearGradient - x1="506.09909" - y1="-11.5137" - x2="527.99609" - y2="2.7063999" - id="linearGradient17368" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)"> - <stop - style="stop-color:#b4daea;stop-opacity:1" - offset="0" - id="stop17370" /> - <stop - style="stop-color:#b4daea;stop-opacity:1" - offset="0.51120001" - id="stop17372" /> - <stop - style="stop-color:#5387ba;stop-opacity:1" - offset="0.64609998" - id="stop17374" /> - <stop - style="stop-color:#16336e;stop-opacity:1" - offset="1" - id="stop17376" /> - <a:midPointStop - style="stop-color:#B4DAEA" - offset="0" /> - <a:midPointStop - style="stop-color:#B4DAEA" - offset="0.5" /> - <a:midPointStop - style="stop-color:#B4DAEA" - offset="0.5112" /> - <a:midPointStop - style="stop-color:#B4DAEA" - offset="0.5" /> - <a:midPointStop - style="stop-color:#5387BA" - offset="0.6461" /> - <a:midPointStop - style="stop-color:#5387BA" - offset="0.5" /> - <a:midPointStop - style="stop-color:#16336E" - offset="1" /> - </linearGradient> - <linearGradient - x1="296.4996" - y1="188.81061" - x2="317.32471" - y2="209.69398" - id="linearGradient2387" - xlink:href="#linearGradient2381" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.90776,0,0,0.90776,24.35648,49.24131)" /> - <linearGradient - x1="296.4996" - y1="188.81061" - x2="317.32471" - y2="209.69398" - id="linearGradient5105" - xlink:href="#linearGradient2381" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.90776,0,0,0.90776,24.35648,49.24131)" /> - <linearGradient - x1="296.4996" - y1="188.81061" - x2="317.32471" - y2="209.69398" - id="linearGradient5145" - xlink:href="#linearGradient2381" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.90776,0,0,0.90776,24.35648,49.24131)" /> - <linearGradient - inkscape:collect="always" - xlink:href="#linearGradient2381" - id="linearGradient2371" - gradientUnits="userSpaceOnUse" - gradientTransform="matrix(0.90776,0,0,0.90776,24.35648,49.24131)" - x1="296.4996" - y1="188.81061" - x2="317.32471" - y2="209.69398" /> + <linearGradient x1="296.4996" y1="188.81061" x2="317.32471" y2="209.69398" id="linearGradient2371" xlink:href="#linearGradient2381" gradientUnits="userSpaceOnUse" gradientTransform="matrix(0.90776,0,0,0.90776,24.35648,49.24131)"/> </defs> - <g - transform="matrix(0.437808,-0.437808,0.437808,0.437808,-220.8237,43.55311)" - id="g5089"> - <path - d="M 8.4382985,-6.28125 C 7.8309069,-6.28125 4.125,-0.33238729 4.125,1.96875 L 4.125,28.6875 C 4.125,29.533884 4.7068159,29.8125 5.28125,29.8125 L 30.84375,29.8125 C 31.476092,29.8125 31.968751,29.319842 31.96875,28.6875 L 31.96875,23.46875 L 32.25,23.46875 C 32.74684,23.46875 33.156249,23.059339 33.15625,22.5625 L 33.15625,-5.375 C 33.15625,-5.8718398 32.74684,-6.28125 32.25,-6.28125 L 8.4382985,-6.28125 z " - transform="translate(282.8327,227.1903)" - style="fill:#5c5c4f;stroke:black;stroke-width:3.23021388;stroke-miterlimit:4;stroke-dasharray:none" - id="path5091" /> - <rect - width="27.85074" - height="29.369793" - rx="1.1414107" - ry="1.1414107" - x="286.96509" - y="227.63805" - style="fill:#032c87" - id="rect5093" /> - <path - d="M 288.43262,225.43675 L 313.67442,225.43675 L 313.67442,254.80655 L 287.29827,254.83069 L 288.43262,225.43675 z " - style="fill:white" - id="rect5095" /> - <path - d="M 302.44536,251.73726 C 303.83227,259.59643 301.75225,263.02091 301.75225,263.02091 C 303.99609,261.41329 305.71651,259.54397 306.65747,257.28491 C 307.62455,259.47755 308.49041,261.71357 310.9319,263.27432 C 310.9319,263.27432 309.33686,256.07392 309.22047,251.73726 L 302.44536,251.73726 z " - style="fill:#a70000;fill-opacity:1;stroke-width:2" - id="path5097" /> - <rect - width="25.241802" - height="29.736675" - rx="0.89682275" - ry="0.89682275" - x="290.73544" - y="220.92249" - style="fill:#809cc9" - id="rect5099" /> - <path - d="M 576.47347,725.93939 L 582.84431,726.35441 L 583.25121,755.8725 C 581.35919,754.55465 576.39694,752.1117 574.98889,754.19149 L 574.98889,727.42397 C 574.98889,726.60151 575.65101,725.93939 576.47347,725.93939 z " - transform="matrix(0.499065,-0.866565,0,1,0,0)" - style="fill:#4573b3;fill-opacity:1" - id="rect5101" /> - <path - d="M 293.2599,221.89363 L 313.99908,221.89363 C 314.45009,221.89363 314.81318,222.25673 314.81318,222.70774 C 315.02865,229.0361 295.44494,244.47124 292.44579,240.30491 L 292.44579,222.70774 C 292.44579,222.25673 292.80889,221.89363 293.2599,221.89363 z " - style="opacity:0.65536726;fill:url(#linearGradient2371);fill-opacity:1" - id="path5103" /> + <g transform="matrix(0.437808,-0.437808,0.437808,0.437808,-220.8237,43.55311)" id="g5089"> + <path d="m 8.4382985,-6.28125 c -0.6073916,0 -4.3132985,5.94886271 -4.3132985,8.25 l 0,26.71875 c 0,0.846384 0.5818159,1.125 1.15625,1.125 l 25.5625,0 c 0.632342,0 1.125001,-0.492658 1.125,-1.125 l 0,-5.21875 0.28125,0 c 0.49684,0 0.906249,-0.409411 0.90625,-0.90625 l 0,-27.9375 c 0,-0.4968398 -0.40941,-0.90625 -0.90625,-0.90625 l -23.8117015,0 z" transform="translate(282.8327,227.1903)" id="path5091" style="fill:#5c5c4f;stroke:#000000;stroke-width:3.23021388;stroke-miterlimit:4;stroke-dasharray:none"/> + <rect width="27.85074" height="29.369793" rx="1.1414107" ry="1.1414107" x="286.96509" y="227.63805" id="rect5093" style="fill:#032c87"/> + <path d="m 288.43262,225.43675 25.2418,0 0,29.3698 -26.37615,0.0241 1.13435,-29.39394 z" id="rect5095" style="fill:#ffffff"/> + <path d="m 302.44536,251.73726 c 1.38691,7.85917 -0.69311,11.28365 -0.69311,11.28365 2.24384,-1.60762 3.96426,-3.47694 4.90522,-5.736 0.96708,2.19264 1.83294,4.42866 4.27443,5.98941 0,0 -1.59504,-7.2004 -1.71143,-11.53706 l -6.77511,0 z" id="path5097" style="fill:#a70000;fill-opacity:1;stroke-width:2"/> + <rect width="25.241802" height="29.736675" rx="0.89682275" ry="0.89682275" x="290.73544" y="220.92249" id="rect5099" style="fill:#809cc9"/> + <path d="m 576.47347,725.93939 6.37084,0.41502 0.4069,29.51809 c -1.89202,-1.31785 -6.85427,-3.7608 -8.26232,-1.68101 l 0,-26.76752 c 0,-0.82246 0.66212,-1.48458 1.48458,-1.48458 z" transform="matrix(0.499065,-0.866565,0,1,0,0)" id="rect5101" style="fill:#4573b3;fill-opacity:1"/> + <path d="m 293.2599,221.89363 20.73918,0 c 0.45101,0 0.8141,0.3631 0.8141,0.81411 0.21547,6.32836 -19.36824,21.7635 -22.36739,17.59717 l 0,-17.59717 c 0,-0.45101 0.3631,-0.81411 0.81411,-0.81411 z" id="path5103" style="opacity:0.65536726;fill:url(#linearGradient2371);fill-opacity:1"/> </g> </svg> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Configuring_Services.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Configuring_Services.xml 2011-12-05 03:51:59 UTC (rev 8190) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Configuring_Services.xml 2011-12-05 04:33:56 UTC (rev 8191) @@ -219,11 +219,11 @@ You see, here the <emphasis>/conf/portal/configuration.xml</emphasis> file of each jar enters the game, they are searched at first. Next, there is nearly always a configuration.xml in the portal.war file (or in the portal webapp folder), you find this file at <emphasis>/WEB-INF/conf/configuration.xml</emphasis>. If you open it, you will find a lot of import statements that point to other configuration files in the same portal.war (or portal webapp). </para> <para> - <emphasis role="bold">Multiple Portals</emphasis> Be aware that you might set up several different portals ("admin", "mexico", etc.), and each of these portals will use a different PortalContainer. And each of these PortalContainers can be configured separately. As of eXo Portal 2.5 you also will be able to provide configurations from outside the jars and wars or webapps. Put a configuration file in <emphasis>exo-tomcat/exo-conf/portal/$portal_name/configuration.xml</emphasis> where <parameter>$portal_name</parameter> is the name of the portal you want to configure for . But normally you only have one portal which is called "portal" so you use <emphasis>exo-tomcat/exo-conf/portal/portal/configuration.xml</emphasis>. + <emphasis role="bold">Multiple Portals</emphasis> Be aware that you might set up several different portals ("admin", "mexico", etc.), and each of these portals will use a different PortalContainer. And each of these PortalContainers can be configured separately. As of JBoss Enterprise Portal Platform &VY; you also will be able to provide configurations from outside the jars and wars or webapps. Put a configuration file in <emphasis>exo-tomcat/exo-conf/portal/$portal_name/configuration.xml</emphasis> where <parameter>$portal_name</parameter> is the name of the portal you want to configure for . But normally you only have one portal which is called "portal" so you use <emphasis>exo-tomcat/exo-conf/portal/portal/configuration.xml</emphasis>. </para> <note> <para> - As of eXo Portal 2.5 you can override the external configuration location with the system property <emphasis>exo.conf.dir</emphasis>. If the property exists its value will be used as path to the eXo configuration directory, that means this is an alternative to <emphasis>exo-tomcat/exo-conf</emphasis>. Just put this property in the command line: <emphasis>java -Dexo.conf.dir=/path/to/exo/conf</emphasis> or use eXo.bat or eXo.sh. In this particular use case, you have no need to use any prefixes in your configuration file to import other files. For example, if your configuration file is <emphasis>exo-tomcat/exo-conf/portal/PORTAL_NAME/configuration.xml</emphasis> and you want to import the configuration file <emphasis>exo-tomcat/exo-conf/portal/PORTAL_NAME/mySubConfDir/myConfig.xml</emphasis>, you can do it by adding <emphasis><import>mySubConfDir/myConfig.xml</import></emphasis> to your configuration file. + As of JBoss Enterprise Portal Platform &VY; you can override the external configuration location with the system property <emphasis>exo.conf.dir</emphasis>. If the property exists its value will be used as path to the eXo configuration directory, that means this is an alternative to <emphasis>exo-tomcat/exo-conf</emphasis>. Just put this property in the command line: <emphasis>java -Dexo.conf.dir=/path/to/exo/conf</emphasis> or use eXo.bat or eXo.sh. In this particular use case, you have no need to use any prefixes in your configuration file to import other files. For example, if your configuration file is <emphasis>exo-tomcat/exo-conf/portal/PORTAL_NAME/configuration.xml</emphasis> and you want to import the configuration file <emphasis>exo-tomcat/exo-conf/portal/PORTAL_NAME/mySubConfDir/myConfig.xml</emphasis>, you can do it by adding <emphasis><import>mySubConfDir/myConfig.xml</import></emphasis> to your configuration file. </para> </note> @@ -905,9 +905,8 @@ </init-params> </component></programlisting> <para> - As these are system properties you use the -D command: <emphasis role="bold">java -DconnectionUrl=jdbc:hsqldb:file:../temp/data/exodb -DdriverClass=org.hsqldb.jdbcDriver</emphasis> Or better use the parameters of eXo.bat / eXo.sh when you start eXo Portal: <emphasis role="bold">set EXO_OPTS="-DconnectionUrl=jdbc:hsqldb:file:../temp/data/exodb -DdriverClass=org.hsqldb.jdbcDriver"</emphasis> + As these are system properties you use the -D command: <emphasis role="bold">java -DconnectionUrl=jdbc:hsqldb:file:../temp/data/exodb -DdriverClass=org.hsqldb.jdbcDriver</emphasis> Or better use the parameters of eXo.bat / eXo.sh when you start JBoss Enterprise Portal Platform: <emphasis role="bold">set EXO_OPTS="-DconnectionUrl=jdbc:hsqldb:file:../temp/data/exodb -DdriverClass=org.hsqldb.jdbcDriver"</emphasis> </para> - </section> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml 2011-12-05 03:51:59 UTC (rev 8190) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml 2011-12-05 04:33:56 UTC (rev 8191) @@ -4,8 +4,7 @@ %BOOK_ENTITIES; ]> <section id="sect-Reference_Guide-SSO_Single_Sign_On_"> - <title><remark>SSO - Single Sign On</remark> - </title> + <title><remark>SSO - Single Sign On</remark></title> <section id="sect-Reference_Guide-SSO_Single_Sign_On_-Overview"> <title>Overview</title> <para> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalConfiguration.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalConfiguration.xml 2011-12-05 03:51:59 UTC (rev 8190) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalConfiguration.xml 2011-12-05 04:33:56 UTC (rev 8191) @@ -4,40 +4,40 @@ %BOOK_ENTITIES; ]> <chapter id="chap-Reference_Guide-Default_Portal_Configuration"> - <title>Default Portal Configuration</title> - <section id="sect-Reference_Guide-Default_Portal_Configuration-Overview"> - <title>Overview</title> - <para> - JBoss Enterprise Portal Platform's default home page URL is <literal>http://{hostname}:{port}/portal/</literal>. There may be multiple independent portals deployed in parallel at any given time, each of which has its root context (<literal>http://{hostname}:{port}/sample-portal/</literal>, for example). - </para> - <para> - Each portal container is internally composed of one or more 'portals'. This is because there needs to be at least one such portal available. The default portal is called '<emphasis>Classic</emphasis>'. When accessing JBoss Enterprise Portal Platform's default URL, you are automatically directed to the '<emphasis>Classic</emphasis>' portal. - </para> - <para> - The default portal performs another important task. When starting up JBoss Enterprise Portal Platform for the first time, its JCR database (where portal runtime-configurable settings are stored) will be empty . The default portal detects this and triggers automatic data initialization. - </para> + <title>Default Portal Configuration</title> + <section id="sect-Reference_Guide-Default_Portal_Configuration-Overview"> + <title>Overview</title> + <para> + JBoss Enterprise Portal Platform's default home page URL is <literal>http://{hostname}:{port}/portal/</literal>. There may be multiple independent portal containers deployed in parallel at any given time, each of which has its root context (<literal>http://{hostname}:{port}/sample-portal/</literal>, for example). + </para> + <para> + Each portal container is internally composed of one or more 'portals'. This is because there needs to be at least one such portal available. The default portal is called '<emphasis>Classic</emphasis>'. When accessing JBoss Enterprise Portal Platform's default URL, you are automatically directed to the '<emphasis>Classic</emphasis>' portal. + </para> + <para> + The default portal performs another important task. When starting up JBoss Enterprise Portal Platform for the first time, its JCR database (where portal runtime-configurable settings are stored) will be empty . The default portal detects this and triggers automatic data initialization. + </para> - </section> - - <section id="sect-Reference_Guide-Default_Portal_Configuration-Configuration"> - <title>Configuration</title> - <para> - The following example configuration can be found at: "<filename>02portal.war:/WEB-INF/conf/portal/portal-configuration.xml</filename>". - </para> - + </section> + + <section id="sect-Reference_Guide-Default_Portal_Configuration-Configuration"> + <title>Configuration</title> + <para> + The following example configuration can be found at: "<filename>02portal.war:/WEB-INF/conf/portal/portal-configuration.xml</filename>". + </para> + <programlisting language="XML" role="XML"><xi:include href="../../extras/PortalDevelopment_DefaultPortalConfiguration/default143.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - <para> - In this example the <emphasis>Classic</emphasis> portal has been set as the default. - </para> - <para> - Notice that the <literal>NewPortalConfigListener</literal> <parameter>component-plugin</parameter> is used to add configuration to <literal>UserPortalConfigService</literal>, which is designed in this way to allow other components to add configuration to it. - </para> - <para> - <emphasis>Components</emphasis>, <emphasis>component-plugins</emphasis>, and <emphasis>init-params</emphasis> are explained in a later chapter of this document. - </para> + <para> + In this example the <emphasis>Classic</emphasis> portal has been set as the default. + </para> + <para> + Notice that the <literal>NewPortalConfigListener</literal> <parameter>component-plugin</parameter> is used to add configuration to <literal>UserPortalConfigService</literal>, which is designed in this way to allow other components to add configuration to it. + </para> + <para> + <emphasis>Components</emphasis>, <emphasis>component-plugins</emphasis>, and <emphasis>init-params</emphasis> are explained in a later chapter of this document. + </para> - </section> - + </section> + </chapter> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalNavigationConfiguration.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalNavigationConfiguration.xml 2011-12-05 03:51:59 UTC (rev 8190) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalNavigationConfiguration.xml 2011-12-05 04:33:56 UTC (rev 8191) @@ -136,7 +136,7 @@ Based on these parameters, the portal will look for the configuration files and create a relevant portal navigation, pages and data import strategy. </para> <para> - The portal configuration files will be stored in folders with path look like <filename>{templateLocation}/{ownerType}/{predefinedOwner}</filename>, all navigations are defined in the <filename>navigation.xml</filename> file, pages are defined in <filename>pages.xml</filename> and portal configuration is defined in <filename>{ownerType}.xml</filename>. + The portal configuration files will be stored in folders with path look like <filename>{templateLocation}/{ownerType}/{predefinedOwner}</filename>, all navigations are defined in the <filename>navigation.xml</filename> file, pages are defined in <filename>pages.xml</filename> and portal configuration is defined in <filename>portal.xml</filename>. </para> <para> For example, with the above configuration, portal will look for all configuration files from <filename>war:/conf/portal/portal/classic path.</filename> @@ -278,11 +278,7 @@   <para> Two files configure the user navigation (<filename>navigation.xml</filename> and <filename>pages.xml</filename>). They are located in the directory "<filename>02portal.war/WEB-INF/conf/portal/users/{userName}</filename>". </para> -  <para> The file <filename>eXoGadgets.war/WEB-INF/gadget.xml</filename> defines the gadgets that will be available on a user dashboard. </para> <para> 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 2011-12-05 03:51:59 UTC (rev 8190) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/NavigationController.xml 2011-12-05 04:33:56 UTC (rev 8191) @@ -4,82 +4,82 @@ %BOOK_ENTITIES; ]> <chapter id="chap-Reference_Guide-Navigation_Controller_"> - <title>Navigation Controller </title> - <section id="sect-Reference_Guide-Navigation_Controller_-Description"> - <title>Description</title> - <para> - The navigation controller is a major enhancement of JBoss Enterprise Portal Platform that has several goals: - </para> - <itemizedlist> - <listitem> - <para> - Provide non ambiguous URLs for portal managed resources such as navigation. Previously different resources were possible for a single URL, even worse, the set of resources available for an URL was depending on one's private navigation (groups and dashboard) - </para> + <title>Navigation Controller </title> + <section id="sect-Reference_Guide-Navigation_Controller_-Description"> + <title>Description</title> + <para> + The navigation controller is a major enhancement of JBoss Enterprise Portal Platform that has several goals: + </para> + <itemizedlist> + <listitem> + <para> + Provide non ambiguous URLs for portal managed resources such as navigation. Previously different resources were possible for a single URL, even worse, the set of resources available for an URL was depending on one's private navigation (groups and dashboard) + </para> - </listitem> - <listitem> - <para> - Decouple the <literal>http</literal> request from the portal request. Previously both were tightly coupled, for instance the URL for a site had to begin with <uri>/public/{sitename}</uri> or <uri>/private/{sitename}</uri>. The navigation controller provides a flexible and configurable mapping. - </para> + </listitem> + <listitem> + <para> + Decouple the <literal>http</literal> request from the portal request. Previously both were tightly coupled, for instance the URL for a site had to begin with <uri>/public/{sitename}</uri> or <uri>/private/{sitename}</uri>. The navigation controller provides a flexible and configurable mapping. + </para> - </listitem> - <listitem> - <para> - Provide more friendly URL and give a degree of freedom for portal administrators by letting them configure how <literal>http</literal> request should look. - </para> + </listitem> + <listitem> + <para> + Provide more friendly URL and give a degree of freedom for portal administrators by letting them configure how <literal>http</literal> request should look. + </para> - </listitem> + </listitem> - </itemizedlist> + </itemizedlist> - </section> - - <section id="sect-Reference_Guide-Navigation_Controller_-Controller_in_Action"> - <title>Controller in Action</title> - <section id="sect-Reference_Guide-Controller_in_Action-Controller"> - <title>Controller</title> - <para> - The <application>WebAppController</application> is the component of JBoss Enterprise Portal Platform that process <literal>http</literal> invocations and transforms them into a portal request. It has been improved with the addition of a request mapping engine (<emphasis role="bold">controller</emphasis>) whose role is to make the decoupling of the <literal>http</literal> request and create a portal request. - </para> - <para> - The mapping engine makes two essential tasks: - </para> - <itemizedlist> - <listitem> - <para> - Create a Map<QualifiedName, String> from an incoming <literal>http</literal> request - </para> + </section> + + <section id="sect-Reference_Guide-Navigation_Controller_-Controller_in_Action"> + <title>Controller in Action</title> + <section id="sect-Reference_Guide-Controller_in_Action-Controller"> + <title>Controller</title> + <para> + The <application>WebAppController</application> is the component of JBoss Enterprise Portal Platform that process <literal>http</literal> invocations and transforms them into a portal request. It has been improved with the addition of a request mapping engine (<emphasis role="bold">controller</emphasis>) whose role is to make the decoupling of the <literal>http</literal> request and create a portal request. + </para> + <para> + The mapping engine makes two essential tasks: + </para> + <itemizedlist> + <listitem> + <para> + Create a Map<QualifiedName, String> from an incoming <literal>http</literal> request + </para> - </listitem> - <listitem> - <para> - Render a Map<QualifiedName, String> as an <literal>http</literal> URL - </para> + </listitem> + <listitem> + <para> + Render a Map<QualifiedName, String> as an <literal>http</literal> URL + </para> - </listitem> + </listitem> - </itemizedlist> - <para> - The goal of the controller (mapping engine) is to <emphasis role="bold">decouple</emphasis> the request processed by JBoss Enterprise Portal Platform from the incoming <literal>HTTP</literal> request. - </para> - <para> - Indeed a request contain data that determines how the request will be processed and such data can be encoded in various places in the request such as the request path or a query parameter. The controller allows JBoss Enterprise Portal Platform route a request according to a set of parameters (a map) instead of the servlet request. - </para> - <para> - The controller configuration is declarative in an XML file, allowing easy reconfiguration of the routing table and it is processed into an internal data structure that is used to perform resolution (routing or rendering) - </para> + </itemizedlist> + <para> + The goal of the controller (mapping engine) is to <emphasis role="bold">decouple</emphasis> the request processed by JBoss Enterprise Portal Platform from the incoming <literal>HTTP</literal> request. + </para> + <para> + Indeed a request contain data that determines how the request will be processed and such data can be encoded in various places in the request such as the request path or a query parameter. The controller allows JBoss Enterprise Portal Platform route a request according to a set of parameters (a map) instead of the servlet request. + </para> + <para> + The controller configuration is declarative in an XML file, allowing easy reconfiguration of the routing table and it is processed into an internal data structure that is used to perform resolution (routing or rendering) + </para> - </section> - - <section id="sect-Reference_Guide-Controller_in_Action-Building_Controller"> - <title>Building Controller</title> - <para> - The controller configuration that contains the routing rules is loaded from a file named <filename>controller.xml</filename> that is retrieved in the JBoss Enterprise Portal Platform configuration directory. Its location is determined by the <parameter>gatein.controller.config</parameter> property. - </para> - <para> - <application>WebAppController</application> loads and initializes the mapping engine - </para> - + </section> + + <section id="sect-Reference_Guide-Controller_in_Action-Building_Controller"> + <title>Building Controller</title> + <para> + The controller configuration that contains the routing rules is loaded from a file named <filename>controller.xml</filename> that is retrieved in the JBoss Enterprise Portal Platform configuration directory. Its location is determined by the <parameter>gatein.controller.config</parameter> property. + </para> + <para> + <application>WebAppController</application> loads and initializes the mapping engine + </para> + <programlisting language="XML">  <component> @@ -92,104 +92,104 @@ </init-params> </component> </programlisting> - <para> - JBoss Enterprise Portal Platform'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> - <itemizedlist> - <listitem> - <para> - <emphasis role="bold">ReBuilding controller</emphasis> - </para> + <para> + JBoss Enterprise Portal Platform'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> + <itemizedlist> + <listitem> + <para> + <emphasis role="bold">ReBuilding controller</emphasis> + </para> - </listitem> + </listitem> - </itemizedlist> - <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 "portalcontroller" REST name. - </para> - <para> - It provides the following attributes and operations - </para> - <itemizedlist> - <listitem> - <para> - Attribute configurationPath : the read only the configuration path of the controller xml file - </para> + </itemizedlist> + <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 "portalcontroller" REST name. + </para> + <para> + It provides the following attributes and operations + </para> + <itemizedlist> + <listitem> + <para> + Attribute configurationPath: the read only the configuration path of the controller xml file + </para> - </listitem> - <listitem> - <para> - Operation loadConfiguration : load a new configuration file from a specified xml path - </para> + </listitem> + <listitem> + <para> + Operation loadConfiguration: load a new configuration file from a specified xml path + </para> - </listitem> - <listitem> - <para> - Operation reloadConfiguration : reload the configuration file - </para> + </listitem> + <listitem> + <para> + Operation reloadConfiguration: reload the configuration file + </para> - </listitem> - <listitem> - <para> - Operation findRoutes : route the request argument through the controller and returns a list of all parameter map resolution. The argument is a request uri such as "/groups/:platform:administrators/administration/registry". It returns a string representation (<code>List<Map></code>) of the matched routes. - </para> + </listitem> + <listitem> + <para> + Operation findRoutes: route the request argument through the controller and returns a list of all parameter map resolution. The argument is a request uri such as <uri>/g/:platform:administrators/administration/registry</uri>. It returns a string representation (<code>List<Map></code>) of the matched routes. + </para> - </listitem> + </listitem> - </itemizedlist> + </itemizedlist> - </section> - - <section id="sect-Reference_Guide-Controller_in_Action-Controller_Configuration_controller.xml"> - <title>Controller Configuration (controller.xml)</title> - <para> - Most of the controller configuration cares about defining rules (Routing table - contains routes object) that will drive the resolution. Routes are processed during the controller initialization to give a tree of node. Each node - </para> - <itemizedlist> - <listitem> - <para> - is related to its parent with a matching rule that can either be an <emphasis role="bold">exact string matching</emphasis> or a <emphasis role="bold">regular expression matching</emphasis> - </para> + </section> + + <section id="sect-Reference_Guide-Controller_in_Action-Controller_Configuration_controller.xml"> + <title>Controller Configuration (controller.xml)</title> + <para> + Most of the controller configuration cares about defining rules (Routing table - contains routes object) that will drive the resolution. Routes are processed during the controller initialization to give a tree of node. Each node + </para> + <itemizedlist> + <listitem> + <para> + is related to its parent with a matching rule that can either be an <emphasis role="bold">exact string matching</emphasis> or a <emphasis role="bold">regular expression matching</emphasis> + </para> - </listitem> - <listitem> - <para> - is associated with a set of parameters - </para> + </listitem> + <listitem> + <para> + is associated with a set of parameters + </para> - </listitem> + </listitem> - </itemizedlist> - <para> - A parameter is defined by a qualified name and there are three kind of parameters - </para> - <section id="sect-Reference_Guide-Controller_Configuration_controller.xml-_Route_parameters_"> - <title> <emphasis role="bold">Route parameters</emphasis> </title> - <para> - Route parameters defines a fixed value associate with a qualified name. - </para> - <itemizedlist> - <listitem> - <para> - Routing: route parameters allow the controller to distinguish branches easily and route the request accordingly. - </para> + </itemizedlist> + <para> + A parameter is defined by a qualified name and there are three kind of parameters + </para> + <section id="sect-Reference_Guide-Controller_Configuration_controller.xml-_Route_parameters_"> + <title> <emphasis role="bold">Route parameters</emphasis> </title> + <para> + Route parameters defines a fixed value associate with a qualified name. + </para> + <itemizedlist> + <listitem> + <para> + Routing: route parameters allow the controller to distinguish branches easily and route the request accordingly. + </para> - </listitem> - <listitem> - <para> - Rendering: selection occurs when always. - </para> + </listitem> + <listitem> + <para> + Rendering: selection occurs when always. + </para> - </listitem> + </listitem> - </itemizedlist> - <para> - <emphasis role="bold">Example:</emphasis> - </para> - + </itemizedlist> + <para> + <emphasis role="bold">Example:</emphasis> + </para> + <programlisting language="XML"> <route path="/foo"> <route-param qname="gtn:handler"> @@ -197,81 +197,81 @@ </route-param> </route> </programlisting> - <para> - This configuration matches the request path "/foo" to the map (gtn:handler=portal). Conversely it renders the (gtn:handler=portal) map as the "/foo" URL. In this example we see two concepts - </para> - <itemizedlist> - <listitem> - <para> - exact path matching ("/foo") - </para> + <para> + This configuration matches the request path "/foo" to the map (gtn:handler=portal). Conversely it renders the (gtn:handler=portal) map as the "/foo" URL. In this example we see two concepts + </para> + <itemizedlist> + <listitem> + <para> + exact path matching ("/foo") + </para> - </listitem> - <listitem> - <para> - route parameters ("gtn:handler") - </para> + </listitem> + <listitem> + <para> + route parameters ("gtn:handler") + </para> - </listitem> + </listitem> - </itemizedlist> + </itemizedlist> - </section> - - <section id="sect-Reference_Guide-Controller_Configuration_controller.xml-_Path_parameters_Regular_expression_support_"> - <title> <emphasis role="bold">Path parameters - <emphasis role="italic">Regular expression support</emphasis> </emphasis> </title> - <para> - Path parameters allow to associate a portion of the request path with a parameter. Such parameter will match any non empty portion of text except the <emphasis role="bold">/</emphasis> character (that is the [^/]+ regular expression) otherwise they can be associated with a regular expression for matching specific patterns. Path parameters are mandatory for matching since they are part of the request path, however it is allowed to write regular expression matching an empty value. - </para> - <itemizedlist> - <listitem> - <para> - Routing: route is accepted if the regular expression is matched. - </para> + </section> + + <section id="sect-Reference_Guide-Controller_Configuration_controller.xml-_Path_parameters_Regular_expression_support_"> + <title> <emphasis role="bold">Path parameters - <emphasis role="italic">Regular expression support</emphasis> </emphasis> </title> + <para> + Path parameters allow to associate a portion of the request path with a parameter. Such parameter will match any non empty portion of text except the <emphasis role="bold">/</emphasis> character (that is the [^/]+ regular expression) otherwise they can be associated with a regular expression for matching specific patterns. Path parameters are mandatory for matching since they are part of the request path, however it is allowed to write regular expression matching an empty value. + </para> + <itemizedlist> + <listitem> + <para> + Routing: route is accepted if the regular expression is matched. + </para> - </listitem> - <listitem> - <para> - Rendering: selection occurs when the regular expression matches the parameter. - </para> + </listitem> + <listitem> + <para> + Rendering: selection occurs when the regular expression matches the parameter. + </para> - </listitem> + </listitem> - </itemizedlist> - <para> - <emphasis role="bold">Encoding</emphasis> - </para> - <para> - Path parameters may contain '/' character which is a reserved char for URI path. This case is specially handled by the navigation controller by using a special character to replace '/' literals. By default the character is the semi colon <emphasis role="bold">:</emphasis> and can be changed to other possible values (see controller XML schema for possible values) to give a greater amount of flexibility. - </para> - <para> - This encoding is applied only when the encoding performed for parameter having a mode set to the <code>default-form</code> value, for instance it does not happen for navigation node URI (for which <emphasis role="bold">/</emphasis> are encoded literally). The separator escape char can still be used but under it's percent escaped form, so by default a path parameter value containing <emphasis role="bold">:</emphasis> would be encoded as <code>%3A</code> and conversely the <code>%3A</code> value will be decoded as <emphasis role="bold">:</emphasis>. - </para> - <para> - <emphasis role="bold">Example:</emphasis> - </para> - + </itemizedlist> + <para> + <emphasis role="bold">Encoding</emphasis> + </para> + <para> + Path parameters may contain '/' character which is a reserved char for URI path. This case is specially handled by the navigation controller by using a special character to replace '/' literals. By default the character is the semi colon <emphasis role="bold">:</emphasis> and can be changed to other possible values (see controller XML schema for possible values) to give a greater amount of flexibility. + </para> + <para> + This encoding is applied only when the encoding performed for parameter having a mode set to the <code>default-form</code> value, for instance it does not happen for navigation node URI (for which <emphasis role="bold">/</emphasis> are encoded literally). The separator escape char can still be used but under it's percent escaped form, so by default a path parameter value containing <emphasis role="bold">:</emphasis> would be encoded as <code>%3A</code> and conversely the <code>%3A</code> value will be decoded as <emphasis role="bold">:</emphasis>. + </para> + <para> + <emphasis role="bold">Example:</emphasis> + </para> + <programlisting language="XML"> <route path="/{gtn:path}"> </route> </programlisting> - <para> - No pattern defined, used the default one [^/]+ - </para> - + <para> + No pattern defined, used the default one [^/]+ + </para> + <programlisting> Routing and Rendering Path "/foo" <--> the map (gtn:path=foo) Path "/foo:bar" <--> the map (gtn:path=foo/bar) </programlisting> - <para> - If the request path contains another "/" char it will not work,default encoding mode is : <emphasis role="bold">default-form</emphasis>. For example:"/foo/bar" --> not matched, return empty parameter map - </para> - <para> - However this could be solved with the following configuration: - </para> - + <para> + If the request path contains another "/" char it will not work,default encoding mode is: <emphasis role="bold">default-form</emphasis>. For example:"/foo/bar" --> not matched, return empty parameter map + </para> + <para> + However this could be solved with the following configuration: + </para> + <programlisting language="XML"> <route path="/{gtn:path}"> <path-param encoding="preserve-path" qname="gtn:path"> @@ -279,116 +279,116 @@ </path-param> </route> </programlisting> - <orderedlist> - <listitem> - <para> - The .* declaration allows to match any char sequence. - </para> + <orderedlist> + <listitem> + <para> + The .* declaration allows to match any char sequence. + </para> - </listitem> - <listitem> - <para> - The <emphasis role="italic">preserve-path</emphasis> <emphasis role="bold">encoding</emphasis> tells the engine that the "/" chars should be handled by the path parameter itself as they have a special meaning for the router. Without this special encoding, "/" would be rendered as the ":<emphasis role="italic">" character and conversely the ":</emphasis>" character would be matched as the "/" character. - </para> + </listitem> + <listitem> + <para> + The <emphasis role="italic">preserve-path</emphasis> <emphasis role="bold">encoding</emphasis> tells the engine that the "/" chars should be handled by the path parameter itself as they have a special meaning for the router. Without this special encoding, "/" would be rendered as the ":<emphasis role="italic">" character and conversely the ":</emphasis>" character would be matched as the "/" character. + </para> - </listitem> + </listitem> - </orderedlist> + </orderedlist> - </section> - - <section id="sect-Reference_Guide-Controller_Configuration_controller.xml-Request_parameters"> - <title>Request parameters</title> - <para> - Request parameters are matched from the request parameters (GET or POST). The match can be optional as their representation in the request allows it. - </para> - <itemizedlist> - <listitem> - <para> - Routing - </para> - <itemizedlist> - <listitem> - <para> - route is accepted when a required parameter is present and matched in the request. - </para> + </section> + + <section id="sect-Reference_Guide-Controller_Configuration_controller.xml-Request_parameters"> + <title>Request parameters</title> + <para> + Request parameters are matched from the request parameters (GET or POST). The match can be optional as their representation in the request allows it. + </para> + <itemizedlist> + <listitem> + <para> + Routing + </para> + <itemizedlist> + <listitem> + <para> + route is accepted when a required parameter is present and matched in the request. + </para> - </listitem> - <listitem> - <para> - route is accepted when an optional parameter is absent or matched in the request. - </para> + </listitem> + <listitem> + <para> + route is accepted when an optional parameter is absent or matched in the request. + </para> - </listitem> + </listitem> - </itemizedlist> + </itemizedlist> - </listitem> - <listitem> - <para> - Rendering: - </para> - <itemizedlist> - <listitem> - <para> - selection occurs for required parameters when is the parameter is present and matched in the map. - </para> + </listitem> + <listitem> + <para> + Rendering: + </para> + <itemizedlist> + <listitem> + <para> + selection occurs for required parameters when is the parameter is present and matched in the map. + </para> - </listitem> - <listitem> - <para> - selection occurs for optional parameters when is the parameter is absent or matched in the map. - </para> + </listitem> + <listitem> + <para> + selection occurs for optional parameters when is the parameter is absent or matched in the map. + </para> - </listitem> + </listitem> - </itemizedlist> + </itemizedlist> - </listitem> + </listitem> - </itemizedlist> - <para> - <emphasis role="bold">Example:</emphasis> - </para> - + </itemizedlist> + <para> + <emphasis role="bold">Example:</emphasis> + </para> + <programlisting language="XML"> <route path="/"> <request-param name="path" qname="gtn:path"/> </route> </programlisting> - <para> - Request parameters are declared by a <code>request-param</code> element and by default will match any value. A request like "/?path=foo" is mapped to the (gtn:path=foo) map. The <code>name</code> attribute of the <code>request-param</code> tag defines the request parameter value. This element accepts more configuration - </para> - <itemizedlist> - <listitem> - <para> - a <code>value</code> or a <code>pattern</code> element a child element to match a constant or a pattern - </para> + <para> + Request parameters are declared by a <code>request-param</code> element and by default will match any value. A request like "/?path=foo" is mapped to the (gtn:path=foo) map. The <code>name</code> attribute of the <code>request-param</code> tag defines the request parameter value. This element accepts more configuration + </para> + <itemizedlist> + <listitem> + <para> + a <code>value</code> or a <code>pattern</code> element a child element to match a constant or a pattern + </para> - </listitem> - <listitem> - <para> - a <code>control-mode</code> attribute with the value <code>optional</code> or <code>required</code> to indicate if matching is mandatory or not - </para> + </listitem> + <listitem> + <para> + a <code>control-mode</code> attribute with the value <code>optional</code> or <code>required</code> to indicate if matching is mandatory or not + </para> - </listitem> - <listitem> - <para> - a <code>value-mapping</code> attribute with the possible values <code>canonical</code>, <code>never-empty</code>, <code>never-null</code> can be used to filter filter values after matching is done. For instance a parameter configured with <code>value-mapping="never-empty"</code> and matching the empty string value will not put the empty string in the map. - </para> + </listitem> + <listitem> + <para> + a <code>value-mapping</code> attribute with the possible values <code>canonical</code>, <code>never-empty</code>, <code>never-null</code> can be used to filter filter values after matching is done. For instance a parameter configured with <code>value-mapping="never-empty"</code> and matching the empty string value will not put the empty string in the map. + </para> - </listitem> + </listitem> - </itemizedlist> + </itemizedlist> - </section> - - <section id="sect-Reference_Guide-Controller_Configuration_controller.xml-Route_precedence"> - <title>Route precedence</title> - <para> - The order of route declaration is important as it influence how rules are matched. Sometimes the same request could be matched by several routes and the routing table is ambiguous. - </para> - + </section> + + <section id="sect-Reference_Guide-Controller_Configuration_controller.xml-Route_precedence"> + <title>Route precedence</title> + <para> + The order of route declaration is important as it influence how rules are matched. Sometimes the same request could be matched by several routes and the routing table is ambiguous. + </para> + <programlisting language="XML"> <route path="/foo"> <route-param qname="gtn:handler"> @@ -401,33 +401,33 @@ </path-param> </route> </programlisting> - <para> - In that case, the request path "/foo" will always be matched by the first rule before the second rule. This can be misleading since the map (gtn:path=foo) would be rendered as "/foo" as well and would not be matched by the first rule. Such ambiguity can happen, it can be desirable or not. - </para> + <para> + In that case, the request path "/foo" will always be matched by the first rule before the second rule. This can be misleading since the map (gtn:path=foo) would be rendered as "/foo" as well and would not be matched by the first rule. Such ambiguity can happen, it can be desirable or not. + </para> - </section> - - <section id="sect-Reference_Guide-Controller_Configuration_controller.xml-Route_nesting"> - <title>Route nesting</title> - <para> - Route nesting is possible and often desirable as it helps to - </para> - <itemizedlist> - <listitem> - <para> - factor common parameters in a common rule - </para> + </section> + + <section id="sect-Reference_Guide-Controller_Configuration_controller.xml-Route_nesting"> + <title>Route nesting</title> + <para> + Route nesting is possible and often desirable as it helps to + </para> + <itemizedlist> + <listitem> + <para> + factor common parameters in a common rule + </para> - </listitem> - <listitem> - <para> - perform more efficient matching as the match of the common rule is done once for all the sub routes - </para> + </listitem> + <listitem> + <para> + perform more efficient matching as the match of the common rule is done once for all the sub routes + </para> - </listitem> + </listitem> - </itemizedlist> - + </itemizedlist> + <programlisting language="XML"> <route path="/foo"> <route-param qname="gtn:handler"> @@ -445,231 +445,231 @@ </route> </route> </programlisting> - <itemizedlist> - <listitem> - <para> - The request path "/foo/bar" is mapped to the (gtn:handler=portal,gtn:path=bar) map - </para> + <itemizedlist> + <listitem> + <para> + The request path "/foo/bar" is mapped to the (gtn:handler=portal,gtn:path=bar) map + </para> - </listitem> - <listitem> - <para> - The request path "/foo/juu" is mapped to the (gtn:handler=portal,gtn:path=juu) map - </para> + </listitem> + <listitem> + <para> + The request path "/foo/juu" is mapped to the (gtn:handler=portal,gtn:path=juu) map + </para> - </listitem> - <listitem> - <para> - The request path "/foo" is not mapped as non leaf routes do not perform matches. - </para> + </listitem> + <listitem> + <para> + The request path "/foo" is not mapped as non leaf routes do not perform matches. + </para> - </listitem> + </listitem> - </itemizedlist> + </itemizedlist> - </section> - + </section> + - </section> - + </section> + - </section> - - <section id="sect-Reference_Guide-Navigation_Controller_-Integrate_to_JBoss_Enterprise_Portal_Platform_WebUI_framework"> - <title>Integrate to JBoss Enterprise Portal Platform WebUI framework</title> - <section id="sect-Reference_Guide-Integrate_to_JBoss_Enterprise_Portal_Platform_WebUI_framework-Routing"> - <title>Routing</title> - <para> - JBoss Enterprise Portal Platform defines a set of parameters in its routing table, for each client request, the mapping engine processes the request path and return the defined parameters with their values as a Map<QualifiedName, String> - </para> - <para> - <emphasis role="bold">gtn:handler</emphasis> - </para> - <para> - The gtn:handler names is one of the most important qualified name as it determines which handler will take care of the request processing just after the controller has determined the parameter map. The handler value is used to make a lookup in the handler map of the controller. An handler is a class that extends the <code>WebRequestHandler</code> class and implements the <code>execute(ControllerContext)</code> method. Several handlers are available by default: - </para> - <itemizedlist> - <listitem> - <para> - portal : process aggregated portal requests - </para> + </section> + + <section id="sect-Reference_Guide-Navigation_Controller_-Integrate_to_JBoss_Enterprise_Portal_Platform_WebUI_framework"> + <title>Integrate to JBoss Enterprise Portal Platform WebUI framework</title> + <section id="sect-Reference_Guide-Integrate_to_JBoss_Enterprise_Portal_Platform_WebUI_framework-Routing"> + <title>Routing</title> + <para> + JBoss Enterprise Portal Platform defines a set of parameters in its routing table, for each client request, the mapping engine processes the request path and return the defined parameters with their values as a Map<QualifiedName, String> + </para> + <para> + <emphasis role="bold">gtn:handler</emphasis> + </para> + <para> + The gtn:handler names is one of the most important qualified name as it determines which handler will take care of the request processing just after the controller has determined the parameter map. The handler value is used to make a lookup in the handler map of the controller. An handler is a class that extends the <code>WebRequestHandler</code> class and implements the <code>execute(ControllerContext)</code> method. Several handlers are available by default: + </para> + <itemizedlist> + <listitem> + <para> + portal: process aggregated portal requests + </para> - </listitem> - <listitem> - <para> - upload / download : process file upload and file download - </para> + </listitem> + <listitem> + <para> + upload / download: process file upload and file download + </para> - </listitem> - <listitem> - <para> - legacy : handle legacy URL redirection (see <emphasis role="bold">Legacy handler</emphasis> section) - </para> + </listitem> + <listitem> + <para> + legacy: handle legacy URL redirection (see <emphasis role="bold">Legacy handler</emphasis> section) + </para> - </listitem> - <listitem> - <para> - default : <literal>http</literal> redirection to the default portal of the container - </para> + </listitem> + <listitem> + <para> + default: <literal>http</literal> redirection to the default portal of the container + </para> - </listitem> - <listitem> - <para> - staticResource: serve static resources like image, css or javascript... files in portal.war (see <emphasis role="bold">Static Resource Handler</emphasis> section) - </para> + </listitem> + <listitem> + <para> + staticResource: serve static resources like image, css or javascript... files in portal.war (see <emphasis role="bold">Static Resource Handler</emphasis> section) + </para> - </listitem> + </listitem> - </itemizedlist> - <para> - <emphasis role="bold">gtn:sitetype / gtn:sitename / gtn:path</emphasis> - </para> - <para> - Those qualified names drives a request for the portal handler. They are used to determine which site to show and which path to resolve against a navigation. For instance the (gtn:sitetype=portal,gtn:sitename=classic,gtn:path=home) instruct the portal handler to show the home page of the classic portal site. - </para> - <para> - <emphasis role="bold">gtn:lang</emphasis> - </para> - <para> - The language in the URL for the portal handler. This is a new feature offered, now language can be specified on URL. that mean user can bookmark that URL (with the information about language) or he can changed language simply by modifying the URL address - </para> - <para> - <emphasis role="bold">gtn:componentid / gtn:action / gtn:objectid</emphasis> - </para> - <para> - The webui parameters used by the portal handler for managing webui component URLs for portal applications (and not for portlet applications). - </para> + </itemizedlist> + <para> + <emphasis role="bold">gtn:sitetype / gtn:sitename / gtn:path</emphasis> + </para> + <para> + Those qualified names drives a request for the portal handler. They are used to determine which site to show and which path to resolve against a navigation. For instance the (gtn:sitetype=portal,gtn:sitename=classic,gtn:path=home) instruct the portal handler to show the home page of the classic portal site. + </para> + <para> + <emphasis role="bold">gtn:lang</emphasis> + </para> + <para> + The language in the URL for the portal handler. This is a new feature offered, now language can be specified on URL. that mean user can bookmark that URL (with the information about language) or he can changed language simply by modifying the URL address + </para> + <para> + <emphasis role="bold">gtn:componentid / gtn:action / gtn:objectid</emphasis> + </para> + <para> + The webui parameters used by the portal handler for managing webui component URLs for portal applications (and not for portlet applications). + </para> - </section> - - <section id="sect-Reference_Guide-Integrate_to_JBoss_Enterprise_Portal_Platform_WebUI_framework-Rendering"> - <title>Rendering</title> - <para> - The <emphasis role="bold">controller</emphasis> is designed to render a Map<QualifiedName, String> as an <literal>http</literal> URL according to its routing table. But to integrate it for using easily in WebUI Framework of JBoss Enterprise Portal Platform, we need some more components - </para> - <section id="sect-Reference_Guide-Rendering-_PortalURL_"> - <title> <emphasis role="bold">PortalURL</emphasis> </title> - <para> - <code>PortalURL</code> play a similar role at the portal level, its main role is to abstract the creation of an URL for a resource managed by the portal. - </para> - + </section> + + <section id="sect-Reference_Guide-Integrate_to_JBoss_Enterprise_Portal_Platform_WebUI_framework-Rendering"> + <title>Rendering</title> + <para> + The <emphasis role="bold">controller</emphasis> is designed to render a Map<QualifiedName, String> as an <literal>http</literal> URL according to its routing table. But to integrate it for using easily in WebUI Framework of JBoss Enterprise Portal Platform, we need some more components + </para> + <section id="sect-Reference_Guide-Rendering-_PortalURL_"> + <title> <emphasis role="bold">PortalURL</emphasis> </title> + <para> + <code>PortalURL</code> play a similar role at the portal level, its main role is to abstract the creation of an URL for a resource managed by the portal. + </para> + <programlisting language="Java"> public abstract class PortalURL<R, U extends PortalURL<U>> { ... } </programlisting> - <para> - The <code>PortalURL</code> declaration may seem a bit strange at first sight with two generic types <code>U</code> and <code>R</code> and the circular recursion of the <code>U</code> generic parameter, but it's because most of the time you will not use the <code>PortalURL</code> object but instead subclasses. - </para> - <itemizedlist> - <listitem> - <para> - The <code>R</code> generic type represents the type of the resource managed by the portal - </para> + <para> + The <code>PortalURL</code> declaration may seem a bit strange at first sight with two generic types <code>U</code> and <code>R</code> and the circular recursion of the <code>U</code> generic parameter, but it's because most of the time you will not use the <code>PortalURL</code> object but instead subclasses. + </para> + <itemizedlist> + <listitem> + <para> + The <code>R</code> generic type represents the type of the resource managed by the portal + </para> - </listitem> - <listitem> - <para> - The <code>U</code> generic type is also described as <emphasis role="bold">self bound generic type</emphasis>. This design pattern allows a class to return subtypes of itself in the class declaring the generic type. Java Enums are based on this principle (<code>class Enum<E extends Enum<E>></code>) - </para> + </listitem> + <listitem> + <para> + The <code>U</code> generic type is also described as <emphasis role="bold">self bound generic type</emphasis>. This design pattern allows a class to return subtypes of itself in the class declaring the generic type. Java Enums are based on this principle (<code>class Enum<E extends Enum<E>></code>) + </para> - </listitem> + </listitem> - </itemizedlist> - <para> - A portal URL has various methods but certainly the most important method is the <code>toString()</code> method that generates an URL representing that will target the resource associated with the URL. The remaining methods are getter and setter for mutating the URL configuration, those options will affect the URL representation when it is generated. - </para> - <itemizedlist> - <listitem> - <para> - resource : the mandatory resource associated with the URL - </para> + </itemizedlist> + <para> + A portal URL has various methods but certainly the most important method is the <code>toString()</code> method that generates an URL representing that will target the resource associated with the URL. The remaining methods are getter and setter for mutating the URL configuration, those options will affect the URL representation when it is generated. + </para> + <itemizedlist> + <listitem> + <para> + resource: the mandatory resource associated with the URL + </para> - </listitem> - <listitem> - <para> - locale : the optional locale used in the URL allowing the creation of bookmarkable URL containing a language - </para> + </listitem> + <listitem> + <para> + locale: the optional locale used in the URL allowing the creation of bookmarkable URL containing a language + </para> - </listitem> - <listitem> - <para> - confirm : the optional confirm message displayed by the portal in the context of the portal UI - </para> + </listitem> + <listitem> + <para> + confirm: the optional confirm message displayed by the portal in the context of the portal UI + </para> - </listitem> - <listitem> - <para> - ajax : the optional ajax option allowing an ajax invocation of the URL - </para> + </listitem> + <listitem> + <para> + ajax: the optional ajax option allowing an ajax invocation of the URL + </para> - </listitem> + </listitem> - </itemizedlist> - <para> - <emphasis role="bold">Obtaining a PortalURL</emphasis> - </para> - <para> - <code>PortalURL</code> objects are obtained from <code>RequestContext</code> instance such as the <code>PortalRequestContext</code> or the PortletRequestContext. Usually those are obtained thanks to <code>getCurrentInstance</code> method of the <code>RequestContext</code> class: - </para> - + </itemizedlist> + <para> + <emphasis role="bold">Obtaining a PortalURL</emphasis> + </para> + <para> + <code>PortalURL</code> objects are obtained from <code>RequestContext</code> instance such as the <code>PortalRequestContext</code> or the PortletRequestContext. Usually those are obtained thanks to <code>getCurrentInstance</code> method of the <code>RequestContext</code> class: + </para> + <programlisting language="Java"> RequestContext ctx = RequestContext.getCurrentInstance(); </programlisting> - <para> - <code>PortalURL</code> are created via to the <code>createURL</code> method that takes as input a resource type. A resource type is usually a constant and is a type safe object that allow to retrieve <code>PortalURL</code> subclasses: - </para> - + <para> + <code>PortalURL</code> are created via to the <code>createURL</code> method that takes as input a resource type. A resource type is usually a constant and is a type safe object that allow to retrieve <code>PortalURL</code> subclasses: + </para> + <programlisting language="Java"> RequestContext ctx = RequestContext.getCurrentInstance(); PortalURL<R, U> URL = ctx.createURL(type); </programlisting> - <para> - In reality you will use a concrete type constant and have instead more concrete code like: - </para> - + <para> + In reality you will use a concrete type constant and have instead more concrete code like: + </para> + <programlisting language="Java"> RequestContext ctx = RequestContext.getCurrentInstance(); NodeURL URL = ctx.createURL(NodeURL.TYPE); </programlisting> - <note> - <para> - The <code>NodeURL.TYPE</code> is actually declared as <code>new ResourceType<NavigationResource, NodeURL>()</code> that can be described as a <emphasis role="bold">type literal</emphasis> object emulated by a Java anonymous inner class. Such literal were introduced by Neil Gafter as Super Type Token and popularized by Google Guice as Type Literal. It's an interesting way to create a literal representing a kind of Java type. - </para> + <note> + <para> + The <code>NodeURL.TYPE</code> is actually declared as <code>new ResourceType<NavigationResource, NodeURL>()</code> that can be described as a <emphasis role="bold">type literal</emphasis> object emulated by a Java anonymous inner class. Such literal were introduced by Neil Gafter as Super Type Token and popularized by Google Guice as Type Literal. It's an interesting way to create a literal representing a kind of Java type. + </para> - </note> + </note> - </section> - - <section id="sect-Reference_Guide-Rendering-_Node_URL_"> - <title> <emphasis role="bold">Node URL</emphasis> </title> - <para> - The class <code>NodeURL</code> is one of the subclass of <code>PortalURL</code> that is specialized for navigation node resources: - </para> - + </section> + + <section id="sect-Reference_Guide-Rendering-_Node_URL_"> + <title> <emphasis role="bold">Node URL</emphasis> </title> + <para> + The class <code>NodeURL</code> is one of the subclass of <code>PortalURL</code> that is specialized for navigation node resources: + </para> + <programlisting language="Java"> public class NodeURL extends PortalURL<NavigationResource, NodeURL> { ... } </programlisting> - <para> - The good news is that the NodeURL does not carry any generic type of its super class, which means that a NodeURL is type safe and one does not have to worry about generic types. - </para> - <para> - Using a NodeURL is pretty straightforward: - </para> - + <para> + The good news is that the NodeURL does not carry any generic type of its super class, which means that a NodeURL is type safe and one does not have to worry about generic types. + </para> + <para> + Using a NodeURL is pretty straightforward: + </para> + <programlisting language="Java"> NodeURL URL = RequestContext.getCurrentInstance().createURL(NodeURL.TYPE); URL.setResource(new NavigationResource("portal", "classic, "home")); String s = URL.toString(); </programlisting> - <para> - The <code>NodeURL</code> subclass contains specialized setter to make its usage even easier: - </para> - + <para> + The <code>NodeURL</code> subclass contains specialized setter to make its usage even easier: + </para> + <programlisting language="Java"> UserNode node = ...; NodeURL URL = RequestContext.getCurrentInstance().createURL(NodeURL.TYPE); @@ -677,98 +677,98 @@ String s = URL.toString(); </programlisting> - </section> - - <section id="sect-Reference_Guide-Rendering-_Component_URL_"> - <title> <emphasis role="bold">Component URL</emphasis> </title> - <para> - The <code>ComponentURL</code> subclass is another specialization of <code>PortalURL</code> that allows the creation of WebUI components URLs. <code>ComponentURL</code> is commonly used to trigger WebUI events from client side: - </para> - + </section> + + <section id="sect-Reference_Guide-Rendering-_Component_URL_"> + <title> <emphasis role="bold">Component URL</emphasis> </title> + <para> + The <code>ComponentURL</code> subclass is another specialization of <code>PortalURL</code> that allows the creation of WebUI components URLs. <code>ComponentURL</code> is commonly used to trigger WebUI events from client side: + </para> + <programlisting> <% def componentURL = uicomponent.event(...); /*or uicomponent.URL(...) */ %> <a href=$componentURL>Click me</a> </programlisting> - <para> - Normally you should not have to deal with it as the WebUI framework has already an abstraction for managing URL known as <code>URLBuilder</code>. The <code>URLBuilder</code> implementation delegates URL creation to <code>ComponentURL</code> objects. - </para> + <para> + Normally you should not have to deal with it as the WebUI framework has already an abstraction for managing URL known as <code>URLBuilder</code>. The <code>URLBuilder</code> implementation delegates URL creation to <code>ComponentURL</code> objects. + </para> - </section> - - <section id="sect-Reference_Guide-Rendering-Portlet_URLs"> - <title>Portlet URLs</title> - <para> - Portlet URLs API implementation delegates to the portal <code>ComponentURL</code> (via the portlet container SPI). It is possible to control the language in the URL from a <code>PortletURL</code> object by setting a property named <code>gtn:lang</code>: - </para> - <itemizedlist> - <listitem> - <para> - when the property value is set to a value returned by <code>Locale#toString()</code> method for locale objects having a non null language value and a null variant value, the URL generated by the <code>PortletURL#toString()</code> method will contain the locale in the URL. - </para> + </section> + + <section id="sect-Reference_Guide-Rendering-Portlet_URLs"> + <title>Portlet URLs</title> + <para> + Portlet URLs API implementation delegates to the portal <code>ComponentURL</code> (via the portlet container SPI). It is possible to control the language in the URL from a <code>PortletURL</code> object by setting a property named <code>gtn:lang</code>: + </para> + <itemizedlist> + <listitem> + <para> + when the property value is set to a value returned by <code>Locale#toString()</code> method for locale objects having a non null language value and a null variant value, the URL generated by the <code>PortletURL#toString()</code> method will contain the locale in the URL. + </para> - </listitem> - <listitem> - <para> - when the property value is set to an empty string, the generated URL will not contain a language. If the incoming URL was carrying a language, this language will be erased. - </para> + </listitem> + <listitem> + <para> + when the property value is set to an empty string, the generated URL will not contain a language. If the incoming URL was carrying a language, this language will be erased. + </para> - </listitem> - <listitem> - <para> - when the property value is not set, it will not affect the generated URL. - </para> + </listitem> + <listitem> + <para> + when the property value is not set, it will not affect the generated URL. + </para> - </listitem> + </listitem> - </itemizedlist> - + </itemizedlist> + <programlisting language="Java"> PortletURL URL = resp.createRenderURL(); URL.setProperty("gtn:lang", "fr"); writer.print("<a href='" + URL + "'>French</a>"); </programlisting> - </section> - - <section id="sect-Reference_Guide-Rendering-Webui_URLBuilder_"> - <title>Webui <code>URLBuilder</code> </title> - <para> - This internal API for creating URL works as before and delegates to the <code>PortletURL</code> API when the framework is executed in a portlet and to a <code>ComponentURL</code> API when the framework is executed in the portal context. The API has been modified to take in account the language in URL with two properties on the builder: - </para> - <itemizedlist> - <listitem> - <para> - locale : a locale for setting on the URL - </para> + </section> + + <section id="sect-Reference_Guide-Rendering-Webui_URLBuilder_"> + <title>Webui <code>URLBuilder</code> </title> + <para> + This internal API for creating URL works as before and delegates to the <code>PortletURL</code> API when the framework is executed in a portlet and to a <code>ComponentURL</code> API when the framework is executed in the portal context. The API has been modified to take in account the language in URL with two properties on the builder: + </para> + <itemizedlist> + <listitem> + <para> + locale: a locale for setting on the URL + </para> - </listitem> - <listitem> - <para> - removeLocale : a boolean for removing the locale present on the URL - </para> + </listitem> + <listitem> + <para> + removeLocale: a boolean for removing the locale present on the URL + </para> - </listitem> + </listitem> - </itemizedlist> + </itemizedlist> - </section> - - <section id="sect-Reference_Guide-Rendering-Groovy_Templates"> - <title>Groovy Templates</title> - <para> - Within a Groovy template the mechanism is the same, however a splash of integration has been done to make creation of NodeURL simpler. A closure is bound under the <code>nodeurl</code> name and is available for invocation anytime. It will simply create a NodeURL object and return it: - </para> - + </section> + + <section id="sect-Reference_Guide-Rendering-Groovy_Templates"> + <title>Groovy Templates</title> + <para> + Within a Groovy template the mechanism is the same, however a splash of integration has been done to make creation of NodeURL simpler. A closure is bound under the <code>nodeurl</code> name and is available for invocation anytime. It will simply create a NodeURL object and return it: + </para> + <programlisting language="Java"> UserNode node = ...; NodeURL URL = nodeurl(); URL.setNode(node); String s = URL.toString(); </programlisting> - <para> - The closure <code>nodeurl</code> is bound to Groovy template in <code>WebuiBindingContext</code> - </para> - + <para> + The closure <code>nodeurl</code> is bound to Groovy template in <code>WebuiBindingContext</code> + </para> + <programlisting language="Java"> // Closure nodeurl() put("nodeurl", new Closure(this) @@ -781,15 +781,15 @@ }); </programlisting> - </section> - + </section> + - </section> - + </section> + - </section> - -  <section id="sect-Reference_Guide-Portal_Life_cycle-The_Command_Servlet"> - <title>The Command Servlet</title> - <para> - The CommandServlet is called by the portlet container for requests to particular portlets, it also includes some <literal>init</literal> code when the portal is launched. This servlet (<literal>org.gatein.wci.command.CommandServlet</literal>) is automatically added during the deployment of each portlet application and mapped to <literal>/gateinservlet</literal>. - </para> - <para> - This is equivalent to adding the following into <filename>web.xml</filename>. - </para> - <note> - <title>Servlet Configuration</title> - <para> - <emphasis role="bold">As the servlet is already configured this example is for information only.</emphasis> - </para> + <title>The Command Servlet</title> + <para> + The CommandServlet is called by the portlet container for requests to particular portlets, it also includes some <literal>init</literal> code when the portal is launched. This servlet (<literal>org.gatein.wci.api.GateInServlet</literal>) is automatically added during the deployment of each portlet application and mapped to <literal>/gateinservlet</literal>. + </para> + <para> + This is equivalent to adding the following into <filename>web.xml</filename>. + </para> + <note> + <title>Servlet Configuration</title> + <para> + <emphasis role="bold">As the servlet is already configured this example is for information only.</emphasis> + </para> - </note> - + </note> + <programlisting language="XML" role="XML"><xi:include href="../../extras/PortalDevelopment_PortalLifecycle/default160.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> -  <para> - It is possible to filter on the <literal>CommandServlet</literal> by filtering the URL pattern used by the servlet mapping. - </para> - <para> - The example below would create a servlet filter that calculates the time of execution of a portlet request. - </para> - <para> - The filter class: - </para> - + It is possible to filter on the <literal>GateInServlet</literal> by filtering the URL pattern used by the servlet mapping. + </para> + <para> + The example below would create a servlet filter that calculates the time of execution of a portlet request. + </para> + <para> + The filter class: + </para> + <programlisting language="Java" role="Java"><xi:include href="../../extras/PortalDevelopment_PortalLifecycle/MyFilter.java" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> -  <para> - The Java EE web application configuration file (<filename>web.xml</filename>) of the portlet is the file on which we want to know the time to serve a portlet request. - </para> - <para> - As mentioned above nothing specific to JBoss Enterprise Portal Platform needs to be included, only the URL pattern to set has to be known. - </para> - + The Java EE web application configuration file (<filename>web.xml</filename>) of the portlet is the file on which we want to know the time to serve a portlet request. + </para> + <para> + As mentioned above nothing specific to JBoss Enterprise Portal Platform needs to be included, only the URL pattern to set has to be known. + </para> + <programlisting language="XML" role="XML"><xi:include href="../../extras/PortalDevelopment_PortalLifecycle/default161.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> -  <para> - <note> - <title>INCLUDE dispatcher</title> - <para> - It is important to set <literal>INCLUDE</literal> as dispatcher as the portal will always hit the <literal>CommandServlet</literal> through a request dispatcher. Without this, the filter will not be triggered, unless direct access to a resource (such as an image) is set. - </para> + <note> + <title>INCLUDE dispatcher</title> + <para> + It is important to set <literal>INCLUDE</literal> as dispatcher as the portal will always hit the <literal>GateInServlet</literal> through a request dispatcher. Without this, the filter will not be triggered, unless direct access to a resource (such as an image) is set. + </para> - </note> + </note> - </para> + </para> - </section> - -  </chapter> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment.xml 2011-12-05 03:51:59 UTC (rev 8190) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment.xml 2011-12-05 04:33:56 UTC (rev 8191) @@ -4,18 +4,20 @@ %BOOK_ENTITIES; ]> <part id="part-Reference_Guide-Portal_Development"> - <title>Portal Development</title> - <xi:include href="PortalDevelopment/Skinning.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="PortalDevelopment/PortalLifecycle.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="PortalDevelopment/DefaultPortalConfiguration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="PortalDevelopment/DefaultPortalPermissionConfiguration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="PortalDevelopment/DefaultPortalNavigationConfiguration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="PortalDevelopment/DataImportStrategy.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="PortalDevelopment/InternationalizationConfiguration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="PortalDevelopment/LocalizationConfiguration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="PortalDevelopment/RTLFramework.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="PortalDevelopment/XMLResourceBundles.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="PortalDevelopment/JavascriptInterApplicationCommunication.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -   <xi:include href="PortalDevelopment/NavigationController.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <title>Portal Development</title> + <xi:include href="PortalDevelopment/Skinning.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="PortalDevelopment/PortalLifecycle.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="PortalDevelopment/DefaultPortalConfiguration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="PortalDevelopment/DefaultPortalPermissionConfiguration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="PortalDevelopment/DefaultPortalNavigationConfiguration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="PortalDevelopment/DataImportStrategy.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="PortalDevelopment/InternationalizationConfiguration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="PortalDevelopment/LocalizationConfiguration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="PortalDevelopment/XMLResourceBundles.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="PortalDevelopment/RTLFramework.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="PortalDevelopment/JavascriptInterApplicationCommunication.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> +  +  + <xi:include href="PortalDevelopment/NavigationController.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> </part> 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 2011-12-05 03:51:59 UTC (rev 8190) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/WSRP.xml 2011-12-05 04:33:56 UTC (rev 8191) @@ -4,7 +4,7 @@ %BOOK_ENTITIES; ]> <chapter id="wsrp"> - <title><remark>Web Services for Remote Portlets (WSRP)</remark></title> + <title><remark>Web Services for Remote Portlets (WSRP)</remark></title> <section> <title>Introduction</title> @@ -135,7 +135,7 @@ </para> <para> - Of course, if you have modified you have modified the host name and port on which your server runs, you will need to update the configuration for the consumer used to consume JBoss Enterprise Portal Platform's 'self' producer. Please refer to the <xref linkend="consumer_configuration"/> to learn how to do so. + Of course, if you have modified the host name and port on which your server runs, you will need to update the configuration for the consumer used to consume JBoss Enterprise Portal Platform's 'self' producer. Please refer to the <xref linkend="consumer_configuration"/> to learn how to do so. </para> </section> </section> @@ -194,7 +194,7 @@ <title>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 indepth configuration options. Please note that since the consumer passes its credentials to the producer, the consumer will act at the wss client and the producer will act as the wss server. + 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 indepth 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. </para> <para> @@ -265,25 +265,25 @@ <itemizedlist> <listitem> <para> - The JBossWS configuration files must be configured + The JBossWS configuration files must be configured. </para> </listitem> <listitem> <para> - The filter must be added to the portal's web.xml + The filter must be added to the portal's web.xml. </para> </listitem> <listitem> <para> - the enable wss feature must be check in the wsrp admin + 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 + The consumer will not properly handle ws-security unless all 3 are properly configured. </para> </section> </section> @@ -332,7 +332,7 @@ </example> <para> - It is also possible to specify that all the portlets declared within a given portlet application to be remotable by default. This is done by specifying the <code> container-runtime-option </code> at the <code>portlet-app</code> element level. Individual portlets can override that value to not be remotely exposed. Let's look at an example: + It is also possible to specify that all the portlets declared within a given portlet application to be remotable by default. This is done by specifying the <code>container-runtime-option</code> at the <code>portlet-app</code> element level. Individual portlets can override that value to not be remotely exposed. Let's look at an example: </para> <example> @@ -370,15 +370,7 @@ </example> <para> - In the example above, we defined two portlets. The <code>org.gatein.pc.remotable container-runtime-option</code> being set to <code>true</code> at the <code>portlet-app</code> level, all portlets defined in this particular portlet application are exposed remotely by JBoss Enterprise Portal Platform's WSRP producer. Note, however, that it is possible to override the default behavior: specifying a value for the <code>org.gatein.pc.remotable container-runtime-option</code> at the <code>portlet</code> level will take precedence over the default. In the example above, the - <varname> - RemotelyExposedPortlet - </varname> - inherits the remotable status defined at the <code>portlet-app</code> level since it does not specify a value for the<code>org.gatein.pc.remotable container-runtime-option</code>. The - <varname> - NotRemotelyExposedPortlet - </varname> - , however, overrides the default behavior and is not remotely exposed. Note that in the absence of a top-level <code>org.gatein.pc.remotable container-runtime-option</code> value set to<code>true</code>, portlets are NOT remotely exposed. + In the example above, we defined two portlets. The <code>org.gatein.pc.remotable container-runtime-option</code> being set to <code>true</code> at the <code>portlet-app</code> level, all portlets defined in this particular portlet application are exposed remotely by JBoss Enterprise Portal Platform's WSRP producer. Note, however, that it is possible to override the default behavior: specifying a value for the <code>org.gatein.pc.remotable container-runtime-option</code> at the <code>portlet</code> level will take precedence over the default. In the example above, the <varname>RemotelyExposedPortlet</varname> inherits the remotable status defined at the <code>portlet-app</code> level since it does not specify a value for the <code>org.gatein.pc.remotable container-runtime-option</code>. The <varname>NotRemotelyExposedPortlet</varname>, however, overrides the default behavior and is not remotely exposed. Note that in the absence of a top-level <code>org.gatein.pc.! remotable container-runtime-option</code> value set to <code>true</code>, portlets are NOT remotely exposed. </para> </section> @@ -423,7 +415,7 @@ </note> <para> - JBoss Enterprise Portal Platform provides a portlet to configure access (among other functions) to remote WSRP Producers grahically. Starting with &VY;, the WSRP configuration portlet is installed by default. You can find it at <ulink + JBoss Enterprise Portal Platform provides a portlet to configure access (among other functions) to remote WSRP Producers graphically. Starting with &VY;, the WSRP configuration portlet is installed by default. You can find it at <ulink url="http://localhost:8080/portal/login?initialURI=%2Fportal%2Fprivate%2Fclass..."> http://localhost:8080/portal/login?initialURI=%2Fportal%2Fprivate%2Fclass... </ulink> </para> @@ -491,7 +483,7 @@ </para> <para> - If we had been dealing with a producer which required registration but didn't require any registration properties, as is the case for the <literal>selfv2</literal> consumer (the consumer that accesses the portlets made remotely available by JBoss Enterprise Portal Platform's producer via WSRP 2), we'd have seen something similar to, after pressing the "Refresh & Save" button: + If we had been dealing with a producer which required registration but didn't require any registration properties, as is the case for the <literal>selfv2</literal> consumer (the consumer that accesses the portlets made remotely available by JBoss Enterprise Portal Platform's producer via WSRP 2), we'd have seen something similar to the screenshot below, after pressing the "Refresh & Save" button: <mediaobject> <imageobject> <imagedata fileref="images/WSRP/config_refresh.png" format="PNG" align="center" valign="middle" @@ -706,7 +698,7 @@ </para> <note> - <title>Note</title> + <title>Note</title> <para> For remote portlets published by JBoss Enterprise Portal Platform's WSRP producer, the portlet handles are, at the time of this writing, following the <literal>/<portlet application name>.<portlet name></literal> format. </para> @@ -720,7 +712,7 @@ </para> <example> - <title>Example</title> + <title>Example</title> <para> <programlisting><![CDATA[ <page> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/backup/exojcr-backup-service.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/backup/exojcr-backup-service.xml 2011-12-05 03:51:59 UTC (rev 8190) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/backup/exojcr-backup-service.xml 2011-12-05 04:33:56 UTC (rev 8191) @@ -78,7 +78,7 @@ Restoring an incremental backup consists in applying the collected set of ChangesLogs to a workspace in the correct order. </para> <note> - <title></title> + <title>Note</title> <para> Incremental backup is an experimental feature and not supported. Please use it with caution. </para> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/nodetype-registration.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/nodetype-registration.xml 2011-12-05 03:51:59 UTC (rev 8190) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/nodetype-registration.xml 2011-12-05 04:33:56 UTC (rev 8191) @@ -4,33 +4,33 @@ %BOOK_ENTITIES; ]> <chapter id="chap-Reference_Guide-NodeType_Registration"> -  <title>NodeType Registration</title> - <para> - The eXo JCR implementation supports two methods of Nodetypes registration: - </para> - <itemizedlist> - <listitem> - <para> - From a <literal>NodeTypeValue</literal> POJO. Refer to <xref linkend="exam-Reference_Guide-Node_type_registration-Run_time_registration_using_NodeTypeValue" /> - </para> +  <title>NodeType Registration</title> + <para> + The eXo JCR implementation supports two methods of Nodetypes registration: + </para> + <itemizedlist> + <listitem> + <para> + From a <literal>NodeTypeValue</literal> POJO. Refer to <xref linkend="exam-Reference_Guide-Node_type_registration-Run_time_registration_using_NodeTypeValue" /> + </para> - </listitem> - <listitem> - <para> - From an XML document. Refer to <xref linkend="exam-Reference_Guide-Node_type_registration-Runtime_Registration_From_XML_File" />. - </para> + </listitem> + <listitem> + <para> + From an XML document. Refer to <xref linkend="exam-Reference_Guide-Node_type_registration-Runtime_Registration_From_XML_File" />. + </para> - </listitem> + </listitem> - </itemizedlist> - <section id="sect-Reference_Guide-NodeType_Registration-Interfaces_and_methods"> - <title>Interfaces and methods</title> - <section id="sect-Reference_Guide-Interfaces_and_methods-ExtendedNodeTypeManager"> - <title><literal>ExtendedNodeTypeManager</literal></title> - <para> - The <literal>ExtendedNodeTypeManager</literal> (from JCR 1.11) interface provides the following methods related to registering node types: - </para> - + </itemizedlist> + <section id="sect-Reference_Guide-NodeType_Registration-Interfaces_and_methods"> + <title>Interfaces and methods</title> + <section id="sect-Reference_Guide-Interfaces_and_methods-ExtendedNodeTypeManager"> + <title><literal>ExtendedNodeTypeManager</literal></title> + <para> + The <literal>ExtendedNodeTypeManager</literal> (from JCR 1.11) interface provides the following methods related to registering node types: + </para> + <programlisting language="Java" role="Java">public static final int IGNORE_IF_EXISTS = 0; public static final int FAIL_IF_EXISTS = 2; @@ -78,14 +78,14 @@ NoSuchNodeTypeException, RepositoryException;</programlisting> - </section> - - <section id="sect-Reference_Guide-Interfaces_and_methods-NodeTypeValue"> - <title><literal>NodeTypeValue</literal></title> - <para> - The NodeTypeValue interface represents a simple container structure used to define node types which are then registered through the ExtendedNodeTypeManager.registerNodeType method. The implementation of this interface does not contain any validation logic. - </para> - + </section> + + <section id="sect-Reference_Guide-Interfaces_and_methods-NodeTypeValue"> + <title><literal>NodeTypeValue</literal></title> + <para> + The NodeTypeValue interface represents a simple container structure used to define node types which are then registered through the ExtendedNodeTypeManager.registerNodeType method. The implementation of this interface does not contain any validation logic. + </para> + <programlisting language="Java" role="Java">/** * @return Returns the declaredSupertypeNames. */ @@ -163,14 +163,14 @@ */ public void setDeclaredPropertyDefinitionValues(List<PropertyDefinitionValue> declaredPropertyDefinitionValues);</programlisting> - </section> - - <section id="sect-Reference_Guide-Interfaces_and_methods-NodeDefinitionValue"> - <title><literal>NodeDefinitionValue</literal></title> - <para> - The <literal>NodeDefinitionValue</literal> interface extends <literal>ItemDefinitionValue</literal> with the addition of writing methods, enabling the characteristics of a child node definition to be set, after that the <literal>NodeDefinitionValue</literal> is added to a <literal>NodeTypeValue</literal>. - </para> - + </section> + + <section id="sect-Reference_Guide-Interfaces_and_methods-NodeDefinitionValue"> + <title><literal>NodeDefinitionValue</literal></title> + <para> + The <literal>NodeDefinitionValue</literal> interface extends <literal>ItemDefinitionValue</literal> with the addition of writing methods, enabling the characteristics of a child node definition to be set, after that the <literal>NodeDefinitionValue</literal> is added to a <literal>NodeTypeValue</literal>. + </para> + <programlisting language="Java" role="Java">/** * @return Returns the declaredSupertypeNames. */ @@ -250,16 +250,16 @@ </programlisting> - </section> - - <section id="sect-Reference_Guide-Interfaces_and_methods-PropertyDefinitionValue"> - <title><literal>PropertyDefinitionValue</literal></title> - <para> - The <literal>PropertyDefinitionValue</literal> interface extends <literal>ItemDefinitionValue</literal> with the addition of writing methods, enabling the characteristics of a child property definition to be set, after that the <literal>PropertyDefinitionValue</literal> is added to a <literal>NodeTypeValue</literal>. - </para> - <example id="exam-Reference_Guide-PropertyDefinitionValue-PropertyDefinitionValue"> - <title><literal>PropertyDefinitionValue</literal></title> - + </section> + + <section id="sect-Reference_Guide-Interfaces_and_methods-PropertyDefinitionValue"> + <title><literal>PropertyDefinitionValue</literal></title> + <para> + The <literal>PropertyDefinitionValue</literal> interface extends <literal>ItemDefinitionValue</literal> with the addition of writing methods, enabling the characteristics of a child property definition to be set, after that the <literal>PropertyDefinitionValue</literal> is added to a <literal>NodeTypeValue</literal>. + </para> + <example id="exam-Reference_Guide-PropertyDefinitionValue-PropertyDefinitionValue"> + <title><literal>PropertyDefinitionValue</literal></title> + <programlisting language="Java" role="Java">/** * @return Returns the defaultValues. */ @@ -300,10 +300,10 @@ */ public void setValueConstraints(List<String> valueConstraints);</programlisting> - </example> - <example id="exam-Reference_Guide-PropertyDefinitionValue-ItemDefinitionValue"> - <title><literal>ItemDefinitionValue</literal></title> - + </example> + <example id="exam-Reference_Guide-PropertyDefinitionValue-ItemDefinitionValue"> + <title><literal>ItemDefinitionValue</literal></title> + <programlisting language="Java" role="Java"> /** * @return Returns the autoCreate. */ @@ -354,27 +354,27 @@ */ public void setReadOnly(boolean readOnly);</programlisting> - </example> + </example> - </section> - - <section id="sect-Reference_Guide-Interfaces_and_methods-Node_type_registration"> - <title>Node type registration</title> - <para> - The eXo JCR implementation supports various methods of the node-type registration. - </para> - <example id="exam-Reference_Guide-Node_type_registration-Runtime_Registration_From_XML_File"> - <title>Runtime Registration From XML File</title> - + </section> + + <section id="sect-Reference_Guide-Interfaces_and_methods-Node_type_registration"> + <title>Node type registration</title> + <para> + The eXo JCR implementation supports various methods of the node-type registration. + </para> + <example id="exam-Reference_Guide-Node_type_registration-Runtime_Registration_From_XML_File"> + <title>Runtime Registration From XML File</title> + <programlisting language="Java" role="Java">ExtendedNodeTypeManager nodeTypeManager = (ExtendedNodeTypeManager) session.getWorkspace() .getNodeTypeManager(); InputStream is = MyClass.class.getResourceAsStream("mynodetypes.xml"); nodeTypeManager.registerNodeTypes(is,ExtendedNodeTypeManager.IGNORE_IF_EXISTS );</programlisting> - </example> - <example id="exam-Reference_Guide-Node_type_registration-Run_time_registration_using_NodeTypeValue"> - <title>Run time registration using NodeTypeValue</title> - + </example> + <example id="exam-Reference_Guide-Node_type_registration-Run_time_registration_using_NodeTypeValue"> + <title>Run time registration using NodeTypeValue</title> + <programlisting language="Java" role="Java">ExtendedNodeTypeManager nodeTypeManager = (ExtendedNodeTypeManager) session.getWorkspace() .getNodeTypeManager(); NodeTypeValue testNValue = new NodeTypeValue(); @@ -398,37 +398,39 @@ nodeTypeManager.registerNodeType(testNValue, ExtendedNodeTypeManager.FAIL_IF_EXISTS);</programlisting> - </example> + </example> - </section> - - <section id="sect-Reference_Guide-Interfaces_and_methods-Changing_Existing_Node_Type"> - <title>Changing Existing Node Type</title> - <para> - To replace an existing node type definition pass <literal>ExtendedNodeTypeManager.REPLACE_IF_EXISTS</literal> as a second parameter for the method <literal>ExtendedNodeTypeManager.registerNodeType</literal>. - </para> - + </section> + + <section id="sect-Reference_Guide-Interfaces_and_methods-Changing_Existing_Node_Type"> + <title>Changing Existing Node Type</title> + <para> + To replace an existing node type definition pass <literal>ExtendedNodeTypeManager.REPLACE_IF_EXISTS</literal> as a second parameter for the method <literal>ExtendedNodeTypeManager.registerNodeType</literal>. + </para> + <programlisting language="Java" role="Java">ExtendedNodeTypeManager nodeTypeManager = (ExtendedNodeTypeManager) session.getWorkspace() .getNodeTypeManager(); InputStream is = MyClass.class.getResourceAsStream("mynodetypes.xml"); ..... nodeTypeManager.registerNodeTypes(is,ExtendedNodeTypeManager.REPLACE_IF_EXISTS );</programlisting> - </section> - - <section id="sect-Reference_Guide-Interfaces_and_methods-Removing_node_type"> - <title>Removing node type</title> - <para> - A node type cannot be removed if the repository contains an instance of that node type. - </para> - + </section> + + <section id="sect-Reference_Guide-Interfaces_and_methods-Removing_node_type"> + <title>Removing node type</title> + <para> + A node type cannot be removed if the repository contains an instance of that node type. + </para> + <programlisting language="Java" role="Java">nodeTypeManager.unregisterNodeType(<literal>myNodeType</literal>);</programlisting> - </section> - - <section id="sect-Reference_Guide-Interfaces_and_methods-Adding_New_PropertyDefinition"> - <title>Adding New <literal>PropertyDefinition</literal></title> - + </section> + + <section id="sect-Reference_Guide-Interfaces_and_methods-Adding_New_PropertyDefinition"> + <title>Adding New <literal>PropertyDefinition</literal></title> + <para> + Use the code below to add a new <literal>PropertyDefinition</literal>: + </para> <programlisting language="Java" role="Java"> NodeTypeValue myNodeTypeValue = nodeTypeManager.getNodeTypeValue(myNodeTypeName); List<PropertyDefinitionValue> props = new ArrayList<PropertyDefinitionValue>(); @@ -445,14 +447,14 @@ nodeTypeManager.registerNodeType(myNodeTypeValue, ExtendedNodeTypeManager.REPLACE_IF_EXISTS);</programlisting> - </section> - - <section id="sect-Reference_Guide-Interfaces_and_methods-Adding_New_Child_NodeDefinition"> - <title>Adding New Child <literal>NodeDefinition</literal></title> - <para> - Use the code below to add a new child <literal>NodeDefinition</literal>. - </para> - + </section> + + <section id="sect-Reference_Guide-Interfaces_and_methods-Adding_New_Child_NodeDefinition"> + <title>Adding New Child <literal>NodeDefinition</literal></title> + <para> + Use the code below to add a new child <literal>NodeDefinition</literal>. + </para> + <programlisting language="Java" role="Java">NodeTypeValue myNodeTypeValue = nodeTypeManager.getNodeTypeValue(myNodeTypeName); List<NodeDefinitionValue> nodes = new ArrayList<NodeDefinitionValue>(); @@ -468,72 +470,72 @@ nodeTypeManager.registerNodeType(myNodeTypeValue, ExtendedNodeTypeManager.REPLACE_IF_EXISTS);</programlisting> - </section> - - <section id="sect-Reference_Guide-Interfaces_and_methods-Edit_Existing_PropertyDefinition_or_Child_NodeDefinition"> - <title>Edit Existing <literal>PropertyDefinition</literal> or Child <literal>NodeDefinition</literal></title> - <para> - Note that the existing data must be consistent before changing or removing a existing definition. - </para> - <para> - The JCR does not allow you to change the node type in any way in which the existing data would be incompatible with the new node type. - </para> - <para> - But if these changes are necessary, an incremental process (which consistently changes the node type and the existing data) can achieve node type changes that would not be possible in a direct call. - </para> - <para> - For example: If you wanted to add a new residual property definition called <literal>downloadCount</literal> to the existing node type <literal>myNodeType</literal>, you would encounter two limitations that would not allow you to execute the task with a single call of registerNodeType method. - </para> - <itemizedlist> - <listitem> - <para> - Existing nodes of the type <literal>myNodeType</literal>, which does not contain properties <literal>downloadCount</literal> that conflicts with node type what we need. - </para> + </section> + + <section id="sect-Reference_Guide-Interfaces_and_methods-Edit_Existing_PropertyDefinition_or_Child_NodeDefinition"> + <title>Edit Existing <literal>PropertyDefinition</literal> or Child <literal>NodeDefinition</literal></title> + <para> + Note that the existing data must be consistent before changing or removing a existing definition. + </para> + <para> + The JCR does not allow you to change the node type in any way in which the existing data would be incompatible with the new node type. + </para> + <para> + But if these changes are necessary, an incremental process (which consistently changes the node type and the existing data) can achieve node type changes that would not be possible in a direct call. + </para> + <para> + For example: If you wanted to add a new residual property definition called <literal>downloadCount</literal> to the existing node type <literal>myNodeType</literal>, you would encounter two limitations that would not allow you to execute the task with a single call of registerNodeType method. + </para> + <itemizedlist> + <listitem> + <para> + Existing nodes of the type <literal>myNodeType</literal>, which does not contain properties <literal>downloadCount</literal> that conflicts with node type what we need. + </para> - </listitem> - <listitem> - <para> - Registered node type <literal>myNodeType</literal> will not allow us to add properties <literal>downloadCount</literal> because it has no such specific properties. - </para> + </listitem> + <listitem> + <para> + Registered node type <literal>myNodeType</literal> will not allow us to add properties <literal>downloadCount</literal> because it has no such specific properties. + </para> - </listitem> + </listitem> - </itemizedlist> - <para> - The task could be executed, however, with the following steps: - </para> - <procedure> - <title></title> - <step> - <para> - Change the existing node type <literal>myNodeType</literal> by adding the mandatory property <literal>downloadCount</literal>. - </para> + </itemizedlist> + <para> + The task could be executed, however, with the following steps: + </para> + <procedure> + <title></title> + <step> + <para> + Change the existing node type <literal>myNodeType</literal> by adding the mandatory property <literal>downloadCount</literal>. + </para> - </step> - <step> - <para> - Add the node type <literal>myNodeType</literal> with the property <literal>downloadCount</literal> to all the existing node types. - </para> + </step> + <step> + <para> + Add the node type <literal>myNodeType</literal> with the property <literal>downloadCount</literal> to all the existing node types. + </para> - </step> - <step> - <para> - Change the definition of the property <literal>downloadCount</literal> of the node type <literal>myNodeType</literal> to mandatory. - </para> + </step> + <step> + <para> + Change the definition of the property <literal>downloadCount</literal> of the node type <literal>myNodeType</literal> to mandatory. + </para> - </step> + </step> - </procedure> - + </procedure> + - </section> - - <section id="sect-Reference_Guide-Interfaces_and_methods-Changing_The_List_of_Super_Types"> - <title>Changing The List of Super Types</title> - <para> - Use the following code to change the list of super types: - </para> - + </section> + + <section id="sect-Reference_Guide-Interfaces_and_methods-Changing_The_List_of_Super_Types"> + <title>Changing The List of Super Types</title> + <para> + Use the following code to change the list of super types: + </para> + <programlisting language="Java" role="Java">NodeTypeValue testNValue = nodeTypeManager.getNodeTypeValue("exo:myNodeType"); List<String> superType = testNValue.getDeclaredSupertypeNames(); @@ -542,11 +544,11 @@ nodeTypeManager.registerNodeType(testNValue, ExtendedNodeTypeManager.REPLACE_IF_EXISTS);</programlisting> - </section> - + </section> + - </section> - + </section> + </chapter> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/jbosscache-configuration-templates.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/jbosscache-configuration-templates.xml 2011-12-05 03:51:59 UTC (rev 8190) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/jbosscache-configuration-templates.xml 2011-12-05 04:33:56 UTC (rev 8191) @@ -82,18 +82,13 @@ <section id="sect-Reference_Guide-JBoss_Cache_configuration-Shipped_JBoss_Cache_configuration_templates"> <title>Shipped JBoss Cache configuration templates</title> <para> - The eXo JCR implementation is shipped with ready-to-use JBoss Cache configuration templates for JCR's components. They are located in an application package in the <filename>/conf/portal/</filename> directory. + The eXo JCR implementation is shipped with ready-to-use JBoss Cache configuration templates for JCR's components. They are located in <filename><replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/02portal.war/WEB-INF/conf/jcr/jbosscache</filename> directory, inside either the <filename>cluster</filename> or <filename>local</filename> directory. </para> <section id="sect-Reference_Guide-Shipped_JBoss_Cache_configuration_templates-Data_container_template"> <title>Data container template</title> <para> - The data container template is <filename>jbosscache-data.xml</filename>: + The data container template is <filename>config.xml</filename>: </para> - <programlistingco> - <areaspec> - <area coords="7" id="area-Reference_Guide-Shipped_JBoss_Cache_configuration_templates-Data_container_template-jbosscache-cluster-name" /> - - </areaspec> <programlisting language="XML" role="XML"><?xml version="1.0" encoding="UTF-8"?> <jbosscache xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:jboss:jbosscache-core:config:3.1"> @@ -117,42 +112,14 @@ </default> </eviction> </jbosscache></programlisting> - <calloutlist id="call-Reference_Guide-Data_container_template-Template_variables"> - <title>Template variables</title> - <callout arearefs="area-Reference_Guide-Shipped_JBoss_Cache_configuration_templates-Data_container_template-jbosscache-cluster-name"> - <para> - <replaceable>jbosscache-cluster-name</replaceable>. - </para> - </callout> - - </calloutlist> - - </programlistingco> - - </section> <section id="sect-Reference_Guide-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template"> <title>Lock manager template</title> <para> - The lock manager template is <filename>jbosscache-lock.xml</filename>: + The lock manager template is <filename>lock-config.xml</filename>: </para> - <programlistingco> - <areaspec> - <area coords="6" id="area-Reference_Guide-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cluster-name" /> - <area coords="18" id="area-Reference_Guide-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cl-cache.jdbc.table.name" /> - <area coords="19" id="area-Reference_Guide-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cl-cache.jdbc.table.create" /> - <area coords="20" id="area-Reference_Guide-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cl-cache.jdbc.table.drop" /> - <area coords="21" id="area-Reference_Guide-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cl-cache.jdbc.table.primarykey" /> - <area coords="22" id="area-Reference_Guide-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cl-cache.jdbc.fqn.column" /> - <area coords="23" id="area-Reference_Guide-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cl-cache.jdbc.fqn.type" /> - <area coords="24" id="area-Reference_Guide-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cl-cache.jdbc.node.column" /> - <area coords="25" id="area-Reference_Guide-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cl-cache.jdbc.node.type" /> - <area coords="26" id="area-Reference_Guide-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cl-cache.jdbc.parent.column" /> - <area coords="27" id="area-Reference_Guide-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cl-cache.jdbc.datasource" /> - - </areaspec> <programlisting language="XML" role="XML"><?xml version="1.0" encoding="UTF-8"?> <jbosscache xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:jboss:jbosscache-core:config:3.1"> @@ -185,92 +152,15 @@ </loader> </loaders> </jbosscache></programlisting> - <calloutlist id="call-Reference_Guide-Lock_manager_template-Template_variables"> - <title>Template variables</title> - <callout arearefs="area-Reference_Guide-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cluster-name"> - <para> - <replaceable>jbosscache-cluster-name</replaceable> - </para> - </callout> - <callout arearefs="area-Reference_Guide-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cl-cache.jdbc.table.name"> - <para> - <replaceable>jbosscache-cl-cache.jdbc.table.name</replaceable> - </para> - - </callout> - <callout arearefs="area-Reference_Guide-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cl-cache.jdbc.table.create"> - <para> - <replaceable>jbosscache-cl-cache.jdbc.table.create</replaceable> - </para> - - </callout> - <callout arearefs="area-Reference_Guide-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cl-cache.jdbc.table.drop"> - <para> - <replaceable>jbosscache-cl-cache.jdbc.table.drop</replaceable> - </para> - - </callout> - <callout arearefs="area-Reference_Guide-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cl-cache.jdbc.table.primarykey"> - <para> - <replaceable>jbosscache-cl-cache.jdbc.table.primarykey</replaceable> - </para> - - </callout> - <callout arearefs="area-Reference_Guide-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cl-cache.jdbc.fqn.column"> - <para> - <replaceable>jbosscache-cl-cache.jdbc.fqn.column</replaceable> - </para> - - </callout> - <callout arearefs="area-Reference_Guide-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cl-cache.jdbc.fqn.type"> - <para> - <replaceable>jbosscache-cl-cache.jdbc.fqn.type</replaceable> - </para> - - </callout> - <callout arearefs="area-Reference_Guide-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cl-cache.jdbc.node.column"> - <para> - <replaceable>jbosscache-cl-cache.jdbc.node.column</replaceable> - </para> - - </callout> - <callout arearefs="area-Reference_Guide-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cl-cache.jdbc.node.type"> - <para> - <replaceable>jbosscache-cl-cache.jdbc.node.type</replaceable> - </para> - - </callout> - <callout arearefs="area-Reference_Guide-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cl-cache.jdbc.parent.column"> - <para> - <replaceable>jbosscache-cl-cache.jdbc.parent.column</replaceable> - </para> - - </callout> - <callout arearefs="area-Reference_Guide-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cl-cache.jdbc.datasource"> - <para> - <replaceable>jbosscache-cl-cache.jdbc.datasource</replaceable> - </para> - - </callout> - - </calloutlist> - - </programlistingco> - - </section> <section id="sect-Reference_Guide-Shipped_JBoss_Cache_configuration_templates-Query_handler_indexer_template"> <title>Query handler (indexer) template</title> <para> - The query handler template is called <filename>jbosscache-indexer.xml</filename>: + The query handler template is called <filename>indexer-config.xml</filename>: </para> - <programlistingco> - <areaspec> - <area coords="5" id="area-Reference_Guide-Shipped_JBoss_Cache_configuration_templates-Query_handler_indexer_template-jbosscache-cluster-name" /> - </areaspec> <programlisting language="XML" role="XML"><?xml version="1.0" encoding="UTF-8"?> <jbosscache xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:jboss:jbosscache-core:config:3.1"> @@ -289,19 +179,8 @@ </default> </eviction> </jbosscache></programlisting> - <calloutlist> - <callout arearefs="area-Reference_Guide-Shipped_JBoss_Cache_configuration_templates-Query_handler_indexer_template-jbosscache-cluster-name"> - <para> - <replaceable>jbosscache-cluster-name</replaceable> - </para> + - </callout> - - </calloutlist> - - </programlistingco> - - </section> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/other/jcr-resources.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/other/jcr-resources.xml 2011-12-05 03:51:59 UTC (rev 8190) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/other/jcr-resources.xml 2011-12-05 04:33:56 UTC (rev 8191) @@ -4,21 +4,18 @@ %BOOK_ENTITIES; ]> <chapter id="chap-Reference_Guide-JCR_Resources"> - <title>JCR Resources:</title> - <para> - * Java Community Process: <ulink url="http://jcp.org/en/jsr/detail?id=170">JSR 170 </ulink> and <ulink url="http://jcp.org/en/jsr/detail?id=283">JSR 283</ulink> - </para> - <para> - * Tom Wheeler, <ulink url="http://www.tomwheeler.com/java_content_repository_tomwheeler_20071007.pdf">The Java Content Repository</ulink> (2007) - </para> - <para> - * Roy T. Fielding, <ulink url="http://www.day.com/content/dam/day/whitepapers/JSR_170_White_Paper.pdf">JSR 170 Overview: Standardizing the Content Repository Interface</ulink> (March 13, 2005) - </para> - <para> - * David Nuescheler and Janus Boye, <ulink url="http://www.cmswatch.com/Feature/123">JSR-170 What's in it for me?</ulink> (April 20, 2005) - </para> - <para> - * Benjamin Mestrallet, Tuan Nguyen, Gennady Azarenkov, Francois Moron and Brice Revenant <ulink url="http://www.theserverside.com/tt/articles/article.tss?l=eXoPlatform2">eXo Platform v2, Portal, JCR, ECM, Groupware and Business Intelligence</ulink> (January 2006) - </para> + <title>JCR Resources:</title> + <para> + * Java Community Process: <ulink url="http://jcp.org/en/jsr/detail?id=170">JSR 170 </ulink> and <ulink url="http://jcp.org/en/jsr/detail?id=283">JSR 283</ulink> + </para> + <para> + * Roy T. Fielding, <ulink url="http://www.day.com/content/dam/day/whitepapers/JSR_170_White_Paper.pdf">JSR 170 Overview: Standardizing the Content Repository Interface</ulink> (March 13, 2005) + </para> + <para> + * David Nuescheler and Janus Boye, <ulink url="http://www.cmswatch.com/Feature/123">JSR-170 What's in it for me?</ulink> (April 20, 2005) + </para> + <para> + * Benjamin Mestrallet, Tuan Nguyen, Gennady Azarenkov, Francois Moron and Brice Revenant <ulink url="http://www.theserverside.com/tt/articles/article.tss?l=eXoPlatform2">eXo Platform v2, Portal, JCR, ECM, Groupware and Business Intelligence</ulink> (January 2006) + </para> </chapter> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/protocols/ftp.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/protocols/ftp.xml 2011-12-05 03:51:59 UTC (rev 8190) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/protocols/ftp.xml 2011-12-05 04:33:56 UTC (rev 8191) @@ -4,61 +4,61 @@ %BOOK_ENTITIES; ]> <chapter id="chap-Reference_Guide-FTP"> - <title>FTP</title> - <section id="sect-Reference_Guide-FTP-Introduction"> - <title>Introduction</title> - <para> - The JCR-FTP Server operates as an FTP server with access to a content stored in JCR repositories in the form of <literal>nt:file/nt:folder</literal> nodes or their successors. The client of an executed Server can be any FTP client. The FTP server is supported by a standard configuration which can be changed as required. - </para> + <title>FTP</title> + <section id="sect-Reference_Guide-FTP-Introduction"> + <title>Introduction</title> + <para> + The JCR-FTP Server operates as an FTP server with access to a content stored in JCR repositories in the form of <literal>nt:file/nt:folder</literal> nodes or their successors. The client of an executed Server can be any FTP client. The FTP server is supported by a standard configuration which can be changed as required. + </para> - </section> - - <section id="sect-Reference_Guide-FTP-Configuration_Parameters"> - <title>Configuration Parameters</title> - <variablelist id="vari-Reference_Guide-Configuration_Parameters-Parameters"> - <title>Parameters</title> - <varlistentry> - <term>command-port:</term> - <listitem> - + </section> + + <section id="sect-Reference_Guide-FTP-Configuration_Parameters"> + <title>Configuration Parameters</title> + <variablelist id="vari-Reference_Guide-Configuration_Parameters-Parameters"> + <title>Parameters</title> + <varlistentry> + <term>command-port:</term> + <listitem> + <programlisting language="XML" role="XML"><value-param> <name>command-port</name> <value>21</value> </value-param></programlisting> - <para> - The value of the command channel port. The value '<literal>21</literal>' is default. - </para> - <para> - If you have already other FTP server installed in your system, this parameter needs to be changed (to <literal>2121</literal>, for example) to avoid conflicts or if the port is protected. - </para> + <para> + The value of the command channel port. The value '<literal>21</literal>' is default. + </para> + <para> + If you have already other FTP server installed in your system, this parameter needs to be changed (to <literal>2121</literal>, for example) to avoid conflicts or if the port is protected. + </para> - </listitem> + </listitem> - </varlistentry> - <varlistentry> - <term>data-min-port & data-max-port</term> - <listitem> - + </varlistentry> + <varlistentry> + <term>data-min-port and data-max-port</term> + <listitem> + <programlisting language="XML" role="XML"><value-param> <name>data-min-port</name> <value>52000</value> </value-param></programlisting> - + <programlisting language="XML" role="XML"><value-param> <name>data-max-port</name> <value>53000</value> </value-param></programlisting> - <para> - These two parameters indicate the minimum and maximum values of the range of ports, used by the server. The usage of the additional data channel is required by the FTP protocol, which is used to transfer the contents of files and the listing of catalogues. This range of ports should be free from listening by other server-programs. - </para> + <para> + These two parameters indicate the minimum and maximum values of the range of ports, used by the server. The usage of the additional data channel is required by the FTP protocol, which is used to transfer the contents of files and the listing of catalogues. This range of ports should be free from listening by other server-programs. + </para> - </listitem> + </listitem> - </varlistentry> - <varlistentry> - <term>system</term> - <listitem> - + </varlistentry> + <varlistentry> + <term>system</term> + <listitem> + <programlisting language="XML" role="XML"><value-param> <name>system</name> @@ -66,17 +66,17 @@ or <value>UNIX Type: L8</value> </value-param></programlisting> - <para> - Types of formats of listing of catalogues which are supported. - </para> + <para> + Types of formats of listing of catalogues which are supported. + </para> - </listitem> + </listitem> - </varlistentry> - <varlistentry> - <term>client-side-encoding</term> - <listitem> - + </varlistentry> + <varlistentry> + <term>client-side-encoding</term> + <listitem> + <programlisting language="XML" role="XML"><value-param> <name>client-side-encoding</name> @@ -85,123 +85,123 @@ <value>KOI8-R</value> </value-param></programlisting> - <para> - This parameter specifies the coding which is used for dialogue with the client. - </para> + <para> + This parameter specifies the coding which is used for dialogue with the client. + </para> - </listitem> + </listitem> - </varlistentry> - <varlistentry> - <term>def-folder-node-type</term> - <listitem> - + </varlistentry> + <varlistentry> + <term>def-folder-node-type</term> + <listitem> + <programlisting language="XML" role="XML"><value-param> <name>def-folder-node-type</name> <value>nt:folder</value> </value-param></programlisting> - <para> - This parameter specifies the type of a node, when an FTP-folder is created. - </para> + <para> + This parameter specifies the type of a node, when an FTP-folder is created. + </para> - </listitem> + </listitem> - </varlistentry> - <varlistentry> - <term>def-file-node-type</term> - <listitem> - + </varlistentry> + <varlistentry> + <term>def-file-node-type</term> + <listitem> + <programlisting language="XML" role="XML"><value-param> <name>def-file-node-type</name> <value>nt:file</value> </value-param></programlisting> - <para> - This parameter specifies the type of a node, when an FTP-file is created. - </para> + <para> + This parameter specifies the type of a node, when an FTP-file is created. + </para> - </listitem> + </listitem> - </varlistentry> - <varlistentry> - <term>def-file-mime-type</term> - <listitem> - + </varlistentry> + <varlistentry> + <term>def-file-mime-type</term> + <listitem> + <programlisting language="XML" role="XML"><value-param> <name>def-file-mime-type</name> <value>application/zip</value> </value-param></programlisting> - <para> - The mime type of a created file is chosen by using its file extention. In case, a server cannot find the corresponding mime type, this value is used. - </para> + <para> + The mime type of a created file is chosen by using its file extention. In case, a server cannot find the corresponding mime type, this value is used. + </para> - </listitem> + </listitem> - </varlistentry> - <varlistentry> - <term>cache-folder-name</term> - <listitem> - + </varlistentry> + <varlistentry> + <term>cache-folder-name</term> + <listitem> + <programlisting language="XML" role="XML"><value-param> <name>cache-folder-name</name> <value>../temp/ftp_cache</value> </value-param></programlisting> - <para> - The Path of the cache folder. - </para> + <para> + The Path of the cache folder. + </para> - </listitem> + </listitem> - </varlistentry> - <varlistentry> - <term>upload-speed-limit</term> - <listitem> - + </varlistentry> + <varlistentry> + <term>upload-speed-limit</term> + <listitem> + <programlisting language="XML" role="XML"><value-param> <name>upload-speed-limit</name> <value>20480</value> </value-param></programlisting> - <para> - Restriction of the upload speed. It is measured in bytes. - </para> + <para> + Restriction of the upload speed. It is measured in bytes. + </para> - </listitem> + </listitem> - </varlistentry> - <varlistentry> - <term>download-speed-limit</term> - <listitem> - + </varlistentry> + <varlistentry> + <term>download-speed-limit</term> + <listitem> + <programlisting language="XML" role="XML"><value-param> <name>download-speed-limit</name> <value>20480</value> </value-param></programlisting> - <para> - Restriction of the download speed. It is measured in bytes. - </para> + <para> + Restriction of the download speed. It is measured in bytes. + </para> - </listitem> + </listitem> - </varlistentry> - <varlistentry> - <term>timeout</term> - <listitem> - + </varlistentry> + <varlistentry> + <term>timeout</term> + <listitem> + <programlisting language="XML" role="XML"><value-param> <name>timeout</name> <value>60</value> </value-param></programlisting> - <para> - Defines the value of a timeout. - </para> + <para> + Defines the value of a timeout. + </para> - </listitem> + </listitem> - </varlistentry> + </varlistentry> - </variablelist> + </variablelist> - </section> - + </section> + </chapter> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/query-handler-config.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/query-handler-config.xml 2011-12-05 03:51:59 UTC (rev 8190) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/query-handler-config.xml 2011-12-05 04:33:56 UTC (rev 8191) @@ -4,50 +4,50 @@ %BOOK_ENTITIES; ]> <chapter id="chap-Reference_Guide-QueryHandler_configuration"> - <title>QueryHandler configuration</title> - <section id="sect-Reference_Guide-QueryHandler_configuration-Indexing_in_clustered_environment"> - <title>Indexing in clustered environment</title> - <para> - JCR offers indexing strategies for clustered environments using the advantages of running in a single JVM or doing the best to use all resources available in cluster. JCR uses Lucene library as underlying search and indexing engine, but it has several limitations that greatly reduce possibilities and limits the usage of cluster advantages. That's why eXo JCR offers two strategies that are suitable for it's own usecases. They are clustered with shared index and clustered with local indexes. Each one has it's pros and cons. - </para> - <para> - Clustered implementation with local indexes combines in-memory buffer index directory with delayed file-system flushing. This index is called "Volatile" and it is invoked in searches also. Within some conditions volatile index is flushed to the persistent storage (file system) as new index directory. This allows to achieve great results for write operations. - </para> - <mediaobject> - <imageobject> - <imagedata align="center" fileref="images/eXoJCR/diagram-local-index.png" width="444" /> - </imageobject> + <title>QueryHandler configuration</title> + <section id="sect-Reference_Guide-QueryHandler_configuration-Indexing_in_clustered_environment"> + <title>Indexing in clustered environment</title> + <para> + JCR offers indexing strategies for clustered environments using the advantages of running in a single JVM or doing the best to use all resources available in cluster. JCR uses Lucene library as underlying search and indexing engine, but it has several limitations that greatly reduce possibilities and limits the usage of cluster advantages. That's why eXo JCR offers two strategies that are suitable for it's own usecases. They are clustered with shared index and clustered with local indexes. Each one has it's pros and cons. + </para> + <para> + Clustered implementation with local indexes combines in-memory buffer index directory with delayed file-system flushing. This index is called "Volatile" and it is invoked in searches also. Within some conditions volatile index is flushed to the persistent storage (file system) as new index directory. This allows to achieve great results for write operations. + </para> + <mediaobject> + <imageobject> + <imagedata align="center" fileref="images/eXoJCR/diagram-local-index.png" width="444" /> + </imageobject> - </mediaobject> - <para> - As this implementation designed for clustered environment it has additional mechanisms for data delivery within cluster. Actual text extraction jobs done on the same node that does content operations (i.e. write operation). Prepared "documents" (Lucene term that means block of data ready for indexing) are replicated withing cluster nodes and processed by local indexes. So each cluster instance has the same index content. When new node joins the cluster it has no initial index, so it must be created. There are some supported ways of doing this operation. The simplest is to simply copy the index manually but this is not intended for use. If no initial index found JCR uses automated sceneries. They are controlled via configuration (see "index-recovery-mode" parameter) offering full re-indexing from database or copying from another cluster node. - </para> - <para> - For some reasons having a multiple index copies on each instance can be costly. So shared index can be used instead (see diagram below). - </para> - <mediaobject> - <imageobject> - <imagedata align="center" fileref="images/eXoJCR/diagram-shared-index.png" width="444" /> - </imageobject> + </mediaobject> + <para> + As this implementation designed for clustered environment it has additional mechanisms for data delivery within cluster. Actual text extraction jobs done on the same node that does content operations (i.e. write operation). Prepared "documents" (Lucene term that means block of data ready for indexing) are replicated withing cluster nodes and processed by local indexes. So each cluster instance has the same index content. When new node joins the cluster it has no initial index, so it must be created. There are some supported ways of doing this operation. The simplest is to simply copy the index manually but this is not intended for use. If no initial index found JCR uses automated sceneries. They are controlled via configuration (see "index-recovery-mode" parameter) offering full re-indexing from database or copying from another cluster node. + </para> + <para> + For some reasons having a multiple index copies on each instance can be costly. So shared index can be used instead (see diagram below). + </para> + <mediaobject> + <imageobject> + <imagedata align="center" fileref="images/eXoJCR/diagram-shared-index.png" width="444" /> + </imageobject> - </mediaobject> - <para> - This indexing strategy combines advantages of in-memory index along with shared persistent index offering "near" real time search capabilities. This means that newly added content is accessible via search practically immediately. This strategy allows nodes to index data in their own volatile (in-memory) indexes, but persistent indexes are managed by single "coordinator" node only. Each cluster instance has a read access for shared index to perform queries combining search results found in own in-memory index also. Take in account that shared folder must be configured in your system environment (i.e. mounted NFS folder). But this strategy in some extremely rare cases can have a bit different volatile indexes within cluster instances for a while. In a few seconds they will be up2date. - </para> - <para> - See more about <xref linkend="chap-Reference_Guide-Search_Configuration" /> . - </para> + </mediaobject> + <para> + This indexing strategy combines advantages of in-memory index along with shared persistent index offering "near" real time search capabilities. This means that newly added content is accessible via search practically immediately. This strategy allows nodes to index data in their own volatile (in-memory) indexes, but persistent indexes are managed by single "coordinator" node only. Each cluster instance has a read access for shared index to perform queries combining search results found in own in-memory index also. Take in account that shared folder must be configured in your system environment (i.e. mounted NFS folder). But this strategy in some extremely rare cases can have a bit different volatile indexes within cluster instances for a while. In a few seconds they will be up2date. + </para> + <para> + See more about <xref linkend="chap-Reference_Guide-Search_Configuration" /> . + </para> - </section> - - <section id="sect-Reference_Guide-QueryHandler_configuration-Configuration"> - <title>Configuration</title> - <section id="sect-Reference_Guide-Configuration-Query_handler_configuration_overview"> - <title>Query-handler configuration overview</title> - <para> - Configuration example: - </para> - + </section> + + <section id="sect-Reference_Guide-QueryHandler_configuration-Configuration"> + <title>Configuration</title> + <section id="sect-Reference_Guide-Configuration-Query_handler_configuration_overview"> + <title>Query-handler configuration overview</title> + <para> + Configuration example: + </para> + <programlisting language="XML" role="XML"><workspace name="ws"> <query-handler class="org.exoplatform.services.jcr.impl.core.query.lucene.SearchIndex"> <properties> @@ -67,195 +67,195 @@ </query-handler> </workspace> </programlisting> - <table id="tabl-Reference_Guide-Query_handler_configuration_overview-Configuration_properties"> - <title>Configuration properties</title> - <tgroup cols="2"> - <thead> - <row> - <entry> - Property name - </entry> - <entry> - Description - </entry> + <table id="tabl-Reference_Guide-Query_handler_configuration_overview-Configuration_properties"> + <title>Configuration properties</title> + <tgroup cols="2"> + <thead> + <row> + <entry> + Property name + </entry> + <entry> + Description + </entry> - </row> + </row> - </thead> - <tbody> - <row> - <entry> - index-dir - </entry> - <entry> - path to index - </entry> + </thead> + <tbody> + <row> + <entry> + index-dir + </entry> + <entry> + path to index + </entry> - </row> - <row> - <entry> - changesfilter-class - </entry> - <entry> - template of JBoss-cache configuration for all query-handlers in repository - </entry> + </row> + <row> + <entry> + changesfilter-class + </entry> + <entry> + template of JBoss-cache configuration for all query-handlers in repository + </entry> - </row> - <row> - <entry> - jbosscache-configuration - </entry> - <entry> - template of JBoss-cache configuration for all query-handlers in repository - </entry> + </row> + <row> + <entry> + jbosscache-configuration + </entry> + <entry> + template of JBoss-cache configuration for all query-handlers in repository + </entry> - </row> - <row> - <entry> - jgroups-configuration - </entry> - <entry> - jgroups-configuration is template configuration for all components (search, cache, locks) [Add link to document describing template configurations] - </entry> + </row> + <row> + <entry> + jgroups-configuration + </entry> + <entry> + jgroups-configuration is template configuration for all components (search, cache, locks) [Add link to document describing template configurations] + </entry> - </row> - <row> - <entry> - jgroups-multiplexer-stack - </entry> - <entry> - [TODO about jgroups-multiplexer-stack - add link to JBoss doc] - </entry> + </row> + <row> + <entry> + jgroups-multiplexer-stack + </entry> + <entry> + [TODO about jgroups-multiplexer-stack - add link to JBoss doc] + </entry> - </row> - <row> - <entry> - jbosscache-cluster-name - </entry> - <entry> - cluster name (must be unique) - </entry> + </row> + <row> + <entry> + jbosscache-cluster-name + </entry> + <entry> + cluster name (must be unique) + </entry> - </row> - <row> - <entry> - max-volatile-time - </entry> - <entry> - max time to live for Volatile Index - </entry> + </row> + <row> + <entry> + max-volatile-time + </entry> + <entry> + max time to live for Volatile Index + </entry> - </row> - <row> - <entry> - rdbms-reindexing - </entry> - <entry> - indicate that need to use rdbms reindexing mechanism if possible, the default value is true - </entry> + </row> + <row> + <entry> + rdbms-reindexing + </entry> + <entry> + indicate that need to use rdbms reindexing mechanism if possible, the default value is true + </entry> - </row> - <row> - <entry> - reindexing-page-size - </entry> - <entry> - maximum amount of nodes which can be retrieved from storage for re-indexing purpose, the default value is 100 - </entry> + </row> + <row> + <entry> + reindexing-page-size + </entry> + <entry> + maximum amount of nodes which can be retrieved from storage for re-indexing purpose, the default value is 100 + </entry> - </row> - <row> - <entry> - index-recovery-mode - </entry> - <entry> - If the parameter has been set to <command>from-indexing</command>, so a full indexing will be automatically launched (default behavior), if the parameter has been set to <command>from-coordinator</command>, the index will be retrieved from coordinator - </entry> + </row> + <row> + <entry> + index-recovery-mode + </entry> + <entry> + If the parameter has been set to <command>from-indexing</command>, so a full indexing will be automatically launched (default behavior), if the parameter has been set to <command>from-coordinator</command>, the index will be retrieved from coordinator + </entry> - </row> - <row> - <entry> - index-recovery-filter - </entry> - <entry> - Defines implementation class or classes of RecoveryFilters, the mechanism of index synchronization for Local Index strategy. - </entry> + </row> + <row> + <entry> + index-recovery-filter + </entry> + <entry> + Defines implementation class or classes of RecoveryFilters, the mechanism of index synchronization for Local Index strategy. + </entry> - </row> - <row> - <entry> - async-reindexing - </entry> - <entry> - Controls the process of re-indexing on JCR's startup. If this flag is set, indexing will be launched asynchronously, without blocking the JCR. Default is "<literal>false</literal>". - </entry> + </row> + <row> + <entry> + async-reindexing + </entry> + <entry> + Controls the process of re-indexing on JCR's startup. If this flag is set, indexing will be launched asynchronously, without blocking the JCR. Default is "<literal>false</literal>". + </entry> - </row> + </row> - </tbody> + </tbody> - </tgroup> + </tgroup> - </table> - <formalpara id="form-Reference_Guide-Query_handler_configuration_overview-Improving_Query_Performance_With_postgreSQL_and_rdbms_reindexing"> - <title>Improving Query Performance With <literal>postgreSQL</literal> and <parameter>rdbms-reindexing</parameter></title> - <para> - If you use <literal>postgreSQL</literal> and <parameter>rdbms-reindexing</parameter> is set to <literal>true</literal>, the performance of the queries used while indexing can be improved by: - </para> + </table> + <formalpara id="form-Reference_Guide-Query_handler_configuration_overview-Improving_Query_Performance_With_postgreSQL_and_rdbms_reindexing"> + <title>Improving Query Performance With <literal>postgreSQL</literal> and <parameter>rdbms-reindexing</parameter></title> + <para> + If you use <literal>postgreSQL</literal> and <parameter>rdbms-reindexing</parameter> is set to <literal>true</literal>, the performance of the queries used while indexing can be improved by: + </para> - </formalpara> - <procedure> - <title></title> - <step> - <para> - Set the parameter "<parameter>enable_seqscan</parameter>" to "<literal>off</literal>" - </para> - <para> - <emphasis role="bold">OR</emphasis> - </para> - <para> - Set "<parameter>default_statistics_target</parameter>" to at least "<literal>50</literal>". - </para> + </formalpara> + <procedure> + <title></title> + <step> + <para> + Set the parameter "<parameter>enable_seqscan</parameter>" to "<literal>off</literal>" + </para> + <para> + <emphasis role="bold">OR</emphasis> + </para> + <para> + Set "<parameter>default_statistics_target</parameter>" to at least "<literal>50</literal>". + </para> - </step> - <step> - <para> - Restart DB server and make analyze of the JCR_SVALUE (or JCR_MVALUE) table. - </para> + </step> + <step> + <para> + Restart DB server and make analyze of the JCR_SVALUE (or JCR_MVALUE) table. + </para> - </step> + </step> - </procedure> - - <formalpara id="form-Reference_Guide-Query_handler_configuration_overview-Improving_Query_Performance_With_DB2_and_rdbms_reindexing"> - <title>Improving Query Performance With <literal>DB2</literal> and <parameter>rdbms-reindexing</parameter></title> - <para> - If you use <literal>DB2</literal> and <parameter>rdbms-reindexing</parameter> is set to <literal>true</literal>, the performance of the queries used while indexing can be improved by: - </para> + </procedure> + + <formalpara id="form-Reference_Guide-Query_handler_configuration_overview-Improving_Query_Performance_With_DB2_and_rdbms_reindexing"> + <title>Improving Query Performance With <literal>DB2</literal> and <parameter>rdbms-reindexing</parameter></title> + <para> + If you use <literal>DB2</literal> and <parameter>rdbms-reindexing</parameter> is set to <literal>true</literal>, the performance of the queries used while indexing can be improved by: + </para> - </formalpara> - <procedure> - <title></title> - <step> - <para> - Make statistics on tables by running the following for <literal>JCR_SITEM</literal> (or <literal>JCR_MITEM</literal>) and <literal>JCR_SVALUE</literal> (or <literal>JCR_MVALUE</literal>) tables: - </para> - + </formalpara> + <procedure> + <title></title> + <step> + <para> + Make statistics on tables by running the following for <literal>JCR_SITEM</literal> (or <literal>JCR_MITEM</literal>) and <literal>JCR_SVALUE</literal> (or <literal>JCR_MVALUE</literal>) tables: + </para> + <programlisting><code>RUNSTATS ON TABLE <scheme>.<table> WITH DISTRIBUTION AND INDEXES ALL</code></programlisting> - </step> + </step> - </procedure> - + </procedure> + - </section> - - <section id="sect-Reference_Guide-Configuration-Cluster_ready_indexing"> - <title>Cluster-ready indexing</title> - <para> - For both cluster-ready implementations JBoss Cache, JGroups and Changes Filter values must be defined. Shared index requires some kind of remote or shared file system to be attached in a system (i.e. NFS, SMB or etc). Indexing directory ("indexDir" value) must point to it. Setting "changesfilter-class" to "org.exoplatform.services.jcr.impl.core.query.jbosscache.JBossCacheIndexChangesFilter" will enable shared index implementation. - </para> - + </section> + + <section id="sect-Reference_Guide-Configuration-Cluster_ready_indexing"> + <title>Cluster-ready indexing</title> + <para> + For both cluster-ready implementations JBoss Cache, JGroups and Changes Filter values must be defined. Shared index requires some kind of remote or shared file system to be attached in a system (i.e. NFS, SMB or etc). Indexing directory ("indexDir" value) must point to it. Setting "changesfilter-class" to "org.exoplatform.services.jcr.impl.core.query.jbosscache.JBossCacheIndexChangesFilter" will enable shared index implementation. + </para> + <programlisting language="XML" role="XML"><workspace name="ws"> <query-handler class="org.exoplatform.services.jcr.impl.core.query.lucene.SearchIndex"> <properties> @@ -273,10 +273,10 @@ </properties> </query-handler> </workspace></programlisting> - <para> - In order to use cluster-ready strategy based on local indexes, when each node has own copy of index on local file system, the following configuration must be applied. Indexing directory must point to any folder on local file system and "changesfilter-class" must be set to "org.exoplatform.services.jcr.impl.core.query.jbosscache.LocalIndexChangesFilter". - </para> - + <para> + In order to use cluster-ready strategy based on local indexes, when each node has own copy of index on local file system, the following configuration must be applied. Indexing directory must point to any folder on local file system and "changesfilter-class" must be set to "org.exoplatform.services.jcr.impl.core.query.jbosscache.LocalIndexChangesFilter". + </para> + <programlisting language="XML" role="XML"><workspace name="ws"> <query-handler class="org.exoplatform.services.jcr.impl.core.query.lucene.SearchIndex"> <properties> @@ -296,108 +296,108 @@ </workspace> </programlisting> - </section> - - <section id="sect-Reference_Guide-Configuration-Local_Index_Recovery_Filters"> - <title>Local Index Recovery Filters</title> - <para> - A common usecase for all cluster-ready applications is a hot joining and leaving of processing units. All nodes that are joining a cluster for the first time or nodes joining after some downtime, must be in a synchronized state. - </para> - <para> - When using shared value storages, databases and indexes, cluster nodes are synchronized at any given time. But is not the case when a local index strategy is used. - </para> - <para> - If a new node joins a cluster, without an index it is retrieved or recreated. Nodes can be also be restarted and thus the index is not empty. By default, even though the existing index is thought to be up to date, it can be outdated. - </para> - <para> - The JBoss Enterprise Portal Platform JCR offers a mechanism called <literal>RecoveryFilters</literal> that will automatically retrieve index for the joining node on start up. This feature is a set of filters that can be defined via <literal>QueryHandler</literal> configuration: - </para> - + </section> + + <section id="sect-Reference_Guide-Configuration-Local_Index_Recovery_Filters"> + <title>Local Index Recovery Filters</title> + <para> + A common usecase for all cluster-ready applications is a hot joining and leaving of processing units. All nodes that are joining a cluster for the first time or nodes joining after some downtime, must be in a synchronized state. + </para> + <para> + When using shared value storages, databases and indexes, cluster nodes are synchronized at any given time. But is not the case when a local index strategy is used. + </para> + <para> + If a new node joins a cluster, without an index it is retrieved or recreated. Nodes can be also be restarted and thus the index is not empty. By default, even though the existing index is thought to be up to date, it can be outdated. + </para> + <para> + The JBoss Enterprise Portal Platform JCR offers a mechanism called <literal>RecoveryFilters</literal> that will automatically retrieve index for the joining node on start up. This feature is a set of filters that can be defined via <literal>QueryHandler</literal> configuration: + </para> + <programlisting language="XML"><property name="index-recovery-filter" value="org.exoplatform.services.jcr.impl.core.query.lucene.DocNumberRecoveryFilter" /></programlisting> - <para> - Filter numbers are not limited so they can be combined: - </para> - + <para> + Filter numbers are not limited so they can be combined: + </para> + <programlisting language="XML"><property name="index-recovery-filter" value="org.exoplatform.services.jcr.impl.core.query.lucene.DocNumberRecoveryFilter" /> <property name="index-recovery-filter" value="org.exoplatform.services.jcr.impl.core.query.lucene.SystemPropertyRecoveryFilter" /> </programlisting> - <para> - If any one returns fires, the index is re-synchronized. This feature uses standard index recovery mode defined by previously described parameter (can be "from-indexing" (default) or "from-coordinator") - </para> - + <para> + If any one returns fires, the index is re-synchronized. This feature uses standard index recovery mode defined by previously described parameter (can be "from-indexing" (default) or "from-coordinator") + </para> + <programlisting language="XML"><property name="index-recovery-mode" value="from-coordinator" /> </programlisting> - <para> - There are multiple filter implementations: - </para> - <variablelist id="vari-Reference_Guide-Local_Index_Recovery_Filters-org.exoplatform.services.jcr.impl.core.query.lucene.DummyRecoveryFilter"> - <title>org.exoplatform.services.jcr.impl.core.query.lucene.DummyRecoveryFilter</title> - <varlistentry> - <term></term> - <listitem> - <para> - Always returns true, for cases when index must be force resynchronized (recovered) each time. - </para> + <para> + There are multiple filter implementations: + </para> + <variablelist id="vari-Reference_Guide-Local_Index_Recovery_Filters-org.exoplatform.services.jcr.impl.core.query.lucene.DummyRecoveryFilter"> + <title>org.exoplatform.services.jcr.impl.core.query.lucene.DummyRecoveryFilter</title> + <varlistentry> + <term></term> + <listitem> + <para> + Always returns true, for cases when index must be force resynchronized (recovered) each time. + </para> - </listitem> + </listitem> - </varlistentry> - <varlistentry> - <term>org.exoplatform.services.jcr.impl.core.query.lucene.SystemPropertyRecoveryFilter</term> - <listitem> - <para> - Returns value of system property "<literal>org.exoplatform.jcr.recoveryfilter.forcereindexing</literal>". So index recovery can be controlled from the top without changing documentation using system properties. - </para> + </varlistentry> + <varlistentry> + <term>org.exoplatform.services.jcr.impl.core.query.lucene.SystemPropertyRecoveryFilter</term> + <listitem> + <para> + Returns value of system property "<literal>org.exoplatform.jcr.recoveryfilter.forcereindexing</literal>". So index recovery can be controlled from the top without changing documentation using system properties. + </para> - </listitem> + </listitem> - </varlistentry> - <varlistentry> - <term>org.exoplatform.services.jcr.impl.core.query.lucene.ConfigurationPropertyRecoveryFilter</term> - <listitem> - <para> - Returns value of <literal>QueryHandler</literal> configuration property "<literal>index-recovery-filter-forcereindexing</literal>". So index recovery can be controlled from configuration separately for each workspace. For example: - </para> - + </varlistentry> + <varlistentry> + <term>org.exoplatform.services.jcr.impl.core.query.lucene.ConfigurationPropertyRecoveryFilter</term> + <listitem> + <para> + Returns value of <literal>QueryHandler</literal> configuration property "<literal>index-recovery-filter-forcereindexing</literal>". So index recovery can be controlled from configuration separately for each workspace. For example: + </para> + <programlisting language="XML"><property name="index-recovery-filter" value="org.exoplatform.services.jcr.impl.core.query.lucene.ConfigurationPropertyRecoveryFilter" /> <property name="index-recovery-filter-forcereindexing" value="true" /> </programlisting> - </listitem> + </listitem> - </varlistentry> - <varlistentry> - <term>org.exoplatform.services.jcr.impl.core.query.lucene.DocNumberRecoveryFilter</term> - <listitem> - <para> - Checks the number of documents in index on coordinator side and self-side. It returns <literal>true</literal> if the count differs. - </para> - <para> - The advantage of this filter compared to others, is that it will skip reindexing for workspaces where the index was not modified. - </para> - <para> - For example; if there is ten repositories with three workspaces in each and only one is heavily used in the cluster, this filter will only reindex those workspaces that have been changed, without affecting other indexes. - </para> - <para> - This greatly reduces start up time. - </para> + </varlistentry> + <varlistentry> + <term>org.exoplatform.services.jcr.impl.core.query.lucene.DocNumberRecoveryFilter</term> + <listitem> + <para> + Checks the number of documents in index on coordinator side and self-side. It returns <literal>true</literal> if the count differs. + </para> + <para> + The advantage of this filter compared to others, is that it will skip reindexing for workspaces where the index was not modified. + </para> + <para> + For example; if there is ten repositories with three workspaces in each and only one is heavily used in the cluster, this filter will only reindex those workspaces that have been changed, without affecting other indexes. + </para> + <para> + This greatly reduces start up time. + </para> - </listitem> + </listitem> - </varlistentry> + </varlistentry> - </variablelist> + </variablelist> - </section> - - <section id="sect-Reference_Guide-Configuration-JBoss_Cache_template_configuration"> - <title>JBoss-Cache template configuration</title> - <para> - JBoss-Cache template configuration for query handler is about the same for both clustered strategies. - </para> - <example id="exam-Reference_Guide-JBoss_Cache_template_configuration-jbosscache_indexer.xml"> - <title>jbosscache-indexer.xml</title> - + </section> + + <section id="sect-Reference_Guide-Configuration-JBoss_Cache_template_configuration"> + <title>JBoss-Cache template configuration</title> + <para> + JBoss-Cache template configuration for query handler is about the same for both clustered strategies. + </para> + <example id="exam-Reference_Guide-JBoss_Cache_template_configuration-jbosscache_indexer.xml"> + <title>jbosscache-indexer.xml</title> + <programlisting language="XML" role="XML"><?xml version="1.0" encoding="UTF-8"?> <jbosscache xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:jboss:jbosscache-core:config:3.1"> <locking useLockStriping="false" concurrencyLevel="50000" lockParentForChildInsertRemove="false" @@ -419,113 +419,170 @@ </eviction> </jbosscache></programlisting> - </example> - <para> - Read more about template configurations <xref linkend="chap-Reference_Guide-JBoss_Cache_configuration" />. - </para> + </example> + <para> + Read more about template configurations <xref linkend="chap-Reference_Guide-JBoss_Cache_configuration" />. + </para> - </section> - + </section> + - </section> - - <section id="sect-Reference_Guide-QueryHandler_configuration-Asynchronous_Reindexing"> - <title>Asynchronous Reindexing</title> - <para> - Managing a large data set using a JCR in a production environment at times requires special operations with Indexes, stored on File System. One of those maintenance operations is a recreation of it. Also called "re-indexing". There are various usecases when it's important to do. They include hardware faults, hard restarts, data-corruption, migrations and JCR updates that brings new features related to index. Usually index re-creation requested on server's startup or in runtime. - </para> - <section id="sect-Reference_Guide-Asynchronous_Reindexing-On_startup_indexing"> - <title>On startup indexing</title> - <para> - Common usecase for updating and re-creating the index is to stop the server and manually remove indexes for workspaces requiring it. When server will be started, missing indexes are automatically recovered by re-indexing. JCR Supports direct RDBMS re-indexing, that usually is faster than ordinary and can be configured via QueryHandler parameter "rdbms-reindexing" set to "true" (for more information please refer to "Query-handler configuration overview"). New feature to introduce is asynchronous indexing on startup. Usually startup is blocked until process is finished. Block can take any period of time, depending on amount of data persisted in repositories. But this can be resolved by using an asynchronous approaches of startup indexation. Saying briefly, it performs all operations with index in background, without blocking the repository. This is controlled by the value of "async-reindexing" parameter in QueryHandler configuration. With asynchronous indexation active, J! CR starts with no active indexes present. Queries on JCR still can be executed without exceptions, but no results will be returned until index creation completed. Checking index state is possible via QueryManagerImpl: - </para> - <para> - + </section> + + <section id="sect-Reference_Guide-QueryHandler_configuration-Asynchronous_Reindexing"> + <title>Asynchronous Reindexing</title> + <para> + Managing a large data set using a JCR in a production environment at times requires special operations with Indexes, stored on File System. One of those maintenance operations is a recreation of it. Also called "re-indexing". There are various usecases when it's important to do. They include hardware faults, hard restarts, data-corruption, migrations and JCR updates that brings new features related to index. Usually index re-creation requested on server's startup or in runtime. + </para> + <section id="sect-Reference_Guide-Asynchronous_Reindexing-On_startup_indexing"> + <title>On startup indexing</title> + <para> + A common usecase for updating and re-creating the index is to stop the server and manually remove indexes for workspaces requiring it. When the server is re-started, the missing indexes are automatically recovered by re-indexing. + </para> + <para> + The eXo JCR Supports direct RDBMS re-indexing, which can be faster than ordinary and can be configured via <literal>QueryHandler</literal> parameter <parameter>rdbms-reindexing</parameter> set to <literal>true</literal>. + </para> + <para> + A new feature is asynchronous indexing on startup. Usually startup is blocked until the indexing process is finished. This block can take any period of time, depending on amount of data persisted in repositories. But this can be resolved by using an asynchronous approaches of startup indexation. + </para> + <para> + Essentially, all indexing operations are performed in the background without blocking the repository. This is controlled by the value of the <parameter>async-reindexing</parameter> parameter in <literal>QueryHandler</literal> configuration. + </para> + <para> + With asynchronous indexation active, the JCR starts with no active indexes present. Queries on JCR still can be executed without exceptions, but no results will be returned until index creation completed. + </para> + <para> + The index state check is accomplished via <literal>QueryManagerImpl</literal>: + </para> + <para> + <programlisting lang="java">boolean online = ((QueryManagerImpl)Workspace.getQueryManager()).getQueryHandeler().isOnline();</programlisting> - </para> - <para> - "OFFLINE" state means that index is currently re-creating. When state changed, corresponding log event is printed. From the start of background task index is switched to "OFFLINE", with following log event : - </para> - + </para> + <para> + The <emphasis role="bold">OFFLINE</emphasis> state means that the index is currently re-creating. When the state is changed, a corresponding log event is printed. When the background index task starts the index is switched to <emphasis role="bold">OFFLINE</emphasis>, with following log event : + </para> + <programlisting>[INFO] Setting index OFFLINE (repository/production[system]).</programlisting> - <para> - When process finished, two events are logged : - </para> - + <para> + When the indexing process is finished, the following two events are logged : + </para> + <programlisting>[INFO] Created initial index for 143018 nodes (repository/production[system]). [INFO] Setting index ONLINE (repository/production[system]).</programlisting> - <para> - Those two log lines indicates the end of process for workspace given in brackets. Calling isOnline() as mentioned above, will also return true. - </para> + <para> + Those two log lines indicates the end of process for workspace given in brackets. Calling isOnline() as mentioned above, will also return true. + </para> - </section> - - <section id="sect-Reference_Guide-Asynchronous_Reindexing-Hot_Asynchronous_Workspace_Reindexing_via_JMX"> - <title>Hot Asynchronous Workspace Reindexing via JMX</title> - <para> - Some hard system faults, error during upgrades, migration issues and some other factors may corrupt the index. Most likely end customers would like the production systems to fix index issues in run-time, without delays and restarts. Current versions of JCR supports "Hot Asynchronous Workspace Reindexing" feature. It allows end-user (Service Administrator) to launch the process in background without stopping or blocking whole application by using any JMX-compatible console (see screenshot below, "JConsole in action"). - </para> - <mediaobject> - <imageobject> - <imagedata align="center" fileref="images/jmx-jconsole.png" /> - </imageobject> + </section> + + <section id="sect-Reference_Guide-Asynchronous_Reindexing-Hot_Asynchronous_Workspace_Reindexing_via_JMX"> + <title>Hot Asynchronous Workspace Reindexing via JMX</title> + <para> + Some hard system faults, errors during upgrades, migration issues and some other factors may corrupt the index. Current versions of JCR supports <emphasis role="bold">Hot Asynchronous Workspace Reindexing</emphasis> feature. It allows Service Administrators to launch the process in background without stopping or blocking the whole application by using any JMX-compatible console. + </para> + <mediaobject> + <imageobject> + <imagedata align="center" fileref="images/eXoJCR/jmx-jconsole.png" /> + </imageobject> - </mediaobject> - <para> - Server can continue working as expected while index is recreated. This depends on the flag "allow queries", passed via JMX interface to reindex operation invocation. If the flag set, then application continues working. But there is one critical limitation the end-users must be aware. Index is frozen while background task is running. It meant that queries are performed on index present on the moment of task startup and data written into repository after startup won't be available through the search until process finished. Data added during re-indexation is also indexed, but will be available only when task is done. Briefly, JCR makes the snapshot of indexes on asynch task startup and uses it for searches. When operation finished, stale indexes replaced by newly created including newly added data. If flag "allow queries" is set to false, then all queries will throw an exception while task is running. Current state can be acquired using the following JMX operation: - </para> - <itemizedlist> - <listitem> - <para> - getHotReindexingState() - returns information about latest invocation: start time, if in progress or finish time if done. - </para> + </mediaobject> + <para> + The server can continue working as expected while the index is recreated. + </para> + <para> + This depends on the flag <parameter>allow queries</parameter> being passed via JMX interface to the reindex operation invocation. If the flag is set, the application continues working. + </para> + <para> + However, there is one critical limitation users must be aware of; <emphasis>the index is frozen while the background task is running</emphasis>. + </para> + <para> + This means that queries are performed on a version of the index present at the moment the indexing task is started, and that data written into the repository after startup will not be available through the search until process completes. + </para> + <para> + Data added during re-indexation is also indexed, but will be available only when reindexing is complete. The JCR makes a snapshot of indexes at the invocation of the asynchronous indexing task and uses that snapshot for searches. + </para> + <para> + When the operation is finished, the stale index is replaced by the newly created index, which included any newly added data. + </para> + <para> + If the <parameter>allow queries</parameter> flag is set to <literal>false</literal>, then all queries will throw an exception while task is running. The current state can be acquired using the following JMX operation: + </para> + <itemizedlist> + <listitem> + <para> + getHotReindexingState() - returns information about latest invocation: start time, if in progress or finish time if done. + </para> - </listitem> + </listitem> - </itemizedlist> + </itemizedlist> - </section> - - <section id="sect-Reference_Guide-Asynchronous_Reindexing-Notices"> - <title>Notices</title> - <para> - First of all, can't launch Hot re-indexing via JMX if index is already in offline mode. It means that index is currently is invoked in some operations, like re-indexing at startup, copying in cluster to another node or whatever. Another important this is Hot Asynchronous Reindexing via JMX and "on startup" reindexing are completely different features. So you can't get the state of startup reindexing using command getHotReindexingState in JMX interface, but there are some common JMX operations: - </para> - <itemizedlist> - <listitem> - <para> - getIOMode - returns current index IO mode (READ_ONLY / READ_WRITE), belongs to clustered configuration states; - </para> + </section> + + <section id="sect-Reference_Guide-Asynchronous_Reindexing-Notices"> + <title>Notices</title> + <para> + Hot re-indexing via JMX cannot be launched if the index is already in offline mode. This means that the index is currently involved in some other operations, such as re-indexing at startup, copying in cluster to another node or whatever. + </para> + <para> + Also; <emphasis>Hot Asynchronous Reindexing via JMX</emphasis> and <literal>on startup</literal> reindexing are different features. So you can't get the state of startup reindexing using command <code>getHotReindexingState</code> in JMX interface, but there are some common JMX operations: + </para> + <itemizedlist> + <listitem> + <para> + getIOMode - returns current index IO mode (READ_ONLY / READ_WRITE), belongs to clustered configuration states; + </para> - </listitem> - <listitem> - <para> - getState - returns current state: ONLINE / OFFLINE. - </para> + </listitem> + <listitem> + <para> + getState - returns current state: ONLINE / OFFLINE. + </para> - </listitem> + </listitem> - </itemizedlist> + </itemizedlist> - </section> - + </section> + - </section> - - <section id="sect-Reference_Guide-QueryHandler_configuration-Advanced_tuning"> - <title>Advanced tuning</title> - <section id="sect-Reference_Guide-Advanced_tuning-Lucene_tuning"> - <title>Lucene tuning</title> - <para> - As mentioned above, JCR Indexing is based on Lucene indexing library as underlying search engine. It uses Directories to store index and manages access to index by Lock Factories. By default JCR implementation uses optimal combination of Directory implementation and Lock Factory implementation. When running on OS different from Windows, NIOFSDirectory implementation used. And SimpleFSDirectory for Windows stations. NativeFSLockFactory is an optimal solution for wide variety of cases including clustered environment with NFS shared resources. But those default can be overridden with the help of system properties. There are two properties: "org.exoplatform.jcr.lucene.store.FSDirectoryLockFactoryClass" and "org.exoplatform.jcr.lucene.FSDirectory.class" that are responsible for changing default behavior. First one defines implementation of abstract Lucene LockFactory class and the second one sets implementation class for FSDirectory instances. For more information please ref! er to Lucene documentation. But be sure You know what You are changing. JCR allows end users to change implementation classes of Lucene internals, but doesn't guarantee it's stability and functionality. - </para> + </section> + + <section id="sect-Reference_Guide-QueryHandler_configuration-Advanced_tuning"> + <title>Advanced tuning</title> + <section id="sect-Reference_Guide-Advanced_tuning-Lucene_tuning"> + <title>Lucene tuning</title> + <para> + As mentioned, JCR Indexing is based on the Lucene indexing library as the underlying search engine. It uses Directories to store index and manages access to index by Lock Factories. + </para> + <para> + By default, the JCR implementation uses optimal combination of Directory implementation and Lock Factory implementation. + </para> + <para> + The <literal>SimpleFSDirectory</literal> is used in Windows environments and the <literal>NIOFSDirectory</literal> implementation is used in non-Windows systems. + </para> + <para> + <literal>NativeFSLockFactory</literal> is an optimal solution for a wide variety of cases including clustered environment with NFS shared resources. + </para> + <para> + But those defaults can be overridden in the system properties. + </para> + <para> + Two properties: <literal>org.exoplatform.jcr.lucene.store.FSDirectoryLockFactoryClass</literal> and <literal>org.exoplatform.jcr.lucene.FSDirectory.class</literal> control (and change) the default behavior. + </para> + <para> + The first defines the implementation of abstract Lucene <literal>LockFactory</literal> class and the second sets implementation class for <literal>FSDirectory</literal> instances. + </para> + <para> + For more information, refer to the Lucene documentation. But be careful, for while the JCR allows users to change implementation classes of Lucene internals, it does not guarantee the stability and functionality of those changes. + </para> - </section> - + </section> + - </section> - + </section> + </chapter> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/statistics.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/statistics.xml 2011-12-05 03:51:59 UTC (rev 8190) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/statistics.xml 2011-12-05 04:33:56 UTC (rev 8191) @@ -4,292 +4,293 @@ %BOOK_ENTITIES; ]> <chapter id="chap-Reference_Guide-eXo_JCR_statistics"> - <title>eXo JCR statistics</title> - <section id="sect-Reference_Guide-eXo_JCR_statistics-Statistics_on_the_Database_Access_Layer"> - <title>Statistics on the Database Access Layer</title> - <para> - In order to have a better idea of the time spent into the database access layer, it can be interesting to get some statistics on that part of the code, knowing that most of the time spent into eXo JCR is mainly the database access. - </para> - <para> - These statistics will then allow you to identify, without using any profiler, what is abnormally slow in this layer which could help diagnose, and fix, a problem. - </para> - <para> - If you use <envar>org.exoplatform.services.jcr.impl.storage.jdbc.optimisation.CQJDBCWorkspaceDataContainer</envar> or <envar>org.exoplatform.services.jcr.impl.storage.jdbc.JDBCWorkspaceDataContainer</envar> as <envar>WorkspaceDataContainer</envar>, you can get statistics on the time spent into the database access layer. - </para> - <para> - The database access layer (in eXo JCR) is represented by the methods of the interface <envar>org.exoplatform.services.jcr.storage.WorkspaceStorageConnection</envar>, so for all the methods defined in this interface, we can have the following figures: - </para> - <itemizedlist> - <listitem> - <para> - The minimum time spent into the method. - </para> + <title>eXo JCR statistics</title> + <section id="sect-Reference_Guide-eXo_JCR_statistics-Statistics_on_the_Database_Access_Layer"> + <title>Statistics on the Database Access Layer</title> + <para> + In order to have a better idea of the time spent into the database access layer, it can be interesting to get some statistics on that part of the code, knowing that most of the time spent into eXo JCR is mainly the database access. + </para> + <para> + These statistics will then allow you to identify, without using any profiler, what is abnormally slow in this layer which could help diagnose, and fix, a problem. + </para> + <para> + If you use <envar>org.exoplatform.services.jcr.impl.storage.jdbc.optimisation.CQJDBCWorkspaceDataContainer</envar> or <envar>org.exoplatform.services.jcr.impl.storage.jdbc.JDBCWorkspaceDataContainer</envar> as <envar>WorkspaceDataContainer</envar>, you can get statistics on the time spent into the database access layer. + </para> + <para> + The database access layer (in eXo JCR) is represented by the methods of the interface <envar>org.exoplatform.services.jcr.storage.WorkspaceStorageConnection</envar>, so for all the methods defined in this interface, we can have the following figures: + </para> + <itemizedlist> + <listitem> + <para> + The minimum time spent into the method. + </para> - </listitem> - <listitem> - <para> - The maximum time spent into the method. - </para> + </listitem> + <listitem> + <para> + The maximum time spent into the method. + </para> - </listitem> - <listitem> - <para> - The average time spent into the method. - </para> + </listitem> + <listitem> + <para> + The average time spent into the method. + </para> - </listitem> - <listitem> - <para> - The total amount of time spent into the method. - </para> + </listitem> + <listitem> + <para> + The total amount of time spent into the method. + </para> - </listitem> - <listitem> - <para> - The total amount of time the method has been called. - </para> + </listitem> + <listitem> + <para> + The total amount of time the method has been called. + </para> - </listitem> + </listitem> - </itemizedlist> - <para> - Those figures are also available globaly for all the methods which gives us the global behavior of this layer. - </para> - <para> - If you want to enable the statistics, you just need to set the JVM parameter called <parameter>JDBCWorkspaceDataContainer.statistics.enabled</parameter> to <emphasis>true</emphasis>. The corresponding CSV file is <filename>StatisticsJDBCStorageConnection-${creation-timestamp}.csv</filename> for more details about how the csv files are managed, please refer to the section dedicated to the statistics manager. - </para> - <para> - The format of each column header is <replaceable>${method-alias}</replaceable>-<replaceable>${metric-alias}</replaceable>. The metric alias are described in the statistics manager section. - </para> - <para> - The name of the category of statistics corresponding to these statistics is <literal>JDBCStorageConnection</literal>, this name is mostly needed to access to the statistics through JMX. - </para> - <table id="tabl-Reference_Guide-Statistics_on_the_Database_Access_Layer-Method_Alias"> - <title>Method Alias</title> - <tgroup cols="2"> - <tbody> - <row> - <entry> - global - </entry> - <entry> - This is the alias for all the methods. - </entry> + </itemizedlist> + <para> + Those figures are also available globaly for all the methods which gives us the global behavior of this layer. + </para> + <para> + If you want to enable the statistics, you just need to set the JVM parameter called <parameter>JDBCWorkspaceDataContainer.statistics.enabled</parameter> to <emphasis>true</emphasis>. The corresponding CSV file is <filename>StatisticsJDBCStorageConnection-${creation-timestamp}.csv</filename> for more details about how the csv files are managed, please refer to the section dedicated to the statistics manager. + </para> + <para> + The format of each column header is <replaceable>${method-alias}</replaceable>-<replaceable>${metric-alias}</replaceable>. The metric alias are described in the statistics manager section. + </para> + <para> + The name of the category of statistics corresponding to these statistics is <literal>JDBCStorageConnection</literal>, this name is mostly needed to access to the statistics through JMX. + </para> + <table id="tabl-Reference_Guide-Statistics_on_the_Database_Access_Layer-Method_Alias"> + <title>Method Alias</title> + <tgroup cols="2"> + <tbody> + <row> + <entry> + global + </entry> + <entry> + This is the alias for all the methods. + </entry> - </row> - <row> - <entry> - getItemDataById - </entry> - <entry> - This is the alias for the method <emphasis>getItemData(String identifier).</emphasis> - </entry> + </row> + <row> + <entry> + getItemDataById + </entry> + <entry> + This is the alias for the method <emphasis>getItemData(String identifier).</emphasis> + </entry> - </row> - <row> - <entry> - getItemDataByNodeDataNQPathEntry - </entry> - <entry> - This is the alias for the method <emphasis>getItemData(NodeData parentData, QPathEntry name).</emphasis> - </entry> + </row> + <row> + <entry> + getItemDataByNodeDataNQPathEntry + </entry> + <entry> + This is the alias for the method <emphasis>getItemData(NodeData parentData, QPathEntry name).</emphasis> + </entry> - </row> - <row> - <entry> - getChildNodesData - </entry> - <entry> - This is the alias for the method <emphasis>getChildNodesData(NodeData parent).</emphasis> - </entry> + </row> + <row> + <entry> + getChildNodesData + </entry> + <entry> + This is the alias for the method <emphasis>getChildNodesData(NodeData parent).</emphasis> + </entry> - </row> - <row> - <entry> - getChildNodesCount - </entry> - <entry> - This is the alias for the method <emphasis>getChildNodesCount(NodeData parent).</emphasis> - </entry> + </row> + <row> + <entry> + getChildNodesCount + </entry> + <entry> + This is the alias for the method <emphasis>getChildNodesCount(NodeData parent).</emphasis> + </entry> - </row> - <row> - <entry> - getChildPropertiesData - </entry> - <entry> - This is the alias for the method <emphasis>getChildPropertiesData(NodeData parent).</emphasis> - </entry> + </row> + <row> + <entry> + getChildPropertiesData + </entry> + <entry> + This is the alias for the method <emphasis>getChildPropertiesData(NodeData parent).</emphasis> + </entry> - </row> - <row> - <entry> - listChildPropertiesData - </entry> - <entry> - This is the alias for the method <emphasis>listChildPropertiesData(NodeData parent).</emphasis> - </entry> + </row> + <row> + <entry> + listChildPropertiesData + </entry> + <entry> + This is the alias for the method <emphasis>listChildPropertiesData(NodeData parent).</emphasis> + </entry> - </row> - <row> - <entry> - getReferencesData - </entry> - <entry> - This is the alias for the method <emphasis>getReferencesData(String nodeIdentifier).</emphasis> - </entry> + </row> + <row> + <entry> + getReferencesData + </entry> + <entry> + This is the alias for the method <emphasis>getReferencesData(String nodeIdentifier).</emphasis> + </entry> - </row> - <row> - <entry> - commit - </entry> - <entry> - This is the alias for the method <emphasis>commit().</emphasis> - </entry> + </row> + <row> + <entry> + commit + </entry> + <entry> + This is the alias for the method <emphasis>commit().</emphasis> + </entry> - </row> - <row> - <entry> - addNodeData - </entry> - <entry> - This is the alias for the method <emphasis>add(NodeData data).</emphasis> - </entry> + </row> + <row> + <entry> + addNodeData + </entry> + <entry> + This is the alias for the method <emphasis>add(NodeData data).</emphasis> + </entry> - </row> - <row> - <entry> - addPropertyData - </entry> - <entry> - This is the alias for the method <emphasis>add(PropertyData data).</emphasis> - </entry> + </row> + <row> + <entry> + addPropertyData + </entry> + <entry> + This is the alias for the method <emphasis>add(PropertyData data).</emphasis> + </entry> - </row> - <row> - <entry> - updateNodeData - </entry> - <entry> - This is the alias for the method <emphasis>update(NodeData data).</emphasis> - </entry> + </row> + <row> + <entry> + updateNodeData + </entry> + <entry> + This is the alias for the method <emphasis>update(NodeData data).</emphasis> + </entry> - </row> - <row> - <entry> - updatePropertyData - </entry> - <entry> - This is the alias for the method <emphasis>update(PropertyData data).</emphasis> - </entry> + </row> + <row> + <entry> + updatePropertyData + </entry> + <entry> + This is the alias for the method <emphasis>update(PropertyData data).</emphasis> + </entry> - </row> - <row> - <entry> - deleteNodeData - </entry> - <entry> - This is the alias for the method <emphasis>delete(NodeData data).</emphasis> - </entry> + </row> + <row> + <entry> + deleteNodeData + </entry> + <entry> + This is the alias for the method <emphasis>delete(NodeData data).</emphasis> + </entry> - </row> - <row> - <entry> - deletePropertyData - </entry> - <entry> - This is the alias for the method <emphasis>delete(PropertyData data).</emphasis> - </entry> + </row> + <row> + <entry> + deletePropertyData + </entry> + <entry> + This is the alias for the method <emphasis>delete(PropertyData data).</emphasis> + </entry> - </row> - <row> - <entry> - renameNodeData - </entry> - <entry> - This is the alias for the method <emphasis>rename(NodeData data).</emphasis> - </entry> + </row> + <row> + <entry> + renameNodeData + </entry> + <entry> + This is the alias for the method <emphasis>rename(NodeData data).</emphasis> + </entry> - </row> - <row> - <entry> - rollback - </entry> - <entry> - This is the alias for the method <emphasis>rollback().</emphasis> - </entry> + </row> + <row> + <entry> + rollback + </entry> + <entry> + This is the alias for the method <emphasis>rollback().</emphasis> + </entry> - </row> - <row> - <entry> - isOpened - </entry> - <entry> - This is the alias for the method <emphasis>isOpened().</emphasis> - </entry> + </row> + <row> + <entry> + isOpened + </entry> + <entry> + This is the alias for the method <emphasis>isOpened().</emphasis> + </entry> - </row> - <row> - <entry> - close - </entry> - <entry> - This is the alias for the method <emphasis>close().</emphasis> - </entry> + </row> + <row> + <entry> + close + </entry> + <entry> + This is the alias for the method <emphasis>close().</emphasis> + </entry> - </row> + </row> - </tbody> + </tbody> - </tgroup> + </tgroup> - </table> + </table> - </section> - - <section id="sect-Reference_Guide-eXo_JCR_statistics-Statistics_on_the_JCR_API_accesses"> - <title>Statistics on the JCR API accesses</title> - <para> - In order to know exactly how your application uses eXo JCR, it can be interesting to register all the JCR API accesses in order to easily create real life test scenario based on pure JCR calls and also to tune your eXo JCR to better fit your requirements. - </para> - <para> - In order to allow you to specify the configuration which part of eXo JCR needs to be monitored without applying any changes in your code and/or building anything, we choose to rely on the Load-time Weaving proposed by AspectJ. - </para> - <para> - To enable this feature, you will have to add in your classpath the following jar files: - </para> - <itemizedlist> - <listitem> - <para> - <emphasis>exo.jcr.component.statistics-X.Y.Z</emphasis>.jar corresponding to your eXo JCR version that you can get from the jboss maven repository <ulink url="http://repository.jboss.com/maven2/org/exoplatform/jcr/exo.jcr.component....">http://repository.jboss.com/maven2/org/exoplatform/jcr/exo.jcr.component....</ulink>. - </para> + </section> + +  + + <section id="sect-Reference_Guide-eXo_JCR_statistics-Statistics_Manager"> + <title>Statistics Manager</title> + <para> + The statistics manager manages all the statistics provided by eXo JCR, it is responsible of printing the data into the CSV files and also exposing the statistics through JMX and/or Rest. + </para> + <para> + The statistics manager will create all the CSV files for each category of statistics that it manages, the format of those files is <emphasis>Statistics${category-name}-${creation-timestamp}.csv</emphasis>. Those files will be created into the user directory if it is possible otherwise it will create them into the temporary directory. The format of those files is <envar>CSV</envar> (i.e. Comma-Separated Values), one new line will be added regularly (every 5 seconds by default) and one last line will be added at JVM exit. Each line, will be composed of the 5 figures described below for each method and globally for all the methods. + </para> + <para> + <table id="tabl-Reference_Guide-Statistics_Manager-Metric_Alias"> + <title>Metric Alias</title> + <tgroup cols="2"> + <tbody> + <row> + <entry> + Min + </entry> + <entry> + The minimum time spent into the method expressed in milliseconds. + </entry> - </row> - <row> - <entry> - Max - </entry> - <entry> - The maximum time spent into the method expressed in milliseconds. - </entry> + </row> + <row> + <entry> + Max + </entry> + <entry> + The maximum time spent into the method expressed in milliseconds. + </entry> - </row> - <row> - <entry> - Total - </entry> - <entry> - The total amount of time spent into the method expressed in milliseconds. - </entry> + </row> + <row> + <entry> + Total + </entry> + <entry> + The total amount of time spent into the method expressed in milliseconds. + </entry> - </row> - <row> - <entry> - Avg - </entry> - <entry> - The average time spent into the method expressed in milliseconds. - </entry> + </row> + <row> + <entry> + Avg + </entry> + <entry> + The average time spent into the method expressed in milliseconds. + </entry> - </row> - <row> - <entry> - Times - </entry> - <entry> - The total amount of times the method has been called. - </entry> + </row> + <row> + <entry> + Times + </entry> + <entry> + The total amount of times the method has been called. + </entry> - </row> + </row> - </tbody> + </tbody> - </tgroup> + </tgroup> - </table> - You can disable the persistence of the statistics by setting the JVM parameter called <parameter>JCRStatisticsManager.persistence.enabled</parameter> to <literal>false</literal>. It is set to <literal>true</literal> by default. - </para> - <para> - You can also define the period of time between each record (that is, line of data into the file) by setting the JVM parameter called <parameter>JCRStatisticsManager.persistence.timeout</parameter> to your expected value expressed in milliseconds. It is set to <literal>5000</literal> by default. - </para> - <para> - You can also access to the statistics via JMX. The available methods are: - </para> - <para> - <table id="tabl-Reference_Guide-Statistics_Manager-JMX_Methods"> - <title>JMX Methods</title> - <tgroup cols="2"> - <tbody> - <row> - <entry> - getMin - </entry> - <entry> - Give the minimum time spent into the method corresponding to the given category name and statistics name. The expected arguments are the name of the category of statistics (<literal>JDBCStorageConnection</literal> for example) and the name of the expected method or global for the global value. - </entry> + </table> + You can disable the persistence of the statistics by setting the JVM parameter called <parameter>JCRStatisticsManager.persistence.enabled</parameter> to <literal>false</literal>. It is set to <literal>true</literal> by default. + </para> + <para> + You can also define the period of time between each record (that is, line of data into the file) by setting the JVM parameter called <parameter>JCRStatisticsManager.persistence.timeout</parameter> to your expected value expressed in milliseconds. It is set to <literal>5000</literal> by default. + </para> + <para> + You can also access to the statistics via JMX. The available methods are: + </para> + <para> + <table id="tabl-Reference_Guide-Statistics_Manager-JMX_Methods"> + <title>JMX Methods</title> + <tgroup cols="2"> + <tbody> + <row> + <entry> + getMin + </entry> + <entry> + Give the minimum time spent into the method corresponding to the given category name and statistics name. The expected arguments are the name of the category of statistics (<literal>JDBCStorageConnection</literal> for example) and the name of the expected method or global for the global value. + </entry> - </row> - <row> - <entry> - getMax - </entry> - <entry> - Give the maximum time spent into the method corresponding to the given category name and statistics name. The expected arguments are the name of the category of statistics and the name of the expected method or global for the global value. - </entry> + </row> + <row> + <entry> + getMax + </entry> + <entry> + Give the maximum time spent into the method corresponding to the given category name and statistics name. The expected arguments are the name of the category of statistics and the name of the expected method or global for the global value. + </entry> - </row> - <row> - <entry> - getTotal - </entry> - <entry> - Give the total amount of time spent into the method corresponding to the given category name and statistics name. The expected arguments are the name of the category of statistics and the name of the expected method or global for the global value. - </entry> + </row> + <row> + <entry> + getTotal + </entry> + <entry> + Give the total amount of time spent into the method corresponding to the given category name and statistics name. The expected arguments are the name of the category of statistics and the name of the expected method or global for the global value. + </entry> - </row> - <row> - <entry> - getAvg - </entry> - <entry> - Give the average time spent into the method corresponding to the given category name and statistics name. The expected arguments are the name of the category of statistics and the name of the expected method or global for the global value. - </entry> + </row> + <row> + <entry> + getAvg + </entry> + <entry> + Give the average time spent into the method corresponding to the given category name and statistics name. The expected arguments are the name of the category of statistics and the name of the expected method or global for the global value. + </entry> - </row> - <row> - <entry> - getTimes - </entry> - <entry> - Give the total amount of times the method has been called corresponding to the given ,category name and statistics name. The expected arguments are the name of the category of statistics (e.g. JDBCStorageConnection) and the name of the expected method or global for the global value. - </entry> + </row> + <row> + <entry> + getTimes + </entry> + <entry> + Give the total amount of times the method has been called corresponding to the given ,category name and statistics name. The expected arguments are the name of the category of statistics (e.g. JDBCStorageConnection) and the name of the expected method or global for the global value. + </entry> - </row> - <row> - <entry> - reset - </entry> - <entry> - Reset the statistics for the given category name and statistics name. The expected arguments are the name of the category of statistics and the name of the expected method or global for the global value. - </entry> + </row> + <row> + <entry> + reset + </entry> + <entry> + Reset the statistics for the given category name and statistics name. The expected arguments are the name of the category of statistics and the name of the expected method or global for the global value. + </entry> - </row> - <row> - <entry> - resetAll - </entry> - <entry> - Reset all the statistics for the given category name. The expected argument is the name of the category of statistics (e.g. JDBCStorageConnection). - </entry> + </row> + <row> + <entry> + resetAll + </entry> + <entry> + Reset all the statistics for the given category name. The expected argument is the name of the category of statistics (e.g. JDBCStorageConnection). + </entry> - </row> + </row> - </tbody> + </tbody> - </tgroup> + </tgroup> - </table> - The full name of the related MBean is <literal>xo:service=statistic, view=jcr</literal>. - </para> + </table> + The full name of the related MBean is <literal>xo:service=statistic, view=jcr</literal>. + </para> - </section> - + </section> + </chapter>

13 years

1
0
0 / 0

gatein SVN: r8190 - in epp/docs/branches/5.2: Release_Notes/en-US and 2 other directories.

by do-not-reply＠jboss.org

Author: jaredmorgs Date: 2011-12-04 22:51:59 -0500 (Sun, 04 Dec 2011) New Revision: 8190 Added: epp/docs/branches/5.2/Release_Notes/en-US/feature_requests.xml epp/docs/branches/5.2/Release_Notes/en-US/new_features.xml epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/feature_requests.xml epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/needinfo.xml epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/resolved_issues_eXo.xml Modified: epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_Release_Notes.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_issues.xml epp/docs/branches/5.2/Release_Notes/en-US/need_info.xml epp/docs/branches/5.2/Release_Notes/en-US/resolved_issues.xml epp/docs/branches/5.2/Release_Notes/publican.cfg epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Book_Info.xml epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Revision_History.xml epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_Release_Notes.xml epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/known_issues.xml epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/resolved_issues.xml epp/docs/branches/5.2/Site_Publisher/Release_Notes/publican.cfg Log: Added all RElease Note related sections to the EPP Repo for fun and profit Modified: epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_Release_Notes.xml =================================================================== --- epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_Release_Notes.xml 2011-12-02 07:39:27 UTC (rev 8189) +++ epp/docs/branches/5.2/Release_Notes/en-US/5.2.0_Release_Notes.xml 2011-12-05 03:51:59 UTC (rev 8190) @@ -3,54 +3,27 @@ <!ENTITY % BOOK_ENTITIES SYSTEM "5.2.0_Release_Notes.ent"> %BOOK_ENTITIES; ]> -<book> +<book status="draft"> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Book_Info.xml"/> <chapter id="Release_Notes-Introduction"> <title>Introduction</title> <para>JBoss Enterprise Portal Platform offers an intuitive, easy to manage user interface and a proven core infrastructure to enable organizations to quickly build dynamic web sites in a highly reusable way. By bringing the principals of Open Choice to the presentation layer, JBoss Enterprise Portal Platform 5 maximizes existing skills and technology investments. </para> - <para>By integrating proven open source frameworks such as JBoss Seam, Hibernate, Tomcat, and JBoss Cache, JBoss Enterprise Portal Platform takes advantage of innovations in the open source community. As well, </para> + <para>By integrating open source frameworks such as JBoss Seam, Hibernate, Tomcat, and JBoss Cache, JBoss Enterprise Portal Platform takes advantage of innovations in the open source community. </para> <para>JBoss Enterprise Portal Platform &VZ; is fully tested and supported by Red Hat, and is certified to work on many leading enterprise hardware and software products.</para> </chapter> - <chapter> - <title>Upgraded Components</title> - <formalpara> - <title>New Components</title> - <para>The following new components warrant special mention.</para> - </formalpara> - <variablelist> - <varlistentry> - <term>Site Migration Utilities</term> - <listitem> - <para>This new functionality is designed to improve the experience of managing unique sites or groups of pages as they progress from the development to production life cycle. The Migration utility has multiple administrative interfaces to support the requirements of different enterprises.</para> - </listitem> - </varlistentry> - <varlistentry> - <term>Site Management Utilities</term> - <listitem> - <para>The new functionality is provided to assist administrators in performing routine tasks. This includes the release of IDM cache, gathering of performance metrics and other processes related to managing the portal server. </para> - </listitem> - </varlistentry> - </variablelist> - <formalpara> - <title>Updated Components</title> - <para>The following updated components warrant special mention.</para> - </formalpara> - <variablelist> - <varlistentry> - <term>Java Content Respostory</term> - <listitem> - <para>This updated release of the eXo Java Content Repository (JCR) has been updated to a newer version designed to improve the performance and scalability of large portal sites. </para> - </listitem> - </varlistentry> - </variablelist> - <note> - <para>For detailed information about component versions included in this release, refer to <xref linkend="Release_Notes-Component_Features"/></para> - </note> + <chapter id="Release_Notes-Installation"> + <title>Installation</title> + <para> + The JBoss Enterprise Portal Platform <citetitle>Installation Guide</citetitle> contains detailed installation instructions as well as environment requirements. + </para> + <para> + The Installation Guide is available in multiple formats from <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/index...." type="http"/>. + </para> </chapter> <chapter id="Release_Notes-Component_Features"> <title>Component Versions </title> - <para><remark>Updated table from https://docspace.corp.redhat.com/docs/DOC-68705 (version 10)</remark></para> + <para><remark>Updated table from https://docspace.corp.redhat.com/docs/DOC-68705 (version 13)</remark></para> <table frame="all" pgwide="1"> <title>Component Versions</title> <tgroup cols="2" colsep="1"> @@ -89,7 +62,7 @@ </row> <row> <entry>Apache Shindig</entry> - <entry>2.0.2</entry> + <entry>2.0.2-CP01</entry> </row> <row> <entry>Simple Captcha</entry> @@ -179,32 +152,64 @@ </tgroup> </table> </chapter> - <chapter id="Release_Notes-Installation"> - <title>Installation</title> - <para> - The JBoss Enterprise Portal Platform <citetitle>Installation Guide</citetitle> contains detailed installation instructions as well as environment requirements. - </para> - <para> - The Installation Guide can be found online at <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/index...." type="http"/>. - </para> + <chapter> + <title>Upgraded Components</title> + <formalpara> + <title>New Components</title> + <para>The following new components warrant special mention.</para> + </formalpara> + <variablelist> + <varlistentry> + <term>Site Migration Utilities</term> + <listitem> + <para>This new functionality is designed to improve the experience of managing unique sites or groups of pages as they progress from the development to production life cycle. The Migration utility has multiple administrative interfaces to support the requirements of different enterprises.</para> + </listitem> + </varlistentry> + <varlistentry> + <term>Site Management Utilities</term> + <listitem> + <para>The new functionality is provided to assist administrators in performing routine tasks. This includes the release of IDM cache, gathering of performance metrics and other processes related to managing the portal server. </para> + </listitem> + </varlistentry> + </variablelist> + <formalpara> + <title>Updated Components</title> + <para>The following updated components warrant special mention.</para> + </formalpara> + <variablelist> + <varlistentry> + <term>Java Content Respostory</term> + <listitem> + <para>This updated release of the eXo Java Content Repository (JCR) has been updated to a newer version designed to improve the performance and scalability of large portal sites. </para> + </listitem> + </varlistentry> + </variablelist> + <note> + <para>For detailed information about component versions included in this release, refer to <xref linkend="Release_Notes-Component_Features"/></para> + </note> </chapter> + <chapter> + <title>New Features</title> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="feature_requests.xml" encoding="XML"/> + </chapter> + <chapter id="Release_Notes-Known_Issues"> + <title>Known Issues </title> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="known_issues.xml" encoding="XML"/> + </chapter> <chapter id="Release_Notes-Issues_Resolved_In_Production"> <title>Resolved Issues </title> <para> The following issues were resolved in this release of JBoss Enterprise Portal Platform. </para> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="resolved_issues.xml"/> </chapter> - <chapter id="Release_Notes-Known_Issues"> - <title>Known Issues </title> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="known_issues.xml" encoding="XML"/> + <chapter> + <title> + <remark>NEEDINFO</remark> + </title> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="need_info.xml"/> </chapter>  <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-736">JBEPP-736</ulink> + </term> + <listitem> + <remark>Assignee is: mposolda</remark> + <remark>JIRA is Closed</remark> + <para> + It is possible to switch portal clusters between UDP and TCP communication modes using a command-line parameter. The -Dgatein.default.jgroups.stack=[tcp | udp] parameter switches EPP clusters (JCR, IDM, MOPSessionManager, NavigationService, DescriptionService) between the two protocols. The functionality is implemented using an adapted, and mutually exclusive implementation of jboss.default.jgroups.stack. + +</para> + <note> + <para>This enhancement is based on, but deliberately independent of, the JBoss Enterprise Application Platform parameter. "jboss.default.jgroups.stack" which supports more values by default than Enterprise Portal Platform currently does. The decision to keep the two parameters separate was for upstream compatibility. + </para> + </note> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-932">JBEPP-932</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + URL handler support is available in this release. The WCM component uses this feature to support locales as part of the URL. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-933">JBEPP-933</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + Performance bottlenecks have been removed when a portal runs with hundreds of navigation nodes. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-934">JBEPP-934</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + In previous releases, navigation node translations had to be managed in language property files. This release allows Navigation nodes to be translated directly through the administration interface. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-937">JBEPP-937</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + It is now possible to define a portlet.xml that describes elements such as filters that need to be applied to all portlets. The file is located in jboss-as/server/[configuration]/conf/gatein/portlet.xml + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-938">JBEPP-938</ulink> + </term> + <listitem> + <remark>Assignee is: mwringe</remark> + <remark>JIRA is Closed</remark> + <para> + This release upgrades Shindig to version 2.0.2. Shindig is used to embed OpenSocial gadgets. Refer to the Component Versions section for the definitive version featured in this release. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-939">JBEPP-939</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + Web service security between WSRP producers and consumers is available in this release. This enhancement allows for encrypted communication and access to authenticated user content over WSRP. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-940">JBEPP-940</ulink> + </term> + <listitem> + <remark>Assignee is: bdaw</remark> + <remark>JIRA is Closed</remark> + <para> + This release makes it possible to configure several LDAP servers containing different users with GateIn. In a ReadOnly scenario, the user is searched in all configured sources. In a ReadWrite scenario, the user is created only in the first configured LDAP server, but obtained from all. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1008">JBEPP-1008</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <warning> + <title>Not Public Yet - RHT+eXo</title> + <para> + Application registry categories are now cached for better performance. + </para> + </warning> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1015">JBEPP-1015</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + Each site can now have a site description, which can be accessed and used by the management applications. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1016">JBEPP-1016</ulink> + </term> + <listitem> + <remark>Assignee is: mwringe</remark> + <remark>JIRA is Closed</remark> + <para> + Priority for the loading of skin css files can now be specified in gatein-resources.xml using the css-priority xml element. This allows the css elements to be loaded in a specific order, which can be useful for overriding existing css elements. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1045">JBEPP-1045</ulink> + </term> + <listitem> + <remark>Assignee is: claprun</remark> + <remark>JIRA is Closed</remark> + <warning> + <title>Not Public Yet - RHT+eXo</title> + <para> + WSRP was previously unavailable for portal extensions. The new WSRP component now properly initializes itself even when started from an extension (as opposed to the default portal container). + </para> + </warning> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1077">JBEPP-1077</ulink> + </term> + <listitem> + <remark>This issue is unassigned!</remark> + <remark>JIRA is Closed</remark> + <para> + The datasource for JCR is now using managed transactions, and required a change in the datasource descriptor. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1078">JBEPP-1078</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + EPP is now partially available in Czech language. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1088">JBEPP-1088</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + When adding a page to a site, pages are displayed in a drop-down list instead of a free form text field. This makes adding pages more intuitive. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1098">JBEPP-1098</ulink> + </term> + <listitem> + <remark>Assignee is: mwringe</remark> + <remark>JIRA is Closed</remark> + <para> + This release of JBoss Enterprise Portal Platform adds a configurable setting to control whether the 'info bar' which surrounds new portlets is displayed by default. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1099">JBEPP-1099</ulink> + </term> + <listitem> + <remark>Assignee is: mposolda</remark> + <remark>JIRA is Closed</remark> + <para> + In this release, the Single Sign On (SSO) component has been enhanced to support FORM authentication for instances where the user can not get access to SSO authentication sessions (such as a Kerberos ticket). Users can now authenticate manually with the portal-specific username and password as a fall-back. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1116">JBEPP-1116</ulink> + </term> + <listitem> + <remark>Assignee is: claprun</remark> + <remark>JIRA is Closed</remark> + <para> + Configuring a page is no longer restricted to local portlets. It is now possible to define remote portlets (WSRP) in page descriptors to populate the base data for the page. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1140">JBEPP-1140</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + In previous releases, the portal did not indicate it had started clearly in the logs. Changes to core portal code now specifies the portal has started in the logs, and includes the portal version number for reference. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1149">JBEPP-1149</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + This release contains enhancements to Gadgets, which, like portlets, can now be integrated on a page definition through XML descriptors. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1158">JBEPP-1158</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + The HTML Document Object Module (DOM) has been optimized to achieve better performance when transmitting markup, and has been simplified for faster rendering on recent web browsers. Older browsers such as Internet Explorer will still work, however performance will be degraded. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1169">JBEPP-1169</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + The Apache Shindig configuration file has been made more accessible to be modified more easily. It is now part of eXoGadgetServer.war/containers/default/container.js + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1197">JBEPP-1197</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + An enhancement to the UserDashboardImpl object now allows dashboard instances to be reused. Dashboards now require less resources to operate correctly. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1210">JBEPP-1210</ulink> + </term> + <listitem> + <remark>Assignee is: mposolda</remark> + <remark>JIRA is Closed</remark> + <para> + Cluster data transportation has been optimized to reduce the number of network connections and threads. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1250">JBEPP-1250</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + When defining navigation in an XML descriptor, it is now possible to define the strategy to apply during startup. It is possible to "conserve", "insert", "merge" or "rewrite" the content previously imported. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1332">JBEPP-1332</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + In this release the default JCR workspace name and system JCR workspace name can now be configured in the configuration.properties file. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1349">JBEPP-1349</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + There was no way to determine the Enterprise Portal Platform version, based on what was displayed when starting the portal. An enhancement to UIFooterPortlet.gtmpl has been implemented, which allows the user to see what portal version is used by mouse-hovering in the site footer. + </para> + </listitem> + </varlistentry> +</variablelist> Modified: epp/docs/branches/5.2/Release_Notes/en-US/known_issues.xml =================================================================== --- epp/docs/branches/5.2/Release_Notes/en-US/known_issues.xml 2011-12-02 07:39:27 UTC (rev 8189) +++ epp/docs/branches/5.2/Release_Notes/en-US/known_issues.xml 2011-12-05 03:51:59 UTC (rev 8190) @@ -5,113 +5,31 @@ <variablelist> -  +  <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1224" /></term> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1352">JBEPP-1352</ulink></term> <listitem> - <remark>This issue is unassigned!</remark> + <remark>Assignee is: hfnukal</remark> - <remark>JIRA is OPEN</remark> + <remark>JIRA is Closed</remark> - <para> - The Services Management Gadget currently has a display issue with the tabs displaying to the left of the table containing the data. This problem presented on Microsoft Internet Explorer 7 on Windows Vista. A fix is being investigated. - </para> + <warning> + <title>Not Public Yet - RHT only</title> + <para> + It was found that JBoss Web Services Native did not properly protect +against recursive entity resolution when processing Document Type +Definitions (DTD). A remote attacker could exploit this flaw by sending a +specially-crafted HTTP POST request to a deployed web service, causing +excessive CPU and memory consumption on the system hosting that service. If +the attack is repeated to consume all available network sockets, the server +will become unavailable. (CVE-2011-1483) + </para> + </warning> </listitem> </varlistentry> -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1236" /></term> - <listitem> - - <remark>Assignee is: mwringe</remark> - - - <remark>JIRA is OPEN</remark> - - - <para> - org.exoplatform.services.cache.impl.jboss.ExoCacheFactoryImpl.createCache runs for both clustered and non-clustered environments. This class registers JBoss Cache to JMX, which produces MBeans for clustered services regardless of whether the clustered services are actively used in the environment. A fix is being investigated. - </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1258" /></term> - <listitem> - - <remark>Assignee is: mwringe</remark> - - - <remark>JIRA is OPEN</remark> - - - <para> - Some CSS issues have been identified with the way the Portal home page is rendered. A fix is being investigated. - </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1271" /></term> - <listitem> - - <remark>This issue is unassigned!</remark> - - - <remark>JIRA is OPEN</remark> - - - <para> - When adding a portlet into a 2-column layout container, the container collapses while dragging the portlet into the container. The container sometimes remains collapsed after moving the portlet into the container. This problem presented on Microsoft Windows 7, using Internet Explorer 8. A fix is being investigated. - </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1345" /></term> - <listitem> - - <remark>This issue is unassigned!</remark> - - - <remark>JIRA is OPEN</remark> - - - <para> - An interface abnormality was discovered in the Account Portlet. If more than one instance of the Account Portlet is present on a page, tabs switching will work in the first portlet as designed. If tab switching is attempted in the other instances, the tab and the content in the portlet flashes temporarily, and the original tab is shown again. A fix is being investigated. - </para> - - </listitem> - </varlistentry> - - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1359" /></term> - <listitem> - - <remark>This issue is unassigned!</remark> - - - <remark>JIRA is OPEN</remark> - - - <para> - Sybase 15.5 imposes a limitation on the case used in portal names. Only lowercase portal names are supported. The problem does not present in Sybase 15.0.3. A fix is being investigated. - </para> - - </listitem> - </varlistentry> - </variablelist> Modified: epp/docs/branches/5.2/Release_Notes/en-US/need_info.xml =================================================================== --- epp/docs/branches/5.2/Release_Notes/en-US/need_info.xml 2011-12-02 07:39:27 UTC (rev 8189) +++ epp/docs/branches/5.2/Release_Notes/en-US/need_info.xml 2011-12-05 03:51:59 UTC (rev 8190) @@ -1,68 +1,4 @@ -<?xml version='1.0'?> -<!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -]> - -<variablelist> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-729" /></term> - <listitem> - - <remark>Assignee is: mposolda</remark> - - - <remark>JIRA is OPEN</remark> - - - <warning> - <title>Not Public Yet - RHT+eXo</title> - <para> - - </para> - </warning> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1125" /></term> - <listitem> - - <remark>Assignee is: prabhat.jha</remark> - - - <remark>JIRA is OPEN</remark> - - - <para> - - </para> - - </listitem> - </varlistentry> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1324" /></term> - <listitem> - - <remark>Assignee is: hfnukal</remark> - - - <remark>JIRA is OPEN</remark> - - - <warning> - <title>Not Public Yet - RHT+eXo</title> - <para> - - </para> - </warning> - - </listitem> - </varlistentry> - -</variablelist> +<para> +There are no issues that require more information at this time. +</para> Added: epp/docs/branches/5.2/Release_Notes/en-US/new_features.xml =================================================================== --- epp/docs/branches/5.2/Release_Notes/en-US/new_features.xml (rev 0) +++ epp/docs/branches/5.2/Release_Notes/en-US/new_features.xml 2011-12-05 03:51:59 UTC (rev 8190) @@ -0,0 +1,117 @@ +<?xml version='1.0'?> +<!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> + + +<variablelist> + +  + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1224" /></term> + <listitem> + + <remark>This issue is unassigned!</remark> + + + <remark>JIRA is OPEN</remark> + + + <para> + The Services Management Gadget currently has a display issue with the tabs displaying to the left of the table containing the data. This problem presented on Microsoft Internet Explorer 7 on Windows Vista. A fix is being investigated. + </para> + + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1236" /></term> + <listitem> + + <remark>Assignee is: mwringe</remark> + + + <remark>JIRA is OPEN</remark> + + + <para> + org.exoplatform.services.cache.impl.jboss.ExoCacheFactoryImpl.createCache runs for both clustered and non-clustered environments. This class registers JBoss Cache to JMX, which produces MBeans for clustered services regardless of whether the clustered services are actively used in the environment. A fix is being investigated. + </para> + + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1258" /></term> + <listitem> + + <remark>Assignee is: mwringe</remark> + + + <remark>JIRA is OPEN</remark> + + + <para> + Some CSS issues have been identified with the way the Portal home page is rendered. A fix is being investigated. + </para> + + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1271" /></term> + <listitem> + + <remark>This issue is unassigned!</remark> + + + <remark>JIRA is OPEN</remark> + + + <para> + When adding a portlet into a 2-column layout container, the container collapses while dragging the portlet into the container. The container sometimes remains collapsed after moving the portlet into the container. This problem presented on Microsoft Windows 7, using Internet Explorer 8. A fix is being investigated. + </para> + + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1345" /></term> + <listitem> + + <remark>This issue is unassigned!</remark> + + + <remark>JIRA is OPEN</remark> + + + <para> + An interface abnormality was discovered in the Account Portlet. If more than one instance of the Account Portlet is present on a page, tabs switching will work in the first portlet as designed. If tab switching is attempted in the other instances, the tab and the content in the portlet flashes temporarily, and the original tab is shown again. A fix is being investigated. + </para> + + </listitem> + </varlistentry> + + +  + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1359" /></term> + <listitem> + + <remark>This issue is unassigned!</remark> + + + <remark>JIRA is OPEN</remark> + + + <para> + Sybase 15.5 imposes a limitation on the case used in portal names. Only lowercase portal names are supported. The problem does not present in Sybase 15.0.3. A fix is being investigated. + </para> + + </listitem> + </varlistentry> + +</variablelist> Modified: epp/docs/branches/5.2/Release_Notes/en-US/resolved_issues.xml =================================================================== --- epp/docs/branches/5.2/Release_Notes/en-US/resolved_issues.xml 2011-12-02 07:39:27 UTC (rev 8189) +++ epp/docs/branches/5.2/Release_Notes/en-US/resolved_issues.xml 2011-12-05 03:51:59 UTC (rev 8190) @@ -1,26 +1,504 @@ -<?xml version='1.0'?> +<?xml version='1.0' encoding='UTF-8'?> <!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> - - <variablelist> - -  - <varlistentry> - <term><ulink url="https://issues.jboss.org/browse/JBEPP-1357" /></term> - <listitem> - - <remark>Assignee is: claprun</remark> - - - <remark>JIRA is Closed</remark> - - - <para> - The Web Servlet for Remote Portlet (WSRP) configuration files for consumers and producers could not be stored in the conf/gatein directory. This resulted in extra configuration complexity for customers when creating the configuration directives for WSRP consumers and producers. The fix implements changes to WSRPServiceIntegration.java that declares the default consumer and producer directive file store as /conf. + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-348">JBEPP-348</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <warning> + <title>Not Public Yet - RHT+eXo</title> + <para> + A Cross-site Scripting (XSS) vulnerability was discovered in the portlet description, which allowed Javascript to be specified in the portlet description through the application registry. The vulnerability has been fixed in this release. + </para> + </warning> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-353">JBEPP-353</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <warning> + <title>Not Public Yet - RHT+eXo</title> + <para> + A Cross-site Scripting (XSS) vulnerability was discovered when adding a portlet to a category. The vulnerability has been fixed in this release. + </para> + </warning> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-631">JBEPP-631</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + Remote Gadgets were not persisting data in category gadgets with more than five categories when the user switched between pages. User data entered in one screen was being lost when the user switched between pages. The fix implements changes to UIForm.js and UIFormCheckBoxInput.java which handles selected values reliably when the user switches between screens. </para> - - </listitem> - </varlistentry> - + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-699">JBEPP-699</ulink> + </term> + <listitem> + <remark>This issue is unassigned!</remark> + <remark>JIRA is Closed</remark> + <para> + A bug in UIUserLanguageSelector caused a problem with dynamically updating the locale when a user selected a different language. The language state had to be saved using the Apply button. The fix introduces changes to locale handling in the affected module which fixes the issue. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-715">JBEPP-715</ulink> + </term> + <listitem> + <remark>This issue is unassigned!</remark> + <remark>JIRA is Closed</remark> + <para> + The page URL conventions in previous versions of JBoss Enterprise Portal Platform did not allow for Portal pages to have the same name. In these instances, pages with identical names were allocated the same URL, with only one page available through it. A change to the way JBoss Enterprise Portal Platform constructs page URLs resolves this issue. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-763">JBEPP-763</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + The platform ships with a resource compressor (CSS and Javascript). Some javascript files were incorrectly compressed and would break unless the developer mode was enabled. Enabling the developer mode introduced performance side-effects. The Javascript compression engine has been replaced, and can be turned off if required, which fixes the issue. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-900">JBEPP-900</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + A bug in the Logo Portlet caused the processAction methods to be called once when the first, valid, processAction method was called to submit the value, and again when the page was rendered. This caused null values to be passed on the second submit. A fix to UILogoPortlet.gtmpl removes the second processAction call issue, which fixes the issue. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-901">JBEPP-901</ulink> + </term> + <listitem> + <remark>Assignee is: bdaw</remark> + <remark>JIRA is Closed</remark> + <warning> + <title>Not Public Yet - RHT+eXo</title> + <para> + When a "root" user (advanced administrative rights) logs onto the portal, part of the logon process calls a query that fetches all the groups from the database. This query was not optimized to handle databases containing very large numbers of groups. When testing with a large group database, the login process took an unacceptable amount of time. The fix implements performance improvements to the query, and provides enhanced caching for large group records. + </para> + </warning> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-903">JBEPP-903</ulink> + </term> + <listitem> + <remark>Assignee is: bdaw</remark> + <remark>JIRA is Closed</remark> + <warning> + <title>Not Public Yet - RHT+eXo</title> + <para> + An issue was identified when the OrganizationManagementPortlet displayed many users from the IDM DB. This caused performance issues, specifically impacting load times for the portlet. The fix implements performance optimizations for specific database queries related to the process. Load time performance is improved for the portlet. + </para> + </warning> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-908">JBEPP-908</ulink> + </term> + <listitem> + <remark>Assignee is: bdaw</remark> + <remark>JIRA is Closed</remark> + <warning> + <title>Not Public Yet - RHT+eXo</title> + <para> + A performance issue in a database query that checked for duplicate emails at user registration caused unacceptable wait times. The larger the user count was in the database, the more pronounced the issue. The fix implements performance optimization in the database query. User registration wait time is improved for portal instances with very large user databases. + </para> + </warning> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-927">JBEPP-927</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + It is not possible to save notes in the TODO gadget when the gadget is placed anywhere except a dashboard. This behavior is expected. A workaround to this issue has been implemented in this version, which allows notes to be entered into this gadget only. Other gadgets still have this issue. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-950">JBEPP-950</ulink> + </term> + <listitem> + <remark>Assignee is: mposolda</remark> + <remark>JIRA is Closed</remark> + <warning> + <title>Not Public Yet - RHT+eXo</title> + <para> + An inefficiency in MOPSessionManager cache was causing unacceptable wait times when an user accessed the portal for the first time, when the portal was idle for an extended period, or when accessing pages that had not been previously cached. The fix implements performance improvements for cases where a portal instance has many pages and navigation nodes, improving overall response time. + </para> + </warning> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-951">JBEPP-951</ulink> + </term> + <listitem> + <remark>Assignee is: mposolda</remark> + <remark>JIRA is Closed</remark> + <warning> + <title>Not Public Yet - RHT+eXo</title> + <para> + Performance issues were discovered in the portal when editing a navigation, or portal page that contained many sub-pages. In some cases, the save action was taking longer than one minute to complete. The fix implements changes to the queries used to retrieve navigation, or portal pages after saving, which improves load times significantly. + </para> + </warning> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-983">JBEPP-983</ulink> + </term> + <listitem> + <remark>Assignee is: claprun</remark> + <remark>JIRA is Closed</remark> + <para> + An inconsistency in how portlets are handled across different part of the administration interface resulted in an error when remote portlets were added to a category from the "Portlet" tab of the Application Registry. The inconsistency has now be resolved and it should be now possible to properly display remote portlets regardless of how they were added to categories. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-985">JBEPP-985</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + DateTimeValidator.java had an unnecessary check where the date input value needed to match the (not localized) DATETIME_REGEX. This superfluous requirement caused localized date input to fail. The fix removes the DATETIME_REGEX, which fixes the issue. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1032">JBEPP-1032</ulink> + </term> + <listitem> + <remark>Assignee is: bdaw</remark> + <remark>JIRA is Closed</remark> + <para> + A bug was discovered where a transaction commit related to IDM database operations was not placed within a final() block. Any misconfiguration, or operation failure, could cause the database connection to remain open. The fix ensures the transaction commit related to IDM database operations is placed within a final() block, which fixes the issue. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1048">JBEPP-1048</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <warning> + <title>Not Public Yet - RHT+eXo</title> + <para> + A Cross-Site Scripting (XSS) vulnerability was discovered in the Edit Page > Container Title field. The vulnerability is fixed in this release. + </para> + </warning> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1049">JBEPP-1049</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <warning> + <title>Not Public Yet - RHT+eXo</title> + <para> + A Cross-site Scripting (XSS) vulnerability was discovered in the New Node label. The vulnerability has been removed in this release. + </para> + </warning> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1050">JBEPP-1050</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <warning> + <title>Not Public Yet - RHT+eXo</title> + <para> + A Cross-site Scripting (XSS) vulnerability was discovered in the RSS reader gadget. The vulnerability has been fixed in this release. + </para> + </warning> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1067">JBEPP-1067</ulink> + </term> + <listitem> + <remark>Assignee is: bdaw</remark> + <remark>JIRA is Closed</remark> + <warning> + <title>Not Public Yet - RHT+eXo</title> + <para> + Only users from the LDAP database were shown in organization management if LDAP did not support sorting. The fix changes the logging level to INFO in PicketLink IDM. + </para> + </warning> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1082">JBEPP-1082</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <warning> + <title>Not Public Yet - RHT+eXo</title> + <para> + If gadget restrict access to specific group, it was accessible for not members in Dashboard and page editing. +Now users cannot add restricted gadget. + </para> + </warning> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1148">JBEPP-1148</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + Activating JRMP configuration in JBoss EPP 5.1.x (or EPP based products) produced a large quantity of JMX/RMI logs in stdout/stderr. The JRMP agent had logging set to FINE, which resulted in verbose log information. The fix removes the embedded logger configuration, which results in the JBoss Enterprise Application Platform server log configuration being used for logging. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1150">JBEPP-1150</ulink> + </term> + <listitem> + <remark>Assignee is: mputz</remark> + <remark>JIRA is Closed</remark> + <para> + An invisible navigation node was displayed in the Sitemap portlet when the parent node was expanded (not with Expand All button). The workaround described in the linked JIRA has been implemented in this release, which corrects the originally reported issue. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1167">JBEPP-1167</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + A problem with regard to the location of token keys prevented Gadgets from working in load-balanced clustered portal environments. Token keys have been moved to a location accessible by all load-balanced clustered portal instances. Gadgets can now be used as intended. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1196">JBEPP-1196</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + A problem with UploadService was causing the MIME type of .rtf files extracted from DiskFileItem in Apache as "text/rtf". The value should have been extracted as "application/rtf", which caused problems for applications dependent on correct MIME type information. The fix corrects the MIME type encoding, and ensures .rtf files are set with the MIME type "application/rtf". + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1221">JBEPP-1221</ulink> + </term> + <listitem> + <remark>Assignee is: mwringe</remark> + <remark>JIRA is Closed</remark> + <para> + A problem with the GroupManagement.java isAdministrator method caused a NullPointerException when the Organization Portlet is placed on a page and an anonymous user tries to access it. The fix changes the behavior of isAdministrator for anonymous users, which fixes the issue. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1241">JBEPP-1241</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <warning> + <title>Not Public Yet - RHT+eXo</title> + <para> + A Cross-site Scripting (XSS) vulnerability was discovered in the UIFormDateTimeInput component. The vulnerability has been fixed in this release. + </para> + </warning> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1243">JBEPP-1243</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <warning> + <title>Not Public Yet - RHT+eXo</title> + <para> + Group descriptions text entered by users was not properly protected from XSS attacks. It was possible to execute arbitrary Javascript if a user had permissions to enter a group description. The group description field has been protected to not execute any Javascript, which resolves the issue. + </para> + </warning> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1293">JBEPP-1293</ulink> + </term> + <listitem> + <remark>Assignee is: kenfinni</remark> + <remark>JIRA is Closed</remark> + <para> + org.jboss.portletbridge.seam.SeamPhaseListenerWrapper.afterPhase() did not correctly handle exceptions. Exceptions that typically occurred during during afterPhase() were truncated (for example StaleObjectStateException in Hibernate commit). The Seam exception handler was not notified of the truncated exceptions therefore the application moves to a next page instead of an error page. The fix ensures org.jboss.portletbridge.seam.SeamPhaseListenerWrapper.afterPhase() catches exceptions and passes them to Seam exception handler (for example, org.jboss.seam.jsf.SeamPhaseListener). Because exceptions are handled correctly, the Seam exception handler displays and error page given the appropriate conditions. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1310">JBEPP-1310</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + If the Opera browser is used to access the portal home page, a Javascript Uncaught exception is raised: "TypeError: 'Browser.setOpacity' is not a function". The fix incorporates a verified customer-submitted patch to Browser.js, which allows Opera browsers to access the portal home page. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1319">JBEPP-1319</ulink> + </term> + <listitem> + <remark>Assignee is: claprun</remark> + <remark>JIRA is Closed</remark> + <para> + If the WSRP consumer was refreshed and activated, WSRP selfv2 prevented the server from starting when it was rebooted. The only way to work around this issue was to perform a force quit. The fix adds a &lt;value-param&gt; configuration option to the main WSRP configuration. consumersInitDelay provides a way to specify a delayed start (configurable, in seconds) of the ConsumerRegistry, which prevents a deadlock situation while the self consumers wait for the producer WSDL to be published. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1324">JBEPP-1324</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <warning> + <title>Not Public Yet - RHT+eXo</title> + <para> + It was found that the invoker servlets, deployed by default via +httpha-invoker, only performed access control on the HTTP GET and POST +methods, allowing remote attackers to make unauthenticated requests by +using different HTTP methods. Due to the second layer of authentication +provided by a security interceptor, this issue is not exploitable on +default installations unless an administrator has misconfigured the +security interceptor or disabled it. (CVE-2011-4085) + </para> + </warning> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1331">JBEPP-1331</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <para> + When a portal host name contained the word "portal" in the name, gadgets were not displayed and a TemplateRuntimeException would occur. The fix adds functionality to several portal components which allows for the word "portal" in the host name. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1336">JBEPP-1336</ulink> + </term> + <listitem> + <remark>Assignee is: theute</remark> + <remark>JIRA is Closed</remark> + <warning> + <title>Not Public Yet - RHT+eXo</title> + <para> + It was found that the GateIn Portal contained verb-specific security constraints. As a result, authentication and authorization were only correctly applied to requests made using the GET and POST HTTP verbs. The GateIn Portal application does not allow a user to trigger any action using HTTP verbs other than POST and GET, so this issue did not expose an exploitable security flaw. As a defence-in-depth measure, the verb-specific security constraints have been removed. Authentication and authorization now correctly apply to requests made using all HTTP verbs. + </para> + </warning> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1351">JBEPP-1351</ulink> + </term> + <listitem> + <remark>Assignee is: hfnukal</remark> + <remark>JIRA is Closed</remark> + <para> + The org.gatein.sso.agent.login.SSOLoginModule contains the common options "portal" and "realmName" as offered in other LoginModule classes. In the packaged gatein-jboss-beans.xml, this login module did not have these options. This caused problems when a customer wanted to implement SSO on a different portal container (for example in ecmdemo). The fix includes these common options in gatein-jboss-beans.xml, which resolves the issue. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1357">JBEPP-1357</ulink> + </term> + <listitem> + <remark>Assignee is: claprun</remark> + <remark>JIRA is Closed</remark> + <para> + The Web Services for Remote Portlet (WSRP) configuration files for consumers and producer were previously only looked for in the WSRP extension archive. This resulted in extra configuration complexity for customers who wanted to edit the configuration directives for WSRP consumers and producer. The fix implements changes to the WSRP integration point that will now also look for WSRP configuration files in the conf/gatein directory of the active JBoss AS profile. + </para> + </listitem> + </varlistentry> + <varlistentry> + <term> + <ulink url="https://issues.jboss.org/browse/JBEPP-1361">JBEPP-1361</ulink> + </term> + <listitem> + <remark>Assignee is: mposolda</remark> + <remark>JIRA is Closed</remark> + <para> + The JBoss Clustered Single Sign On (SSO) Valve must authenticate on all clustered nodes using the same password. The login process in Enterprise Portal Platform differed from normal authentication methods, and customers had to bypass standard authentication by enabling BASIC authentication, or patch login.jsp as described in the Reference Guide. The fix introduces PortalClusteredSSOSupportValve, which removes the patching and workarounds customers had to implement in earlier versions of the product, and increases overall platform security. + </para> + </listitem> + </varlistentry> </variablelist> Modified: epp/docs/branches/5.2/Release_Notes/publican.cfg =================================================================== --- epp/docs/branches/5.2/Release_Notes/publican.cfg 2011-12-02 07:39:27 UTC (rev 8189) +++ epp/docs/branches/5.2/Release_Notes/publican.cfg 2011-12-05 03:51:59 UTC (rev 8190) @@ -4,7 +4,7 @@ xml_lang: en-US type: Book brand: JBoss -#show_remarks: 1 +show_remarks: 1 cvs_branch: DOCS-RHEL-6 cvs_root: :ext:cvs.devel.redhat.com:/cvs/dist cvs_pkg: JBoss_Enterprise_Portal_Platform-5.2.0_BETA_Release_Notes-5.2-web-__LANG__ Modified: epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Book_Info.xml =================================================================== --- epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Book_Info.xml 2011-12-02 07:39:27 UTC (rev 8189) +++ epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Book_Info.xml 2011-12-05 03:51:59 UTC (rev 8190) @@ -4,12 +4,12 @@ %BOOK_ENTITIES; ]> <bookinfo id="arti-Release_Notes-Release_Notes"> - <title>Site Publisher 5.2.0 BETA Release Notes</title> + <title>Site Publisher 5.2.0 Release Notes</title> <subtitle>For the JBoss Enterprise Portal Platform Site Publisher extension.</subtitle> <productname>JBoss Enterprise Portal Platform</productname> <productnumber>5.2</productnumber> <edition>5.2.0</edition> - <pubsnumber>4</pubsnumber> + <pubsnumber>8</pubsnumber> <abstract> <para> These release notes contain important information related to JBoss Site Publisher that may not be currently available in the Product Manuals. Modified: epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Revision_History.xml =================================================================== --- epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Revision_History.xml 2011-12-02 07:39:27 UTC (rev 8189) +++ epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Revision_History.xml 2011-12-05 03:51:59 UTC (rev 8190) @@ -8,8 +8,8 @@ <simpara> <revhistory> <revision> - <revnumber>5.2.0-4</revnumber> - <date>Tue Nov 15 2011</date> + <revnumber>5.2.0-8</revnumber> + <date>Thu Dec 01 2011</date> <author> <firstname>Jared</firstname> <surname>Morgan</surname> @@ -17,10 +17,38 @@ </author> <revdescription> <simplelist> - <member>Release Notes prepared for Enterprise Portal Platform Site Publisher 5.2.0 Beta.</member> + <member>Second Draft of Enterprise Portal Platform 5.2.0 Release Notes with NEEDINFO issues highlighted.</member> </simplelist> </revdescription> </revision> + <revision> + <revnumber>5.2.0-7</revnumber> + <date>Thu Nov 25 2011</date> + <author> + <firstname>Jared</firstname> + <surname>Morgan</surname> + <email>jmorgan at redhat dot com</email> + </author> + <revdescription> + <simplelist> + <member>Draft prepared for Enterprise Portal Platform Site Publisher 5.2.0, with some issues still needinfo. Critical and Blocker Resolved eXo Platform JIRAs <emphasis role="italic">are now included for your enjoyment</emphasis>.</member> + </simplelist> + </revdescription> + </revision> + <revision> + <revnumber>5.2.0-6</revnumber> + <date>Thu Nov 24 2011</date> + <author> + <firstname>Jared</firstname> + <surname>Morgan</surname> + <email>jmorgan at redhat dot com</email> + </author> + <revdescription> + <simplelist> + <member>Draft prepared for Enterprise Portal Platform Site Publisher 5.2.0, with some issues still needinfo. eXo Platform JIRAs have not yet been triaged.</member> + </simplelist> + </revdescription> + </revision> </revhistory> </simpara> </appendix> Modified: epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_Release_Notes.xml =================================================================== --- epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_Release_Notes.xml 2011-12-02 07:39:27 UTC (rev 8189) +++ epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/Site_Publisher_5.2.0_Release_Notes.xml 2011-12-05 03:51:59 UTC (rev 8190) @@ -1,6 +1,6 @@ <?xml version='1.0' encoding='UTF-8'?> <!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 "Site_Publisher_5.2.0_BETA_Release_Notes.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Site_Publisher_5.2.0_Release_Notes.ent"> %BOOK_ENTITIES; ]> <book> @@ -69,6 +69,16 @@ </varlistentry> </variablelist> </chapter> + <chapter> + <title>New Features</title> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="feature_requests.xml" encoding="XML"/> + </chapter> + <chapter id="Release_Notes-Documentation"> + <title>Documentation</title> + <para> + An <citetitle>Installation Guide</citetitle> and a <citetitle>User Guide</citetitle> for JBoss Site Publisher are available at <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/index...." type="http"/>. JBoss Enterprise Portal Platform specific documentation is also available from this location. + </para> + </chapter> <chapter id="Release_Notes-Installation"> <title>Installation</title> <para> @@ -78,35 +88,6 @@ The <citetitle>Installation Guide</citetitle> can be found online at <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/index...." type="http"/>. </para> </chapter> - <chapter id="Release_Notes-Issues_Resolved_In_Production"> - <title>Issues Resolved In Production</title> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="resolved_issues.xml" encoding="XML"/> - </chapter> - <chapter id="Release_Notes-Issues_Resolved_Upstream"> - <title>Issues Resolved Upstream</title> - <para>This release contains Site Publisher issues resolved upstream by eXo Platform. These issues have been verified by the JBoss Enterprise Portal Platform Engineering team and included as part of this release. </para> - </chapter> - <chapter id="Release_Notes-Known_Issues"> - <title>Known Issues</title> - <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="known_issues.xml"/> - </chapter> - <chapter id="Release_Notes-Documentation"> - <title>Documentation</title> - <para> - An <citetitle>Installation Guide</citetitle> and a <citetitle>User Guide</citetitle> for JBoss Site Publisher are available at <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Portal_Platform/index...." type="http"/>. JBoss Enterprise Portal Platform specific documentation is also available from this location. - </para> - </chapter> <chapter id="Release_Notes-_Product_Support_and_License_Website_Links_"> <title> Product Support and License Website Links </title> <formalpara id="form-Release_Notes-_Product_Support_and_License_Website_Links_-Support_Processes"> @@ -152,5 +133,30 @@ </para> </formalpara> </chapter> + <chapter> + <title> + <remark>NEEDINFO</remark> + </title> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="need_info.xml"/> + </chapter> + <chapter id="Release_Notes-Known_Issues"> + <title>Known Issues</title> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="known_issues.xml"/> + </chapter> + <chapter id="Release_Notes-Issues_Resolved_In_Production"> + <title>Issues Resolved In Production</title> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="resolved_issues.xml" encoding="XML"/> + </chapter> + <chapter id="Release_Notes-Issues_Resolved_Upstream"> + <title>Issues Resolved Upstream<remark>Issues Resolved Upstream</remark></title> + <para>This release contains Site Publisher issues resolved upstream by eXo Platform. The following major issues fixed by eXo Platform have been verified by the JBoss Enterprise Portal Platform Engineering team and included as part of this release. </para> + <para><remark>These issues have been pulled out of eXo Platform's JIRA instance using a modified version of JOT. The issues included here are CRITICAL and BLOCKER issues only, due to the sheer volume of issues over the various Site Publisher releases since the last EPP version. </remark></para> + <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="resolved_issues_eXo.xml" encoding="XML"/> + </chapter> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="Revision_History.xml"/> </book> Added: epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/feature_requests.xml =================================================================== --- epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/feature_requests.xml (rev 0) +++ epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/feature_requests.xml 2011-12-05 03:51:59 UTC (rev 8190) @@ -0,0 +1,26 @@ +<?xml version='1.0'?> +<!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> + + +<variablelist> + +  + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1029">JBEPP-1029</ulink></term> + <listitem> + + <remark>Assignee is: theute</remark> + + + <remark>JIRA is Closed</remark> + + + <para> + It is now possible to inject custom Javascript per site the same way it was possible to inject custom stylesheets per site. + </para> + + </listitem> + </varlistentry> + +</variablelist> Modified: epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/known_issues.xml =================================================================== --- epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/known_issues.xml 2011-12-02 07:39:27 UTC (rev 8189) +++ epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/known_issues.xml 2011-12-05 03:51:59 UTC (rev 8190) @@ -1,29 +1,26 @@ -<?xml version='1.0' encoding='UTF-8'?> +<?xml version='1.0'?> <!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> + + <variablelist> - <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1029"/> - </term> - <listitem> - <remark>Assignee is: theute</remark> - <remark>JIRA is OPEN</remark> - <para> - It is not possible to add custom javascript to Site Publisher managed websites. While customers can inject custom CSS into their pages, javascript injection is not available. A fix is being investigated. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term> - <ulink url="https://issues.jboss.org/browse/JBEPP-1362"/> - </term> - <listitem> - <remark>Assignee is: jaredmorgs</remark> - <remark>JIRA is OPEN</remark> - <para> + +  + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1362">JBEPP-1362</ulink></term> + <listitem> + + <remark>Assignee is: jaredmorgs</remark> + + + <remark>JIRA is Closed</remark> + + + <para> A problem has been identified with adding roles as the root user using the User and Group Management interface, when following the instructions in http://community.jboss.org/wiki/GateInwithLDAPinreadonlymode. Investigation is ongoing. </para> - </listitem> - </varlistentry> + + </listitem> + </varlistentry> + </variablelist> Added: epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/needinfo.xml =================================================================== --- epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/needinfo.xml (rev 0) +++ epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/needinfo.xml 2011-12-05 03:51:59 UTC (rev 8190) @@ -0,0 +1,4 @@ + +<para> +There are no issues that require more information at this time. +</para> Modified: epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/resolved_issues.xml =================================================================== --- epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/resolved_issues.xml 2011-12-02 07:39:27 UTC (rev 8189) +++ epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/resolved_issues.xml 2011-12-05 03:51:59 UTC (rev 8190) @@ -1,4 +1,86 @@ +<?xml version='1.0'?> +<!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> -<para> -There are no resolved issues in this release. -</para> + +<variablelist> + +  + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-648">JBEPP-648</ulink></term> + <listitem> + + <remark>This issue is unassigned!</remark> + + + <remark>JIRA is Closed</remark> + + + <warning> + <title>Not Public Yet - RHT+eXo</title> + <para> + A problem with the search filter returned incorrect query results when filter options "Page" and "Document" were selected. Items of both types were returned independently on the options checked. The fix implements searching on SEO page metadata, which corrects the search result issue. + </para> + </warning> + + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-716">JBEPP-716</ulink></term> + <listitem> + + <remark>Assignee is: hfnukal</remark> + + + <remark>JIRA is Closed</remark> + + + <para> + The Add Node button in Navigation Management (Site or Group) always created a new node at the top level, and not as a child of the selected node. This was counter-intuitive behavior and resulted in manual reordering after a node was created. The fix ensures new nodes are created as children of the selected node. + </para> + + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-949">JBEPP-949</ulink></term> + <listitem> + + <remark>Assignee is: smumford</remark> + + + <remark>JIRA is Closed</remark> + + + <warning> + <title>Not Public Yet - RHT+eXo</title> + <para> + Broken Link Detection was mentioned in the user documentation as a feature. It was discovered that this feature was disabled by eXo Platform in Site Publisher. The information was removed from the documentation to ensure customers did not attempt to use a feature that no longer exists. + </para> + </warning> + + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://issues.jboss.org/browse/JBEPP-1154">JBEPP-1154</ulink></term> + <listitem> + + <remark>Assignee is: mputz</remark> + + + <remark>JIRA is Closed</remark> + + + <para> + When an AccessControlException occurred, a stacktrace was logged, however there was no useful information to help identify the root cause of the problem. It was not possible to identify the root cause of the problem from the exception. The AccessControlException now contains details about the cause of the problem. + </para> + + </listitem> + </varlistentry> + +</variablelist> Added: epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/resolved_issues_eXo.xml =================================================================== --- epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/resolved_issues_eXo.xml (rev 0) +++ epp/docs/branches/5.2/Site_Publisher/Release_Notes/en-US/resolved_issues_eXo.xml 2011-12-05 03:51:59 UTC (rev 8190) @@ -0,0 +1,328 @@ +<?xml version='1.0'?> +<!DOCTYPE variablelist PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> + + +<variablelist> + +  + <varlistentry> + <term><ulink url="https://jira.exoplatform.org/browse/ECMS-1878">ECMS-1878</ulink></term> + <listitem> + <para> + Sometimes an Older version of document is shown instead of its last published one in published mode + </para> + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://jira.exoplatform.org/browse/ECMS-1895">ECMS-1895</ulink></term> + <listitem> + <para> + RTF documents edition dialog should provide an upload box instead of the text area + </para> + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://jira.exoplatform.org/browse/ECMS-1948">ECMS-1948</ulink></term> + <listitem> + <para> + SNF_ECMS_03: Draft document is displayed in public mode in CLV + </para> + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://jira.exoplatform.org/browse/ECMS-1952">ECMS-1952</ulink></term> + <listitem> + <para> + Cannot load and merge the bundle + </para> + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://jira.exoplatform.org/browse/ECMS-2201">ECMS-2201</ulink></term> + <listitem> + <para> + InlineEditing in exo:webContent nodetype + </para> + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://jira.exoplatform.org/browse/ECMS-2207">ECMS-2207</ulink></term> + <listitem> + <para> + Startup error after JCR 1.14-CR1 upgrade + </para> + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://jira.exoplatform.org/browse/ECMS-2234">ECMS-2234</ulink></term> + <listitem> + <para> + Date time format should be with correct time zone. + </para> + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://jira.exoplatform.org/browse/ECMS-2275">ECMS-2275</ulink></term> + <listitem> + <para> + When a link is created (multi filling) search returns the document in double + </para> + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://jira.exoplatform.org/browse/ECMS-2333">ECMS-2333</ulink></term> + <listitem> + <para> + Bug in Content Explorer when use Advanced Search + </para> + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://jira.exoplatform.org/browse/ECMS-2422">ECMS-2422</ulink></term> + <listitem> + <para> + CLV: Cannot select a hidden detail page + </para> + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://jira.exoplatform.org/browse/ECMS-2429">ECMS-2429</ulink></term> + <listitem> + <para> + On startup, lucene find more than one item with same uuid + </para> + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://jira.exoplatform.org/browse/ECMS-2478">ECMS-2478</ulink></term> + <listitem> + <para> + WYSIWYG not retaining its value on category selection during Edit + </para> + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://jira.exoplatform.org/browse/ECMS-2501">ECMS-2501</ulink></term> + <listitem> + <para> + WYSIWYG field not retaining its value on category selection in workflow + </para> + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://jira.exoplatform.org/browse/ECMS-2504">ECMS-2504</ulink></term> + <listitem> + <para> + corrupted link in the WYSIWYG field + </para> + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://jira.exoplatform.org/browse/ECMS-2526">ECMS-2526</ulink></term> + <listitem> + <para> + Bug in "View Properties" Component + </para> + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://jira.exoplatform.org/browse/ECMS-2621">ECMS-2621</ulink></term> + <listitem> + <para> + CLV by query : shouldn't see app with Mary + </para> + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://jira.exoplatform.org/browse/ECMS-2660">ECMS-2660</ulink></term> + <listitem> + <para> + Can not go to Space Document after create new Space + </para> + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://jira.exoplatform.org/browse/ECMS-2667">ECMS-2667</ulink></term> + <listitem> + <para> + Return to main form whenever select document in CLV + </para> + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://jira.exoplatform.org/browse/ECMS-2671">ECMS-2671</ulink></term> + <listitem> + <para> + [ECMS] Can not drag & drop node and show alert message + </para> + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://jira.exoplatform.org/browse/ECMS-2698">ECMS-2698</ulink></term> + <listitem> + <para> + java.lang.ArrayIndexOutOfBoundsException appears when process by method splif of class NodeLocation + </para> + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://jira.exoplatform.org/browse/ECMS-2718">ECMS-2718</ulink></term> + <listitem> + <para> + Cannot access Content Explorer portlet + </para> + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://jira.exoplatform.org/browse/ECMS-2734">ECMS-2734</ulink></term> + <listitem> + <para> + Unable to download document from Space/Documents + </para> + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://jira.exoplatform.org/browse/ECMS-2775">ECMS-2775</ulink></term> + <listitem> + <para> + can't access /ecmdemo : Locale classic cannot be parsed + </para> + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://jira.exoplatform.org/browse/ECMS-2794">ECMS-2794</ulink></term> + <listitem> + <para> + JS content is modified when saving on SitesExplorer + </para> + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://jira.exoplatform.org/browse/ECMS-2800">ECMS-2800</ulink></term> + <listitem> + <para> + Unknown error on "Add Drive", can't select applicable views + </para> + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://jira.exoplatform.org/browse/ECMS-2817">ECMS-2817</ulink></term> + <listitem> + <para> + Failing when edit dialogs & views template + </para> + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://jira.exoplatform.org/browse/ECMS-2830">ECMS-2830</ulink></term> + <listitem> + <para> + Cannot login into wcm system + </para> + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://jira.exoplatform.org/browse/ECMS-2834">ECMS-2834</ulink></term> + <listitem> + <para> + Exception when remove a document + </para> + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://jira.exoplatform.org/browse/ECMS-2845">ECMS-2845</ulink></term> + <listitem> + <para> + Incontext editing doesn't work + </para> + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://jira.exoplatform.org/browse/ECMS-2857">ECMS-2857</ulink></term> + <listitem> + <para> + Can't add content/manage contents in Content List portlet + </para> + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://jira.exoplatform.org/browse/ECMS-2873">ECMS-2873</ulink></term> + <listitem> + <para> + Can't save/create a file template + </para> + </listitem> + </varlistentry> + +  + <varlistentry> + <term><ulink url="https://jira.exoplatform.org/browse/ECMS-2899">ECMS-2899</ulink></term> + <listitem> + <para> + [WCM] Do not display folder tree when click Download and Allow Edition + </para> + </listitem> + </varlistentry> + +</variablelist> Modified: epp/docs/branches/5.2/Site_Publisher/Release_Notes/publican.cfg =================================================================== --- epp/docs/branches/5.2/Site_Publisher/Release_Notes/publican.cfg 2011-12-02 07:39:27 UTC (rev 8189) +++ epp/docs/branches/5.2/Site_Publisher/Release_Notes/publican.cfg 2011-12-05 03:51:59 UTC (rev 8190) @@ -4,7 +4,7 @@ xml_lang: en-US type: Book brand: JBoss -#show_remarks: 1 +show_remarks: 1 cvs_branch: DOCS-RHEL-6 cvs_root: :ext:cvs.devel.redhat.com:/cvs/dist cvs_pkg: JBoss_Enterprise_Portal_Platform-Site_Publisher_5.2.0_BETA_Release_Notes-5.2-web-__LANG__

13 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-commits December 2011