November 2011 - gatein-commits - Jboss List Archives

gatein SVN: r8150 - epp/docs/branches/5.2/Reference_Guide/en-US.

by do-not-reply＠jboss.org

Author: smumford Date: 2011-11-27 18:56:55 -0500 (Sun, 27 Nov 2011) New Revision: 8150 Added: epp/docs/branches/5.2/Reference_Guide/en-US/Reference_Guide.xml Log: Adding renamed toplevel xml file Added: epp/docs/branches/5.2/Reference_Guide/en-US/Reference_Guide.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/Reference_Guide.xml (rev 0) +++ epp/docs/branches/5.2/Reference_Guide/en-US/Reference_Guide.xml 2011-11-27 23:56:55 UTC (rev 8150) @@ -0,0 +1,18 @@ +<?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 "Reference_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="modules/Introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="modules/PortalDevelopment.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="modules/PortletDevelopment.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> +  <xi:include href="modules/AuthenticationAndIdentity.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="modules/WSRP.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="modules/Advanced.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + <xi:include href="modules/eXoJCR.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 month

1
0
0 / 0

gatein SVN: r8149 - in epp/portal/tags: EPP_5_2_0_CR02 and 110 other directories.

by do-not-reply＠jboss.org

Author: hfnukal Date: 2011-11-25 15:28:34 -0500 (Fri, 25 Nov 2011) New Revision: 8149 Added: epp/portal/tags/EPP_5_2_0_CR02/ Modified: epp/portal/tags/EPP_5_2_0_CR02/component/application-registry/pom.xml epp/portal/tags/EPP_5_2_0_CR02/component/common/pom.xml epp/portal/tags/EPP_5_2_0_CR02/component/identity/pom.xml epp/portal/tags/EPP_5_2_0_CR02/component/management/pom.xml epp/portal/tags/EPP_5_2_0_CR02/component/pc/pom.xml epp/portal/tags/EPP_5_2_0_CR02/component/pom.xml epp/portal/tags/EPP_5_2_0_CR02/component/portal/pom.xml epp/portal/tags/EPP_5_2_0_CR02/component/resources/pom.xml epp/portal/tags/EPP_5_2_0_CR02/component/scripting/pom.xml epp/portal/tags/EPP_5_2_0_CR02/component/test/core/pom.xml epp/portal/tags/EPP_5_2_0_CR02/component/test/jcr/pom.xml epp/portal/tags/EPP_5_2_0_CR02/component/test/pom.xml epp/portal/tags/EPP_5_2_0_CR02/component/web/api/pom.xml epp/portal/tags/EPP_5_2_0_CR02/component/web/controller/pom.xml epp/portal/tags/EPP_5_2_0_CR02/component/web/pom.xml epp/portal/tags/EPP_5_2_0_CR02/component/web/resources/pom.xml epp/portal/tags/EPP_5_2_0_CR02/component/web/security/pom.xml epp/portal/tags/EPP_5_2_0_CR02/component/web/server/pom.xml epp/portal/tags/EPP_5_2_0_CR02/distribution/jboss-epp/examples/pom.xml epp/portal/tags/EPP_5_2_0_CR02/distribution/jboss-epp/gatein-management/pom.xml epp/portal/tags/EPP_5_2_0_CR02/distribution/jboss-epp/pom.xml epp/portal/tags/EPP_5_2_0_CR02/distribution/jboss-epp/portletbridge/pom.xml epp/portal/tags/EPP_5_2_0_CR02/distribution/jboss-epp/serverAddon/gatein.ear/pom.xml epp/portal/tags/EPP_5_2_0_CR02/distribution/jboss-epp/serverAddon/integration.war/pom.xml epp/portal/tags/EPP_5_2_0_CR02/distribution/jboss-epp/serverAddon/pom.xml epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/exo-core/pom.xml epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/exo-doc/pom.xml epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/exo-jcr/pom.xml epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/exo-junit/pom.xml epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/exo-kernel/pom.xml epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/exo-parent/pom.xml epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/exo-ws/pom.xml epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/gatein-common/pom.xml epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/gatein-dep/pom.xml epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/gatein-examples/pom.xml epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/gatein-management/pom.xml epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/gatein-mop/pom.xml epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/gatein-parent/pom.xml epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/gatein-pc/pom.xml epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/gatein-portal/pom.xml epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/gatein-shindig/pom.xml epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/gatein-simplecaptcha/pom.xml epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/gatein-sso/pom.xml epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/gatein-wci/pom.xml epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/gatein-wsrp/pom.xml epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/jboss-eppsp/pom.xml epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/jboss-picketlink-idm/pom.xml epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/jboss-portletbridge/pom.xml epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/mead.parent/pom.xml epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/pom.xml epp/portal/tags/EPP_5_2_0_CR02/distribution/pom.xml epp/portal/tags/EPP_5_2_0_CR02/examples/extension/config/pom.xml epp/portal/tags/EPP_5_2_0_CR02/examples/extension/ear/pom.xml epp/portal/tags/EPP_5_2_0_CR02/examples/extension/jar/pom.xml epp/portal/tags/EPP_5_2_0_CR02/examples/extension/pom.xml epp/portal/tags/EPP_5_2_0_CR02/examples/extension/war/pom.xml epp/portal/tags/EPP_5_2_0_CR02/examples/pom.xml epp/portal/tags/EPP_5_2_0_CR02/examples/portal/config/pom.xml epp/portal/tags/EPP_5_2_0_CR02/examples/portal/ear/pom.xml epp/portal/tags/EPP_5_2_0_CR02/examples/portal/jar/pom.xml epp/portal/tags/EPP_5_2_0_CR02/examples/portal/pom.xml epp/portal/tags/EPP_5_2_0_CR02/examples/portal/rest-war/pom.xml epp/portal/tags/EPP_5_2_0_CR02/examples/portal/war/pom.xml epp/portal/tags/EPP_5_2_0_CR02/examples/portlets/api/pom.xml epp/portal/tags/EPP_5_2_0_CR02/examples/portlets/jsfhellouser/pom.xml epp/portal/tags/EPP_5_2_0_CR02/examples/portlets/jsphellouser/pom.xml epp/portal/tags/EPP_5_2_0_CR02/examples/portlets/pom.xml epp/portal/tags/EPP_5_2_0_CR02/examples/portlets/simplesthelloworld/pom.xml epp/portal/tags/EPP_5_2_0_CR02/examples/portlets/struts-jpetstore/pom.xml epp/portal/tags/EPP_5_2_0_CR02/examples/skins/pom.xml epp/portal/tags/EPP_5_2_0_CR02/examples/skins/simpleskin/pom.xml epp/portal/tags/EPP_5_2_0_CR02/gadgets/core/pom.xml epp/portal/tags/EPP_5_2_0_CR02/gadgets/eXoGadgets/pom.xml epp/portal/tags/EPP_5_2_0_CR02/gadgets/gwtGadgets/pom.xml epp/portal/tags/EPP_5_2_0_CR02/gadgets/pom.xml epp/portal/tags/EPP_5_2_0_CR02/gadgets/server/pom.xml epp/portal/tags/EPP_5_2_0_CR02/pom.xml epp/portal/tags/EPP_5_2_0_CR02/portlet/dashboard/pom.xml epp/portal/tags/EPP_5_2_0_CR02/portlet/exoadmin/pom.xml epp/portal/tags/EPP_5_2_0_CR02/portlet/pom.xml epp/portal/tags/EPP_5_2_0_CR02/portlet/web/pom.xml epp/portal/tags/EPP_5_2_0_CR02/server/jboss/patch-ear/pom.xml epp/portal/tags/EPP_5_2_0_CR02/server/jboss/patch-ear/src/main/jboss/server/default/deploy/gatein.ear/integration.war/pom.xml epp/portal/tags/EPP_5_2_0_CR02/server/jboss/plugin/pom.xml epp/portal/tags/EPP_5_2_0_CR02/server/jboss/pom.xml epp/portal/tags/EPP_5_2_0_CR02/server/pom.xml epp/portal/tags/EPP_5_2_0_CR02/starter/ear/pom.xml epp/portal/tags/EPP_5_2_0_CR02/starter/jar/pom.xml epp/portal/tags/EPP_5_2_0_CR02/starter/pom.xml epp/portal/tags/EPP_5_2_0_CR02/starter/war/pom.xml epp/portal/tags/EPP_5_2_0_CR02/testsuite/htmlunit-tests/pom.xml epp/portal/tags/EPP_5_2_0_CR02/testsuite/pom.xml epp/portal/tags/EPP_5_2_0_CR02/testsuite/selenium-snifftests/pom.xml epp/portal/tags/EPP_5_2_0_CR02/testsuite/webuibasedsamples/pom.xml epp/portal/tags/EPP_5_2_0_CR02/web/eXoResources/pom.xml epp/portal/tags/EPP_5_2_0_CR02/web/pom.xml epp/portal/tags/EPP_5_2_0_CR02/web/portal/pom.xml epp/portal/tags/EPP_5_2_0_CR02/web/rest/pom.xml epp/portal/tags/EPP_5_2_0_CR02/webui/core/pom.xml epp/portal/tags/EPP_5_2_0_CR02/webui/dashboard/pom.xml epp/portal/tags/EPP_5_2_0_CR02/webui/eXo/pom.xml epp/portal/tags/EPP_5_2_0_CR02/webui/framework/pom.xml epp/portal/tags/EPP_5_2_0_CR02/webui/pom.xml epp/portal/tags/EPP_5_2_0_CR02/webui/portal/pom.xml epp/portal/tags/EPP_5_2_0_CR02/webui/portlet/pom.xml epp/portal/tags/EPP_5_2_0_CR02/wsrp-integration/extension-component/pom.xml epp/portal/tags/EPP_5_2_0_CR02/wsrp-integration/extension-config/pom.xml epp/portal/tags/EPP_5_2_0_CR02/wsrp-integration/extension-ear-as5/pom.xml epp/portal/tags/EPP_5_2_0_CR02/wsrp-integration/extension-ear/pom.xml epp/portal/tags/EPP_5_2_0_CR02/wsrp-integration/extension-war/pom.xml epp/portal/tags/EPP_5_2_0_CR02/wsrp-integration/pom.xml Log: New release EPP 5.2.0.CR02 Property changes on: epp/portal/tags/EPP_5_2_0_CR02 ___________________________________________________________________ Added: svn:ignore + *.iml .idea Added: svn:mergeinfo + /epp/portal/branches/EPP_5_1_0_GA_JBEPP-795:5868 /portal/branches/branch-GTNPORTAL-1592:4868,4875,4894 /portal/branches/branch-GTNPORTAL-1643:5002,5063,5167 /portal/branches/branch-GTNPORTAL-1700:5348,5363,5402,5445 /portal/branches/branch-GTNPORTAL-1731:5622,5644,5668 /portal/branches/branch-GTNPORTAL-1745:5765 /portal/branches/branch-GTNPORTAL-1790:5871 /portal/branches/branch-GTNPORTAL-1822:5943,5952 /portal/branches/branch-GTNPORTAL-1832:6030,6063 /portal/branches/branch-GTNPORTAL-1872:6400,6551 /portal/branches/branch-GTNPORTAL-1921:6603,6771-6772,6774 /portal/branches/branch-GTNPORTAL-1963:6904,6915-6916 /portal/branches/decoupled-webos:6214-6243 /portal/branches/gatein-management:6920-6958 /portal/branches/global-portlet-metadata:6298-6384 /portal/branches/site-describability:6171-6235 /portal/branches/xss:7377-7595,7597 /portal/branches/xss-issues:7350-7351,7358 /portal/trunk:4876,4891,5269,5744,5822,5943,6168,6196,6201-6203,6205-6206,6223,6323,6437,6440,6449,6452,6573,6783-6784,6912-6913,6960,7042,7061,7085,7095,7117,7125,7132-7134,7186,7239,7262,7308,7326,7330-7334,7359,7367,7412,7433,7450,7452,7454,7478,7497,7500,7552,7554-7555,7570-7571,7573,7577,7598,7614-7615,7695-7696,7701-7704,7741,7748,7773,7780,7877,7900,7928,7938,8045,8053,8072 Modified: epp/portal/tags/EPP_5_2_0_CR02/component/application-registry/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/component/application-registry/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/component/application-registry/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -23,7 +23,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.component</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: epp/portal/tags/EPP_5_2_0_CR02/component/common/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/component/common/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/component/common/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -23,7 +23,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.component</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <modelVersion>4.0.0</modelVersion> <artifactId>exo.portal.component.common</artifactId> Modified: epp/portal/tags/EPP_5_2_0_CR02/component/identity/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/component/identity/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/component/identity/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -23,7 +23,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.component</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: epp/portal/tags/EPP_5_2_0_CR02/component/management/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/component/management/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/component/management/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -21,7 +21,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.component</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: epp/portal/tags/EPP_5_2_0_CR02/component/pc/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/component/pc/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/component/pc/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -23,7 +23,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.component</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: epp/portal/tags/EPP_5_2_0_CR02/component/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/component/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/component/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -26,7 +26,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <artifactId>exo.portal.component</artifactId> Modified: epp/portal/tags/EPP_5_2_0_CR02/component/portal/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/component/portal/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/component/portal/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -23,7 +23,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.component</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: epp/portal/tags/EPP_5_2_0_CR02/component/resources/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/component/resources/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/component/resources/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -23,7 +23,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.component</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: epp/portal/tags/EPP_5_2_0_CR02/component/scripting/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/component/scripting/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/component/scripting/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -23,7 +23,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.component</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: epp/portal/tags/EPP_5_2_0_CR02/component/test/core/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/component/test/core/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/component/test/core/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -22,7 +22,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.component.test</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: epp/portal/tags/EPP_5_2_0_CR02/component/test/jcr/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/component/test/jcr/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/component/test/jcr/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -22,7 +22,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.component.test</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: epp/portal/tags/EPP_5_2_0_CR02/component/test/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/component/test/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/component/test/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -22,7 +22,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.component</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: epp/portal/tags/EPP_5_2_0_CR02/component/web/api/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/component/web/api/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/component/web/api/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -21,7 +21,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.component.web</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: epp/portal/tags/EPP_5_2_0_CR02/component/web/controller/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/component/web/controller/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/component/web/controller/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -21,7 +21,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.component.web</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: epp/portal/tags/EPP_5_2_0_CR02/component/web/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/component/web/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/component/web/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -23,7 +23,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.component</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: epp/portal/tags/EPP_5_2_0_CR02/component/web/resources/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/component/web/resources/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/component/web/resources/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -21,7 +21,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.component.web</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: epp/portal/tags/EPP_5_2_0_CR02/component/web/security/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/component/web/security/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/component/web/security/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -21,7 +21,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.component.web</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: epp/portal/tags/EPP_5_2_0_CR02/component/web/server/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/component/web/server/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/component/web/server/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -21,7 +21,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.component.web</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: epp/portal/tags/EPP_5_2_0_CR02/distribution/jboss-epp/examples/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/examples/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/distribution/jboss-epp/examples/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -5,7 +5,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>distribution.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../../pom.xml</relativePath> </parent> Modified: epp/portal/tags/EPP_5_2_0_CR02/distribution/jboss-epp/gatein-management/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/gatein-management/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/distribution/jboss-epp/gatein-management/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -5,7 +5,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>distribution.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../../pom.xml</relativePath> </parent> Modified: epp/portal/tags/EPP_5_2_0_CR02/distribution/jboss-epp/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/distribution/jboss-epp/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -7,7 +7,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>distribution.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <groupId>org.jboss.portal</groupId> Modified: epp/portal/tags/EPP_5_2_0_CR02/distribution/jboss-epp/portletbridge/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/portletbridge/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/distribution/jboss-epp/portletbridge/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -5,7 +5,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>distribution.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../../pom.xml</relativePath> </parent> Modified: epp/portal/tags/EPP_5_2_0_CR02/distribution/jboss-epp/serverAddon/gatein.ear/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/serverAddon/gatein.ear/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/distribution/jboss-epp/serverAddon/gatein.ear/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -5,7 +5,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>distribution.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../../../pom.xml</relativePath> </parent> <artifactId>gatein</artifactId> Modified: epp/portal/tags/EPP_5_2_0_CR02/distribution/jboss-epp/serverAddon/integration.war/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/serverAddon/integration.war/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/distribution/jboss-epp/serverAddon/integration.war/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -4,7 +4,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>distribution.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../../../pom.xml</relativePath> </parent> <artifactId>integration</artifactId> Modified: epp/portal/tags/EPP_5_2_0_CR02/distribution/jboss-epp/serverAddon/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/distribution/jboss-epp/serverAddon/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/distribution/jboss-epp/serverAddon/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -5,7 +5,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>distribution.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../../pom.xml</relativePath> </parent> Modified: epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/exo-core/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/distribution/mead-tools/exo-core/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/exo-core/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -7,7 +7,7 @@ <parent> <groupId>org.exoplatform.portal.mead</groupId> <artifactId>mead.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../mead.parent/pom.xml</relativePath> </parent> Modified: epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/exo-doc/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/distribution/mead-tools/exo-doc/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/exo-doc/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -7,7 +7,7 @@ <parent> <groupId>org.exoplatform.portal.mead</groupId> <artifactId>mead.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../mead.parent/pom.xml</relativePath> </parent> Modified: epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/exo-jcr/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/distribution/mead-tools/exo-jcr/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/exo-jcr/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -7,7 +7,7 @@ <parent> <groupId>org.exoplatform.portal.mead</groupId> <artifactId>mead.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../mead.parent/pom.xml</relativePath> </parent> Modified: epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/exo-junit/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/distribution/mead-tools/exo-junit/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/exo-junit/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -7,7 +7,7 @@ <parent> <groupId>org.exoplatform.portal.mead</groupId> <artifactId>mead.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../mead.parent/pom.xml</relativePath> </parent> Modified: epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/exo-kernel/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/distribution/mead-tools/exo-kernel/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/exo-kernel/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -7,7 +7,7 @@ <parent> <groupId>org.exoplatform.portal.mead</groupId> <artifactId>mead.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../mead.parent/pom.xml</relativePath> </parent> Modified: epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/exo-parent/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/distribution/mead-tools/exo-parent/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/exo-parent/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -7,7 +7,7 @@ <parent> <groupId>org.exoplatform.portal.mead</groupId> <artifactId>mead.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../mead.parent/pom.xml</relativePath> </parent> Modified: epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/exo-ws/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/distribution/mead-tools/exo-ws/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/exo-ws/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -7,7 +7,7 @@ <parent> <groupId>org.exoplatform.portal.mead</groupId> <artifactId>mead.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../mead.parent/pom.xml</relativePath> </parent> Modified: epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/gatein-common/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/distribution/mead-tools/gatein-common/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/gatein-common/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -7,7 +7,7 @@ <parent> <groupId>org.exoplatform.portal.mead</groupId> <artifactId>mead.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../mead.parent/pom.xml</relativePath> </parent> Modified: epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/gatein-dep/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/distribution/mead-tools/gatein-dep/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/gatein-dep/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -7,7 +7,7 @@ <parent> <groupId>org.exoplatform.portal.mead</groupId> <artifactId>mead.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../mead.parent/pom.xml</relativePath> </parent> Modified: epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/gatein-examples/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/distribution/mead-tools/gatein-examples/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/gatein-examples/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -7,7 +7,7 @@ <parent> <groupId>org.exoplatform.portal.mead</groupId> <artifactId>mead.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../mead.parent/pom.xml</relativePath> </parent> Modified: epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/gatein-management/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/distribution/mead-tools/gatein-management/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/gatein-management/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -7,7 +7,7 @@ <parent> <groupId>org.exoplatform.portal.mead</groupId> <artifactId>mead.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../mead.parent/pom.xml</relativePath> </parent> Modified: epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/gatein-mop/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/distribution/mead-tools/gatein-mop/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/gatein-mop/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -7,7 +7,7 @@ <parent> <groupId>org.exoplatform.portal.mead</groupId> <artifactId>mead.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../mead.parent/pom.xml</relativePath> </parent> Modified: epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/gatein-parent/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/distribution/mead-tools/gatein-parent/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/gatein-parent/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -7,7 +7,7 @@ <parent> <groupId>org.exoplatform.portal.mead</groupId> <artifactId>mead.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../mead.parent/pom.xml</relativePath> </parent> Modified: epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/gatein-pc/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/distribution/mead-tools/gatein-pc/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/gatein-pc/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -7,7 +7,7 @@ <parent> <groupId>org.exoplatform.portal.mead</groupId> <artifactId>mead.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../mead.parent/pom.xml</relativePath> </parent> Modified: epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/gatein-portal/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/distribution/mead-tools/gatein-portal/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/gatein-portal/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -7,7 +7,7 @@ <parent> <groupId>org.exoplatform.portal.mead</groupId> <artifactId>mead.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../mead.parent/pom.xml</relativePath> </parent> Modified: epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/gatein-shindig/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/distribution/mead-tools/gatein-shindig/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/gatein-shindig/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -7,7 +7,7 @@ <parent> <groupId>org.exoplatform.portal.mead</groupId> <artifactId>mead.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../mead.parent/pom.xml</relativePath> </parent> Modified: epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/gatein-simplecaptcha/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/distribution/mead-tools/gatein-simplecaptcha/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/gatein-simplecaptcha/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -7,7 +7,7 @@ <parent> <groupId>org.exoplatform.portal.mead</groupId> <artifactId>mead.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../mead.parent/pom.xml</relativePath> </parent> Modified: epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/gatein-sso/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/distribution/mead-tools/gatein-sso/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/gatein-sso/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -7,7 +7,7 @@ <parent> <groupId>org.exoplatform.portal.mead</groupId> <artifactId>mead.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../mead.parent/pom.xml</relativePath> </parent> Modified: epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/gatein-wci/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/distribution/mead-tools/gatein-wci/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/gatein-wci/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -7,7 +7,7 @@ <parent> <groupId>org.exoplatform.portal.mead</groupId> <artifactId>mead.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../mead.parent/pom.xml</relativePath> </parent> Modified: epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/gatein-wsrp/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/distribution/mead-tools/gatein-wsrp/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/gatein-wsrp/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -7,7 +7,7 @@ <parent> <groupId>org.exoplatform.portal.mead</groupId> <artifactId>mead.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../mead.parent/pom.xml</relativePath> </parent> Modified: epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/jboss-eppsp/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/distribution/mead-tools/jboss-eppsp/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/jboss-eppsp/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -7,7 +7,7 @@ <parent> <groupId>org.exoplatform.portal.mead</groupId> <artifactId>mead.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../mead.parent/pom.xml</relativePath> </parent> Modified: epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/jboss-picketlink-idm/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/distribution/mead-tools/jboss-picketlink-idm/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/jboss-picketlink-idm/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -7,7 +7,7 @@ <parent> <groupId>org.exoplatform.portal.mead</groupId> <artifactId>mead.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../mead.parent/pom.xml</relativePath> </parent> Modified: epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/jboss-portletbridge/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/distribution/mead-tools/jboss-portletbridge/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/jboss-portletbridge/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -7,7 +7,7 @@ <parent> <groupId>org.exoplatform.portal.mead</groupId> <artifactId>mead.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../mead.parent/pom.xml</relativePath> </parent> Modified: epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/mead.parent/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/distribution/mead-tools/mead.parent/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/mead.parent/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -6,7 +6,7 @@ <parent> <groupId>org.exoplatform.portal.mead</groupId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <artifactId>mead-tools</artifactId> <relativePath>../pom.xml</relativePath> </parent> Modified: epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/distribution/mead-tools/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/distribution/mead-tools/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -7,7 +7,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>distribution.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <groupId>org.exoplatform.portal.mead</groupId> @@ -55,7 +55,7 @@ </build> <properties> - <gatein.tag>EPP_5.2.0.GA-SNAPSHOT</gatein.tag> + <gatein.tag>EPP_5_2_0_CR02</gatein.tag>   Modified: epp/portal/tags/EPP_5_2_0_CR02/distribution/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/distribution/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/distribution/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -5,7 +5,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <artifactId>distribution.parent</artifactId> Modified: epp/portal/tags/EPP_5_2_0_CR02/examples/extension/config/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/examples/extension/config/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/examples/extension/config/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -23,7 +23,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../../../pom.xml</relativePath> </parent> Modified: epp/portal/tags/EPP_5_2_0_CR02/examples/extension/ear/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/examples/extension/ear/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/examples/extension/ear/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -23,7 +23,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../../../pom.xml</relativePath> </parent> @@ -38,23 +38,23 @@ <dependency> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.sample.extension.config</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </dependency> <dependency> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.sample.extension.jar</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </dependency> <dependency> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.component.web.api</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <scope>provided</scope> </dependency> <dependency> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.sample.extension.war</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <type>war</type> </dependency> </dependencies> Modified: epp/portal/tags/EPP_5_2_0_CR02/examples/extension/jar/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/examples/extension/jar/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/examples/extension/jar/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -23,7 +23,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../../../pom.xml</relativePath> </parent> Modified: epp/portal/tags/EPP_5_2_0_CR02/examples/extension/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/examples/extension/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/examples/extension/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -24,7 +24,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../../pom.xml</relativePath> </parent> Modified: epp/portal/tags/EPP_5_2_0_CR02/examples/extension/war/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/examples/extension/war/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/examples/extension/war/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -23,7 +23,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../../../pom.xml</relativePath> </parent> Modified: epp/portal/tags/EPP_5_2_0_CR02/examples/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/examples/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/examples/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -26,7 +26,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <artifactId>exo.portal.sample</artifactId> Modified: epp/portal/tags/EPP_5_2_0_CR02/examples/portal/config/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/examples/portal/config/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/examples/portal/config/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -23,7 +23,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../../../pom.xml</relativePath> </parent> Modified: epp/portal/tags/EPP_5_2_0_CR02/examples/portal/ear/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/examples/portal/ear/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/examples/portal/ear/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -23,7 +23,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../../../pom.xml</relativePath> </parent> @@ -38,29 +38,29 @@ <dependency> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.sample.portal.config</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </dependency> <dependency> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.sample.portal.jar</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </dependency> <dependency> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.component.web.api</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <scope>provided</scope> </dependency> <dependency> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.sample.portal.war</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <type>war</type> </dependency> <dependency> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.sample.portal.rest-war</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <type>war</type> </dependency> </dependencies> Modified: epp/portal/tags/EPP_5_2_0_CR02/examples/portal/jar/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/examples/portal/jar/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/examples/portal/jar/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -23,7 +23,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../../../pom.xml</relativePath> </parent> Modified: epp/portal/tags/EPP_5_2_0_CR02/examples/portal/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/examples/portal/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/examples/portal/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -24,7 +24,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../../pom.xml</relativePath> </parent> Modified: epp/portal/tags/EPP_5_2_0_CR02/examples/portal/rest-war/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/examples/portal/rest-war/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/examples/portal/rest-war/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -23,7 +23,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../../../pom.xml</relativePath> </parent> Modified: epp/portal/tags/EPP_5_2_0_CR02/examples/portal/war/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/examples/portal/war/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/examples/portal/war/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -23,7 +23,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../../../pom.xml</relativePath> </parent> Modified: epp/portal/tags/EPP_5_2_0_CR02/examples/portlets/api/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/examples/portlets/api/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/examples/portlets/api/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -9,7 +9,7 @@ <parent> <groupId>org.gatein.portal.examples.portlets</groupId> <artifactId>portlets-parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <artifactId>gatein-api</artifactId> Modified: epp/portal/tags/EPP_5_2_0_CR02/examples/portlets/jsfhellouser/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/examples/portlets/jsfhellouser/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/examples/portlets/jsfhellouser/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -9,7 +9,7 @@ <parent> <groupId>org.gatein.portal.examples.portlets</groupId> <artifactId>portlets-parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <artifactId>gatein-jsf-hellouser</artifactId> Modified: epp/portal/tags/EPP_5_2_0_CR02/examples/portlets/jsphellouser/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/examples/portlets/jsphellouser/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/examples/portlets/jsphellouser/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -9,7 +9,7 @@ <parent> <groupId>org.gatein.portal.examples.portlets</groupId> <artifactId>portlets-parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <artifactId>gatein-jsp-hellouser</artifactId> Modified: epp/portal/tags/EPP_5_2_0_CR02/examples/portlets/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/examples/portlets/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/examples/portlets/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -5,7 +5,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../../pom.xml</relativePath> </parent> Modified: epp/portal/tags/EPP_5_2_0_CR02/examples/portlets/simplesthelloworld/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/examples/portlets/simplesthelloworld/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/examples/portlets/simplesthelloworld/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -9,7 +9,7 @@ <parent> <groupId>org.gatein.portal.examples.portlets</groupId> <artifactId>portlets-parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <artifactId>gatein-simplest-helloworld</artifactId> Modified: epp/portal/tags/EPP_5_2_0_CR02/examples/portlets/struts-jpetstore/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/examples/portlets/struts-jpetstore/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/examples/portlets/struts-jpetstore/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -5,7 +5,7 @@ <parent> <groupId>org.gatein.portal.examples.portlets</groupId> <artifactId>portlets-parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <artifactId>struts-jpetstore</artifactId> Modified: epp/portal/tags/EPP_5_2_0_CR02/examples/skins/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/examples/skins/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/examples/skins/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -5,7 +5,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../../pom.xml</relativePath> </parent> Modified: epp/portal/tags/EPP_5_2_0_CR02/examples/skins/simpleskin/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/examples/skins/simpleskin/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/examples/skins/simpleskin/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -25,7 +25,7 @@ <parent> <groupId>org.gatein.portal.examples.skins</groupId> <artifactId>skins-parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <artifactId>gatein-sample-skin</artifactId> Modified: epp/portal/tags/EPP_5_2_0_CR02/gadgets/core/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/gadgets/core/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/gadgets/core/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -14,7 +14,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.gadgets</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <artifactId>exo.portal.gadgets-core</artifactId> Modified: epp/portal/tags/EPP_5_2_0_CR02/gadgets/eXoGadgets/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/gadgets/eXoGadgets/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/gadgets/eXoGadgets/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -23,7 +23,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.gadgets</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: epp/portal/tags/EPP_5_2_0_CR02/gadgets/gwtGadgets/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/gadgets/gwtGadgets/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/gadgets/gwtGadgets/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -28,7 +28,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.gadgets</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <artifactId>exo.portal.gwtGadgets</artifactId> Modified: epp/portal/tags/EPP_5_2_0_CR02/gadgets/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/gadgets/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/gadgets/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -24,7 +24,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <artifactId>exo.portal.gadgets</artifactId> Modified: epp/portal/tags/EPP_5_2_0_CR02/gadgets/server/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/gadgets/server/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/gadgets/server/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -25,7 +25,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.gadgets</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <artifactId>exo.portal.gadgets-server</artifactId> Modified: epp/portal/tags/EPP_5_2_0_CR02/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -31,7 +31,7 @@ <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <packaging>pom</packaging> <name>EPP GateIn - Portal - ${project.version}</name> @@ -75,9 +75,9 @@ </properties> <scm> - <connection>scm:svn:http://anonsvn.jboss.org/repos/gatein/epp/portal/tags/EPP_5.2.0.G...</connection> - <developerConnection>scm:svn:http://svn.jboss.org/repos/gatein/epp/portal/tags/EPP_5.2.0.GA-SN...</developerConnection> - <url>http://fisheye.jboss.org/browse/gatein/epp/portal/tags/EPP_5.2.0.GA-SNAPSHOT</url> + <connection>scm:svn:http://anonsvn.jboss.org/repos/gatein/epp/portal/tags/EPP_5.2.0.CR02</connection> + <developerConnection>scm:svn:http://svn.jboss.org/repos/gatein/epp/portal/tags/EPP_5.2.0.CR02</developerConnection> + <url>http://fisheye.jboss.org/browse/gatein/epp/portal/tags/EPP_5.2.0.CR02</url> </scm> <modules> @@ -464,74 +464,74 @@ <dependency> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.component.common</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </dependency> <dependency> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.component.web</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </dependency> <dependency> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.component.web.controller</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </dependency> <dependency> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.component.web.security</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </dependency> <dependency> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.component.web.server</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </dependency> <dependency> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.component.web.api</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </dependency> <dependency> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.component.web.resources</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </dependency> <dependency> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.component.portal</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </dependency> <dependency> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.component.portal</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <type>test-jar</type> </dependency> <dependency> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.component.pc</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </dependency> <dependency> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.component.identity</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </dependency> <dependency> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.component.identity</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <type>test-jar</type> </dependency> <dependency> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.component.resources</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </dependency> <dependency> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.component.application-registry</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </dependency> <dependency> <groupId>org.exoplatform.portal</groupId> @@ -541,85 +541,85 @@ <dependency> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.component.scripting</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </dependency> <dependency> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.component.management</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </dependency> <dependency> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.webui.framework</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </dependency> <dependency> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.webui.portlet</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </dependency> <dependency> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.webui.portal</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </dependency> <dependency> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.webui.eXo</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </dependency> <dependency> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.webui.core</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </dependency> <dependency> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.webui.dashboard</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </dependency> <dependency> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.gadgets-core</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </dependency> <dependency> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.component.test.core</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </dependency> <dependency> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.component.test.core</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <type>test-jar</type> </dependency> <dependency> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.component.test.jcr</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </dependency> <dependency> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.component.test.jcr</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <type>test-jar</type> </dependency> <dependency> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.component.test.organization</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </dependency> <dependency> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.component.test.organization</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <type>test-jar</type> </dependency> <dependency> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.server.jboss.plugin</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </dependency>  Modified: epp/portal/tags/EPP_5_2_0_CR02/portlet/dashboard/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/portlet/dashboard/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/portlet/dashboard/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -23,7 +23,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.portlet</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: epp/portal/tags/EPP_5_2_0_CR02/portlet/exoadmin/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/portlet/exoadmin/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/portlet/exoadmin/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -23,7 +23,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.portlet</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: epp/portal/tags/EPP_5_2_0_CR02/portlet/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/portlet/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/portlet/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -26,7 +26,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <artifactId>exo.portal.portlet</artifactId> Modified: epp/portal/tags/EPP_5_2_0_CR02/portlet/web/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/portlet/web/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/portlet/web/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -23,7 +23,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.portlet</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: epp/portal/tags/EPP_5_2_0_CR02/server/jboss/patch-ear/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/server/jboss/patch-ear/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/server/jboss/patch-ear/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -23,7 +23,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.server.jboss</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: epp/portal/tags/EPP_5_2_0_CR02/server/jboss/patch-ear/src/main/jboss/server/default/deploy/gatein.ear/integration.war/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/server/jboss/patch-ear/src/main/jboss/server/default/deploy/gatein.ear/integration.war/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/server/jboss/patch-ear/src/main/jboss/server/default/deploy/gatein.ear/integration.war/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -4,7 +4,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <artifactId>exo.portal.packaging.jboss-as.integration</artifactId> <packaging>war</packaging> Modified: epp/portal/tags/EPP_5_2_0_CR02/server/jboss/plugin/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/server/jboss/plugin/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/server/jboss/plugin/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -23,7 +23,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.server.jboss</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: epp/portal/tags/EPP_5_2_0_CR02/server/jboss/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/server/jboss/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/server/jboss/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -26,7 +26,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.server</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <artifactId>exo.portal.server.jboss</artifactId> Modified: epp/portal/tags/EPP_5_2_0_CR02/server/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/server/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/server/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -26,7 +26,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <artifactId>exo.portal.server</artifactId> Modified: epp/portal/tags/EPP_5_2_0_CR02/starter/ear/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/starter/ear/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/starter/ear/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -23,7 +23,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../../pom.xml</relativePath> </parent> @@ -38,7 +38,7 @@ <dependency> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.starter.war</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <type>war</type> </dependency> </dependencies> Modified: epp/portal/tags/EPP_5_2_0_CR02/starter/jar/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/starter/jar/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/starter/jar/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -23,7 +23,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../../pom.xml</relativePath> </parent> Modified: epp/portal/tags/EPP_5_2_0_CR02/starter/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/starter/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/starter/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -24,7 +24,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <artifactId>exo.portal.starter.root</artifactId> Modified: epp/portal/tags/EPP_5_2_0_CR02/starter/war/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/starter/war/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/starter/war/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -23,7 +23,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> <relativePath>../../pom.xml</relativePath> </parent> @@ -51,7 +51,7 @@ <dependency> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.starter.jar</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </dependency> </dependencies> </project> Modified: epp/portal/tags/EPP_5_2_0_CR02/testsuite/htmlunit-tests/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/testsuite/htmlunit-tests/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/testsuite/htmlunit-tests/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -26,7 +26,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.testsuite</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <groupId>org.jboss.gatein</groupId> Modified: epp/portal/tags/EPP_5_2_0_CR02/testsuite/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/testsuite/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/testsuite/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -3,7 +3,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <artifactId>exo.portal.testsuite</artifactId> Modified: epp/portal/tags/EPP_5_2_0_CR02/testsuite/selenium-snifftests/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/testsuite/selenium-snifftests/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/testsuite/selenium-snifftests/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -3,7 +3,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.testsuite</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <artifactId>exo.portal.selenium.snifftests</artifactId> Modified: epp/portal/tags/EPP_5_2_0_CR02/testsuite/webuibasedsamples/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/testsuite/webuibasedsamples/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/testsuite/webuibasedsamples/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -3,7 +3,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.testsuite</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <artifactId>exo.webui.based.samples</artifactId> Modified: epp/portal/tags/EPP_5_2_0_CR02/web/eXoResources/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/web/eXoResources/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/web/eXoResources/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -23,7 +23,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.web</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: epp/portal/tags/EPP_5_2_0_CR02/web/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/web/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/web/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -26,7 +26,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <artifactId>exo.portal.web</artifactId> Modified: epp/portal/tags/EPP_5_2_0_CR02/web/portal/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/web/portal/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/web/portal/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -23,7 +23,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.web</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: epp/portal/tags/EPP_5_2_0_CR02/web/rest/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/web/rest/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/web/rest/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -23,7 +23,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.web</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: epp/portal/tags/EPP_5_2_0_CR02/webui/core/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/webui/core/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/webui/core/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -23,7 +23,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.webui</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: epp/portal/tags/EPP_5_2_0_CR02/webui/dashboard/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/webui/dashboard/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/webui/dashboard/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -23,7 +23,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.webui</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: epp/portal/tags/EPP_5_2_0_CR02/webui/eXo/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/webui/eXo/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/webui/eXo/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -23,7 +23,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.webui</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: epp/portal/tags/EPP_5_2_0_CR02/webui/framework/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/webui/framework/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/webui/framework/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -23,7 +23,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.webui</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: epp/portal/tags/EPP_5_2_0_CR02/webui/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/webui/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/webui/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -26,7 +26,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <artifactId>exo.portal.webui</artifactId> Modified: epp/portal/tags/EPP_5_2_0_CR02/webui/portal/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/webui/portal/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/webui/portal/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -23,7 +23,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.webui</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: epp/portal/tags/EPP_5_2_0_CR02/webui/portlet/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/webui/portlet/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/webui/portlet/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -23,7 +23,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.webui</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: epp/portal/tags/EPP_5_2_0_CR02/wsrp-integration/extension-component/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/wsrp-integration/extension-component/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/wsrp-integration/extension-component/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -26,7 +26,7 @@ <parent> <artifactId>gatein-wsrp-integration-parent</artifactId> <groupId>org.gatein.integration</groupId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <modelVersion>4.0.0</modelVersion> Modified: epp/portal/tags/EPP_5_2_0_CR02/wsrp-integration/extension-config/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/wsrp-integration/extension-config/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/wsrp-integration/extension-config/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -26,7 +26,7 @@ <parent> <artifactId>gatein-wsrp-integration-parent</artifactId> <groupId>org.gatein.integration</groupId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <artifactId>extension-config</artifactId> Modified: epp/portal/tags/EPP_5_2_0_CR02/wsrp-integration/extension-ear/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/wsrp-integration/extension-ear/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/wsrp-integration/extension-ear/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -28,7 +28,7 @@ <parent> <artifactId>gatein-wsrp-integration-parent</artifactId> <groupId>org.gatein.integration</groupId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <artifactId>extension-ear</artifactId> Modified: epp/portal/tags/EPP_5_2_0_CR02/wsrp-integration/extension-ear-as5/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/wsrp-integration/extension-ear-as5/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/wsrp-integration/extension-ear-as5/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -27,7 +27,7 @@ <parent> <groupId>org.gatein.integration</groupId> <artifactId>gatein-wsrp-integration-parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <artifactId>extension-ear-as5</artifactId> Modified: epp/portal/tags/EPP_5_2_0_CR02/wsrp-integration/extension-war/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/wsrp-integration/extension-war/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/wsrp-integration/extension-war/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -27,7 +27,7 @@ <parent> <artifactId>gatein-wsrp-integration-parent</artifactId> <groupId>org.gatein.integration</groupId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <artifactId>extension-war</artifactId> Modified: epp/portal/tags/EPP_5_2_0_CR02/wsrp-integration/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/wsrp-integration/pom.xml 2011-11-25 16:47:21 UTC (rev 8148) +++ epp/portal/tags/EPP_5_2_0_CR02/wsrp-integration/pom.xml 2011-11-25 20:28:34 UTC (rev 8149) @@ -34,7 +34,7 @@ <parent> <groupId>org.exoplatform.portal</groupId> <artifactId>exo.portal.parent</artifactId> - <version>5.2.0.GA-SNAPSHOT</version> + <version>5.2.0.CR02</version> </parent> <description>GateIn WSRP Integration extension parent</description>

13 years, 1 month

1
0
0 / 0

gatein SVN: r8148 - components/wsrp/trunk/wsrp-producer-war/src/main/webapp/WEB-INF/wsdl.

by do-not-reply＠jboss.org

Author: chris.laprun(a)jboss.com Date: 2011-11-25 11:47:21 -0500 (Fri, 25 Nov 2011) New Revision: 8148 Modified: components/wsrp/trunk/wsrp-producer-war/src/main/webapp/WEB-INF/wsdl/wsrp-2.0-types.xsd components/wsrp/trunk/wsrp-producer-war/src/main/webapp/WEB-INF/wsdl/wsrp_v1_types.xsd Log: - GTNWSRP-259: removing schemaLocation from WSRP types XSD doesn't seem to be causing adverse issues and would work without having to add a jax-ws-catalog.xml file in all situations. Modified: components/wsrp/trunk/wsrp-producer-war/src/main/webapp/WEB-INF/wsdl/wsrp-2.0-types.xsd =================================================================== --- components/wsrp/trunk/wsrp-producer-war/src/main/webapp/WEB-INF/wsdl/wsrp-2.0-types.xsd 2011-11-25 16:29:52 UTC (rev 8147) +++ components/wsrp/trunk/wsrp-producer-war/src/main/webapp/WEB-INF/wsdl/wsrp-2.0-types.xsd 2011-11-25 16:47:21 UTC (rev 8148) @@ -33,7 +33,8 @@  - <import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="http://www.w3.org/2001/xml.xsd"/> +  + <import namespace="http://www.w3.org/XML/1998/namespace"/>   Modified: components/wsrp/trunk/wsrp-producer-war/src/main/webapp/WEB-INF/wsdl/wsrp_v1_types.xsd =================================================================== --- components/wsrp/trunk/wsrp-producer-war/src/main/webapp/WEB-INF/wsdl/wsrp_v1_types.xsd 2011-11-25 16:29:52 UTC (rev 8147) +++ components/wsrp/trunk/wsrp-producer-war/src/main/webapp/WEB-INF/wsdl/wsrp_v1_types.xsd 2011-11-25 16:47:21 UTC (rev 8148) @@ -32,7 +32,8 @@  - <import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="http://www.w3.org/2001/xml.xsd"/> +  + <import namespace="http://www.w3.org/XML/1998/namespace"/>

13 years, 1 month

1
0
0 / 0

gatein SVN: r8147 - in components/wsrp/trunk: consumer/src/test/java/org/gatein/wsrp/consumer and 2 other directories.

by do-not-reply＠jboss.org

Author: chris.laprun(a)jboss.com Date: 2011-11-25 11:29:52 -0500 (Fri, 25 Nov 2011) New Revision: 8147 Added: components/wsrp/trunk/consumer/src/test/java/org/gatein/wsrp/test/protocol/v2/behaviors/SupportedOptionsServiceDescriptionBehavior.java Modified: components/wsrp/trunk/consumer/src/main/java/org/gatein/wsrp/consumer/ProducerInfo.java components/wsrp/trunk/consumer/src/test/java/org/gatein/wsrp/consumer/ProducerInfoTestCase.java components/wsrp/trunk/wsrp-producer-war/src/main/java/org/gatein/wsrp/endpoints/v2/ServiceDescriptionEndpoint.java Log: - GTNWSRP-262: several pieces of information (in particular, supportedOptions) from the service description weren't properly transmitted by the producer, nor properly handled on the consumer. :( Modified: components/wsrp/trunk/consumer/src/main/java/org/gatein/wsrp/consumer/ProducerInfo.java =================================================================== --- components/wsrp/trunk/consumer/src/main/java/org/gatein/wsrp/consumer/ProducerInfo.java 2011-11-25 15:23:47 UTC (rev 8146) +++ components/wsrp/trunk/consumer/src/main/java/org/gatein/wsrp/consumer/ProducerInfo.java 2011-11-25 16:29:52 UTC (rev 8147) @@ -882,6 +882,8 @@ Holder<List<String>> supportedOptions = new Holder<List<String>>(); Holder<ExportDescription> exportDescription = new Holder<ExportDescription>(); Holder<Boolean> mayReturnRegistrationState = new Holder<Boolean>(); + final Holder<List<ExtensionDescription>> extensionDescriptions = new Holder<List<ExtensionDescription>>(); + final Holder<List<Extension>> extensions = new Holder<List<Extension>>(); // invocation persistentEndpointInfo.getServiceDescriptionService().getServiceDescription( @@ -892,7 +894,7 @@ requiresRegistration, offeredPortlets, userCategoryDescriptions, - new Holder<List<ExtensionDescription>>(), + extensionDescriptions, windowStateDescriptions, modeDescriptions, requiresInitCookie, @@ -904,13 +906,17 @@ supportedOptions, exportDescription, mayReturnRegistrationState, - new Holder<List<Extension>>()); + extensions); // TODO: fix-me serviceDescription = WSRPTypeFactory.createServiceDescription(requiresRegistration.value); serviceDescription.setRegistrationPropertyDescription(registrationPropertyDescription.value); serviceDescription.setRequiresInitCookie(requiresInitCookie.value); serviceDescription.setResourceList(resourceList.value); + serviceDescription.setSchemaType(schemaTypes.value); + serviceDescription.setExportDescription(exportDescription.value); + serviceDescription.setMayReturnRegistrationState(mayReturnRegistrationState.value); + if (ParameterValidation.existsAndIsNotEmpty(modeDescriptions.value)) { serviceDescription.getCustomModeDescriptions().addAll(modeDescriptions.value); @@ -931,6 +937,22 @@ { serviceDescription.getUserCategoryDescriptions().addAll(userCategoryDescriptions.value); } + if (ParameterValidation.existsAndIsNotEmpty(eventDescriptions.value)) + { + serviceDescription.getEventDescriptions().addAll(eventDescriptions.value); + } + if (ParameterValidation.existsAndIsNotEmpty(extensionDescriptions.value)) + { + serviceDescription.getExtensionDescriptions().addAll(extensionDescriptions.value); + } + if (ParameterValidation.existsAndIsNotEmpty(extensions.value)) + { + serviceDescription.getExtensions().addAll(extensions.value); + } + if (ParameterValidation.existsAndIsNotEmpty(supportedOptions.value)) + { + serviceDescription.getSupportedOptions().addAll(supportedOptions.value); + } return serviceDescription; } Modified: components/wsrp/trunk/consumer/src/test/java/org/gatein/wsrp/consumer/ProducerInfoTestCase.java =================================================================== --- components/wsrp/trunk/consumer/src/test/java/org/gatein/wsrp/consumer/ProducerInfoTestCase.java 2011-11-25 15:23:47 UTC (rev 8146) +++ components/wsrp/trunk/consumer/src/test/java/org/gatein/wsrp/consumer/ProducerInfoTestCase.java 2011-11-25 16:29:52 UTC (rev 8147) @@ -26,12 +26,14 @@ import junit.framework.TestCase; import org.gatein.pc.api.Portlet; import org.gatein.pc.api.PortletInvokerException; +import org.gatein.wsrp.spec.v2.WSRP2Constants; import org.gatein.wsrp.spec.v2.WSRP2ExceptionFactory; import org.gatein.wsrp.test.protocol.v2.BehaviorBackedServiceFactory; import org.gatein.wsrp.test.protocol.v2.PortletManagementBehavior; import org.gatein.wsrp.test.protocol.v2.RegistrationBehavior; import org.gatein.wsrp.test.protocol.v2.ServiceDescriptionBehavior; import org.gatein.wsrp.test.protocol.v2.behaviors.GroupedPortletsServiceDescriptionBehavior; +import org.gatein.wsrp.test.protocol.v2.behaviors.SupportedOptionsServiceDescriptionBehavior; import org.gatein.wsrp.test.support.MockConsumerRegistry; import org.oasis.wsrp.v2.AccessDenied; import org.oasis.wsrp.v2.CookieProtocol; @@ -58,6 +60,7 @@ import javax.xml.namespace.QName; import javax.xml.ws.Holder; import java.util.ArrayList; +import java.util.Collection; import java.util.List; /** @@ -465,6 +468,19 @@ assertEquals(CookieProtocol.PER_GROUP, info.getRequiresInitCookie()); } + public void testSupportedOptions() throws PortletInvokerException + { + ServiceDescriptionBehavior sdb = new SupportedOptionsServiceDescriptionBehavior(); + serviceFactory.getRegistry().setServiceDescriptionBehavior(sdb); + + info.refresh(false); + + final Collection<String> supportedOptions = info.getSupportedOptions(); + assertEquals(2, supportedOptions.size()); + assertTrue(supportedOptions.contains(WSRP2Constants.OPTIONS_EXPORT)); + assertTrue(supportedOptions.contains(WSRP2Constants.OPTIONS_IMPORT)); + } + private static class TestPortletManagementBehavior extends PortletManagementBehavior { Added: components/wsrp/trunk/consumer/src/test/java/org/gatein/wsrp/test/protocol/v2/behaviors/SupportedOptionsServiceDescriptionBehavior.java =================================================================== --- components/wsrp/trunk/consumer/src/test/java/org/gatein/wsrp/test/protocol/v2/behaviors/SupportedOptionsServiceDescriptionBehavior.java (rev 0) +++ components/wsrp/trunk/consumer/src/test/java/org/gatein/wsrp/test/protocol/v2/behaviors/SupportedOptionsServiceDescriptionBehavior.java 2011-11-25 16:29:52 UTC (rev 8147) @@ -0,0 +1,61 @@ +/* + * JBoss, a division of Red Hat + * Copyright 2011, Red Hat Middleware, LLC, and individual + * contributors as indicated by the @authors tag. See the + * copyright.txt in the distribution for a full listing of + * individual contributors. + * + * This is free software; you can redistribute it and/or modify it + * under the terms of the GNU Lesser General Public License as + * published by the Free Software Foundation; either version 2.1 of + * the License, or (at your option) any later version. + * + * This software is distributed in the hope that it will be useful, + * but WITHOUT ANY WARRANTY; without even the implied warranty of + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU + * Lesser General Public License for more details. + * + * You should have received a copy of the GNU Lesser General Public + * License along with this software; if not, write to the Free + * Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA + * 02110-1301 USA, or see the FSF site: http://www.fsf.org. + */ + +package org.gatein.wsrp.test.protocol.v2.behaviors; + +import org.gatein.wsrp.spec.v2.WSRP2Constants; +import org.gatein.wsrp.test.protocol.v2.ServiceDescriptionBehavior; +import org.oasis.wsrp.v2.CookieProtocol; +import org.oasis.wsrp.v2.EventDescription; +import org.oasis.wsrp.v2.ExportDescription; +import org.oasis.wsrp.v2.Extension; +import org.oasis.wsrp.v2.ExtensionDescription; +import org.oasis.wsrp.v2.InvalidRegistration; +import org.oasis.wsrp.v2.ItemDescription; +import org.oasis.wsrp.v2.ModelDescription; +import org.oasis.wsrp.v2.ModelTypes; +import org.oasis.wsrp.v2.ModifyRegistrationRequired; +import org.oasis.wsrp.v2.OperationFailed; +import org.oasis.wsrp.v2.PortletDescription; +import org.oasis.wsrp.v2.RegistrationContext; +import org.oasis.wsrp.v2.ResourceList; +import org.oasis.wsrp.v2.ResourceSuspended; +import org.oasis.wsrp.v2.UserContext; + +import javax.jws.WebParam; +import javax.xml.ws.Holder; +import java.util.ArrayList; +import java.util.List; + +/** @author <a href="mailto:chris.laprun@jboss.com">Chris Laprun</a> */ +public class SupportedOptionsServiceDescriptionBehavior extends ServiceDescriptionBehavior +{ + @Override + public void getServiceDescription(@WebParam(name = "registrationContext", targetNamespace = "urn:oasis:names:tc:wsrp:v2:types") RegistrationContext registrationContext, @WebParam(name = "desiredLocales", targetNamespace = "urn:oasis:names:tc:wsrp:v2:types") List<String> desiredLocales, @WebParam(name = "portletHandles", targetNamespace = "urn:oasis:names:tc:wsrp:v2:types") List<String> portletHandles, @WebParam(name = "userContext", targetNamespace = "urn:oasis:names:tc:wsrp:v2:types") UserContext userContext, @WebParam(name = "requiresRegistration", targetNamespace = "urn:oasis:names:tc:wsrp:v2:types", mode = WebParam.Mode.OUT) Holder<Boolean> requiresRegistration, @WebParam(name = "offeredPortlets", targetNamespace = "urn:oasis:names:tc:wsrp:v2:types", mode = WebParam.Mode.OUT) Holder<List<PortletDescription>> offeredPortlets, @WebParam(name = "userCategoryDescriptions", targetNamespace = "urn:oasis:names:tc:wsrp:v2:types", mode = WebParam.Mode.OUT) Holder<List<ItemDes! cription>> userCategoryDescriptions, @WebParam(name = "extensionDescriptions", targetNamespace = "urn:oasis:names:tc:wsrp:v2:types", mode = WebParam.Mode.OUT) Holder<List<ExtensionDescription>> extensionDescriptions, @WebParam(name = "customWindowStateDescriptions", targetNamespace = "urn:oasis:names:tc:wsrp:v2:types", mode = WebParam.Mode.OUT) Holder<List<ItemDescription>> customWindowStateDescriptions, @WebParam(name = "customModeDescriptions", targetNamespace = "urn:oasis:names:tc:wsrp:v2:types", mode = WebParam.Mode.OUT) Holder<List<ItemDescription>> customModeDescriptions, @WebParam(name = "requiresInitCookie", targetNamespace = "urn:oasis:names:tc:wsrp:v2:types", mode = WebParam.Mode.OUT) Holder<CookieProtocol> requiresInitCookie, @WebParam(name = "registrationPropertyDescription", targetNamespace = "urn:oasis:names:tc:wsrp:v2:types", mode = WebParam.Mode.OUT) Holder<ModelDescription> registrationPropertyDescription, @WebParam(name = "locales", targetNamespace = "urn:! oasis:names:tc:wsrp:v2:types", mode = WebParam.Mode.OUT) Holde! r<List<S tring>> locales, @WebParam(name = "resourceList", targetNamespace = "urn:oasis:names:tc:wsrp:v2:types", mode = WebParam.Mode.OUT) Holder<ResourceList> resourceList, @WebParam(name = "eventDescriptions", targetNamespace = "urn:oasis:names:tc:wsrp:v2:types", mode = WebParam.Mode.OUT) Holder<List<EventDescription>> eventDescriptions, @WebParam(name = "schemaType", targetNamespace = "urn:oasis:names:tc:wsrp:v2:types", mode = WebParam.Mode.OUT) Holder<ModelTypes> schemaType, @WebParam(name = "supportedOptions", targetNamespace = "urn:oasis:names:tc:wsrp:v2:types", mode = WebParam.Mode.OUT) Holder<List<String>> supportedOptions, @WebParam(name = "exportDescription", targetNamespace = "urn:oasis:names:tc:wsrp:v2:types", mode = WebParam.Mode.OUT) Holder<ExportDescription> exportDescription, @WebParam(name = "mayReturnRegistrationState", targetNamespace = "urn:oasis:names:tc:wsrp:v2:types", mode = WebParam.Mode.OUT) Holder<Boolean> mayReturnRegistrationState, @WebParam(name = "extens! ions", targetNamespace = "urn:oasis:names:tc:wsrp:v2:types", mode = WebParam.Mode.OUT) Holder<List<Extension>> extensions) throws InvalidRegistration, ModifyRegistrationRequired, OperationFailed, ResourceSuspended + { + super.getServiceDescription(registrationContext, desiredLocales, portletHandles, userContext, requiresRegistration, offeredPortlets, userCategoryDescriptions, extensionDescriptions, customWindowStateDescriptions, customModeDescriptions, requiresInitCookie, registrationPropertyDescription, locales, resourceList, eventDescriptions, schemaType, supportedOptions, exportDescription, mayReturnRegistrationState, extensions); + supportedOptions.value = new ArrayList<String>(2); + supportedOptions.value.add(WSRP2Constants.OPTIONS_EXPORT); + supportedOptions.value.add(WSRP2Constants.OPTIONS_IMPORT); + } +} Modified: components/wsrp/trunk/wsrp-producer-war/src/main/java/org/gatein/wsrp/endpoints/v2/ServiceDescriptionEndpoint.java =================================================================== --- components/wsrp/trunk/wsrp-producer-war/src/main/java/org/gatein/wsrp/endpoints/v2/ServiceDescriptionEndpoint.java 2011-11-25 15:23:47 UTC (rev 8146) +++ components/wsrp/trunk/wsrp-producer-war/src/main/java/org/gatein/wsrp/endpoints/v2/ServiceDescriptionEndpoint.java 2011-11-25 16:29:52 UTC (rev 8147) @@ -1,6 +1,6 @@ /* * JBoss, a division of Red Hat - * Copyright 2010, Red Hat Middleware, LLC, and individual + * Copyright 2011, Red Hat Middleware, LLC, and individual * contributors as indicated by the @authors tag. See the * copyright.txt in the distribution for a full listing of * individual contributors. @@ -62,7 +62,7 @@ wsdlLocation = "/WEB-INF/wsdl/wsrp-2.0-services.wsdl", endpointInterface = "org.oasis.wsrp.v2.WSRPV2ServiceDescriptionPortType" ) -@HandlerChain(file="../producer-handler-chains.xml") +@HandlerChain(file = "../producer-handler-chains.xml") public class ServiceDescriptionEndpoint extends WSRPBaseEndpoint implements WSRPV2ServiceDescriptionPortType { public void getServiceDescription( @@ -98,12 +98,18 @@ offeredPortlets.value = description.getOfferedPortlets(); userCategoryDescriptions.value = description.getUserCategoryDescriptions(); // customUserProfileItemDescriptions.value = description.getCustomUserProfileItemDescriptions(); + extensionDescriptions.value = description.getExtensionDescriptions(); customWindowStateDescriptions.value = description.getCustomWindowStateDescriptions(); customModeDescriptions.value = description.getCustomModeDescriptions(); requiresInitCookie.value = description.getRequiresInitCookie(); registrationPropertyDescription.value = description.getRegistrationPropertyDescription(); locales.value = description.getLocales(); resourceList.value = description.getResourceList(); + eventDescriptions.value = description.getEventDescriptions(); + schemaType.value = description.getSchemaType(); + supportedOptions.value = description.getSupportedOptions(); + exportDescription.value = description.getExportDescription(); + mayReturnRegistrationState.value = description.isMayReturnRegistrationState(); extensions.value = description.getExtensions(); } }

13 years, 1 month

1
0
0 / 0

gatein SVN: r8146 - in epp/portal/branches/EPP_5_2_Branch/distribution/mead-tools: gatein-portal and 1 other directory.

by do-not-reply＠jboss.org

Author: theute Date: 2011-11-25 10:23:47 -0500 (Fri, 25 Nov 2011) New Revision: 8146 Modified: epp/portal/branches/EPP_5_2_Branch/distribution/mead-tools/build.xml epp/portal/branches/EPP_5_2_Branch/distribution/mead-tools/gatein-portal/pom.xml Log: JBEPP-1398: MEAD built bouncy castle jars are not signed with a sun/oracle authorized key for a JCE extension Modified: epp/portal/branches/EPP_5_2_Branch/distribution/mead-tools/build.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/distribution/mead-tools/build.xml 2011-11-25 10:06:30 UTC (rev 8145) +++ epp/portal/branches/EPP_5_2_Branch/distribution/mead-tools/build.xml 2011-11-25 15:23:47 UTC (rev 8146) @@ -25,7 +25,7 @@  <target name="build-doc"> - + </target>  Modified: epp/portal/branches/EPP_5_2_Branch/distribution/mead-tools/gatein-portal/pom.xml =================================================================== --- epp/portal/branches/EPP_5_2_Branch/distribution/mead-tools/gatein-portal/pom.xml 2011-11-25 10:06:30 UTC (rev 8145) +++ epp/portal/branches/EPP_5_2_Branch/distribution/mead-tools/gatein-portal/pom.xml 2011-11-25 15:23:47 UTC (rev 8146) @@ -17,7 +17,7 @@ <properties> - <mead.target>jboss-epp-5</mead.target> + <mead.target>jboss-epp-5</mead.target> <doc.path>${project.name}-apidoc</doc.path> <source.path>${project.name}</source.path> @@ -29,7 +29,7 @@ <mead.build.profiles>release epp-distribution epp-distribution-assembly epp-distribution-zip</mead.build.profiles> <mead.build.properties></mead.build.properties> <mead.patch.path></mead.patch.path> - <mead.parameters>-p patch -Dmavensign.sign.skip=wstx.jar -Dmavensign.expand.skip=wstx.jar</mead.parameters> + <mead.parameters>-p patch -Dmavensign.sign.skip=wstx.jar,bcprov-jdk15-1.40.jar,bcmail-jdk15-1.45.jar,bcprov-jdk15-1.45.jar -Dmavensign.expand.skip=wstx.jar</mead.parameters> </properties> </project>

13 years, 1 month

1
0
0 / 0

gatein SVN: r8145 - epp/portal/branches/EPP_5_2_Branch/component/web/security/src/main/java/org/exoplatform/web/security.

by do-not-reply＠jboss.org

Author: mposolda Date: 2011-11-25 05:06:30 -0500 (Fri, 25 Nov 2011) New Revision: 8145 Modified: epp/portal/branches/EPP_5_2_Branch/component/web/security/src/main/java/org/exoplatform/web/security/PortalLoginModule.java Log: GTNMGMT-33 Fix NPE in PortalLoginModule, which can happen during CLI login Modified: epp/portal/branches/EPP_5_2_Branch/component/web/security/src/main/java/org/exoplatform/web/security/PortalLoginModule.java =================================================================== --- epp/portal/branches/EPP_5_2_Branch/component/web/security/src/main/java/org/exoplatform/web/security/PortalLoginModule.java 2011-11-25 10:00:28 UTC (rev 8144) +++ epp/portal/branches/EPP_5_2_Branch/component/web/security/src/main/java/org/exoplatform/web/security/PortalLoginModule.java 2011-11-25 10:06:30 UTC (rev 8145) @@ -1,16 +1,20 @@ -/** - * Copyright (C) 2009 eXo Platform SAS. - * +/* + * JBoss, a division of Red Hat + * Copyright 2011, Red Hat Middleware, LLC, and individual + * contributors as indicated by the @authors tag. See the + * copyright.txt in the distribution for a full listing of + * individual contributors. + * * This is free software; you can redistribute it and/or modify it * under the terms of the GNU Lesser General Public License as * published by the Free Software Foundation; either version 2.1 of * the License, or (at your option) any later version. - * + * * This software is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU * Lesser General Public License for more details. - * + * * You should have received a copy of the GNU Lesser General Public * License along with this software; if not, write to the Free * Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA @@ -26,12 +30,8 @@ import org.exoplatform.services.security.Identity; import org.exoplatform.services.security.UsernameCredential; import org.exoplatform.services.security.jaas.AbstractLoginModule; -import org.exoplatform.web.login.InitiateLoginServlet; import org.gatein.wci.security.Credentials; -import javax.security.auth.callback.Callback; -import javax.security.auth.callback.NameCallback; -import javax.security.auth.callback.PasswordCallback; import javax.security.auth.login.LoginException; import javax.servlet.http.HttpServletRequest; import java.lang.reflect.Method; @@ -92,7 +92,15 @@ try { - HttpServletRequest request = (HttpServletRequest)getContextMethod.invoke(null, "javax.servlet.http.HttpServletRequest"); + HttpServletRequest request = getCurrentHttpServletRequest(); + + // This can be the case with CLI login + if (request == null) + { + log.debug("Unable to find HTTPServletRequest."); + return false; + } + authCredentials = (Credentials)request.getSession().getAttribute(AUTHENTICATED_CREDENTIALS); // If authenticated credentials were presented in HTTP session, it means that we were already logged on different cluster node @@ -139,6 +147,7 @@ { // Add authenticated credentials to session only if we were logged on this host with "real" credentials if (getContextMethod != null && + isClusteredSSO() && sharedState.containsKey("javax.security.auth.login.name") && sharedState.containsKey("javax.security.auth.login.password") && sharedState.get(LOGIN_ON_DIFFERENT_NODE) == null) @@ -150,9 +159,18 @@ HttpServletRequest request = null; try { - request = (HttpServletRequest)getContextMethod.invoke(null, "javax.servlet.http.HttpServletRequest"); - request.getSession().setAttribute(AUTHENTICATED_CREDENTIALS, wc); - handleCredentialsRemoving(request); + request = getCurrentHttpServletRequest(); + + // This can be the case with CLI login + if (request == null) + { + log.debug("Unable to find HTTPServletRequest."); + } + else + { + request.getSession().setAttribute(AUTHENTICATED_CREDENTIALS, wc); + handleCredentialsRemoving(request); + } } catch(Exception e) { @@ -201,4 +219,22 @@ // TODO: We can't remove credentials from HTTP session right now because WSRP-Security relies on it. See method WSSecurityCredentialHelper.handleRequest // request.getSession().removeAttribute(Credentials.CREDENTIALS); } + + private HttpServletRequest getCurrentHttpServletRequest() + { + HttpServletRequest request = null; + try + { + if (getContextMethod != null) + { + request = (HttpServletRequest)getContextMethod.invoke(null, "javax.servlet.http.HttpServletRequest"); + } + } + catch (Exception e) + { + log.debug("Exception when trying to obtain HTTPServletRequest.", e); + } + + return request; + } }

13 years, 1 month

1
0
0 / 0

gatein SVN: r8144 - portal/trunk/component/web/security/src/main/java/org/exoplatform/web/security.

by do-not-reply＠jboss.org

Author: mposolda Date: 2011-11-25 05:00:28 -0500 (Fri, 25 Nov 2011) New Revision: 8144 Modified: portal/trunk/component/web/security/src/main/java/org/exoplatform/web/security/PortalLoginModule.java Log: GTNMGMT-33 Fix NPE in PortalLoginModule, which can happen during CLI login Modified: portal/trunk/component/web/security/src/main/java/org/exoplatform/web/security/PortalLoginModule.java =================================================================== --- portal/trunk/component/web/security/src/main/java/org/exoplatform/web/security/PortalLoginModule.java 2011-11-25 03:22:16 UTC (rev 8143) +++ portal/trunk/component/web/security/src/main/java/org/exoplatform/web/security/PortalLoginModule.java 2011-11-25 10:00:28 UTC (rev 8144) @@ -92,7 +92,15 @@ try { - HttpServletRequest request = (HttpServletRequest)getContextMethod.invoke(null, "javax.servlet.http.HttpServletRequest"); + HttpServletRequest request = getCurrentHttpServletRequest(); + + // This can be the case with CLI login + if (request == null) + { + log.debug("Unable to find HTTPServletRequest."); + return false; + } + authCredentials = (Credentials)request.getSession().getAttribute(AUTHENTICATED_CREDENTIALS); // If authenticated credentials were presented in HTTP session, it means that we were already logged on different cluster node @@ -139,6 +147,7 @@ { // Add authenticated credentials to session only if we were logged on this host with "real" credentials if (getContextMethod != null && + isClusteredSSO() && sharedState.containsKey("javax.security.auth.login.name") && sharedState.containsKey("javax.security.auth.login.password") && sharedState.get(LOGIN_ON_DIFFERENT_NODE) == null) @@ -150,9 +159,18 @@ HttpServletRequest request = null; try { - request = (HttpServletRequest)getContextMethod.invoke(null, "javax.servlet.http.HttpServletRequest"); - request.getSession().setAttribute(AUTHENTICATED_CREDENTIALS, wc); - handleCredentialsRemoving(request); + request = getCurrentHttpServletRequest(); + + // This can be the case with CLI login + if (request == null) + { + log.debug("Unable to find HTTPServletRequest."); + } + else + { + request.getSession().setAttribute(AUTHENTICATED_CREDENTIALS, wc); + handleCredentialsRemoving(request); + } } catch(Exception e) { @@ -201,4 +219,22 @@ // TODO: We can't remove credentials from HTTP session right now because WSRP-Security relies on it. See method WSSecurityCredentialHelper.handleRequest // request.getSession().removeAttribute(Credentials.CREDENTIALS); } + + private HttpServletRequest getCurrentHttpServletRequest() + { + HttpServletRequest request = null; + try + { + if (getContextMethod != null) + { + request = (HttpServletRequest)getContextMethod.invoke(null, "javax.servlet.http.HttpServletRequest"); + } + } + catch (Exception e) + { + log.debug("Exception when trying to obtain HTTPServletRequest.", e); + } + + return request; + } }

13 years, 1 month

1
0
0 / 0

gatein SVN: r8143 - in epp/docs/branches/5.2/Migration_Guide/en-US: icons and 1 other directory.

by do-not-reply＠jboss.org

Author: smumford Date: 2011-11-24 22:22:16 -0500 (Thu, 24 Nov 2011) New Revision: 8143 Added: epp/docs/branches/5.2/Migration_Guide/en-US/icons/ epp/docs/branches/5.2/Migration_Guide/en-US/icons/icon.svg epp/docs/branches/5.2/Migration_Guide/en-US/images/ 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-3-Portal_URLs.xml epp/docs/branches/5.2/Migration_Guide/en-US/chapter-5-User_interface.xml Log: Pushed to documentation stage. 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-11-25 01:13:48 UTC (rev 8142) +++ epp/docs/branches/5.2/Migration_Guide/en-US/Book_Info.xml 2011-11-25 03:22:16 UTC (rev 8143) @@ -6,7 +6,7 @@ <productname>JBoss Enterprise Portal Platform</productname> <productnumber>5.2</productnumber> <edition>5.2.0</edition> - <pubsnumber>1</pubsnumber> + <pubsnumber>2</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-11-25 01:13:48 UTC (rev 8142) +++ epp/docs/branches/5.2/Migration_Guide/en-US/Revision_History.xml 2011-11-25 03:22:16 UTC (rev 8143) @@ -4,6 +4,20 @@ <title>Revision History</title> <simpara> <revhistory> + <revision> + <revnumber>5.2.0-2</revnumber> + <date>Fri Nov 25 2011</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email></email> + </author> + <revdescription> + <simplelist> + <member>Pushed to documentation stage.</member> + </simplelist> + </revdescription> + </revision> <revision> <revnumber>5.2.0-1</revnumber> <date>Tue Nov 22 2011</date> 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-11-25 01:13:48 UTC (rev 8142) +++ epp/docs/branches/5.2/Migration_Guide/en-US/chapter-3-Portal_URLs.xml 2011-11-25 03:22:16 UTC (rev 8143) @@ -222,7 +222,7 @@ <URL-pattern>/dologin</URL-pattern> </servlet-mapping></programlisting> </example> - <para>Delare portal servlet as default Servlet</para> + <para>Declare portal servlet as default Servlet</para> <example> <title>Example</title> <programlisting><servlet-mapping> 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-11-25 01:13:48 UTC (rev 8142) +++ epp/docs/branches/5.2/Migration_Guide/en-US/chapter-5-User_interface.xml 2011-11-25 03:22:16 UTC (rev 8143) @@ -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 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> + <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> </section> <section id="sid-13467777_Userinterface-Cleanthecookies"> Added: epp/docs/branches/5.2/Migration_Guide/en-US/icons/icon.svg =================================================================== --- epp/docs/branches/5.2/Migration_Guide/en-US/icons/icon.svg (rev 0) +++ epp/docs/branches/5.2/Migration_Guide/en-US/icons/icon.svg 2011-11-25 03:22:16 UTC (rev 8143) @@ -0,0 +1,3936 @@ +<?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" /> + </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" /> + </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> +</svg>

13 years, 1 month

1
0
0 / 0

gatein SVN: r8142 - in epp/docs/branches/5.2/Reference_Guide: en-US and 22 other directories.

by do-not-reply＠jboss.org

Author: smumford Date: 2011-11-24 20:13:48 -0500 (Thu, 24 Nov 2011) New Revision: 8142 Modified: epp/docs/branches/5.2/Reference_Guide/en-US/Author_Group.xml epp/docs/branches/5.2/Reference_Guide/en-US/Book_Info.xml epp/docs/branches/5.2/Reference_Guide/en-US/Preface.xml epp/docs/branches/5.2/Reference_Guide/en-US/Revision_History.xml epp/docs/branches/5.2/Reference_Guide/en-US/fallback_content/Conventions.xml epp/docs/branches/5.2/Reference_Guide/en-US/fallback_content/Feedback.xml epp/docs/branches/5.2/Reference_Guide/en-US/fallback_content/Legal_Notice.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Advanced_Concepts.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Config_Retrieval.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Configuring_Containers.xml 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/Extensions_And_Multiple_Portals.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Kernel.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Management.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Profiles.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Requests.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Specific_Services.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/System_Properties.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/AccessingUserProfile.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/AuthenticationTokenConfiguration.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/BackendConfiguration.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/LDAP.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/OrganizationAPI.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/PredefinedUserConfiguration.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/Configuration.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/Configuration/DatabaseConfiguration.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/Configuration/EMailServiceConfiguration.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/GadgetDevelopment.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/GadgetDevelopment/Gadgets.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/GadgetDevelopment/SetupGadgetServer.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/Introduction.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/DataImportStrategy.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/DefaultPortalPermissionConfiguration.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/InternationalizationConfiguration.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/JavascriptConfiguration.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/JavascriptInterApplicationCommunication.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/LocalizationConfiguration.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/PortalDevelopment/RTLFramework.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/Skinning.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/XMLResourceBundles.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortletDevelopment.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortletDevelopment/Global_Portlet.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortletDevelopment/PortletBridge.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortletDevelopment/PortletBridge/configuration.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortletDevelopment/PortletBridge/gettingstarted.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortletDevelopment/PortletBridge/overview.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortletDevelopment/PortletBridge/portlet_development.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortletDevelopment/Standard.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/RH-WSRP.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/conversationstate-when-membership-changed.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/core.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/db-configuration-hibernate.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/db-creator-service.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/db-schema-creator-service.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/digest-auth.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/ldap-configuration.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/organization-service-initalizer.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/organization-service-listener.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/organization-service.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/security-service.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/spring-security-integration.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/tika-document-reader-service.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/faq.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/faq/jcr-faq.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr-with-gatein.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr-with-gtn/managed-datasources-under-jboss-as.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/api-extensions.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/backup/backup-client.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/backup/backup-clonsole-dist.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/backup/use-external-backup-tool.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/cluster-config.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/jcr-advantages.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/jcr-applications.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/jcr-compatibility-levels.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/jcr-exo-implementation.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/jcr-extensions.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/jcr-namespace-altering.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/jcr-registry-service.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/jcr-usage.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/concepts/nodetypes-and-namespaces.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/why-jcr.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/configuration-persister.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/exo-jcr-configuration.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/external-value-storages.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/jdbc-data-container-config.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/multilanguage-support.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/rest-services-on-groovy.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/search-configuration.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/workspace-persistence-storage.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/data-container-howto.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/data-container.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/db-cleaner-service.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/intro.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/jbossts-transaction-service.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/jca.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/jta.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/lock-manager-config.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/other/acl-ext.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/other/acl.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/other/binary-values-processing.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/other/link-producer.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/performance-tuning-guide.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/protocols/webdav.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/repository-check-controller.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/repository-creation-service.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/aggregation-rule.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/and-constraint.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/child-node-constraint.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/date-property-comparison.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/escaping-like-statements.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/exact-path-constraint.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/find-all-descendant-nodes.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/find-all-nodes.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/find-nodes-by-mixin-type.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/find-nodes-by-primary-type.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/find-nodes-case-insensitive.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/find-similar-nodes.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/fulltext-search-and-settings.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/fulltext-search-by-all-properties.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/fulltext-search-by-property.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/higlight.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/ignore-accent-symbols.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/index-boost-value.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/jcr-query-usecases.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/like-constraint.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/multivalue-property-comparison.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/node-name-constraint.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/node-scope-index.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/not-constraint.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/offset-and-limit.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/or-constraint.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/order-by-descendant.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/order-by-path-or-name.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/order-by-property.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/order-by-score.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/property-comparison.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/property-existance-constraint.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/regexp-indexing-rule.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/searching-repository-content.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/spell-checker.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/synonim-provider.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/tip-nodename-with-number.xml 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/transaction-manager-lookup.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/ws.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/ws/framework-for-cross-domain-ajax.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/ws/groovy-scripts-as-rest-services.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/ws/introduction-to-rest.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/ws/overwrite-default-providers.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/ws/restservicelist-service.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/ws/ws.xml epp/docs/branches/5.2/Reference_Guide/publican.cfg Log: Internal book changes for to remove eXo_JCR_1.14 from name and ids Modified: epp/docs/branches/5.2/Reference_Guide/en-US/Author_Group.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/Author_Group.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/Author_Group.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,6 +1,6 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE authorgroup PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> <authorgroup> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/Book_Info.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/Book_Info.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/Book_Info.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,15 +1,15 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<bookinfo id="book-Reference_Guide_eXo_JCR_1.14-Reference_Guide_eXo_JCR_1.14"> - <title>Reference Guide eXo JCR 1.14</title> +<bookinfo id="book-Reference_Guide-Reference_Guide"> + <title>Reference Guide</title> <subtitle>An in-depth guide to Enterprise Portal Platform &VZ;</subtitle> <productname>JBoss Enterprise Portal Platform</productname> <productnumber>5.2</productnumber> <edition>5.2.0</edition> - <pubsnumber>9</pubsnumber> + <pubsnumber>10</pubsnumber> <abstract> <para> This Reference Guide is a high-level usage document. It deals with more advanced topics than the Installation and User Guides, adding new content or taking concepts discussed in the earlier documents further. It aims to provide supporting documentation for advanced users of the JBoss Enterprise Portal Platform product. Its primary focus is on advanced use of the product and it assumes an intermediate or advanced knowledge of the technology and terms. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/Preface.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/Preface.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/Preface.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE preface PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<preface id="pref-Reference_Guide_eXo_JCR_1.14-Preface"> +<preface id="pref-Reference_Guide-Preface"> <title>Preface</title>  <xi:include href="Common_Content/Conventions.xml" xmlns:xi="http://www.w3.org/2001/XInclude">  <xi:fallback xmlns:xi="http://www.w3.org/2001/XInclude"> <xi:include href="fallback_content/Conventions.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> </xi:fallback> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/Revision_History.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/Revision_History.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/Revision_History.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,14 +1,14 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<appendix id="appe-Reference_Guide_eXo_JCR_1.14-Revision_History"> +<appendix id="appe-Reference_Guide-Revision_History"> <title>Revision History</title> <simpara> <revhistory> <revision> - <revnumber>5.2.0-9</revnumber> + <revnumber>5.2.0-10</revnumber> <date>Fri Nov 25 2011</date> <author> <firstname>Scott</firstname> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/fallback_content/Conventions.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/fallback_content/Conventions.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/fallback_content/Conventions.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Document_Conventions"> +<section id="sect-Reference_Guide-Document_Conventions"> <title>Document Conventions</title> <para> This manual uses several conventions to highlight certain words and phrases and draw attention to specific pieces of information. @@ -11,7 +11,7 @@ <para> In PDF and paper editions, this manual uses typefaces drawn from the <ulink url="https://fedorahosted.org/liberation-fonts/">Liberation Fonts</ulink> set. The Liberation Fonts set is also used in HTML editions if the set is installed on your system. If not, alternative but equivalent typefaces are displayed. Note: Red Hat Enterprise Linux 5 and later includes the Liberation Fonts set by default. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Document_Conventions-Typographic_Conventions"> + <section id="sect-Reference_Guide-Document_Conventions-Typographic_Conventions"> <title>Typographic Conventions</title> <para> Four typographic conventions are used to call attention to specific words and phrases. These conventions, and the circumstances they apply to, are as follows. @@ -109,7 +109,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Document_Conventions-Pull_quote_Conventions"> + <section id="sect-Reference_Guide-Document_Conventions-Pull_quote_Conventions"> <title>Pull-quote Conventions</title> <para> Terminal output and source code listings are set off visually from the surrounding text. @@ -144,7 +144,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Document_Conventions-Notes_and_Warnings"> + <section id="sect-Reference_Guide-Document_Conventions-Notes_and_Warnings"> <title>Notes and Warnings</title> <para> Finally, we use three visual styles to draw attention to information that might otherwise be overlooked. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/fallback_content/Feedback.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/fallback_content/Feedback.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/fallback_content/Feedback.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-We_Need_Feedback"> +<section id="sect-Reference_Guide-We_Need_Feedback"> <title>We Need Feedback!</title> <indexterm> <primary>feedback</primary> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/fallback_content/Legal_Notice.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/fallback_content/Legal_Notice.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/fallback_content/Legal_Notice.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,6 +1,6 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE legalnotice PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> <legalnotice> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Advanced_Concepts.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Advanced_Concepts.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Advanced_Concepts.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,14 +1,14 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Advanced_concepts_for_the_PortalContainers"> +<section id="sect-Reference_Guide-Advanced_concepts_for_the_PortalContainers"> <title>Advanced concepts for the <emphasis>PortalContainers</emphasis></title> <para> Since eXo JCR 1.12, we added a set of new features that have been designed to extend portal applications such as GateIn. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Advanced_concepts_for_the_PortalContainers-Add_new_configuration_files_from_a_WAR_file"> + <section id="sect-Reference_Guide-Advanced_concepts_for_the_PortalContainers-Add_new_configuration_files_from_a_WAR_file"> <title>Add new configuration files from a WAR file</title> <para> A <envar>ServletContextListener</envar> called <envar>org.exoplatform.container.web.PortalContainerConfigOwner</envar> has been added in order to notify the application that a given web application provides some configuration to the portal container, and this configuration file is the file <emphasis>WEB-INF/conf/configuration.xml</emphasis> available in the web application itself. @@ -33,7 +33,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Advanced_concepts_for_the_PortalContainers-Creating_your_PortalContainers_from_a_WAR_file"> + <section id="sect-Reference_Guide-Advanced_concepts_for_the_PortalContainers-Creating_your_PortalContainers_from_a_WAR_file"> <title>Creating your <emphasis>PortalContainers</emphasis> from a WAR file</title> <para> A <envar>ServletContextListener</envar> called <envar>org.exoplatform.container.web.PortalContainerCreator</envar> has been added in order to create the current portal containers that have been registered. We assume that all the web applications have already been loaded before calling <envar>PortalContainerCreator.contextInitialized.</envar> @@ -50,7 +50,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Advanced_concepts_for_the_PortalContainers-Defining_a_PortalContainer_with_its_dependencies_and_its_settings"> + <section id="sect-Reference_Guide-Advanced_concepts_for_the_PortalContainers-Defining_a_PortalContainer_with_its_dependencies_and_its_settings"> <title>Defining a <emphasis>PortalContainer</emphasis> with its dependencies and its settings</title> <para> Now we can define precisely a portal container and its dependencies and settings thanks to the <envar>PortalContainerDefinition</envar> that currently contains the name of the portal container, the name of the rest context, the name of the realm, the web application dependencies ordered by loading priority (i.e. the first dependency must be loaded at first and so on..) and the settings. @@ -139,7 +139,7 @@ </object-param> </init-params> </component></programlisting> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Defining_a_PortalContainer_with_its_dependencies_and_its_settings-Descriptions_of_the_fields_of_PortalContainerConfig"> + <table id="tabl-Reference_Guide-Defining_a_PortalContainer_with_its_dependencies_and_its_settings-Descriptions_of_the_fields_of_PortalContainerConfig"> <title>Descriptions of the fields of <envar>PortalContainerConfig</envar></title> <tgroup cols="2"> <tbody> @@ -314,7 +314,7 @@ </init-params> </component-plugin> </external-component-plugins></programlisting> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Defining_a_PortalContainer_with_its_dependencies_and_its_settings-Descriptions_of_the_fields_of_a_PortalContainerDefinition_when_it_is_used_to_define_a_new_portal_container"> + <table id="tabl-Reference_Guide-Defining_a_PortalContainer_with_its_dependencies_and_its_settings-Descriptions_of_the_fields_of_a_PortalContainerDefinition_when_it_is_used_to_define_a_new_portal_container"> <title>Descriptions of the fields of a <envar>PortalContainerDefinition</envar> when it is used to define a new portal container</title> <tgroup cols="2"> <tbody> @@ -441,7 +441,7 @@ </tgroup> </table> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Defining_a_PortalContainer_with_its_dependencies_and_its_settings-Descriptions_of_the_fields_of_a_PortalContainerDefinition_when_it_is_used_to_define_the_default_portal_container"> + <table id="tabl-Reference_Guide-Defining_a_PortalContainer_with_its_dependencies_and_its_settings-Descriptions_of_the_fields_of_a_PortalContainerDefinition_when_it_is_used_to_define_the_default_portal_container"> <title>Descriptions of the fields of a <envar>PortalContainerDefinition</envar> when it is used to define the default portal container</title> <tgroup cols="2"> <tbody> @@ -663,12 +663,12 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Advanced_concepts_for_the_PortalContainers-PortalContainer_settings"> + <section id="sect-Reference_Guide-Advanced_concepts_for_the_PortalContainers-PortalContainer_settings"> <title><envar>PortalContainer</envar> settings</title> <para> We can inject the value of the portal container settings into the portal container configuration files thanks to the variables which name start with "<emphasis>portal.container.</emphasis>", so to get the value of a setting called "<emphasis>foo</emphasis>", just use the following syntax <emphasis>${portal.container.foo}</emphasis>. You can also use internal variables, such as: </para> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-PortalContainer_settings-Definition_of_the_internal_variables"> + <table id="tabl-Reference_Guide-PortalContainer_settings-Definition_of_the_internal_variables"> <title>Definition of the internal variables</title> <tgroup cols="2"> <tbody> @@ -766,7 +766,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Advanced_concepts_for_the_PortalContainers-Adding_dynamically_settings_andor_dependencies_to_a_PortalContainer"> + <section id="sect-Reference_Guide-Advanced_concepts_for_the_PortalContainers-Adding_dynamically_settings_andor_dependencies_to_a_PortalContainer"> <title>Adding dynamically settings and/or dependencies to a <envar>PortalContainer</envar></title> <para> It is possible to use <envar>component-plugin</envar> elements in order to dynamically change a PortalContainerDefinition. In the example below, we add the dependency <envar>foo</envar> to the default portal container and to the portal containers called <envar>foo1</envar> and <envar>foo2</envar>: @@ -808,7 +808,7 @@ </init-params> </component-plugin> </external-component-plugins></programlisting> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Adding_dynamically_settings_andor_dependencies_to_a_PortalContainer-Descriptions_of_the_fields_of_a_PortalContainerDefinitionChangePlugin"> + <table id="tabl-Reference_Guide-Adding_dynamically_settings_andor_dependencies_to_a_PortalContainer-Descriptions_of_the_fields_of_a_PortalContainerDefinitionChangePlugin"> <title>Descriptions of the fields of a <envar>PortalContainerDefinitionChangePlugin</envar></title> <tgroup cols="2"> <tbody> @@ -896,17 +896,17 @@ </listitem> </orderedlist> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Adding_dynamically_settings_andor_dependencies_to_a_PortalContainer-The_existing_implementations_of_PortalContainerDefinitionChange"> + <section id="sect-Reference_Guide-Adding_dynamically_settings_andor_dependencies_to_a_PortalContainer-The_existing_implementations_of_PortalContainerDefinitionChange"> <title>The existing implementations of <envar>PortalContainerDefinitionChange</envar></title> <para> The modifications that can be applied to a <envar>PortalContainerDefinition</envar> must be a class of type <envar>PortalContainerDefinitionChange</envar>. The product proposes out of the box some implementations that we describe in the next sub sections. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-The_existing_implementations_of_PortalContainerDefinitionChange-AddDependencies"> + <section id="sect-Reference_Guide-The_existing_implementations_of_PortalContainerDefinitionChange-AddDependencies"> <title><envar>AddDependencies</envar></title> <para> This modification adds a list of dependencies at the end of the list of dependencies defined into the <envar>PortalContainerDefinition</envar>. The full qualified name is <emphasis>org.exoplatform.container.definition.PortalContainerDefinitionChange$AddDependencies</emphasis>. </para> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-AddDependencies-Descriptions_of_the_fields_of_an_AddDependencies"> + <table id="tabl-Reference_Guide-AddDependencies-Descriptions_of_the_fields_of_an_AddDependencies"> <title>Descriptions of the fields of an <envar>AddDependencies</envar></title> <tgroup cols="2"> <tbody> @@ -963,12 +963,12 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-The_existing_implementations_of_PortalContainerDefinitionChange-AddDependenciesBefore"> + <section id="sect-Reference_Guide-The_existing_implementations_of_PortalContainerDefinitionChange-AddDependenciesBefore"> <title><envar>AddDependenciesBefore</envar></title> <para> This modification adds a list of dependencies before a given target dependency defined into the list of dependencies of the <envar>PortalContainerDefinition</envar>. The full qualified name is <emphasis>org.exoplatform.container.definition.PortalContainerDefinitionChange$AddDependenciesBefore</emphasis>. </para> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-AddDependenciesBefore-Descriptions_of_the_fields_of_an_AddDependenciesBefore"> + <table id="tabl-Reference_Guide-AddDependenciesBefore-Descriptions_of_the_fields_of_an_AddDependenciesBefore"> <title>Descriptions of the fields of an <envar>AddDependenciesBefore</envar></title> <tgroup cols="2"> <tbody> @@ -1038,12 +1038,12 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-The_existing_implementations_of_PortalContainerDefinitionChange-AddDependenciesAfter"> + <section id="sect-Reference_Guide-The_existing_implementations_of_PortalContainerDefinitionChange-AddDependenciesAfter"> <title><envar>AddDependenciesAfter</envar></title> <para> This modification adds a list of dependencies before a given target dependency defined into the list of dependencies of the <envar>PortalContainerDefinition</envar>. The full qualified name is <emphasis>org.exoplatform.container.definition.PortalContainerDefinitionChange$AddDependenciesAfter</emphasis>. </para> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-AddDependenciesAfter-Descriptions_of_the_fields_of_an_AddDependenciesAfter"> + <table id="tabl-Reference_Guide-AddDependenciesAfter-Descriptions_of_the_fields_of_an_AddDependenciesAfter"> <title>Descriptions of the fields of an <envar>AddDependenciesAfter</envar></title> <tgroup cols="2"> <tbody> @@ -1113,12 +1113,12 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-The_existing_implementations_of_PortalContainerDefinitionChange-AddSettings"> + <section id="sect-Reference_Guide-The_existing_implementations_of_PortalContainerDefinitionChange-AddSettings"> <title><envar>AddSettings</envar></title> <para> This modification adds new settings to a <envar>PortalContainerDefinition</envar>. The full qualified name is <emphasis>org.exoplatform.container.definition.PortalContainerDefinitionChange$AddSettings</emphasis>. </para> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-AddSettings-Descriptions_of_the_fields_of_an_AddSettings"> + <table id="tabl-Reference_Guide-AddSettings-Descriptions_of_the_fields_of_an_AddSettings"> <title>Descriptions of the fields of an <envar>AddSettings</envar></title> <tgroup cols="2"> <tbody> @@ -1194,7 +1194,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Advanced_concepts_for_the_PortalContainers-Disable_dynamically_a_portal_container"> + <section id="sect-Reference_Guide-Advanced_concepts_for_the_PortalContainers-Disable_dynamically_a_portal_container"> <title>Disable dynamically a portal container</title> <para> It is possible to use <envar>component-plugin</envar> elements in order to dynamically disable one or several portal containers. In the example below, we disable the portal container named <envar>foo</envar>: @@ -1219,7 +1219,7 @@ </init-params> </component-plugin> </external-component-plugins></programlisting> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Disable_dynamically_a_portal_container-Descriptions_of_the_fields_of_a_PortalContainerDefinitionDisablePlugin"> + <table id="tabl-Reference_Guide-Disable_dynamically_a_portal_container-Descriptions_of_the_fields_of_a_PortalContainerDefinitionDisablePlugin"> <title>Descriptions of the fields of a <envar>PortalContainerDefinitionDisablePlugin</envar></title> <tgroup cols="2"> <tbody> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Config_Retrieval.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Config_Retrieval.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Config_Retrieval.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Configuration_Retrieval"> +<section id="sect-Reference_Guide-Configuration_Retrieval"> <title>Configuration Retrieval</title> <para> The container performs the following steps for configuration retrieval, depending on the container type. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Configuring_Containers.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Configuring_Containers.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Configuring_Containers.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Configuring_a_portal_container"> +<section id="sect-Reference_Guide-Configuring_a_portal_container"> <title>Configuring a portal container</title> <para> A <literal>portal container</literal> is defined by several attributes: 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-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Configuring_Services.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Configuring_Services"> +<section id="sect-Reference_Guide-Configuring_Services"> <title>Configuring Services</title> <para> The eXo Kernel uses dependency injection to create services based on <filename>configuration.xml</filename> configuration files. The location of the configuration files determines if services are placed into the <literal>RootContainer</literal> scope, or into the <literal>PortalContainer</literal> scope. @@ -32,9 +32,9 @@ </para> </note> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuring_Services-Configuration_syntax"> + <section id="sect-Reference_Guide-Configuring_Services-Configuration_syntax"> <title>Configuration syntax</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuration_syntax-Components"> + <section id="sect-Reference_Guide-Configuration_syntax-Components"> <title>Components</title> <para> A service component is defined in <filename>configuration.xml</filename> by using a <emphasis role="bold"><component></emphasis> element. @@ -130,7 +130,7 @@ <para> Many other examples exist such as for the Scheduler Service where you can add a job with a simple XML configuration or the JCR Service where you can add a NodeType from your own configuration.xml file. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Components-RootContainer"> + <section id="sect-Reference_Guide-Components-RootContainer"> <title>RootContainer</title> <para> As PortalContainer depends on the RootContainer, we will start by looking into this one. @@ -180,7 +180,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Components-PortalContainer"> + <section id="sect-Reference_Guide-Components-PortalContainer"> <title>PortalContainer</title> <para> The PortalContainer takes the hashtable filled by the RootContainer and continues to look in some more places. Here you get the opportunity to replace RootContainer configurations by those which are specific to your portal. Again, the configurations are overridden whenever necessary. @@ -236,7 +236,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Components-External_Plug_ins"> + <section id="sect-Reference_Guide-Components-External_Plug_ins"> <title>External Plug-ins</title> <para> The eXo Kernel supports non-component objects that can be configured, instantiated, and injected into registered components using method calls. This '<emphasis>plugin</emphasis>' method allows portal extensions to add additional configurations to core services. @@ -282,7 +282,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Components-Service_instantiation"> + <section id="sect-Reference_Guide-Components-Service_instantiation"> <title>Service instantiation</title> <para> As you have already learned the services are all singletons, so that the container creates only one single instance of each container. The services are created by calling the constructors (called <emphasis>constructor injection</emphasis>). If there are only zero-arguments constructors (<code>Foo public Foo(){}</code>) there are no problems to be expected. That's easy. @@ -310,7 +310,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Components-Service_Access"> + <section id="sect-Reference_Guide-Components-Service_Access"> <title>Service Access</title> <para> As you want to follow the principle of <emphasis role="bold">Inversion of Control,</emphasis> you <emphasis role="bold">must not</emphasis> access the service directly. You need a <emphasis role="bold">Container</emphasis> to access the service. @@ -382,7 +382,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Components-Includes_and_special_URLs"> + <section id="sect-Reference_Guide-Components-Includes_and_special_URLs"> <title>Includes, and special URLs</title> <para> It is possible to divide the <filename>configuration.xml</filename> file into many smaller files, which are then included into the main configuration file. @@ -395,13 +395,13 @@ </para> <programlistingco> <areaspec> - <area coords="6" id="area-Reference_Guide_eXo_JCR_1.14-Components-Includes_and_special_URLs-url_schema" /> + <area coords="6" id="area-Reference_Guide-Components-Includes_and_special_URLs-url_schema" /> </areaspec> <programlisting language="XML" role="XML"><xi:include href="../../../extras/Advanced_Development_Foundations/default2.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> <calloutlist> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Components-Includes_and_special_URLs-url_schema"> + <callout arearefs="area-Reference_Guide-Components-Includes_and_special_URLs-url_schema"> <para> This line is being used to reference another configuration file. The <code>war:</code> URL schema indicates that the following path is to be resolved relative to the current <literal>PortalContainer</literal>'s servlet context resource path, starting with <emphasis role="bold">WEB-INF</emphasis> as a root. </para> @@ -427,7 +427,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Components-Special_variables"> + <section id="sect-Reference_Guide-Components-Special_variables"> <title>Special variables</title> <para> Configuration files may contain a <emphasis role="bold">special variable</emphasis> reference <emphasis>${container.name.suffix}</emphasis>. This variable resolves to the name of the current portal container, prefixed by underscore (_). @@ -449,7 +449,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuration_syntax-InitParams_configuration_element"> + <section id="sect-Reference_Guide-Configuration_syntax-InitParams_configuration_element"> <title>InitParams configuration element</title> <para> <parameter>InitParams</parameter> is a configuration element that is essentially a map of key-value pairs, where <emphasis role="bold">key</emphasis> is always a <literal>String</literal>, and <emphasis role="bold">value</emphasis> can be any type that can be described using the kernel XML configuration. @@ -535,7 +535,7 @@ <para> The <parameter>InitParams</parameter> structure (the names and types of entries) is specific for each service, as it is the code inside a service components' class that defines which entry names to look up and what types it expects to find. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-InitParams_configuration_element-Value_Param"> + <section id="sect-Reference_Guide-InitParams_configuration_element-Value_Param"> <title>Value-Param</title> <para> There is an value-param example: @@ -568,7 +568,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-InitParams_configuration_element-Properties_Param"> + <section id="sect-Reference_Guide-InitParams_configuration_element-Properties_Param"> <title>Properties-Param</title> <para> Properties are name-value pairs. Both the name and the value are Java Strings. @@ -606,7 +606,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-InitParams_configuration_element-Object_Param"> + <section id="sect-Reference_Guide-InitParams_configuration_element-Object_Param"> <title>Object-Param</title> <para> Let's have a look at the configuration of the LDAPService. It's not important to know LDAP, we only discuss the parameters. @@ -682,7 +682,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-InitParams_configuration_element-Collection"> + <section id="sect-Reference_Guide-InitParams_configuration_element-Collection"> <title>Collection</title> <para> You also can use java collections to configure your service. In order to see an example, let's open the database-organization-configuration.xml file. This file defines a default user organization (users, groups, memberships/roles) of your portal. They use component-plugins which are explained later. You will see that object-param is used again. @@ -760,7 +760,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuration_syntax-Component_Plugin_Priority"> + <section id="sect-Reference_Guide-Configuration_syntax-Component_Plugin_Priority"> <title>Component Plugin Priority</title> <para> Since kernel version 2.0.6 it is possible to setup order of loading for ComponentPlugin. Use the ' <emphasis role="bold">priority</emphasis>' tag to define plugin's load priority. By <emphasis role="bold">default</emphasis> all plugins get <emphasis role="bold">priority '0'</emphasis>; they will be loaded in the container's natural way. If you want one plugin to be loaded later than the others then just set priority for it <emphasis role="bold">higher than zero</emphasis>. @@ -811,7 +811,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuration_syntax-Configuration_Logging"> + <section id="sect-Reference_Guide-Configuration_syntax-Configuration_Logging"> <title>Configuration Logging</title> <para> In case you need to solve problems with your service configuration, you have to know from which JAR/WAR causes your troubles. Add the JVM system property <parameter>org.exoplatform.container.configuration.debug</parameter> to your eXo.bat or eXo.sh file (exo-tomcat/bin/). @@ -832,7 +832,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuration_syntax-Import"> + <section id="sect-Reference_Guide-Configuration_syntax-Import"> <title>Import</title> <para> The import tag allows to link to other configuration files. These imported files can be placed anywhere. If you write a default configuration which is part of your jar file you should not import files from outside your jar. @@ -877,7 +877,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuration_syntax-System_properties"> + <section id="sect-Reference_Guide-Configuration_syntax-System_properties"> <title>System properties</title> <para> Since kernel 2.0.7 and 2.1, it is possible to use system properties in literal values of component configuration meta data. This makes it possible to resolve properties at runtime instead of providing a value at packaging time. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Extensions_And_Multiple_Portals.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Extensions_And_Multiple_Portals.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Extensions_And_Multiple_Portals.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-The_Extension_Mechanism_and_Portal_Extensions"> +<section id="sect-Reference_Guide-The_Extension_Mechanism_and_Portal_Extensions"> <title>The Extension Mechanism and Portal Extensions</title> <para> The <emphasis role="bold">Extension mechanism</emphasis> makes it possible to override portal resources in a way similar to hardware plug-and-play functionalities. @@ -14,7 +14,7 @@ <para> These archives, packaged for use through the extension mechanism, are called <emphasis role="bold">portal extensions</emphasis>. </para> - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-The_Extension_Mechanism_and_Portal_Extensions-Creating_a_portal_extension"> + <procedure id="proc-Reference_Guide-The_Extension_Mechanism_and_Portal_Extensions-Creating_a_portal_extension"> <title>Creating a portal extension</title> <step> <para> @@ -48,11 +48,11 @@ <note> <title>Example</title> <para> - Refer to the code extract in <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Configuring_a_portal_container" /> for an example of a <literal>PortalContainerDefinition</literal> that has <emphasis role="bold">sample-ext</emphasis> in its list of dependencies. + Refer to the code extract in <xref linkend="sect-Reference_Guide-Configuring_a_portal_container" /> for an example of a <literal>PortalContainerDefinition</literal> that has <emphasis role="bold">sample-ext</emphasis> in its list of dependencies. </para> </note> - <section id="sect-Reference_Guide_eXo_JCR_1.14-The_Extension_Mechanism_and_Portal_Extensions-Running_Multiple_Portals"> + <section id="sect-Reference_Guide-The_Extension_Mechanism_and_Portal_Extensions-Running_Multiple_Portals"> <title>Running Multiple Portals</title>  <para> It is possible to run several independent portal containers, each bound to a different URL context, within the same JVM instance. @@ -79,7 +79,7 @@ A servlet in this instance should extend the <literal>org.exoplatform.container.web.AbstractHttpServlet</literal> class so as to properly initialize the current <literal>PortalContainer</literal>. </para> <para> - This will also set the current thread's context Classloader to one that looks for resources in associated web applications in the order specified by the <emphasis role="bold">dependencies</emphasis> configuration (as seen in <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-The_Extension_Mechanism_and_Portal_Extensions" />). + This will also set the current thread's context Classloader to one that looks for resources in associated web applications in the order specified by the <emphasis role="bold">dependencies</emphasis> configuration (as seen in <xref linkend="sect-Reference_Guide-The_Extension_Mechanism_and_Portal_Extensions" />). </para> <para> Filter classes need to extend the <literal>org.exoplatform.container.web.AbstractFilter</literal>. @@ -120,7 +120,7 @@ <para> This method exists on both <literal>AbstractHttpServlet</literal> and <literal>AbstractFilter</literal>. This is a default implementation that automatically returns <emphasis>true</emphasis> when it detects there is a current <literal>PortalContainer</literal> present and <emphasis>false</emphasis> otherwise. </para> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Running_Multiple_Portals-ServletContextListener_based_initialization_access_to_PortalContainer"> + <formalpara id="form-Reference_Guide-Running_Multiple_Portals-ServletContextListener_based_initialization_access_to_PortalContainer"> <title>ServletContextListener-based initialization access to PortalContainer</title> <para> JBoss Enterprise Portal Platform has no direct control over the deployment of application archives (<code>.war</code> and <code>.ear</code> files); it is the application server that performs the deployment. @@ -153,7 +153,7 @@ <para> Use <emphasis role="bold">PortalContainerPostCreateTask</emphasis> if initialization is required <emphasis>after</emphasis> all the <code>post-init</code> tasks have been executed. </para> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Running_Multiple_Portals-LoginModules"> + <formalpara id="form-Reference_Guide-Running_Multiple_Portals-LoginModules"> <title>LoginModules</title> <para> If some custom <literal>LoginModules</literal> require the current <literal>eXoContainer</literal> for initialization ensure they extend <emphasis role="bold">org.exoplatform.services.security.jaas.AbstractLoginModule</emphasis>. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Kernel.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Kernel.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Kernel.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-The_eXo_Kernel"> +<section id="sect-Reference_Guide-The_eXo_Kernel"> <title>The eXo Kernel</title> <para> JBoss Enterprise Portal Platform is built as a set of services on top of a dependency injection kernel. The kernel provides configuration, life-cycle handling, component scopes and some core services. @@ -106,7 +106,7 @@ </para> </important> - <section id="sect-Reference_Guide_eXo_JCR_1.14-The_eXo_Kernel-Kernel_configuration_namespace"> + <section id="sect-Reference_Guide-The_eXo_Kernel-Kernel_configuration_namespace"> <title>Kernel configuration namespace</title> <para> To be effective, the namespace URI <uri>http://www.exoplaform.org/xml/ns/kernel_1_2.xsd</uri> must be target namespace of the XML configuration file. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Management.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Management.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Management.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Manageability"> +<section id="sect-Reference_Guide-Manageability"> <title>Manageability</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Manageability-Introduction"> + <section id="sect-Reference_Guide-Manageability-Introduction"> <title>Introduction</title> <para> The kernel has a framework for exposing a management view of the various sub systems of the platform. The management view is a lose term for defining how we can access relevant information about the system and how we can apply management operations. JMX is the de facto standard for exposing a management view in the Java Platform but we take in consideration other kind of views such as REST web services. Therefore, the framework is not tied to JMX, yet it provides a JMX part to define more precisely details related to the JMX management view. The legacy framework is still in use but is deprecated in favor of the new framework as it is less tested and less efficient. It will be removed by sanitization in the future. @@ -13,14 +13,14 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Manageability-Managed_framework_API"> + <section id="sect-Reference_Guide-Manageability-Managed_framework_API"> <title>Managed framework API</title> <para> The managed frameworks defines an API for exposing a management view of objects. The API is targeted for internal use and is not a public API. The framework leverages Java 5 annotations to describe the management view from an object. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Managed_framework_API-Annotations"> + <section id="sect-Reference_Guide-Managed_framework_API-Annotations"> <title>Annotations</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Annotations-org.exoplatform.management.annotations.Managed_annotation"> + <section id="sect-Reference_Guide-Annotations-org.exoplatform.management.annotations.Managed_annotation"> <title>@org.exoplatform.management.annotations.Managed annotation</title> <para> The @Managed annotates elements that wants to expose a management view to a management layer. @@ -46,7 +46,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Annotations-org.exoplatform.management.annotations.ManagedDescription"> + <section id="sect-Reference_Guide-Annotations-org.exoplatform.management.annotations.ManagedDescription"> <title>@org.exoplatform.management.annotations.ManagedDescription</title> <para> The @ManagedDescription annotation provides a description of a managed element. It is valid to annotated object or methods. It takes as sole argument a string that is the description value. @@ -54,7 +54,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Annotations-org.exoplatform.management.annotations.ManagedName"> + <section id="sect-Reference_Guide-Annotations-org.exoplatform.management.annotations.ManagedName"> <title>@org.exoplatform.management.annotations.ManagedName</title> <para> The @ManagedName annotation provides an alternative name for managed properties. It is used to accomodate legacy methods of an object that can be renamed for compatibility reasons. It takes as sole argument a string that is the name value. @@ -62,7 +62,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Annotations-org.exoplatform.management.annotations.ManagedBy"> + <section id="sect-Reference_Guide-Annotations-org.exoplatform.management.annotations.ManagedBy"> <title>@org.exoplatform.management.annotations.ManagedBy</title> <para> The @ManagedBy annotation defines a delegate class for exposing a management view. The sole argument of the annotation are class literals. The delegate class must provide a constructor with the managed object as argument. @@ -76,11 +76,11 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Manageability-JMX_Management_View"> + <section id="sect-Reference_Guide-Manageability-JMX_Management_View"> <title>JMX Management View</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JMX_Management_View-JMX_Annotations"> + <section id="sect-Reference_Guide-JMX_Management_View-JMX_Annotations"> <title>JMX Annotations</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JMX_Annotations-org.exoplatform.management.jmx.annotations.Property_annotation"> + <section id="sect-Reference_Guide-JMX_Annotations-org.exoplatform.management.jmx.annotations.Property_annotation"> <title>@org.exoplatform.management.jmx.annotations.Property annotation</title> <para> The @Property annotation is used to within other annotations such as @NameTemplate or @NamingContext. It should be seen as a structural way for a list of properties. A property is made of a key and a value. The value can either be a string literal or it can be surrounded by curly brace to be a dynamic property. A dynamic property is resolved against the instance of the object at runtime. @@ -88,7 +88,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JMX_Annotations-org.exoplatform.management.jmx.annotations.NameTemplate_annotation"> + <section id="sect-Reference_Guide-JMX_Annotations-org.exoplatform.management.jmx.annotations.NameTemplate_annotation"> <title>@org.exoplatform.management.jmx.annotations.NameTemplate annotation</title> <para> The @NameTemplate defines a template that is used at registration time of a managed object to create the JMX object name. The template is formed of properties. @@ -100,7 +100,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JMX_Annotations-org.exoplatform.management.jmx.annotations.NamingContext_annotation"> + <section id="sect-Reference_Guide-JMX_Annotations-org.exoplatform.management.jmx.annotations.NamingContext_annotation"> <title>@org.exoplatform.management.jmx.annotations.NamingContext annotation</title> <para> The @NamingContext annotations defines a set of properties which are used within a management context. It allows to propagate properties down to managed objects which are defined by an object implementing the ManagementAware interface. The goal is to scope different instances of the same class that would have the same object name otherwise. @@ -116,9 +116,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Manageability-Example"> + <section id="sect-Reference_Guide-Manageability-Example"> <title>Example</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Example-CacheService_example"> + <section id="sect-Reference_Guide-Example-CacheService_example"> <title>CacheService example</title> <para> The cache service delegates most of the work to the CacheServiceManaged class by using the @ManagedBy annotation. At runtime when a new cache is created, it calls the CacheServiceManaged class in order to let the CacheServiceManaged object register the cache. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Profiles.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Profiles.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Profiles.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,14 +1,14 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Runtime_configuration_profiles"> +<section id="sect-Reference_Guide-Runtime_configuration_profiles"> <title>Runtime configuration profiles</title> <para> The kernel configuration is able to handle configuration profiles at runtime (as opposed to packaging time). </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Runtime_configuration_profiles-Profiles_activation"> + <section id="sect-Reference_Guide-Runtime_configuration_profiles-Profiles_activation"> <title>Profiles activation</title> <para> An active profile list is obtained during the boot of the root container and is composed of the system property <emphasis>exo.profiles</emphasis> sliced according the "," delimiter and also a server specific profile value (tomcat for tomcat, jboss for jboss, etc...). @@ -22,12 +22,12 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Runtime_configuration_profiles-Profiles_configuration"> + <section id="sect-Reference_Guide-Runtime_configuration_profiles-Profiles_configuration"> <title>Profiles configuration</title> <para> Profiles are configured in the configuration files of the eXo kernel. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Profiles_configuration-Profiles_definition"> + <section id="sect-Reference_Guide-Profiles_configuration-Profiles_definition"> <title>Profiles definition</title> <para> Profile activation occurs at XML to configuration object unmarshalling time. It is based on an "profile" attribute that is present on some of the XML element of the configuration files. To enable this, the kernel configuration schema has been upgraded to kernel_1_2.xsd. The configuration is based on the following rules: @@ -62,12 +62,12 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Profiles_configuration-Profiles_capable_configuration_elements"> + <section id="sect-Reference_Guide-Profiles_configuration-Profiles_capable_configuration_elements"> <title>Profiles capable configuration elements</title> <para> A configuration element is <emphasis>profiles</emphasis> capable when it carries a profiles element. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Profiles_capable_configuration_elements-Component_element"> + <section id="sect-Reference_Guide-Profiles_capable_configuration_elements-Component_element"> <title>Component element</title> <para> The component element declares a component when activated. It will shadow any element with the same key declared before in the same configuration file: @@ -85,7 +85,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Profiles_capable_configuration_elements-Component_plugin_element"> + <section id="sect-Reference_Guide-Profiles_capable_configuration_elements-Component_plugin_element"> <title>Component plugin element</title> <para> The component-plugin element is used to dynamically extend the configuration of a given component. Thanks to the profiles the component-plugins could be enabled or disabled: @@ -108,7 +108,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Profiles_capable_configuration_elements-Import_element"> + <section id="sect-Reference_Guide-Profiles_capable_configuration_elements-Import_element"> <title>Import element</title> <para> The import element imports a referenced configuration file when activated: @@ -120,7 +120,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Profiles_capable_configuration_elements-Init_param_element"> + <section id="sect-Reference_Guide-Profiles_capable_configuration_elements-Init_param_element"> <title>Init param element</title> <para> The init param element configures the parameter argument of the construction of a component service: @@ -147,7 +147,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Profiles_capable_configuration_elements-Value_collection_element"> + <section id="sect-Reference_Guide-Profiles_capable_configuration_elements-Value_collection_element"> <title>Value collection element</title> <para> The value collection element configures one of the value of collection data: @@ -165,7 +165,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Profiles_capable_configuration_elements-Field_configuration_element"> + <section id="sect-Reference_Guide-Profiles_capable_configuration_elements-Field_configuration_element"> <title>Field configuration element</title> <para> The field configuration element configures the field of an object: Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Requests.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Requests.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Requests.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Component_request_life_cycle"> +<section id="sect-Reference_Guide-Component_request_life_cycle"> <title>Component request life cycle</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Component_request_life_cycle-Component_request_life_cycle_contract"> + <section id="sect-Reference_Guide-Component_request_life_cycle-Component_request_life_cycle_contract"> <title>Component request life cycle contract</title> <para> The component request life cycle is an interface that defines a contract for a component for being involved into a request: @@ -34,12 +34,12 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Component_request_life_cycle-Request_life_cycle"> + <section id="sect-Reference_Guide-Component_request_life_cycle-Request_life_cycle"> <title>Request life cycle</title> <para> The <envar>RequestLifeCycle</envar> class has several statics methods that are used to schedule the component request life cycle of components. Its main responsibility is to perform scheduling while respecting the constraint to execute the request life cycle of a component only once even if it can be scheduled several times. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Request_life_cycle-Scheduling_a_component_request_life_cycle"> + <section id="sect-Reference_Guide-Request_life_cycle-Scheduling_a_component_request_life_cycle"> <title>Scheduling a component request life cycle</title> <programlisting language="Java" role="Java">RequestLifeCycle.begin(component); @@ -54,7 +54,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Request_life_cycle-Scheduling_a_container_request_life_cycle"> + <section id="sect-Reference_Guide-Request_life_cycle-Scheduling_a_container_request_life_cycle"> <title>Scheduling a container request life cycle</title> <para> Scheduling a container triggers the component request life cycle of all the components that implement the interface <envar>ComponentRequestLifeCycle</envar>. If one of the component has already been scheduled before and then that component will not be scheduled again. When the local value is true, then the looked components will be those of the container, when it is false then the scheduler will also look at the components in the ancestor containers. @@ -72,9 +72,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Request_life_cycle-When_request_life_cycle_is_triggered"> + <section id="sect-Reference_Guide-Request_life_cycle-When_request_life_cycle_is_triggered"> <title>When request life cycle is triggered</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-When_request_life_cycle_is_triggered-Portal_request_life_cycle"> + <section id="sect-Reference_Guide-When_request_life_cycle_is_triggered-Portal_request_life_cycle"> <title>Portal request life cycle</title> <para> Each portal request triggers the life cycle of the associated portal container. @@ -82,7 +82,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-When_request_life_cycle_is_triggered-JMX_request_Life_Cycle"> + <section id="sect-Reference_Guide-When_request_life_cycle_is_triggered-JMX_request_Life_Cycle"> <title>JMX request Life Cycle</title> <para> When a JMX bean is invoked, the request life cycle of the container to which it belongs it scheduled. Indeed JMX is an entry point of the system that may need component to have a request life cycle triggered. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Specific_Services.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Specific_Services.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Specific_Services.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,13 +1,13 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Specific_Services"> +<section id="sect-Reference_Guide-Specific_Services"> <title>Specific Services</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Specific_Services-ListenerService"> + <section id="sect-Reference_Guide-Specific_Services-ListenerService"> <title>ListenerService</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-ListenerService-Asynchronous_Event_Broadcast"> + <section id="sect-Reference_Guide-ListenerService-Asynchronous_Event_Broadcast"> <title>Asynchronous Event Broadcast</title> <para> Basically, ListenerService used to store Listeners and broadcast events to them. @@ -62,9 +62,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Specific_Services-Understanding_the_ListenerService"> + <section id="sect-Reference_Guide-Specific_Services-Understanding_the_ListenerService"> <title>Understanding the ListenerService</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Understanding_the_ListenerService-Objectives"> + <section id="sect-Reference_Guide-Understanding_the_ListenerService-Objectives"> <title>Objectives</title> <para> This article will first describe how the ListenerService works and then it will show you how to configure the ListenerService. @@ -72,7 +72,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Understanding_the_ListenerService-What_is_the_ListenerService_"> + <section id="sect-Reference_Guide-Understanding_the_ListenerService-What_is_the_ListenerService_"> <title>What is the ListenerService ?</title> <para> Inside eXo, an event mechanism allows to trigger and listen to events under specific conditions. This mechanism is used in several places in eXo such as login/logout time. @@ -80,12 +80,12 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Understanding_the_ListenerService-How_does_it_work"> + <section id="sect-Reference_Guide-Understanding_the_ListenerService-How_does_it_work"> <title>How does it work?</title> <para> Listeners must be subclasses of org.exoplatform.services.listener.Listener registered by the ListenerService. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-How_does_it_work-Registering_a_listener"> + <section id="sect-Reference_Guide-How_does_it_work-Registering_a_listener"> <title>Registering a listener</title> <para> To register a listener, you need to call the addListener() method. @@ -108,7 +108,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-How_does_it_work-Triggering_an_event"> + <section id="sect-Reference_Guide-How_does_it_work-Triggering_an_event"> <title>Triggering an event</title> <para> To trigger an event, an application can call one of the broadcast() methods of ListenerService. @@ -187,7 +187,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Understanding_the_ListenerService-How_to_configure_a_listener"> + <section id="sect-Reference_Guide-Understanding_the_ListenerService-How_to_configure_a_listener"> <title>How to configure a listener?</title> <para> All listeners are in fact a ComponentPlugin so it must be configured as below: @@ -214,7 +214,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Understanding_the_ListenerService-Concrete_Example"> + <section id="sect-Reference_Guide-Understanding_the_ListenerService-Concrete_Example"> <title>Concrete Example</title> <para> The org.exoplatform.services.security.ConversationRegistry uses the ListenerService to notify that a user has just signed in or just left the application. For example, when a new user signs in, the following code is called: @@ -253,9 +253,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Specific_Services-Job_Schedule"> + <section id="sect-Reference_Guide-Specific_Services-Job_Schedule"> <title>Job Schedule</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Job_Schedule-What_is_Job_Scheduler"> + <section id="sect-Reference_Guide-Job_Schedule-What_is_Job_Scheduler"> <title>What is Job Scheduler?</title> <para> <emphasis role="bold">Job scheduler</emphasis> defines a job to execute a given number of times during a given period. It is a service that is in charge of unattended background executions, commonly known for historical reasons as batch processing. It is used to create and run jobs automatically and continuously, to schedule event-driven jobs and reports. @@ -263,7 +263,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Job_Schedule-How_does_Job_Scheduler_work"> + <section id="sect-Reference_Guide-Job_Schedule-How_does_Job_Scheduler_work"> <title>How does Job Scheduler work?</title> <para> Jobs are scheduled to run when a given Trigger occurs. Triggers can be created with nearly any combination of the following directives: @@ -346,7 +346,7 @@ <para> (Source: quartz-scheduler.org) </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-How_does_Job_Scheduler_work-How_can_Job_Scheduler_Service_be_used_in_Kernel"> + <section id="sect-Reference_Guide-How_does_Job_Scheduler_work-How_can_Job_Scheduler_Service_be_used_in_Kernel"> <title>How can Job Scheduler Service be used in Kernel?</title> <para> Kernel leverages <ulink url="http://www.quartz-scheduler.org">Quartz</ulink> for its scheduler service and wraps <classname>org.quartz.Scheduler</classname> in <classname>org.exoplatform.services.scheduler.impl.QuartzSheduler</classname> for easier service wiring and configuration like any other services. To work with Quartz in Kernel, you will mostly work with <classname>org.exoplatform.services.scheduler.JobSchedulerService</classname> (implemented by <classname>org.exoplatform.services.scheduler.impl.JobSchedulerServiceImpl</classname>. @@ -378,7 +378,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-How_does_Job_Scheduler_work-Samples"> + <section id="sect-Reference_Guide-How_does_Job_Scheduler_work-Samples"> <title>Samples</title> <note> <para> @@ -459,7 +459,7 @@ <para> eXo Kernel makes it easier to work with job scheduler service. All you need is just to define your "job" class to be performed by implementing <emphasis role="italic">org.quartz.Job</emphasis> interface and add configuration for it. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Samples-Define_a_job"> + <section id="sect-Reference_Guide-Samples-Define_a_job"> <title>Define a job</title> <para> To define a job, do as follows: @@ -502,7 +502,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Samples-Job_configuration"> + <section id="sect-Reference_Guide-Samples-Job_configuration"> <title>Job configuration</title> <para> After defining the "job", the only next step is to configure it by using <emphasis role="italic">external-component-plugin</emphasis> configuration for <emphasis role="italic">org.exoplatform.services.scheduler.JobSchedulerService</emphasis>. You can use these methods below for setting component plugin: @@ -578,7 +578,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Samples-Run_the_project"> + <section id="sect-Reference_Guide-Samples-Run_the_project"> <title>Run the project</title> <para> Create <emphasis role="italic">conf.portal</emphasis> package in your sample project. Add the configuration.xml file with the content as follows: @@ -639,7 +639,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Job_Schedule-Reference"> + <section id="sect-Reference_Guide-Job_Schedule-Reference"> <title>Reference</title> <para> To further understand about Job Scheduler, you can refer the following links: @@ -677,15 +677,15 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Specific_Services-The_data_source_provider"> + <section id="sect-Reference_Guide-Specific_Services-The_data_source_provider"> <title>The data source provider</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-The_data_source_provider-Description"> + <section id="sect-Reference_Guide-The_data_source_provider-Description"> <title>Description</title> <para> The <emphasis>DataSourceProvider</emphasis> is a service used to give access to a data source in an uniform manner in order to be able to support data sources that are managed by the application server. </para> <para> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Description-List_methods"> + <table id="tabl-Reference_Guide-Description-List_methods"> <title>List methods</title> <tgroup cols="2"> <tbody> @@ -718,7 +718,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-The_data_source_provider-Configuration"> + <section id="sect-Reference_Guide-The_data_source_provider-Configuration"> <title>Configuration</title> <para> The configuration of the <emphasis>DataSourceProvider</emphasis> should be defined only if you use managed data sources since by default all the data sources are considered as not managed. See below the default configuration @@ -760,7 +760,7 @@ </component> ... </configuration></programlisting> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Configuration-Fields_description"> + <table id="tabl-Reference_Guide-Configuration-Fields_description"> <title>Fields description</title> <tgroup cols="2"> <tbody> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/System_Properties.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/System_Properties.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/System_Properties.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-System_property_configuration"> +<section id="sect-Reference_Guide-System_property_configuration"> <title>System property configuration</title> <para> A new property configurator service has been developed for taking care of configuring system properties from the inline kernel configuration or from specified property files. @@ -11,7 +11,7 @@ <para> The services is scoped at the root container level because it is used by all the services in the different portal containers in the application runtime. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-System_property_configuration-Properties_init_param"> + <section id="sect-Reference_Guide-System_property_configuration-Properties_init_param"> <title>Properties init param</title> <para> The properties init param takes a property declared to configure various properties. @@ -30,7 +30,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-System_property_configuration-Properties_URL_init_param"> + <section id="sect-Reference_Guide-System_property_configuration-Properties_URL_init_param"> <title>Properties URL init param</title> <para> The properties URL init param allow to load an external file by specifying its URL. Both property and XML format are supported, see the javadoc of the <emphasis><envar>java.util.Properties</envar></emphasis> class for more information. When a property file is loaded the various property declarations are loaded in the order in which the properties are declared sequentially in the file. @@ -56,7 +56,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-System_property_configuration-System_Property_configuration_of_the_properties_URL"> + <section id="sect-Reference_Guide-System_property_configuration-System_Property_configuration_of_the_properties_URL"> <title>System Property configuration of the properties URL</title> <para> It is possible to replace the properties URL init param by a system property that overwrites it. The name of that property is <emphasis>exo.properties.url</emphasis>. @@ -64,7 +64,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-System_property_configuration-Variable_Syntaxes"> + <section id="sect-Reference_Guide-System_property_configuration-Variable_Syntaxes"> <title>Variable Syntaxes</title> <para> All the variables that we described in the previous sections can be defined thanks to 2 possible syntaxes which are <emphasis>${variable-name}</emphasis> or <emphasis>${variable-name:default-value}</emphasis>. The first syntax doesn't define any default value so if the variable has not be set the value will be <emphasis>${variable-name}</emphasis> to indicate that it could not be resolved. The second syntax allows you to define the default value after the semi colon so if the variable has not be set the value will be the given default value. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Foundations"> +<chapter id="chap-Reference_Guide-Foundations"> <title>Foundations</title> <xi:include href="Foundations/Kernel.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> <xi:include href="Foundations/Config_Retrieval.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE part PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<part id="part-Reference_Guide_eXo_JCR_1.14-Advanced_Development"> +<part id="part-Reference_Guide-Advanced_Development"> <title>Advanced Development</title> <xi:include href="Advanced/Foundations.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/AccessingUserProfile.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/AccessingUserProfile.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/AccessingUserProfile.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Accessing_User_Profile"> +<section id="sect-Reference_Guide-Accessing_User_Profile"> <title>Accessing User Profile</title> <para> The following code retrieves the details for a logged-in user: Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/AuthenticationTokenConfiguration.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/AuthenticationTokenConfiguration.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/AuthenticationTokenConfiguration.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Authentication_Token_Configuration"> +<section id="sect-Reference_Guide-Authentication_Token_Configuration"> <title>Authentication Token Configuration</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Authentication_Token_Configuration-The_Token_Service"> + <section id="sect-Reference_Guide-Authentication_Token_Configuration-The_Token_Service"> <title>The Token Service</title> <para> The <emphasis>Token Service</emphasis> is used in authentication. @@ -19,7 +19,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Authentication_Token_Configuration-Implementing_the_Token_Service_API"> + <section id="sect-Reference_Guide-Authentication_Token_Configuration-Implementing_the_Token_Service_API"> <title>Implementing the Token Service API</title> <para> All token services used in JBoss Enterprise Portal Platform authentication must be implemented by subclassing an <emphasis role="bold">AbstractTokenService</emphasis> abstract class. @@ -35,7 +35,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Authentication_Token_Configuration-Configuring_Token_Services"> + <section id="sect-Reference_Guide-Authentication_Token_Configuration-Configuring_Token_Services"> <title>Configuring Token Services</title> <para> Token services configuration includes specifying the token validity period. The token service is configured as a portal component using the <filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable>PROFILE</replaceable>/deploy/gatein.ear/02portal.war/WEB-INF/conf/common/autologin-configuration.xml</filename> file. @@ -51,27 +51,27 @@ </para> <programlistingco> <areaspec> - <area coords="7 50" id="area-Reference_Guide_eXo_JCR_1.14-Authentication_Token_Configuration-Configuring_Token_Services-name" /> - <area coords="8 50" id="area-Reference_Guide_eXo_JCR_1.14-Authentication_Token_Configuration-Configuring_Token_Services-time" /> - <area coords="9 50" id="area-Reference_Guide_eXo_JCR_1.14-Authentication_Token_Configuration-Configuring_Token_Services-unit" /> + <area coords="7 50" id="area-Reference_Guide-Authentication_Token_Configuration-Configuring_Token_Services-name" /> + <area coords="8 50" id="area-Reference_Guide-Authentication_Token_Configuration-Configuring_Token_Services-time" /> + <area coords="9 50" id="area-Reference_Guide-Authentication_Token_Configuration-Configuring_Token_Services-unit" /> </areaspec> <programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_AuthenticationTokenConfiguration/default95.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> <calloutlist> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Authentication_Token_Configuration-Configuring_Token_Services-name"> + <callout arearefs="area-Reference_Guide-Authentication_Token_Configuration-Configuring_Token_Services-name"> <para> Service name </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Authentication_Token_Configuration-Configuring_Token_Services-time"> + <callout arearefs="area-Reference_Guide-Authentication_Token_Configuration-Configuring_Token_Services-time"> <para> Amount of time </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Authentication_Token_Configuration-Configuring_Token_Services-unit"> + <callout arearefs="area-Reference_Guide-Authentication_Token_Configuration-Configuring_Token_Services-unit"> <para> Unit of time </para> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/BackendConfiguration.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/BackendConfiguration.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/BackendConfiguration.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-PicketLink_IDM_integration"> +<section id="sect-Reference_Guide-PicketLink_IDM_integration"> <title>PicketLink IDM integration</title> <para> JBoss Enterprise Portal Platform uses the <literal>PicketLink IDM</literal> component to store necessary identity information about users, groups and memberships. While legacy interfaces are still used (<literal>org.exoplatform.services.organization</literal>) for identity management, there is a wrapper implementation that delegates to PicketLink IDM framework. @@ -26,21 +26,21 @@ <para> Additionally, <literal>org.exoplatform.services.organization</literal> <emphasis>membership</emphasis> concept needs to be translated into the IDM <emphasis>Role</emphasis> concept. Therefore <literal>PicketLink IDM</literal> model is used in a limited way. All these translations are applied by the integration layer. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-PicketLink_IDM_integration-Configuration_Files"> + <section id="sect-Reference_Guide-PicketLink_IDM_integration-Configuration_Files"> <title>Configuration Files</title> <para> The main configuration file is <filename>02portal.war/WEB-INF/conf/organization/idm-configuration.xml</filename>: </para> <programlistingco> <areaspec> - <area coords="6 90" id="area-Reference_Guide_eXo_JCR_1.14-PicketLink_IDM_integration-Configuration_Files-JBossIDMServiceImpl" /> - <area coords="22 80" id="area-Reference_Guide_eXo_JCR_1.14-PicketLink_IDM_integration-Configuration_Files-JBossIDMOrganizationServiceImpl" /> + <area coords="6 90" id="area-Reference_Guide-PicketLink_IDM_integration-Configuration_Files-JBossIDMServiceImpl" /> + <area coords="22 80" id="area-Reference_Guide-PicketLink_IDM_integration-Configuration_Files-JBossIDMOrganizationServiceImpl" /> </areaspec> <programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_BackendConfiguration/default96.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> <calloutlist> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-PicketLink_IDM_integration-Configuration_Files-JBossIDMServiceImpl"> + <callout arearefs="area-Reference_Guide-PicketLink_IDM_integration-Configuration_Files-JBossIDMServiceImpl"> <para> The <emphasis role="bold">org.exoplatform.services.organization.idm.PicketLinkIDMServiceImpl</emphasis> service has the following options: </para> @@ -141,7 +141,7 @@ </variablelist> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-PicketLink_IDM_integration-Configuration_Files-JBossIDMOrganizationServiceImpl"> + <callout arearefs="area-Reference_Guide-PicketLink_IDM_integration-Configuration_Files-JBossIDMOrganizationServiceImpl"> <para> The <emphasis role="bold">org.exoplatform.services.organization.idm.PicketLinkIDMOrganizationServiceImpl</emphasis> key is a main entrypoint implementing <emphasis role="bold">org.exoplatform.services.organization.OrganizationService</emphasis> and is dependent on <emphasis role="bold">org.exoplatform.services.organization.idm.PicketLinkIDMService</emphasis> </para> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/LDAP.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/LDAP.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/LDAP.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -4,7 +4,7 @@ <!ENTITY % BOOK_ENTITIES SYSTEM "../../Reference_Guide.ent"> ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14_eXo_JCR_1.14-LDAP_Integration"> +<section id="sect-Reference_Guide_eXo_JCR_1.14-LDAP_Integration"> <title>LDAP Integration</title> <note> <title>Notational Device</title> @@ -102,7 +102,7 @@ These examples are in the <filename><replaceable>ID_HOME</replaceable>/picketlink-idm/examples</filename> directory and can be deployed in a testing environment to assist in configuring LDAP. </para> </note> - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-LDAP_Set_Up"> + <procedure id="proc-Reference_Guide-LDAP_Integration-LDAP_Set_Up"> <title>LDAP Set Up</title> <step> <substeps> @@ -267,13 +267,13 @@ </step> </procedure> - <section id="sect-Reference_Guide_eXo_JCR_1.14_eXo_JCR_1.14-LDAP_Integration-LDAP_in_Read-only_Mode"> + <section id="sect-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-LDAP_in_Read-only_Mode"> <title>LDAP in Read-only Mode</title> <para> This section will show you how to add LDAP in read-only mode. This means that user data entries (both pre-existing, and newly added through the JBoss Enterprise Portal Platform User Interface) will be consumed though the Directory Server and LDAP services, but written to the underlying database. The only exception is that passwords updated via the UI will also be propagated into the appropriate LDAP entry. </para> - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-LDAP_in_Read-only_mode-Set_up_LDAP_read-only_Mode"> + <procedure id="proc-Reference_Guide-LDAP_Integration-LDAP_in_Read-only_mode-Set_up_LDAP_read-only_Mode"> <title>Set up LDAP read-only Mode</title> <step> <para> @@ -297,22 +297,22 @@ <itemizedlist> <listitem> <para> - <xref linkend="proc-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-LDAP_in_Read-only_Mode-Set_up_LDAP_read-only_Mode-RHDS_or_OpenDS"/> + <xref linkend="proc-Reference_Guide-LDAP_Integration-LDAP_in_Read-only_Mode-Set_up_LDAP_read-only_Mode-RHDS_or_OpenDS"/> </para> </listitem> <listitem> <para> - <xref linkend="proc-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-LDAP_in_Read-only_Mode-Set_up_LDAP_read-only_Mode-MSAD"/> + <xref linkend="proc-Reference_Guide-LDAP_Integration-LDAP_in_Read-only_Mode-Set_up_LDAP_read-only_Mode-MSAD"/> </para> </listitem> <listitem> <para> - <xref linkend="proc-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-LDAP_in_Read-only_Mode-Set_up_LDAP_read-only_Mode-OpenLDAP"/> + <xref linkend="proc-Reference_Guide-LDAP_Integration-LDAP_in_Read-only_Mode-Set_up_LDAP_read-only_Mode-OpenLDAP"/> </para> </listitem> </itemizedlist> - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-LDAP_in_Read-only_Mode-Set_up_LDAP_read-only_Mode-RHDS_or_OpenDS"> + <procedure id="proc-Reference_Guide-LDAP_Integration-LDAP_in_Read-only_Mode-Set_up_LDAP_read-only_Mode-RHDS_or_OpenDS"> <title>Red Hat Directory Server or OpenDS</title> <step> <para> @@ -338,17 +338,17 @@ </entry> ]]></programlisting> <para> - Refer to <xref linkend="exam-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-Examples-Read_Only_groupTypeMappings"/> for more information about how these <parameter>groupTypeMappings</parameter> operate. + Refer to <xref linkend="exam-Reference_Guide-LDAP_Integration-Examples-Read_Only_groupTypeMappings"/> for more information about how these <parameter>groupTypeMappings</parameter> operate. </para> </step> <step> <para> - Continue to <xref linkend="step-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-LDAP_in_Read-only_Mode-Set_up_LDAP_read-only_Mode-Step-4"/>. + Continue to <xref linkend="step-Reference_Guide-LDAP_Integration-LDAP_in_Read-only_Mode-Set_up_LDAP_read-only_Mode-Step-4"/>. </para> </step> </procedure> - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-LDAP_in_Read-only_Mode-Set_up_LDAP_read-only_Mode-MSAD"> + <procedure id="proc-Reference_Guide-LDAP_Integration-LDAP_in_Read-only_Mode-Set_up_LDAP_read-only_Mode-MSAD"> <title>Microsoft Active Directory</title> <step> <para> @@ -369,21 +369,21 @@ </entry> ]]></programlisting> <para> - Refer to <xref linkend="exam-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-Examples-Read_Only_groupTypeMappings"/> for more information about how these <parameter>groupTypeMappings</parameter> operate. + Refer to <xref linkend="exam-Reference_Guide-LDAP_Integration-Examples-Read_Only_groupTypeMappings"/> for more information about how these <parameter>groupTypeMappings</parameter> operate. </para> </step> <step> <para> - Continue to <xref linkend="step-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-LDAP_in_Read-only_Mode-Set_up_LDAP_read-only_Mode-Step-4"/>. + Continue to <xref linkend="step-Reference_Guide-LDAP_Integration-LDAP_in_Read-only_Mode-Set_up_LDAP_read-only_Mode-Step-4"/>. </para> </step> </procedure> - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-LDAP_in_Read-only_Mode-Set_up_LDAP_read-only_Mode-OpenLDAP"> + <procedure id="proc-Reference_Guide-LDAP_Integration-LDAP_in_Read-only_Mode-Set_up_LDAP_read-only_Mode-OpenLDAP"> <title>OpenLDAP</title> <step> <para> - If you have not done so already, install your LDAP server. Refer to <xref linkend="proc-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-LDAP_Set_Up"/> for some assistance. + If you have not done so already, install your LDAP server. Refer to <xref linkend="proc-Reference_Guide-LDAP_Integration-LDAP_Set_Up"/> for some assistance. </para> </step> <step> @@ -409,23 +409,23 @@ </entry> ]]></programlisting> <para> - Refer to <xref linkend="exam-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-Examples-Read_Only_groupTypeMappings"/> for more information about how these <parameter>groupTypeMappings</parameter> operate. + Refer to <xref linkend="exam-Reference_Guide-LDAP_Integration-Examples-Read_Only_groupTypeMappings"/> for more information about how these <parameter>groupTypeMappings</parameter> operate. </para> </step> <step> <para> - Continue to <xref linkend="step-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-LDAP_in_Read-only_Mode-Set_up_LDAP_read-only_Mode-Step-4"/>. + Continue to <xref linkend="step-Reference_Guide-LDAP_Integration-LDAP_in_Read-only_Mode-Set_up_LDAP_read-only_Mode-Step-4"/>. </para> </step> </procedure> </step> - <step id="step-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-LDAP_in_Read-only_Mode-Set_up_LDAP_read-only_Mode-Step-4"> + <step id="step-Reference_Guide-LDAP_Integration-LDAP_in_Read-only_Mode-Set_up_LDAP_read-only_Mode-Step-4"> <para> To use a different LDAP server or directory data, edit the DS-specific <filename>.xml</filename> file you uncommented in <emphasis role="bold">Substep 3a</emphasis> above and change the values to suit your requirements. </para> <para> - Refer to the list in <xref linkend="exam-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-Examples-LDAP_configuration_options"/> for some examples or refer to the product-specific documentation for more information. + Refer to the list in <xref linkend="exam-Reference_Guide-LDAP_Integration-Examples-LDAP_configuration_options"/> for some examples or refer to the product-specific documentation for more information. </para> </step> <step> @@ -480,11 +480,11 @@ Users defined in LDAP should be visible in "<emphasis>Users and groups management</emphasis>" and groups from LDAP should be present as children of <emphasis>/acme/roles</emphasis> and <emphasis>/acme/organization_units</emphasis>. </para> <para> - More information about configuration can be found in <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-PicketLink_IDM_integration"/> and in the PicketLink project <ulink type="http" url="http://anonsvn.jboss.org/repos/picketlink/idm/downloads/docs/1.0.0.GA/Ref...">Reference Guide</ulink>. + More information about configuration can be found in <xref linkend="sect-Reference_Guide-PicketLink_IDM_integration"/> and in the PicketLink project <ulink type="http" url="http://anonsvn.jboss.org/repos/picketlink/idm/downloads/docs/1.0.0.GA/Ref...">Reference Guide</ulink>. </para> </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14_eXo_JCR_1.14-LDAP_Integration-LDAP_as_Default_Store"> + <section id="sect-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-LDAP_as_Default_Store"> <title>LDAP as Default Store</title> <para> Follow the procedure below to set LDAP up as the default identity store for JBoss Enterprise Portal Platform. All default accounts and some of groups that comes with JBoss Enterprise Portal Platform will be created in the LDAP store. @@ -492,11 +492,11 @@ <para> The LDAP server will be configured to store part of the JBoss Enterprise Portal Platform group tree. This means that groups under specified part of the tree will be stored in directory server while all others will be stored in database. </para> - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-LDAP_as_Default_Store-Set_up_LDAP_as_Default_Indentity_Store"> + <procedure id="proc-Reference_Guide-LDAP_Integration-LDAP_as_Default_Store-Set_up_LDAP_as_Default_Indentity_Store"> <title>Set up LDAP as Default Indentity Store</title> <step> <para> - If you have not done so already, install your LDAP server. Refer to <xref linkend="proc-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-LDAP_Set_Up"/> for some assistance. + If you have not done so already, install your LDAP server. Refer to <xref linkend="proc-Reference_Guide-LDAP_Integration-LDAP_Set_Up"/> for some assistance. </para> </step> <step> @@ -528,7 +528,7 @@ </step> <step> <para> - Continue to <xref linkend="step-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-LDAP_as_Default_Store-Set_up_LDAP_as_Default_Indentity_Store-Step-5"/> + Continue to <xref linkend="step-Reference_Guide-LDAP_Integration-LDAP_as_Default_Store-Set_up_LDAP_as_Default_Indentity_Store-Step-5"/> </para> </step> </procedure> @@ -568,7 +568,7 @@ </step> <step> <para> - Continue to <xref linkend="step-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-LDAP_as_Default_Store-Set_up_LDAP_as_Default_Indentity_Store-Step-5"/> + Continue to <xref linkend="step-Reference_Guide-LDAP_Integration-LDAP_as_Default_Store-Set_up_LDAP_as_Default_Indentity_Store-Step-5"/> </para> </step> </procedure> @@ -584,12 +584,12 @@ </step> <step> <para> - Continue to <xref linkend="step-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-LDAP_as_Default_Store-Set_up_LDAP_as_Default_Indentity_Store-Step-5"/> + Continue to <xref linkend="step-Reference_Guide-LDAP_Integration-LDAP_as_Default_Store-Set_up_LDAP_as_Default_Indentity_Store-Step-5"/> </para> </step> </procedure> </step> - <step id="step-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-LDAP_as_Default_Store-Set_up_LDAP_as_Default_Indentity_Store-Step-5"> + <step id="step-Reference_Guide-LDAP_Integration-LDAP_as_Default_Store-Set_up_LDAP_as_Default_Indentity_Store-Step-5"> <para> Uncomment the <parameter>groupTypeMappings</parameter> under "<emphasis>Uncomment for sample LDAP configuration</emphasis>": </para> @@ -603,7 +603,7 @@ </entry> ]]></programlisting> <para> - Refer to <xref linkend="exam-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-Examples-Default_groupTypeMappings"/> for more information about how these <parameter>groupTypeMappings</parameter> operate. + Refer to <xref linkend="exam-Reference_Guide-LDAP_Integration-Examples-Default_groupTypeMappings"/> for more information about how these <parameter>groupTypeMappings</parameter> operate. </para> </step> <step> @@ -611,7 +611,7 @@ To use a different LDAP server or directory data, edit the DS-specific <filename>.xml</filename> file you uncommented in <emphasis role="bold">Step 4</emphasis> above and change the values to suit your requirements. </para> <para> - Refer to the list in <xref linkend="exam-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-Examples-LDAP_configuration_options"/> for some examples or refer to the product-specific documentation for more information. + Refer to the list in <xref linkend="exam-Reference_Guide-LDAP_Integration-Examples-LDAP_configuration_options"/> for some examples or refer to the product-specific documentation for more information. </para> </step> <step> @@ -627,9 +627,9 @@ </procedure> </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14_eXo_JCR_1.14-LDAP_Integration-Examples"> + <section id="sect-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-Examples"> <title>Examples</title> - <example id="exam-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-Examples-LDAP_configuration_options"> + <example id="exam-Reference_Guide-LDAP_Integration-Examples-LDAP_configuration_options"> <title>LDAP configuration</title> <para> The following settings are stored in the Picketlink configuration file that is nominated in the <filename>idm-configuration.xml</filename> file of your deployment (under the <parameter>config</parameter> parameter of the <parameter>PicketLinkIDMService</parameter> component): @@ -645,7 +645,7 @@ </listitem> <listitem> <para> - One of the three example configuration files discussed in <xref linkend="proc-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-LDAP_in_Read-only_mode-Set_up_LDAP_read-only_Mode"/>: + One of the three example configuration files discussed in <xref linkend="proc-Reference_Guide-LDAP_Integration-LDAP_in_Read-only_mode-Set_up_LDAP_read-only_Mode"/>: </para> <simplelist> <member><filename>picketlink-idm-ldap-acme-config.xml</filename></member> @@ -756,7 +756,7 @@ Author [w/email]: Bolesław Dawidowicz (bdawidow(a)redhat.com), Jeff Yu License: ?? --> - <example id="exam-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-Examples-Read_Only_groupTypeMappings"> + <example id="exam-Reference_Guide-LDAP_Integration-Examples-Read_Only_groupTypeMappings"> <title>Read Only groupTypeMappings</title> <para> The <parameter>groupTypeMappings</parameter> exposed in the <filename>idm-configuration.xml</filename> file correspond to <parameter>identity-object-type</parameter> values defined in the DS-specific configuration file (referenced in <emphasis>Sub-step 3a</emphasis> of the DS-specific procedure above). @@ -766,22 +766,22 @@ </para> <programlistingco> <areaspec> - <areaset id="area-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-Examples-Read_Only_groupTypeMappings-config-opends" coords=""> - <area coords="10 40" id="area-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-Examples-Read_Only_groupTypeMappings-config-users-opends" /> - <area coords="14 40" id="area-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-Examples-Read_Only_groupTypeMappings-config-groups-opends" /> + <areaset id="area-Reference_Guide-LDAP_Integration-Examples-Read_Only_groupTypeMappings-config-opends" coords=""> + <area coords="10 40" id="area-Reference_Guide-LDAP_Integration-Examples-Read_Only_groupTypeMappings-config-users-opends" /> + <area coords="14 40" id="area-Reference_Guide-LDAP_Integration-Examples-Read_Only_groupTypeMappings-config-groups-opends" /> </areaset> - <area coords="17 40" id="area-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-Examples-Read_Only_groupTypeMappings-config-read-only-opends" /> + <area coords="17 40" id="area-Reference_Guide-LDAP_Integration-Examples-Read_Only_groupTypeMappings-config-read-only-opends" /> </areaspec> <programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_LDAP/readonly-opends.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> <calloutlist>  - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-Examples-Read_Only_groupTypeMappings-config-opends"> + <callout arearefs="area-Reference_Guide-LDAP_Integration-Examples-Read_Only_groupTypeMappings-config-opends"> <para> The PicketLink IDM configuration file dictates that users and those two group types be stored in LDAP. </para> </callout>  - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-Examples-Read_Only_groupTypeMappings-config-read-only-opends"> + <callout arearefs="area-Reference_Guide-LDAP_Integration-Examples-Read_Only_groupTypeMappings-config-read-only-opends"> <para> An additional option defines that nothing else (except password updates) should be written there. </para> @@ -801,7 +801,7 @@ </para> </example> - <example id="exam-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-Examples-Default_groupTypeMappings"> + <example id="exam-Reference_Guide-LDAP_Integration-Examples-Default_groupTypeMappings"> <title>Default groupTypeMappings</title> <para> The <parameter>groupTypeMappings</parameter> exposed in the <filename>idm-configuration.xml</filename> file correspond to <parameter>identity-object-type</parameter> values defined in the DS-specific configuration file (referenced in <emphasis>Sub-step 3a</emphasis> of the DS-specific procedure above). @@ -811,15 +811,15 @@ </para> <programlistingco> <areaspec> - <areaset id="area-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-Examples-Default_groupTypeMappings-config" coords=""> - <area coords="10 40" id="area-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-Examples-Default_groupTypeMappings-config-1" /> - <area coords="14 40" id="area-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-Examples-Default_groupTypeMappings-config-2" /> + <areaset id="area-Reference_Guide-LDAP_Integration-Examples-Default_groupTypeMappings-config" coords=""> + <area coords="10 40" id="area-Reference_Guide-LDAP_Integration-Examples-Default_groupTypeMappings-config-1" /> + <area coords="14 40" id="area-Reference_Guide-LDAP_Integration-Examples-Default_groupTypeMappings-config-2" /> </areaset> </areaspec> <programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_LDAP/default-ldap.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> <calloutlist>  - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-LDAP_Integration-Examples-Default_groupTypeMappings-config"> + <callout arearefs="area-Reference_Guide-LDAP_Integration-Examples-Default_groupTypeMappings-config"> <para> The <parameter>groupTypeMappings</parameter> define that all groups under <parameter>/platform</parameter> should be stored in PicketLink IDM with the <parameter>platform_type</parameter> group type name and groups under <parameter>/organization</parameter> should be stored in PicketLink IDM with <parameter>organization_type</parameter> group type name. </para> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/OrganizationAPI.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/OrganizationAPI.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/OrganizationAPI.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Organization_API"> +<section id="sect-Reference_Guide-Organization_API"> <title>Organization API</title> <para> The <literal>exo.platform.services.organization</literal> package has five main components: Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/PredefinedUserConfiguration.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/PredefinedUserConfiguration.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/PredefinedUserConfiguration.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Predefined_User_Configuration"> +<section id="sect-Reference_Guide-Predefined_User_Configuration"> <title>Predefined User Configuration</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Predefined_User_Configuration-Overview"> + <section id="sect-Reference_Guide-Predefined_User_Configuration-Overview"> <title>Overview</title> <para> The initial Organization configuration should be specified by editing the content of <filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/02portal.war:/WEB-INF/conf/organization/organization-configuration.xml</filename>. This file uses the portal XML configuration schema. It lists several configuration plug-ins. @@ -13,7 +13,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Predefined_User_Configuration-Plugin_for_adding_users_groups_and_membership_types"> + <section id="sect-Reference_Guide-Predefined_User_Configuration-Plugin_for_adding_users_groups_and_membership_types"> <title>Plugin for adding users, groups and membership types</title> <para> The plugin type <literal>org.exoplatform.services.organization.OrganizationDatabaseInitializer</literal> is used to specify a list of membership types, a list of groups and a list of users to be created. @@ -30,7 +30,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Predefined_User_Configuration-Membership_types"> + <section id="sect-Reference_Guide-Predefined_User_Configuration-Membership_types"> <title>Membership types</title> <para> The predefined membership types are specified in the <emphasis role="bold">membershipType</emphasis> field of the <emphasis role="bold">OrganizationConfig</emphasis> plugin parameter. @@ -46,7 +46,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Predefined_User_Configuration-Groups"> + <section id="sect-Reference_Guide-Predefined_User_Configuration-Groups"> <title>Groups</title> <para> The predefined groups are specified in the <emphasis role="bold">group</emphasis> field of the <emphasis role="bold">OrganizationConfig</emphasis> plugin parameter. @@ -62,7 +62,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Predefined_User_Configuration-Users"> + <section id="sect-Reference_Guide-Predefined_User_Configuration-Users"> <title>Users</title> <para> The predefined users are specified in the <emphasis role="bold">user</emphasis> field of the <emphasis role="bold">OrganizationConfig</emphasis> plugin parameter. @@ -78,7 +78,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Predefined_User_Configuration-Plugin_for_managing_user_creation"> + <section id="sect-Reference_Guide-Predefined_User_Configuration-Plugin_for_managing_user_creation"> <title>Plugin for managing user creation</title> <para> The plugin type <literal>org.exoplatform.services.organization.impl.NewUserEventListener</literal> specifies which groups all newly created users should become members of. 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-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,12 +1,12 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-SSO_Single_Sign_On_"> +<section id="sect-Reference_Guide-SSO_Single_Sign_On_"> <title><remark>SSO - Single Sign On</remark> </title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-SSO_Single_Sign_On_-Overview"> + <section id="sect-Reference_Guide-SSO_Single_Sign_On_-Overview"> <title>Overview</title> <para> JBoss Enterprise Portal Platform provides an implementation of Single Sign On (<literal>SSO</literal>) as an integration and aggregation platform. @@ -23,25 +23,25 @@ <itemizedlist> <listitem> <para> - <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-SSO_Single_Sign_On_-Central_Authentication_Service" /> + <xref linkend="sect-Reference_Guide-SSO_Single_Sign_On_-Central_Authentication_Service" /> </para> </listitem> <listitem> <para> - <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-SSO_Single_Sign_On_-Java_Open_Single_Sign_On_Project" /> + <xref linkend="sect-Reference_Guide-SSO_Single_Sign_On_-Java_Open_Single_Sign_On_Project" /> </para> </listitem> <listitem> <para> - <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-SSO_Single_Sign_On_-OpenSSO" /> + <xref linkend="sect-Reference_Guide-SSO_Single_Sign_On_-OpenSSO" /> </para> </listitem> <listitem> <para> - <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-SSO_Single_Sign_On_-SPNEGO_Simple_and_Protected_GSSAPI_Negotiation_Mechanism" /> + <xref linkend="sect-Reference_Guide-SSO_Single_Sign_On_-SPNEGO_Simple_and_Protected_GSSAPI_Negotiation_Mechanism" /> </para> </listitem> @@ -72,7 +72,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-SSO_Single_Sign_On_-Enabling_SSO_using_JBoss_SSO_Valve"> + <section id="sect-Reference_Guide-SSO_Single_Sign_On_-Enabling_SSO_using_JBoss_SSO_Valve"> <title>Enabling SSO using JBoss SSO Valve</title>  <warning> <title>Username and passwords stored in clear text</title> @@ -28,7 +28,7 @@ <para> Passwords can be encoded prior to being saved to the JCR. This option requires administrators to provide a custom subclass of <parameter>org.exoplatform.web.security.security.AbstractCodec</parameter> and set up a codec implementation with <parameter>CookieTokenService</parameter>: </para> - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Password_Encryption-Encrypt_Password_in_JCR"> + <procedure id="proc-Reference_Guide-Password_Encryption-Encrypt_Password_in_JCR"> <title>Encrypt Password in JCR</title> <step> <para> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/Configuration/DatabaseConfiguration.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/Configuration/DatabaseConfiguration.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/Configuration/DatabaseConfiguration.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Database_Configuration"> +<section id="sect-Reference_Guide-Database_Configuration"> <title>Database Configuration</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Database_Configuration-Overview"> + <section id="sect-Reference_Guide-Database_Configuration-Overview"> <title>Overview</title> <para> JBoss Enterprise Portal Platform has two different database dependencies. One is the identity service configuration, which depends on Hibernate. The other is Java content repository (JCR) service, which depends on JDBC API, and can integrate with any existing datasource implementation. @@ -19,7 +19,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Database_Configuration-Configuring_the_database_for_JCR"> + <section id="sect-Reference_Guide-Database_Configuration-Configuring_the_database_for_JCR"> <title>Configuring the database for JCR</title> <para> To configure the database used by JCR you will need to edit the file: @@ -75,7 +75,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Database_Configuration-Configuring_the_database_for_the_default_identity_store"> + <section id="sect-Reference_Guide-Database_Configuration-Configuring_the_database_for_the_default_identity_store"> <title>Configuring the database for the default identity store</title> <para> By default, users are stored in a database. To change the database in which to store users, you will need to edit the file: Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/Configuration/EMailServiceConfiguration.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/Configuration/EMailServiceConfiguration.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/Configuration/EMailServiceConfiguration.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-E_Mail_Service_Configuration"> +<section id="sect-Reference_Guide-E_Mail_Service_Configuration"> <title>E-Mail Service Configuration</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-E_Mail_Service_Configuration-Overview"> + <section id="sect-Reference_Guide-E_Mail_Service_Configuration-Overview"> <title>Overview</title> <para> JBoss Enterprise Portal Platform includes an e-mail sending service that needs to be configured before it can function properly. This service, for instance, is used to send e-mails to users who forgot their password or username. @@ -13,7 +13,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-E_Mail_Service_Configuration-Configuring_the_outgoing_e_mail_account"> + <section id="sect-Reference_Guide-E_Mail_Service_Configuration-Configuring_the_outgoing_e_mail_account"> <title>Configuring the outgoing e-mail account</title> <para> The e-mail service can use any SMTP account configured in <replaceable>JBOSS_AS</replaceable>/server/<replaceable>PROFILE</replaceable>/conf/gatein/configuration.properties (or <replaceable>TOMCAT_HOME</replaceable>/gatein/conf/configuration.properties if you are using Tomcat). Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/Configuration.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/Configuration.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/Configuration.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Configuration"> +<chapter id="chap-Reference_Guide-Configuration"> <title>Configuration</title> <xi:include href="Configuration/DatabaseConfiguration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> <xi:include href="Configuration/EMailServiceConfiguration.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/GadgetDevelopment/Gadgets.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/GadgetDevelopment/Gadgets.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/GadgetDevelopment/Gadgets.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,14 +1,14 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Concept"> +<section id="sect-Reference_Guide-Concept"> <title>Concept</title> <para> A gadget is a mini web application, embedded in a web page and running on an application server platform. These small applications help users perform various tasks. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Concept-Basic_Usage"> + <section id="sect-Reference_Guide-Concept-Basic_Usage"> <title>Basic Usage</title> <para> JBoss Enterprise Portal Platform includes a Todo gadget, Calendar gadget, Calculator gadget and RSS Reader gadget by default. Many other, third-party gadgets are also supported. Refer to the JBoss Enterprise Portal Platform User Guide at <ulink type="http" url="http://docs.redhat.com" />for information about obtaining and installing gadgets. @@ -16,7 +16,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Concept-Existing_Gadgets"> + <section id="sect-Reference_Guide-Concept-Existing_Gadgets"> <title>Existing Gadgets</title> <mediaobject> <imageobject role="html"> @@ -30,7 +30,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Concept-Create_a_new_Gadget"> + <section id="sect-Reference_Guide-Concept-Create_a_new_Gadget"> <title>Create a new Gadget</title> <mediaobject> <imageobject role="html"> @@ -44,7 +44,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Concept-Remote_Gadget"> + <section id="sect-Reference_Guide-Concept-Remote_Gadget"> <title>Remote Gadget</title> <para> This is the reference to a remote gadget (stock one). @@ -61,7 +61,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Concept-Gadget_Importing"> + <section id="sect-Reference_Guide-Concept-Gadget_Importing"> <title>Gadget Importing</title> <para> After referencing the gadget successfully, then import it into the local repository. @@ -78,7 +78,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Concept-Gadget_Web_Editing"> + <section id="sect-Reference_Guide-Concept-Gadget_Web_Editing"> <title>Gadget Web Editing</title> <para> Edit it from the Web the imported Gadget to modify it: @@ -95,7 +95,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Concept-Gadget_IDE_Editing"> + <section id="sect-Reference_Guide-Concept-Gadget_IDE_Editing"> <title>Gadget IDE Editing</title> <para> Edit it from your IDE thanks to the WebDAV protocol: @@ -112,7 +112,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Concept-Dashboard_Viewing"> + <section id="sect-Reference_Guide-Concept-Dashboard_Viewing"> <title>Dashboard Viewing</title> <para> View it from the Dashboard when you drag and drop the Gadget from listing to the dashboard. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/GadgetDevelopment/SetupGadgetServer.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/GadgetDevelopment/SetupGadgetServer.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/GadgetDevelopment/SetupGadgetServer.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Advanced_Gadget_Administration"> +<section id="sect-Reference_Guide-Advanced_Gadget_Administration"> <title>Advanced Gadget Administration</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Advanced_Gadget_Administration-Virtual_servers_for_gadget_rendering"> + <section id="sect-Reference_Guide-Advanced_Gadget_Administration-Virtual_servers_for_gadget_rendering"> <title>Virtual servers for gadget rendering</title> <para> JBoss Enterprise Portal Platform recommends using two virtual hosts for security. If the gadget is running on a different domain than the container, it is unable to interfere with the portal by modifying code or cookies. @@ -28,9 +28,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Advanced_Gadget_Administration-Configuration"> + <section id="sect-Reference_Guide-Advanced_Gadget_Administration-Configuration"> <title>Configuration</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuration-Security_key"> + <section id="sect-Reference_Guide-Configuration-Security_key"> <title>Security key</title> <para> In JBoss Enterprise Portal Platform, the gadget container uses three security files for authentication and authorization of gadgets: @@ -85,7 +85,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuration-Gadget_proxy_and_concat_configuration"> + <section id="sect-Reference_Guide-Configuration-Gadget_proxy_and_concat_configuration"> <title>Gadget proxy and concat configuration</title> <para> These servers have to be on the same domain as the gadget server. You can configure the container in <filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/eXoGadgetServer.war:/WEB-INF/classes/containers/default/container.js</filename>. @@ -96,7 +96,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuration-Proxy"> + <section id="sect-Reference_Guide-Configuration-Proxy"> <title>Proxy</title> <para> To allow external gadgets when the server is behind a proxy, add the following code to the beginning of the JVM: Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/GadgetDevelopment.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/GadgetDevelopment.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/GadgetDevelopment.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Gadgets"> +<chapter id="chap-Reference_Guide-Gadgets"> <title>Gadgets</title> <xi:include href="GadgetDevelopment/Gadgets.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> <xi:include href="GadgetDevelopment/SetupGadgetServer.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/Introduction.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/Introduction.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/Introduction.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Introduction"> +<chapter id="chap-Reference_Guide-Introduction"> <title>Introduction</title> <para> JBoss Enterprise Portal Platform is based on the GateIn project which is the merge of two mature Java projects; JBoss Portal and eXo Portal. This new community project takes the best of both offerings and incorporates them into a single portal framework. The aim is to provide an intuitive user-friendly portal, and a framework to address the needs of today's Web 2.0 applications. @@ -23,8 +23,8 @@ <note> <title>Notational Devices</title> <para> - Along with the <emphasis>Document Conventions</emphasis> outlined in the <xref linkend="pref-Reference_Guide_eXo_JCR_1.14-Preface" />, this document will also use the following notational devices: - <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Introduction-Devices"> + Along with the <emphasis>Document Conventions</emphasis> outlined in the <xref linkend="pref-Reference_Guide-Preface" />, this document will also use the following notational devices: + <variablelist id="vari-Reference_Guide-Introduction-Devices"> <title>Devices</title> <varlistentry> <term><replaceable><JBOSS_HOME></replaceable></term> @@ -61,7 +61,7 @@ </para> </note> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Introduction-Related_Links"> + <section id="sect-Reference_Guide-Introduction-Related_Links"> <title>Related Links</title> <variablelist> <varlistentry> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/DataImportStrategy.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/DataImportStrategy.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/DataImportStrategy.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Data_Import_Strategy"> +<chapter id="chap-Reference_Guide-Data_Import_Strategy"> <title>Data Import Strategy</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Data_Import_Strategy-Introduction"> + <section id="sect-Reference_Guide-Data_Import_Strategy-Introduction"> <title>Introduction</title> <para> In the Portal extension mechanism, developers can define an extension that Portal data can be customized by configurations in the extension. There are several cases which an extension developer wants to define how to customize the Portal data, for example modifying, overwriting or just inserting a bit into the data defined by the portal. Therefore, GateIn also defines several modes for each case and the only thing which a developer has to do is to clarify the usecase and reasonably configure extensions. @@ -16,7 +16,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Data_Import_Strategy-Import_Mode"> + <section id="sect-Reference_Guide-Data_Import_Strategy-Import_Mode"> <title>Import Mode</title> <para> In this section, the following modes for the import strategy are introduced: @@ -74,12 +74,12 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Data_Import_Strategy-Data_Import_Strategy"> + <section id="sect-Reference_Guide-Data_Import_Strategy-Data_Import_Strategy"> <title>Data Import Strategy</title> <para> The 'Portal Data' term which has been referred in the previous sections can be classified into three types of object data: Portal Config, Page Data and Navigation Data; each of which has some differences in the import strategy. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Data_Import_Strategy-Navigation_Data"> + <section id="sect-Reference_Guide-Data_Import_Strategy-Navigation_Data"> <title>Navigation Data</title> <para> The navigation data import strategy will be processed to the import mode level as the followings: @@ -187,7 +187,7 @@ <para> For example, the <emphasis>navigation1</emphasis> is loaded before <emphasis>navigation2</emphasis>. The Navigation Importer processes on two navigation definitions, depending on the Import Mode defined in portal configuration. </para> - <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Navigation_Data-Import_Mode_Cases"> + <variablelist id="vari-Reference_Guide-Navigation_Data-Import_Mode_Cases"> <title>Import Mode Cases</title> <varlistentry> <term>Case 1: <literal>CONSERVE</literal></term> @@ -261,7 +261,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Data_Import_Strategy-Portal_Config"> + <section id="sect-Reference_Guide-Data_Import_Strategy-Portal_Config"> <title>Portal Config</title> <para> PortalConfig defines the portal name, permission, layout and some properties of a site. These information are configured in the <emphasis>portal.xml</emphasis>, <emphasis>group.xml</emphasis> or <emphasis>user.xml</emphasis>, depending on the site type. The PortalConfig importer performs a strategy that is based on the mode defined in NewPortalConfigListener, including <literal>CONSERVE</literal>, <literal>INSERT</literal>, <literal>MERGE</literal> or <literal>OVERWRITE</literal>. Let's see how the import mode affects in the process of portal data performance: @@ -290,7 +290,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Data_Import_Strategy-Page_Data"> + <section id="sect-Reference_Guide-Data_Import_Strategy-Page_Data"> <title>Page Data</title> <para> The import mode affects the page data import as the same as Portal Config. 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-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalConfiguration.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Default_Portal_Configuration"> +<chapter id="chap-Reference_Guide-Default_Portal_Configuration"> <title>Default Portal Configuration</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Default_Portal_Configuration-Overview"> + <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). @@ -19,7 +19,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Default_Portal_Configuration-Configuration"> + <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>". 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-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalNavigationConfiguration.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Portal_Navigation_Configuration"> +<chapter id="chap-Reference_Guide-Portal_Navigation_Configuration"> <title>Portal Navigation Configuration</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Portal_Navigation_Configuration-Overview"> + <section id="sect-Reference_Guide-Portal_Navigation_Configuration-Overview"> <title>Overview</title> <para> There are three types of navigation available to portal users: @@ -13,19 +13,19 @@ <itemizedlist> <listitem> <para> - <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Portal_Navigation_Configuration-Portal_Navigation" /> + <xref linkend="sect-Reference_Guide-Portal_Navigation_Configuration-Portal_Navigation" /> </para> </listitem> <listitem> <para> - <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Portal_Navigation_Configuration-Group_Navigation" /> + <xref linkend="sect-Reference_Guide-Portal_Navigation_Configuration-Group_Navigation" /> </para> </listitem> <listitem> <para> - <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Portal_Navigation_Configuration-User_Navigation" /> + <xref linkend="sect-Reference_Guide-Portal_Navigation_Configuration-User_Navigation" /> </para> </listitem> @@ -47,10 +47,10 @@ </para> <programlistingco> <areaspec> - <area coords="5" id="area-Reference_Guide_eXo_JCR_1.14-Portal_Navigation_Configuration-Overview-predifinedOwner" /> - <area coords="10" id="area-Reference_Guide_eXo_JCR_1.14-Portal_Navigation_Configuration-Overview-ownerType" /> - <area coords="13" id="area-Reference_Guide_eXo_JCR_1.14-Portal_Navigation_Configuration-Overview-templateLocation" /> - <area coords="16" id="area-Reference_Guide_eXo_JCR_1.14-Portal_Navigation_Configuration-Overview-importMode" /> + <area coords="5" id="area-Reference_Guide-Portal_Navigation_Configuration-Overview-predifinedOwner" /> + <area coords="10" id="area-Reference_Guide-Portal_Navigation_Configuration-Overview-ownerType" /> + <area coords="13" id="area-Reference_Guide-Portal_Navigation_Configuration-Overview-templateLocation" /> + <area coords="16" id="area-Reference_Guide-Portal_Navigation_Configuration-Overview-importMode" /> </areaspec> @@ -79,25 +79,25 @@ </programlistingco> <calloutlist> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Portal_Navigation_Configuration-Overview-predifinedOwner"> + <callout arearefs="area-Reference_Guide-Portal_Navigation_Configuration-Overview-predifinedOwner"> <para> <parameter>predefinedOwner</parameter> defines the navigation owner, portal will look for the configuration files in folder with this name, if there is no suitable folder, a default portal will be created with name is this value. </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Portal_Navigation_Configuration-Overview-ownerType"> + <callout arearefs="area-Reference_Guide-Portal_Navigation_Configuration-Overview-ownerType"> <para> <parameter>ownerType</parameter> define the type of portal navigation. It may be a portal, group or user </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Portal_Navigation_Configuration-Overview-templateLocation"> + <callout arearefs="area-Reference_Guide-Portal_Navigation_Configuration-Overview-templateLocation"> <para> <parameter>templateLocation</parameter> the classpath where contains all portal configuration files </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Portal_Navigation_Configuration-Overview-importMode"> + <callout arearefs="area-Reference_Guide-Portal_Navigation_Configuration-Overview-importMode"> <para> <parameter>importMode</parameter> The mode for navigation import. There are 4 types of import mode: </para> @@ -144,7 +144,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Portal_Navigation_Configuration-Portal_Navigation"> + <section id="sect-Reference_Guide-Portal_Navigation_Configuration-Portal_Navigation"> <title>Portal Navigation</title>  <para> The portal navigation incorporates the pages that can be accessed even when a user is not logged in (assuming the applicable permissions allow public access). For example; several portal navigations could be used when a company has multiple trademarks, and websites are set up for each of them. @@ -215,13 +215,13 @@ </para> <programlistingco> <areaspec> - <area coords="9 40" id="area-Reference_Guide_eXo_JCR_1.14-Portal_Navigation_Configuration-Portal_Navigation-subpage" /> + <area coords="9 40" id="area-Reference_Guide-Portal_Navigation_Configuration-Portal_Navigation-subpage" /> </areaspec> <programlisting language="XML" role="XML"><xi:include href="../../extras/PortalDevelopment_DefaultPortalNavigationConfiguration/subpage.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> <calloutlist> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Portal_Navigation_Configuration-Portal_Navigation-subpage"> + <callout arearefs="area-Reference_Guide-Portal_Navigation_Configuration-Portal_Navigation-subpage"> <para> This element defines the parent/child relationship between a page and a subnode. </para> @@ -256,13 +256,13 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Portal_Navigation_Configuration-Group_Navigation"> + <section id="sect-Reference_Guide-Portal_Navigation_Configuration-Group_Navigation"> <title>Group Navigation</title> <para> Group navigations are dynamically added to the user navigation at login. This allows users to see the pages assigned to any groups they belong to in the menu. </para> <para> - The group navigation menu is configured by two XML files (<filename>navigation.xml</filename> and <filename>pages.xml</filename>). The syntax used in these files is the same as those covered in <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Portal_Navigation_Configuration-Portal_Navigation" />. + The group navigation menu is configured by two XML files (<filename>navigation.xml</filename> and <filename>pages.xml</filename>). The syntax used in these files is the same as those covered in <xref linkend="sect-Reference_Guide-Portal_Navigation_Configuration-Portal_Navigation" />. </para> <para> They are located in <filename>02portal.war/WEB-INF/conf/portal/group<replaceable>/group-name-path/</replaceable></filename> directory (For example; <filename>02portal.war/WEB-INF/conf/portal/group/platform/administrators/</filename>). @@ -270,7 +270,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Portal_Navigation_Configuration-User_Navigation"> + <section id="sect-Reference_Guide-Portal_Navigation_Configuration-User_Navigation"> <title>User Navigation</title> <para> User navigation is the set of nodes and pages that are owned by a user. They are part of the user's dashboard. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalPermissionConfiguration.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalPermissionConfiguration.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/DefaultPortalPermissionConfiguration.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Portal_Default_Permission_Configuration"> +<chapter id="chap-Reference_Guide-Portal_Default_Permission_Configuration"> <title>Portal Default Permission Configuration</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Portal_Default_Permission_Configuration-Overview"> + <section id="sect-Reference_Guide-Portal_Default_Permission_Configuration-Overview"> <title>Overview</title> <para> The default permission configuration for the portal is defined through the <literal>org.exoplatform.portal.config.UserACL</literal> component configuration in the <filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/02portal.war:/WEB-INF/conf/portal/portal-configuration.xml</filename> file. @@ -101,7 +101,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Portal_Default_Permission_Configuration-Overwrite_Portal_Default_Permissions"> + <section id="sect-Reference_Guide-Portal_Default_Permission_Configuration-Overwrite_Portal_Default_Permissions"> <title>Overwrite Portal Default Permissions</title> <para> When creating custom portals and portal extensions it is possible to override the default configuration by using <literal>org.exoplatform.portal.config.PortalACLPlugin</literal>, configuring it as an external-plugin of <literal>org.exoplatform.portal.config.UserACL</literal> service: Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/InternationalizationConfiguration.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/InternationalizationConfiguration.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/InternationalizationConfiguration.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Internationalization_Configuration"> +<chapter id="chap-Reference_Guide-Internationalization_Configuration"> <title>Internationalization Configuration</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Internationalization_Configuration-Overview"> + <section id="sect-Reference_Guide-Internationalization_Configuration-Overview"> <title>Overview</title> <note> <title>Assumed Knowledge</title> @@ -51,14 +51,14 @@ Property files have to be ISO 8859-1 encoded, while the XML file can define its encoding. As a result it's easier for a human being to read a translation in XML instead of having to decode and encode the property file. </para> <para> - For more information refer to: <xref linkend="chap-Reference_Guide_eXo_JCR_1.14-XML_Resources_Bundles" /> + For more information refer to: <xref linkend="chap-Reference_Guide-XML_Resources_Bundles" /> </para> </note> </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Internationalization_Configuration-Locales_Configuration"> + <section id="sect-Reference_Guide-Internationalization_Configuration-Locales_Configuration"> <title>Locales Configuration</title> <para> Various languages are available in the portal package. The configuration below will define which languages are shown in the "<emphasis role="bold">Change Language</emphasis>" section and made available to users. @@ -76,43 +76,43 @@ </para> <programlistingco> <areaspec> - <area coords="4" id="area-Reference_Guide_eXo_JCR_1.14-Internationalization_Configuration-Locales_Configuration-locale" /> - <area coords="5" id="area-Reference_Guide_eXo_JCR_1.14-Internationalization_Configuration-Locales_Configuration-output-encoding" /> - <area coords="6" id="area-Reference_Guide_eXo_JCR_1.14-Internationalization_Configuration-Locales_Configuration-input-encoding" /> - <area coords="7" id="area-Reference_Guide_eXo_JCR_1.14-Internationalization_Configuration-Locales_Configuration-description" /> - <area coords="22" id="area-Reference_Guide_eXo_JCR_1.14-Internationalization_Configuration-Locales_Configuration-orientation" /> + <area coords="4" id="area-Reference_Guide-Internationalization_Configuration-Locales_Configuration-locale" /> + <area coords="5" id="area-Reference_Guide-Internationalization_Configuration-Locales_Configuration-output-encoding" /> + <area coords="6" id="area-Reference_Guide-Internationalization_Configuration-Locales_Configuration-input-encoding" /> + <area coords="7" id="area-Reference_Guide-Internationalization_Configuration-Locales_Configuration-description" /> + <area coords="22" id="area-Reference_Guide-Internationalization_Configuration-Locales_Configuration-orientation" /> </areaspec> <programlisting language="XML" role="XML"><xi:include href="../../extras/PortalDevelopment_InternationalizationConfiguration/default150.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> <calloutlist> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Internationalization_Configuration-Locales_Configuration-locale"> + <callout arearefs="area-Reference_Guide-Internationalization_Configuration-Locales_Configuration-locale"> <para> <emphasis>locale</emphasis>: The locale has to be defined as per the codes defined <ulink type="http" url="http://ftp.ics.uci.edu/pub/ietf/http/related/iso639.txt">here</ulink>. In this example "<emphasis>ar</emphasis>" is Arabic. </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Internationalization_Configuration-Locales_Configuration-output-encoding"> + <callout arearefs="area-Reference_Guide-Internationalization_Configuration-Locales_Configuration-output-encoding"> <para> <emphasis>output-encoding</emphasis>: deals with character encoding. It is recommended that <emphasis role="bold">UTF-8</emphasis> be used. </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Internationalization_Configuration-Locales_Configuration-input-encoding"> + <callout arearefs="area-Reference_Guide-Internationalization_Configuration-Locales_Configuration-input-encoding"> <para> <emphasis>input-encoding</emphasis>: In the Java implementation, the encoding parameters will be used for the request response stream. The input-encoding parameter will be used for request <literal>setCharacterEncoding(..)</literal>. </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Internationalization_Configuration-Locales_Configuration-description"> + <callout arearefs="area-Reference_Guide-Internationalization_Configuration-Locales_Configuration-description"> <para> <emphasis>description</emphasis>: A description of the language </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Internationalization_Configuration-Locales_Configuration-orientation"> + <callout arearefs="area-Reference_Guide-Internationalization_Configuration-Locales_Configuration-orientation"> <para> - <emphasis>orientation</emphasis>: Although the default orientation of text and images is Left-To-Right, JBoss Enterprise Portal Platform supports <emphasis role="bold">Right-To-Left</emphasis> orientation. Modifying text orientation is explained in <xref linkend="chap-Reference_Guide_eXo_JCR_1.14-Right_To_Left_RTL_Framework" />. + <emphasis>orientation</emphasis>: Although the default orientation of text and images is Left-To-Right, JBoss Enterprise Portal Platform supports <emphasis role="bold">Right-To-Left</emphasis> orientation. Modifying text orientation is explained in <xref linkend="chap-Reference_Guide-Right_To_Left_RTL_Framework" />. </para> </callout> @@ -124,27 +124,27 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Internationalization_Configuration-ResourceBundleService"> + <section id="sect-Reference_Guide-Internationalization_Configuration-ResourceBundleService"> <title>ResourceBundleService</title> <para> The resource bundle service is configured in: <filename>02portal.war:/WEB-INF/conf/common/common-configuration.xml</filename>: </para> <programlistingco> <areaspec> - <area coords="6 60" id="area-Reference_Guide_eXo_JCR_1.14-Internationalization_Configuration-ResourceBundleService-classpath_resources" /> - <area coords="24 60" id="area-Reference_Guide_eXo_JCR_1.14-Internationalization_Configuration-ResourceBundleService-portal_resource_names" /> + <area coords="6 60" id="area-Reference_Guide-Internationalization_Configuration-ResourceBundleService-classpath_resources" /> + <area coords="24 60" id="area-Reference_Guide-Internationalization_Configuration-ResourceBundleService-portal_resource_names" /> </areaspec> <programlisting language="XML" role="XML"><xi:include href="../../extras/PortalDevelopment_InternationalizationConfiguration/default151.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> <calloutlist> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Internationalization_Configuration-ResourceBundleService-classpath_resources"> + <callout arearefs="area-Reference_Guide-Internationalization_Configuration-ResourceBundleService-classpath_resources"> <para> <emphasis>classpath.resources</emphasis>: These are discussed in a later section. </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Internationalization_Configuration-ResourceBundleService-portal_resource_names"> + <callout arearefs="area-Reference_Guide-Internationalization_Configuration-ResourceBundleService-portal_resource_names"> <para> <emphasis>portal.resource.names</emphasis>: Defines all resources that belong to the <emphasis>Portal Resource Bundle</emphasis>. </para> @@ -161,7 +161,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Internationalization_Configuration-Navigation_Resource_Bundles"> + <section id="sect-Reference_Guide-Internationalization_Configuration-Navigation_Resource_Bundles"> <title>Navigation Resource Bundles</title> <para> There is a resource bundle for each navigation. A navigation can exist for user, groups, and portal. @@ -189,7 +189,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Internationalization_Configuration-Portlets"> + <section id="sect-Reference_Guide-Internationalization_Configuration-Portlets"> <title>Portlets</title> <para> Portlets are independent applications and deliver their own resource files. @@ -197,7 +197,7 @@ <para> All shipped portlet resources are located in the <emphasis role="bold">locale/portlet</emphasis> subfolder. The ResourceBundleService parameter <emphasis role="bold">classpath.resources</emphasis> defines this subfolder.  </para> - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Portlets-To_add_a_Spanish_translation_to_the_GadgetPortlet"> + <procedure id="proc-Reference_Guide-Portlets-To_add_a_Spanish_translation_to_the_GadgetPortlet"> <title>To add a Spanish translation to the <parameter>GadgetPortlet</parameter></title> <step> <para> @@ -221,7 +221,7 @@ <para> See the portlet specification for more details about portlet internationalization. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Portlets-Standard_Portlet_Resource_Keys"> + <section id="sect-Reference_Guide-Portlets-Standard_Portlet_Resource_Keys"> <title>Standard Portlet Resource Keys</title> <para> The portlet specification defines three standard keys: <emphasis>Title</emphasis>, <emphasis>Short Title</emphasis> and <emphasis>Keywords</emphasis>. Keywords is formatted as a comma-separated list of tags. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/JavascriptConfiguration.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/JavascriptConfiguration.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/JavascriptConfiguration.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Javascript_Configuration"> +<chapter id="chap-Reference_Guide-Javascript_Configuration">  <title>Javascript Configuration</title> <para> Managing Javascript scripts in an application like JBoss Enterprise Portal Platform is a critical part of the configuration work. Configuring the scripts correctly will result in a faster response time from the portal. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/JavascriptInterApplicationCommunication.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/JavascriptInterApplicationCommunication.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/JavascriptInterApplicationCommunication.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-JavaScript_Inter_Application_Communication"> +<chapter id="chap-Reference_Guide-JavaScript_Inter_Application_Communication"> <title>JavaScript Inter Application Communication</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JavaScript_Inter_Application_Communication-Overview"> + <section id="sect-Reference_Guide-JavaScript_Inter_Application_Communication-Overview"> <title>Overview</title> <para> JavaScript Inter Application Communication is designed to allow applications within a page to exchange data. This library is made for broadcasting messages on topic. @@ -37,7 +37,7 @@ <para> A subscription to a topic will receive any subtopic messages. For example, an application subscribed to "<literal>/eXo/application</literal>" will receive messages sent on the "<literal>/eXo/application/map</literal>" topic. A message sent on "<literal>/eXo</literal>", however, would not be received. </para> - <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Overview-Subscription_Topics"> + <variablelist id="vari-Reference_Guide-Overview-Subscription_Topics"> <title>Subscription Topics</title> <varlistentry> <term>/eXo</term> @@ -64,7 +64,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JavaScript_Inter_Application_Communication-Library"> + <section id="sect-Reference_Guide-JavaScript_Inter_Application_Communication-Library"> <title>Library</title> <para> The Inter Application Communication library is found in <filename>01eXoResources.war:/javascript/eXo/core/Topic.js</filename> @@ -74,7 +74,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JavaScript_Inter_Application_Communication-Syntax"> + <section id="sect-Reference_Guide-JavaScript_Inter_Application_Communication-Syntax"> <title>Syntax</title> <para> The three messaging functions require particular objects and definitions in their syntax: @@ -201,7 +201,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JavaScript_Inter_Application_Communication-Example_of_Javascript_events_usage"> + <section id="sect-Reference_Guide-JavaScript_Inter_Application_Communication-Example_of_Javascript_events_usage"> <title>Example of Javascript events usage</title> <programlisting language="XML" role="XML"><xi:include href="../../extras/PortalDevelopment_JavascriptInterApplicationCommunication/default157.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/LocalizationConfiguration.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/LocalizationConfiguration.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/LocalizationConfiguration.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Localization_Configuration"> +<chapter id="chap-Reference_Guide-Localization_Configuration"> <title>Localization Configuration</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Localization_Configuration-Pluggable_Locale_Policy"> + <section id="sect-Reference_Guide-Localization_Configuration-Pluggable_Locale_Policy"> <title>Pluggable Locale Policy</title> <para> Every request processed by every portlet is invoked within a context of the current <literal>Locale</literal>. @@ -25,7 +25,7 @@ <para> As there is more than one way to determine the <literal>Locale</literal> to be used for displaying a portal page, the mechanism for determining the current <literal>Locale</literal> of the request is pluggable in JBoss Enterprise Portal Platform, and the exact algorithm can be customized. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Pluggable_Locale_Policy-LocalePolicy_API"> + <section id="sect-Reference_Guide-Pluggable_Locale_Policy-LocalePolicy_API"> <title>LocalePolicy API</title> <para> Customization is achieved by using LocalePolicy API, which is a simple API consisting of one interface, and one class: @@ -61,7 +61,7 @@ The returned <literal>Locale</literal> has to be one of the locales supported by portal, otherwise it will fall back to the portal default <literal>Locale</literal>. </para> <para> - The supported locales are listed in <filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/02portal.war/WEB-INF/conf/common/locales-config.xml</filename> file as described in <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Internationalization_Configuration-Locales_Configuration" /> . + The supported locales are listed in <filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/02portal.war/WEB-INF/conf/common/locales-config.xml</filename> file as described in <xref linkend="sect-Reference_Guide-Internationalization_Configuration-Locales_Configuration" /> . </para> <para> The <literal>determineLocale()</literal> method takes a parameter of type <literal>LocaleContextInfo</literal>, which represents a compilation of preferred locales from different sources; user’s profile, portal default, browser language settings, current session, browser cookie. @@ -72,7 +72,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Pluggable_Locale_Policy-Default_LocalePolicy"> + <section id="sect-Reference_Guide-Pluggable_Locale_Policy-Default_LocalePolicy"> <title>Default <literal>LocalePolicy</literal></title> <para> By default, <literal>org.exoplatform.portal.application.localization.DefaultLocalePolicyService</literal>, an implementation of <literal>LocalePolicy</literal>, is installed to provide the default behavior. This, however, can easily be extended and overridden. A completely new implementation can also be written from scratch. @@ -83,7 +83,7 @@ <para> Here is an algorithm used for anonymous users. </para> - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Default_LocalePolicy-An_algorithm_for_anonymous_users"> + <procedure id="proc-Reference_Guide-Default_LocalePolicy-An_algorithm_for_anonymous_users"> <title>An algorithm for anonymous users</title> <step> <para> @@ -151,7 +151,7 @@ <para> The algorithm for logged-in users is virtually the same except that the first <literal>Locale</literal> source checked is user's profile. </para> - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Default_LocalePolicy-An_algorithm_for_logged_in_users"> + <procedure id="proc-Reference_Guide-Default_LocalePolicy-An_algorithm_for_logged_in_users"> <title>An algorithm for logged-in users</title> <step> <para> @@ -194,7 +194,7 @@ </step> <step> <para> - Perform the rest of the steps in <xref linkend="proc-Reference_Guide_eXo_JCR_1.14-Default_LocalePolicy-An_algorithm_for_anonymous_users" />. + Perform the rest of the steps in <xref linkend="proc-Reference_Guide-Default_LocalePolicy-An_algorithm_for_anonymous_users" />. </para> </step> @@ -204,7 +204,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Pluggable_Locale_Policy-Custom_LocalePolicy"> + <section id="sect-Reference_Guide-Pluggable_Locale_Policy-Custom_LocalePolicy"> <title>Custom <literal>LocalePolicy</literal></title> <para> The easiest way to customize the <literal>LocalePolicy</literal> is to extend <literal>DefaultLocalePolicyService</literal>. A study of the source code is required. JavaDocs provide thorough information on this. @@ -234,7 +234,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Pluggable_Locale_Policy-LocalePolicy_Configuration"> + <section id="sect-Reference_Guide-Pluggable_Locale_Policy-LocalePolicy_Configuration"> <title>LocalePolicy Configuration</title> <para> The <literal>LocalePolicy</literal> framework is enabled for portlets by configuring <literal>LocalizationLifecycle</literal> class in portal's webui configuration file: <filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/02portal.war/WEB-INF/webui-configuration.xml</filename>: @@ -266,7 +266,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Pluggable_Locale_Policy-Keeping_non_bridged_resources_in_sync_with_current_Locale"> + <section id="sect-Reference_Guide-Pluggable_Locale_Policy-Keeping_non_bridged_resources_in_sync_with_current_Locale"> <title>Keeping non-bridged resources in sync with current Locale</title> <para> All the resources in portals that are not portlets themselves, but are accessed through portlets - reading data through <literal>PortletRequest</literal>, and writing to <literal>PortletResponse</literal> - are referred to as 'bridged'. Any resources that are accessed directly, bypassing portal filters and servlets, are referred to as 'non-bridged'. 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-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/NavigationController.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Navigation_Controller_"> +<chapter id="chap-Reference_Guide-Navigation_Controller_"> <title>Navigation Controller </title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Navigation_Controller_-Description"> + <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: @@ -34,9 +34,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Navigation_Controller_-Controller_in_Action"> + <section id="sect-Reference_Guide-Navigation_Controller_-Controller_in_Action"> <title>Controller in Action</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Controller_in_Action-Controller"> + <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. @@ -71,7 +71,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Controller_in_Action-Building_Controller"> + <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. @@ -143,7 +143,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Controller_in_Action-Controller_Configuration_controller.xml"> + <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 @@ -166,7 +166,7 @@ <para> A parameter is defined by a qualified name and there are three kind of parameters </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Controller_Configuration_controller.xml-_Route_parameters_"> + <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. @@ -218,7 +218,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Controller_Configuration_controller.xml-_Path_parameters_Regular_expression_support_"> + <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. @@ -297,7 +297,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Controller_Configuration_controller.xml-Request_parameters"> + <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. @@ -383,7 +383,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Controller_Configuration_controller.xml-Route_precedence"> + <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. @@ -407,7 +407,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Controller_Configuration_controller.xml-Route_nesting"> + <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 @@ -475,9 +475,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Navigation_Controller_-Integrate_to_JBoss_Enterprise_Portal_Platform_WebUI_framework"> + <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_eXo_JCR_1.14-Integrate_to_JBoss_Enterprise_Portal_Platform_WebUI_framework-Routing"> + <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> @@ -542,12 +542,12 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Integrate_to_JBoss_Enterprise_Portal_Platform_WebUI_framework-Rendering"> + <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_eXo_JCR_1.14-Rendering-_PortalURL_"> + <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. @@ -642,7 +642,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Rendering-_Node_URL_"> + <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: @@ -679,7 +679,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Rendering-_Component_URL_"> + <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: @@ -695,7 +695,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Rendering-Portlet_URLs"> + <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>: @@ -730,7 +730,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Rendering-Webui_URLBuilder_"> + <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: @@ -753,7 +753,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Rendering-Groovy_Templates"> + <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: @@ -789,7 +789,7 @@ </section> -  <section id="sect-Reference_Guide_eXo_JCR_1.14-Portal_Life_cycle-The_Command_Servlet"> + --> <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>. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/RTLFramework.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/RTLFramework.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/RTLFramework.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Right_To_Left_RTL_Framework"> +<chapter id="chap-Reference_Guide-Right_To_Left_RTL_Framework"> <title>Right To Left (RTL) Framework</title> <para> The text orientation depends on the current locale setting. The orientation is a Java 5 enum that provides a set of functionalities: @@ -19,7 +19,7 @@ </para> <para> In the case of a different context, it delegates to the parent context given the fact that the root <literal>RequestContext</literal> is always a <literal>PortalRequestContext</literal>. - </para> --> <section id="sect-Reference_Guide_eXo_JCR_1.14-Right_To_Left_RTL_Framework-Groovy_templates"> + </para> --> <section id="sect-Reference_Guide-Right_To_Left_RTL_Framework-Groovy_templates"> <title>Groovy templates</title> <para> Orientation is defined by implicit variables passed into the groovy binding context: @@ -70,7 +70,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Right_To_Left_RTL_Framework-Stylesheet"> + <section id="sect-Reference_Guide-Right_To_Left_RTL_Framework-Stylesheet"> <title>Stylesheet</title> <para> The skin service handles stylesheet rewriting to accommodate the orientation. @@ -87,7 +87,7 @@ <para> In the example below we need to use the orientation to modify the float attribute that will make the horizontal tabs either float on left or on right: </para> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Stylesheet-Example_1"> + <example id="exam-Reference_Guide-Stylesheet-Example_1"> <title>Example 1</title> <programlisting language="Java" role="Java"><xi:include href="../../extras/PortalDevelopment_RTLFramework/default173.java" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> @@ -106,7 +106,7 @@ <para> In this example we need to modify the padding according to the orientation: </para> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Stylesheet-Example_2"> + <example id="exam-Reference_Guide-Stylesheet-Example_2"> <title>Example 2</title> <programlisting language="Java" role="Java"><xi:include href="../../extras/PortalDevelopment_RTLFramework/default176.java" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> @@ -125,7 +125,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Right_To_Left_RTL_Framework-Images"> + <section id="sect-Reference_Guide-Right_To_Left_RTL_Framework-Images"> <title>Images</title> <para> Sometimes it is necessary to create an RT version of an image that will be used from a template or from a stylesheet. However symmetric images can be automatically generated, avoiding the necessity to create a mirrored version of an image and further maintenance costs. @@ -150,7 +150,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Right_To_Left_RTL_Framework-Client_Side_JavaScript"> + <section id="sect-Reference_Guide-Right_To_Left_RTL_Framework-Client_Side_JavaScript"> <title>Client Side JavaScript</title> <para> The <literal>eXo.core.I18n</literal> object provides the following parameters for orientation: Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/Skinning.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/Skinning.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/Skinning.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Skinning_the_Portal"> +<chapter id="chap-Reference_Guide-Skinning_the_Portal"> <title>Skinning the Portal</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Skinning_the_Portal-Overview"> + <section id="sect-Reference_Guide-Skinning_the_Portal-Overview"> <title>Overview</title> <para> JBoss Enterprise Portal Platform provides robust skinning support for the entire portal User Interface (UI). This includes support for skinning all of the common portal elements as well as being able to provide custom skins and window decoration for individual portlets. This has been designed with common graphic resource reuse and ease of development in mind. @@ -13,7 +13,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Skinning_the_Portal-Skin_Components"> + <section id="sect-Reference_Guide-Skinning_the_Portal-Skin_Components"> <title>Skin Components</title> <para> The skin of a page is composed of three separate parts: @@ -87,9 +87,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Skinning_the_Portal-Skin_Selection"> + <section id="sect-Reference_Guide-Skinning_the_Portal-Skin_Selection"> <title>Skin Selection</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Skin_Selection-Skin_Selection_Through_the_User_Interface"> + <section id="sect-Reference_Guide-Skin_Selection-Skin_Selection_Through_the_User_Interface"> <title>Skin Selection Through the User Interface</title> <para> A skin can be selected to be displayed to the user by multiple means. The easiest way to change the skin is to select it through the user interface. An administrator can change the default skin for the portal, or a logged in user can select which skin they would prefer to be displayed. @@ -100,7 +100,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Skin_Selection-Setting_the_Default_Skin_within_the_Configuration_Files"> + <section id="sect-Reference_Guide-Skin_Selection-Setting_the_Default_Skin_within_the_Configuration_Files"> <title>Setting the Default Skin within the Configuration Files</title> <para> The default skin can also be configured using the portal configuration files. This allows the portal to have the new default skin ready for use when JBoss Enterprise Portal Platform is first started. @@ -119,7 +119,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Skinning_the_Portal-Skins_in_Page_Markups"> + <section id="sect-Reference_Guide-Skinning_the_Portal-Skins_in_Page_Markups"> <title>Skins in Page Markups</title> <para> A JBoss Enterprise Portal Platform skin contains CSS styles for the portal's components but also shares components that may be reused in portlets. When JBoss Enterprise Portal Platform generates a portal page markup, it inserts stylesheet links in the page's <literal>head</literal> tag. @@ -165,12 +165,12 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Skinning_the_Portal-The_Skin_Service"> + <section id="sect-Reference_Guide-Skinning_the_Portal-The_Skin_Service"> <title>The Skin Service</title> <para> The skin service manages the various types of skins. It is responsible for discovering and deploying skins into the portal. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-The_Skin_Service-Skin_configuration"> + <section id="sect-Reference_Guide-The_Skin_Service-Skin_configuration"> <title>Skin configuration</title> <para> JBoss Enterprise Portal Platform automatically discovers web archives that contain a file descriptor for skins (<filename>WEB-INF/gatein-resources.xml</filename>). This file is responsible for specifying the portal, portlet and window decorators to be deployed into the skin service. @@ -186,7 +186,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-The_Skin_Service-Resource_Request_Filter"> + <section id="sect-Reference_Guide-The_Skin_Service-Resource_Request_Filter"> <title>Resource Request Filter</title> <para> Because of JBoss Enterprise Portal Platform's Right-To-Left support, all CSS files need to be retrieved through a Servlet filter and the web application needs to be configured to activate this filter. This is already done for <literal>01eXoResources.war</literal> web application which contains the default skin. @@ -209,7 +209,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Skinning_the_Portal-The_Default_Skin"> + <section id="sect-Reference_Guide-Skinning_the_Portal-The_Default_Skin"> <title>The Default Skin</title> <para> The default skin for JBoss Enterprise Portal Platform is located as part of the <literal>01eXoResources.war</literal>. The main files associated with the skin are: @@ -243,34 +243,34 @@ </para> <programlistingco> <areaspec> - <area coords="1" id="area-Reference_Guide_eXo_JCR_1.14-Skinning_the_Portal-The_Default_Skin-uiportletapplication" /> - <area coords="2" id="area-Reference_Guide_eXo_JCR_1.14-Skinning_the_Portal-The_Default_Skin-components" /> - <area coords="3" id="area-Reference_Guide_eXo_JCR_1.14-Skinning_the_Portal-The_Default_Skin-portletthemes" /> - <area coords="4" id="area-Reference_Guide_eXo_JCR_1.14-Skinning_the_Portal-The_Default_Skin-portlet" /> + <area coords="1" id="area-Reference_Guide-Skinning_the_Portal-The_Default_Skin-uiportletapplication" /> + <area coords="2" id="area-Reference_Guide-Skinning_the_Portal-The_Default_Skin-components" /> + <area coords="3" id="area-Reference_Guide-Skinning_the_Portal-The_Default_Skin-portletthemes" /> + <area coords="4" id="area-Reference_Guide-Skinning_the_Portal-The_Default_Skin-portlet" /> </areaspec> <programlisting language="Java" role="Java"><xi:include href="../../extras/PortalDevelopment_Skinning/default184.java" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> <calloutlist> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Skinning_the_Portal-The_Default_Skin-uiportletapplication"> + <callout arearefs="area-Reference_Guide-Skinning_the_Portal-The_Default_Skin-uiportletapplication"> <para> The skin for the main portal page. </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Skinning_the_Portal-The_Default_Skin-components"> + <callout arearefs="area-Reference_Guide-Skinning_the_Portal-The_Default_Skin-components"> <para> Skins for various portal components. </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Skinning_the_Portal-The_Default_Skin-portletthemes"> + <callout arearefs="area-Reference_Guide-Skinning_the_Portal-The_Default_Skin-portletthemes"> <para> Window decoration skins. </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Skinning_the_Portal-The_Default_Skin-portlet"> + <callout arearefs="area-Reference_Guide-Skinning_the_Portal-The_Default_Skin-portlet"> <para> The portlet specification CSS classes. </para> @@ -305,14 +305,14 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Skinning_the_Portal-Creating_New_Skins"> + <section id="sect-Reference_Guide-Skinning_the_Portal-Creating_New_Skins"> <title>Creating New Skins</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Creating_New_Skins-Creating_a_New_Portal_Skin"> + <section id="sect-Reference_Guide-Creating_New_Skins-Creating_a_New_Portal_Skin"> <title>Creating a New Portal Skin</title> <para> New portal skins will need to be added to the portal through the skin service. Therefore, the web application which contains the skins will need to be properly configured for the skin service to discover them. This means properly configuring the <literal>ResourceRequestFilter</literal> and <filename>gatein-resources.xml</filename>. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Creating_a_New_Portal_Skin-Portal_Skin_Configuration"> + <section id="sect-Reference_Guide-Creating_a_New_Portal_Skin-Portal_Skin_Configuration"> <title>Portal Skin Configuration</title> <para> The <filename>gatein-resources.xml</filename> will need to specify the new portal skin. This will include the name of the new skin, where to locate its CSS stylesheet file and whether to overwrite an existing portal theme with the same name. @@ -332,7 +332,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Creating_a_New_Portal_Skin-Portal_Skin_Preview_Icon"> + <section id="sect-Reference_Guide-Creating_a_New_Portal_Skin-Portal_Skin_Preview_Icon"> <title>Portal Skin Preview Icon</title> <para> It is possible to see a preview of what the portal will look like when selecting a new skin. This functionality relies on the current skin being updated with skin icons for all other available skins. Otherwise it will not be able to show the previews. @@ -371,7 +371,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Creating_New_Skins-Creating_a_New_Window_Style"> + <section id="sect-Reference_Guide-Creating_New_Skins-Creating_a_New_Window_Style"> <title>Creating a New Window Style</title> <para> Window styles are the CSS applied to window decorations. An administrator can decide which style of decoration should go around the window when they add a new application or gadget to a page. @@ -385,7 +385,7 @@ </imageobject> </mediaobject> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Creating_a_New_Window_Style-Window_Style_Configuration"> + <section id="sect-Reference_Guide-Creating_a_New_Window_Style-Window_Style_Configuration"> <title>Window Style Configuration</title> <para> Window Styles are defined within a <filename>gatein-resources.xml</filename> file which is used by the skin service to deploy the window style into the portal. Window styles can belong in a window style category. This category and the window styles will need to be specified in resources file. @@ -411,7 +411,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Creating_a_New_Window_Style-Window_Style_CSS"> + <section id="sect-Reference_Guide-Creating_a_New_Window_Style-Window_Style_CSS"> <title>Window Style CSS</title> <para> In order for the skin service to display the window decorators, it must have CSS classes specifically named in relation to the window style name. The service will try and display CSS based on this naming convention. The CSS class must be included as part of the current portal skin for the window decorators to be displayed. @@ -430,7 +430,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Creating_a_New_Window_Style-How_to_Set_the_Default_Window_Style"> + <section id="sect-Reference_Guide-Creating_a_New_Window_Style-How_to_Set_the_Default_Window_Style"> <title>How to Set the Default Window Style</title> <para> To set the default window style to be used for a portal you will need to specify the CSS classes for a theme called <literal>DefaultTheme</literal>. @@ -448,7 +448,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Creating_New_Skins-How_to_Create_New_Portlet_Skins"> + <section id="sect-Reference_Guide-Creating_New_Skins-How_to_Create_New_Portlet_Skins"> <title>How to Create New Portlet Skins</title> <para> Portlets often require additional styles that may not be defined by the portal skin. JBoss Enterprise Portal Platform allows portlets to define additional stylesheets for each portlet and will append the corresponding <literal>link</literal> tags to the <literal>head</literal>. @@ -474,7 +474,7 @@ </para> </note> - <section id="sect-Reference_Guide_eXo_JCR_1.14-How_to_Create_New_Portlet_Skins-Change_Portlet_Icons"> + <section id="sect-Reference_Guide-How_to_Create_New_Portlet_Skins-Change_Portlet_Icons"> <title>Change Portlet Icons</title> <para> Each portlet can be registered by a unique icon in the portlet registry or page editor. This icon can be changed by adding an image to the directory of the portlet web application: @@ -516,7 +516,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Creating_New_Skins-Create_New_Portlet_Specification_CSS_Classes"> + <section id="sect-Reference_Guide-Creating_New_Skins-Create_New_Portlet_Specification_CSS_Classes"> <title>Create New Portlet Specification CSS Classes</title> <para> The portlet specification defines a set of default CSS classes that should be available for portlets. These classes are included as part of the portal skin. Please see the portlet specification for a list of the default classes that should be available. @@ -530,9 +530,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Skinning_the_Portal-Tips_and_Tricks"> + <section id="sect-Reference_Guide-Skinning_the_Portal-Tips_and_Tricks"> <title>Tips and Tricks</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Tips_and_Tricks-Easier_CSS_Debugging"> + <section id="sect-Reference_Guide-Tips_and_Tricks-Easier_CSS_Debugging"> <title>Easier CSS Debugging</title> <para> By default, CSS files are cached and their imports are merged into a single CSS file at the server side. This reduces the number of HTTP requests from the browser to the server. @@ -557,7 +557,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Tips_and_Tricks-Some_CSS_Techniques"> + <section id="sect-Reference_Guide-Tips_and_Tricks-Some_CSS_Techniques"> <title>Some CSS Techniques</title> <para> It is recommended that users have some experience with CSS before studying JBoss Enterprise Portal Platform CSS. @@ -565,7 +565,7 @@ <para> JBoss Enterprise Portal Platform relies heavily on CSS to create the layout and effects for the UI. Some common techniques for customizing JBoss Enterprise Portal Platform CSS are explained below. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Some_CSS_Techniques-Border_Pattern"> + <section id="sect-Reference_Guide-Some_CSS_Techniques-Border_Pattern"> <title>Border Pattern</title> <para> The decorator is a pattern to create a contour or a curve around an area. In order to achieve this effect you need to create nine cells. The <literal>BODY</literal> is the central area that you want to decorate. The other eight cells are distributed around the <literal>BODY</literal> cell. You can use the width, height and background image properties to achieve any decoration effect that you want. @@ -581,7 +581,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Some_CSS_Techniques-Left_Margin_Left_Pattern"> + <section id="sect-Reference_Guide-Some_CSS_Techniques-Left_Margin_Left_Pattern"> <title>Left Margin Left Pattern</title> <para> Left margin left pattern is a technique to create two blocks side by side. The left block will have a fixed size and the right block will take the rest of the available space. When the user resizes the browser the added or removed space will be taken from the right block. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/XMLResourceBundles.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/XMLResourceBundles.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment/XMLResourceBundles.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-XML_Resources_Bundles"> +<chapter id="chap-Reference_Guide-XML_Resources_Bundles"> <title>XML Resources Bundles</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-XML_Resources_Bundles-Overview"> + <section id="sect-Reference_Guide-XML_Resources_Bundles-Overview"> <title>Overview</title> <para> Resource bundles are usually stored in property files. However, as property files are plain files, issues with the encoding of the file may arise. The XML resource bundle format has been developed to provide an alternative to property files. @@ -34,7 +34,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-XML_Resources_Bundles-XML_format"> + <section id="sect-Reference_Guide-XML_Resources_Bundles-XML_format"> <title>XML format</title> <para> The XML format is very simple and has been developed based on the 'Don't Repeat Yourself' (DRY) principle. Usually resource bundle keys are hierarchically defined and we can leverage the hierarchic nature of the XML for that purpose. Here is an example of turning a property file into an XML resource bundle file: @@ -76,7 +76,7 @@ </bundle>]]></programlisting> --> </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-XML_Resources_Bundles-Portal_Support"> + <section id="sect-Reference_Guide-XML_Resources_Bundles-Portal_Support"> <title>Portal Support</title> <para> In order to be loaded by the portal at runtime (actually the resource bundle service), the name of the file must be the same as a property file and it must use the <emphasis role="bold">.xml</emphasis> suffix. 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-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortalDevelopment.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE part PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<part id="part-Reference_Guide_eXo_JCR_1.14-Portal_Development"> +<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" /> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortletDevelopment/Global_Portlet.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortletDevelopment/Global_Portlet.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortletDevelopment/Global_Portlet.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Shared_portlet.xml"> +<chapter id="chap-Reference_Guide-Shared_portlet.xml"> <title>Shared <filename>portlet.xml</filename></title> <para> The Java Portlet Specification introduces <literal>PortletFilter</literal> as a standard approach to extend the behaviors of portlet objects. For example, a filter can transform the content of portlet requests and portlet responses. @@ -51,7 +51,7 @@ <para> <emphasis role="bold">For JBoss</emphasis>: The file path is <filename><replaceable><JBOSS_HOME></replaceable>/server/default/conf/gatein/portlet.xml</filename>. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Shared_portlet.xml-Global_Metadata_Elements"> + <section id="sect-Reference_Guide-Shared_portlet.xml-Global_Metadata_Elements"> <title>Global Metadata Elements</title> <para> The global <filename>portlet.xml</filename> file conforms, with some restrictions, to the portlet deployment descriptor schema defined in the Portlet Specification. In this file, the following elements are supported: @@ -59,7 +59,7 @@ <orderedlist> <listitem> <para> - <xref linkend="form-Reference_Guide_eXo_JCR_1.14-Global_Metadata_Elements-Portlet_Filter" /> + <xref linkend="form-Reference_Guide-Global_Metadata_Elements-Portlet_Filter" /> </para> </listitem> @@ -77,7 +77,7 @@ </listitem> </orderedlist> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Global_Metadata_Elements-Portlet_Filter"> + <formalpara id="form-Reference_Guide-Global_Metadata_Elements-Portlet_Filter"> <title>Portlet Filter</title> <para> Portlet filter mappings declared in the global <filename>portlet.xml</filename> file are applied across portlet applications. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortletDevelopment/PortletBridge/configuration.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortletDevelopment/PortletBridge/configuration.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortletDevelopment/PortletBridge/configuration.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Bridge_Configuration"> +<section id="sect-Reference_Guide-Bridge_Configuration"> <title>Bridge Configuration</title> <para> The 329 specification is aimed at making the developer's life as easy as possible with JSF+Portlet development. You will see below that there are minimal settings to getting any JSF web application up and running in the Portal environment. @@ -11,9 +11,9 @@  <section id="sect-Reference_Guide_eXo_JCR_1.14-Bridge_Configuration-Core_Setup_and_Configuration"> + </para> --> <section id="sect-Reference_Guide-Bridge_Configuration-Core_Setup_and_Configuration"> <title>Core Setup and Configuration</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Core_Setup_and_Configuration-portlet.xml"> + <section id="sect-Reference_Guide-Core_Setup_and_Configuration-portlet.xml"> <title>portlet.xml</title> <para> The basic JSR-329 portlet configuration. @@ -31,7 +31,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Core_Setup_and_Configuration-faces_config.xml"> + <section id="sect-Reference_Guide-Core_Setup_and_Configuration-faces_config.xml"> <title>faces-config.xml</title> <para> The <parameter>PortletViewHandler</parameter> ensures that each JSF portlet instance is properly namespaced. @@ -41,18 +41,18 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Core_Setup_and_Configuration-Facelets_Configuration"> + <section id="sect-Reference_Guide-Core_Setup_and_Configuration-Facelets_Configuration"> <title>Facelets Configuration</title> <para> The following <filename>web.xml</filename> setting is only for <literal>Facelets</literal> based applications </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Facelets_Configuration-web.xml"> + <section id="sect-Reference_Guide-Facelets_Configuration-web.xml"> <title>web.xml</title> <programlisting language="XML" role="XML"><xi:include href="../../../extras/PortletBridge_Configuration/default200.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> <programlisting language="XML" role="XML"><xi:include href="../../../extras/PortletBridge_Configuration/default201.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-web.xml-RenderPolicy_Options"> + <variablelist id="vari-Reference_Guide-web.xml-RenderPolicy_Options"> <title>RenderPolicy Options</title> <varlistentry> <term>ALWAYS_DELEGATE</term> @@ -92,12 +92,12 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Core_Setup_and_Configuration-JSP_Only_Configuration"> + <section id="sect-Reference_Guide-Core_Setup_and_Configuration-JSP_Only_Configuration"> <title>JSP Only Configuration</title> <para> The following <filename>web.xml</filename> setting is only for JSP based applications. Download the demonstration application <ulink url="http://anonsvn.jboss.org/repos/portletbridge/trunk/examples/jsf-ri/1.2-ba...">here</ulink>. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JSP_Only_Configuration-web.xml"> + <section id="sect-Reference_Guide-JSP_Only_Configuration-web.xml"> <title>web.xml</title> <programlisting language="XML" role="XML"><xi:include href="../../../extras/PortletBridge_Configuration/default202.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> @@ -119,9 +119,9 @@ </section> --> </section> -  <section id="sect-Reference_Guide_eXo_JCR_1.14-Bridge_Configuration-RichFaces_Setup_and_Configuration_Options"> +  <section id="sect-Reference_Guide-Bridge_Configuration-RichFaces_Setup_and_Configuration_Options"> <title>RichFaces Setup and Configuration Options</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-RichFaces_Setup_and_Configuration_Options-web.xml"> + <section id="sect-Reference_Guide-RichFaces_Setup_and_Configuration_Options-web.xml"> <title>web.xml</title> <para> The following configuration is designated for portlets using the <application>RichFaces</application> library. These settings will vary based on your individual needs. @@ -153,7 +153,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-RichFaces_Setup_and_Configuration_Options-Configuration_needed_for_Richfaces_to_work_with_WSRP_and_PortletBridge"> + <section id="sect-Reference_Guide-RichFaces_Setup_and_Configuration_Options-Configuration_needed_for_Richfaces_to_work_with_WSRP_and_PortletBridge">  <title>Configuration needed for Richfaces to work with WSRP and PortletBridge</title> <para> Use the following settings in <filename>web.xml</filename> when running WSRP portlets: @@ -187,7 +187,7 @@ <para> The table below outlines the current status of RichFaces features when used in both local and remote portlets. </para> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Configuration_needed_for_Richfaces_to_work_with_WSRP_and_PortletBridge-RichFaces_Feature_Status"> + <table id="tabl-Reference_Guide-Configuration_needed_for_Richfaces_to_work_with_WSRP_and_PortletBridge-RichFaces_Feature_Status"> <title>RichFaces Feature Status</title> <tgroup cols="3"> <thead> @@ -893,9 +893,9 @@ </section> --> </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Bridge_Configuration-Seam_Setup_and_Configuration_Options"> + <section id="sect-Reference_Guide-Bridge_Configuration-Seam_Setup_and_Configuration_Options"> <title>Seam Setup and Configuration Options</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Seam_Setup_and_Configuration_Options-Configuration"> + <section id="sect-Reference_Guide-Seam_Setup_and_Configuration_Options-Configuration"> <title>Configuration</title> <para> The <literal>ExceptionHandler</literal> is used to clean <application>Seam</application> contexts and transactions after errors. @@ -913,7 +913,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Bridge_Configuration-Portlet_2.0_Coordination"> + <section id="sect-Reference_Guide-Bridge_Configuration-Portlet_2.0_Coordination"> <title>Portlet 2.0 Coordination</title> <note> <title>Schema and XSD Definitions</title> @@ -924,9 +924,9 @@ </note> <programlisting language="XML" role="XML"><xi:include href="../../../extras/PortletBridge_Configuration/default209.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Portlet_2.0_Coordination-Sending_and_Receiving_Events"> + <section id="sect-Reference_Guide-Portlet_2.0_Coordination-Sending_and_Receiving_Events"> <title>Sending and Receiving Events</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Sending_and_Receiving_Events-Configuration"> + <section id="sect-Reference_Guide-Sending_and_Receiving_Events-Configuration"> <title>Configuration</title> <para> Just like with any portlet 2.0 event consumer and receiver, you must define them in the <filename>portlet.xml</filename>. @@ -955,9 +955,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Portlet_2.0_Coordination-Public_Render_Parameters"> + <section id="sect-Reference_Guide-Portlet_2.0_Coordination-Public_Render_Parameters"> <title>Public Render Parameters</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Public_Render_Parameters-Configuration"> + <section id="sect-Reference_Guide-Public_Render_Parameters-Configuration"> <title>Configuration</title> <para> Public Render Parameters (or PRPs) are one of the most powerful and simple Portlet 2.0 features. Several portlets (JSF or otherwise) can share the same render parameters. This feature can be used to present a cohesive UI to the user across all portlets on the page. An example would be using an employee ID to display relative data. @@ -994,9 +994,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Portlet_2.0_Coordination-Serving_Your_JSF_Resources_in_a_Portlet"> + <section id="sect-Reference_Guide-Portlet_2.0_Coordination-Serving_Your_JSF_Resources_in_a_Portlet"> <title>Serving Your JSF Resources in a Portlet</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Serving_Your_JSF_Resources_in_a_Portlet-Configuration"> + <section id="sect-Reference_Guide-Serving_Your_JSF_Resources_in_a_Portlet-Configuration"> <title>Configuration</title> <para> We have setup a few examples to show you how to use <literal>EL</literal> and a simple bean that will allow you to use the portlet resource serving mechanism within a JSF portlet. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortletDevelopment/PortletBridge/gettingstarted.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortletDevelopment/PortletBridge/gettingstarted.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortletDevelopment/PortletBridge/gettingstarted.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,16 +1,16 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Getting_started_with_JBoss_Portlet_Bridge"> +<section id="sect-Reference_Guide-Getting_started_with_JBoss_Portlet_Bridge"> <title>Getting started with JBoss Portlet Bridge</title> <para> JBoss Portlet Bridge not only gives you the ability to run JSF web applications in a portlet, but also gives you the benefit of running supported JBoss frameworks like <application>Seam</application> and <application>RichFaces</application>. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Getting_started_with_JBoss_Portlet_Bridge-Whats_New_in_2.0"> + <section id="sect-Reference_Guide-Getting_started_with_JBoss_Portlet_Bridge-Whats_New_in_2.0"> <title>What's New in 2.0?</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Whats_New_in_2.0-Eventing"> + <section id="sect-Reference_Guide-Whats_New_in_2.0-Eventing"> <title>Eventing</title> <para> The bridge considers a portlet event a model event. The event is targeted to the applications data model, not its view. @@ -22,12 +22,12 @@ Since event payloads are arbitrarily complex, the manual processing of the data, though managed by the bridge, is left to the (portlet) application to support. </para> <para> - See <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Portlet_2.0_Coordination-Sending_and_Receiving_Events" /> for details and examples. + See <xref linkend="sect-Reference_Guide-Portlet_2.0_Coordination-Sending_and_Receiving_Events" /> for details and examples. </para> </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Whats_New_in_2.0-Portlet_Served_Resources"> + <section id="sect-Reference_Guide-Whats_New_in_2.0-Portlet_Served_Resources"> <title>Portlet Served Resources</title> <para> The bridge deals with portlet served resources in one of two ways: @@ -39,12 +39,12 @@ If the request is for a JSF resource, the bridge runs the full JSF life-cycle ensuring that data is processed and the resource (markup) is rendered. </para> <para> - See <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Portlet_2.0_Coordination-Serving_Your_JSF_Resources_in_a_Portlet" /> for details and examples. + See <xref linkend="sect-Reference_Guide-Portlet_2.0_Coordination-Serving_Your_JSF_Resources_in_a_Portlet" /> for details and examples. </para> </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Whats_New_in_2.0-Public_Render_Parameters"> + <section id="sect-Reference_Guide-Whats_New_in_2.0-Public_Render_Parameters"> <title>Public Render Parameters</title> <para> The bridge automates the processing of public render parameters. @@ -59,7 +59,7 @@ At the end of a request, if the current value of any mapped public render parameter doesn't match the current incoming value, the bridge sets the new value in an outgoing public render parameter (if feasible in the given phase). </para> <para> - See <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Portlet_2.0_Coordination-Public_Render_Parameters" /> for details and examples. + See <xref linkend="sect-Reference_Guide-Portlet_2.0_Coordination-Public_Render_Parameters" /> for details and examples. </para> </section> @@ -67,10 +67,10 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Getting_started_with_JBoss_Portlet_Bridge-Bridge_Frameworks_and_Extensions"> + <section id="sect-Reference_Guide-Getting_started_with_JBoss_Portlet_Bridge-Bridge_Frameworks_and_Extensions"> <title>Bridge Frameworks and Extensions</title> <para> - The JBoss Portlet Bridge currently supports JBoss Enterprise Portal Platform, <application>GateIn</application>, <application>JSF 1.2</application>, <application>JBoss Seam</application>, and <application>JBoss Richfaces</application>. There are configurations that apply to supporting each framework. See section <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Bridge_Configuration" /> for instructions. + The JBoss Portlet Bridge currently supports JBoss Enterprise Portal Platform, <application>GateIn</application>, <application>JSF 1.2</application>, <application>JBoss Seam</application>, and <application>JBoss Richfaces</application>. There are configurations that apply to supporting each framework. See section <xref linkend="sect-Reference_Guide-Bridge_Configuration" /> for instructions. </para> <para> The JBoss Portlet Bridge project is also actively developing extensions called "<emphasis role="bold">Bridgelets</emphasis>". @@ -78,7 +78,7 @@ <para> In this release it was decided to bring all available bridgelets into the impl code base since they are critical in most JSF portlet applications. A single line of configuration utilizes these features. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Bridge_Frameworks_and_Extensions-Seam_Bridgelets"> + <section id="sect-Reference_Guide-Bridge_Frameworks_and_Extensions-Seam_Bridgelets"> <title>Seam Bridgelets</title> <para> For example, the <literal>PortalIdentity</literal> <application>Seam</application> component allows you to instantly have Single Sign-On (SSO) between <application>Seam</application> and <application>GateIn</application> or <application>JBoss Enterprise Portal Platform</application>. @@ -91,7 +91,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Bridge_Frameworks_and_Extensions-RichFaces_Bridgelets"> + <section id="sect-Reference_Guide-Bridge_Frameworks_and_Extensions-RichFaces_Bridgelets"> <title>RichFaces Bridgelets</title> <para> <application>Richfaces</application> does not account for multiple components on the same portal page by default. This following <filename>web.xml</filename> renders all <application>RichFaces</application> component javascript portal-friendly. @@ -104,7 +104,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Getting_started_with_JBoss_Portlet_Bridge-Before_You_Start"> + <section id="sect-Reference_Guide-Getting_started_with_JBoss_Portlet_Bridge-Before_You_Start"> <title>Before You Start</title> <para> The embedded version in the JBoss Enterprise Portal Platform is made to be compatible with the JSF implementation, portal and application server that compose the product. You will find the binaries embedded in <filename>jboss-epp-<VERSION>/portletbridge</filename> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortletDevelopment/PortletBridge/overview.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortletDevelopment/PortletBridge/overview.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortletDevelopment/PortletBridge/overview.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-JBoss_Portlet_Bridge_Overview"> +<section id="sect-Reference_Guide-JBoss_Portlet_Bridge_Overview"> <title>JBoss Portlet Bridge Overview</title> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-JBoss_Portlet_Bridge_Overview-What_is_the_JBoss_Portlet_Bridge"> + <formalpara id="form-Reference_Guide-JBoss_Portlet_Bridge_Overview-What_is_the_JBoss_Portlet_Bridge"> <title>What is the JBoss Portlet Bridge?</title> <para> The JBoss Portlet Bridge (or <literal>JBPB</literal> for short) is a non-final implementation of the <ulink url="http://jcp.org/en/jsr/detail?id=329">JSR-329</ulink> specification. @@ -21,7 +21,7 @@ <para> Find more information about the JBoss Portlet Bridge, the developers, the community at <ulink url="http://www.jboss.org/portletbridge/">the project page</ulink>. </para> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-JBoss_Portlet_Bridge_Overview-Understanding_how_JSF_works_with_Portal"> + <formalpara id="form-Reference_Guide-JBoss_Portlet_Bridge_Overview-Understanding_how_JSF_works_with_Portal"> <title>Understanding how JSF works with Portal</title> <para> The portlet bridge is not a portlet. It is the mediator between the two environments and allows JSF and Portal to be completely unaware of each other. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortletDevelopment/PortletBridge/portlet_development.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortletDevelopment/PortletBridge/portlet_development.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortletDevelopment/PortletBridge/portlet_development.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,14 +1,14 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Developing_Portlets_with_the_Bridge"> +<section id="sect-Reference_Guide-Developing_Portlets_with_the_Bridge"> <title>Developing Portlets with the Bridge</title> <para> This chapter demonstrates common development tasks described by the 329 specification. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Developing_Portlets_with_the_Bridge-Excluding_Attributes_from_the_Bridge_Request_Scope"> + <section id="sect-Reference_Guide-Developing_Portlets_with_the_Bridge-Excluding_Attributes_from_the_Bridge_Request_Scope"> <title>Excluding Attributes from the Bridge Request Scope</title> <para> When your application uses request attributes on a per request basis and you do not want that particular attribute to be managed in the extended bridge request scope, you must use the following configuration in your <filename>faces-config.xml</filename>. @@ -21,7 +21,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Developing_Portlets_with_the_Bridge-Supporting_PortletMode_Changes"> + <section id="sect-Reference_Guide-Developing_Portlets_with_the_Bridge-Supporting_PortletMode_Changes"> <title>Supporting PortletMode Changes</title> <para> A <literal>PortletMode</literal> represents a distinct render path within an application. There are three standard modes: <emphasis>view</emphasis>, <emphasis>edit</emphasis>, and <emphasis>help</emphasis>. @@ -37,7 +37,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Developing_Portlets_with_the_Bridge-Navigating_to_a_modes_last_viewId"> + <section id="sect-Reference_Guide-Developing_Portlets_with_the_Bridge-Navigating_to_a_modes_last_viewId"> <title>Navigating to a mode's last viewId</title> <para> By default a mode change will start in the mode's default view without any (prior) existing state. One common portlet pattern when returning to a mode left after entering another mode (e.g.. view -> edit -> view) is to return to the last view (and state) of this origin mode. @@ -53,7 +53,7 @@ </para> <programlisting language="XML" role="XML"><xi:include href="../../../extras/PortletBridge_Portlet_Development/default225.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Navigating_to_a_modes_last_viewId-Note_to_Portlet_Developers"> + <section id="sect-Reference_Guide-Navigating_to_a_modes_last_viewId-Note_to_Portlet_Developers"> <title>Note to Portlet Developers</title> <para> Depending on the bridge implementation, when using values from these session scoped attributes or any viewIds which may contain query string parameters it may be necessary to use the wild-card syntax when identifying the rule target. In the above, for example, the @@ -89,7 +89,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Developing_Portlets_with_the_Bridge-Clearing_The_View_History_When_Changing_Portlet_Modes"> + <section id="sect-Reference_Guide-Developing_Portlets_with_the_Bridge-Clearing_The_View_History_When_Changing_Portlet_Modes"> <title>Clearing The View History When Changing Portlet Modes</title> <para> By default the bridge remembers the view history when you switch to a different portlet mode (like "Help" or "Edit"). You can use the following parameter in your <filename>portlet.xml</filename> to use the default viewId each time you switch modes. @@ -99,7 +99,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Developing_Portlets_with_the_Bridge-General_Error_Handling"> + <section id="sect-Reference_Guide-Developing_Portlets_with_the_Bridge-General_Error_Handling"> <title>General Error Handling</title> <note> <para> @@ -122,7 +122,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Developing_Portlets_with_the_Bridge-Custom_Ajax_Error_Handling"> + <section id="sect-Reference_Guide-Developing_Portlets_with_the_Bridge-Custom_Ajax_Error_Handling"> <title>Custom Ajax Error Handling</title> <para> By default, error handling is sent to a standard servlet page for Ajax requests. To handle the error inside the portlet, use the following javascript: @@ -140,7 +140,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Developing_Portlets_with_the_Bridge-Communication_Between_Your_Portlets"> + <section id="sect-Reference_Guide-Developing_Portlets_with_the_Bridge-Communication_Between_Your_Portlets"> <title>Communication Between Your Portlets</title> <para> There are four different ways to send messages, events, and parameters between portlets which are contained in different <literal>ears/wars</literal> or contained in the same <literal>war</literal>. @@ -149,7 +149,7 @@ Having two portlets in the same <literal>war</literal> or having them separated does not affect the Portlet Container because each portlet has a different <parameter>HttpSession</parameter>. </para> <para> - The recommended way to share a parameter or event payload between two or more portlets with the Portlet 2.0 specification are the <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Portlet_2.0_Coordination-Public_Render_Parameters" /> and <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Portlet_2.0_Coordination-Sending_and_Receiving_Events" /> mechanisms. + The recommended way to share a parameter or event payload between two or more portlets with the Portlet 2.0 specification are the <xref linkend="sect-Reference_Guide-Portlet_2.0_Coordination-Public_Render_Parameters" /> and <xref linkend="sect-Reference_Guide-Portlet_2.0_Coordination-Sending_and_Receiving_Events" /> mechanisms. </para> <para> This allows you to decouple your application from surgically managing objects in the <parameter>PortletSession.APPLICATION_SCOPE.</parameter> @@ -157,7 +157,7 @@ <para> However, if these do not meet your use case or you have a different strategy, you can use one of the following methods. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Communication_Between_Your_Portlets-Storing_Components_in_PortletSession.APPLICATION_SCOPE"> + <section id="sect-Reference_Guide-Communication_Between_Your_Portlets-Storing_Components_in_PortletSession.APPLICATION_SCOPE"> <title>Storing Components in <parameter>PortletSession.APPLICATION_SCOPE</parameter></title> <para> Sometimes it is beneficial to store your <application>Seam</application> components in the portlet <parameter>APPLICATION_SCOPE</parameter>. @@ -179,7 +179,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Communication_Between_Your_Portlets-Using_the_PortletSession"> + <section id="sect-Reference_Guide-Communication_Between_Your_Portlets-Using_the_PortletSession"> <title>Using the PortletSession</title> <para> If you need to access the <literal>PortletSession</literal> to simply share a parameter or value across multiple portlets, you can use the following: @@ -208,7 +208,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Developing_Portlets_with_the_Bridge-Linking_to_PortletJSF_Pages_Using_houtputlink"> + <section id="sect-Reference_Guide-Developing_Portlets_with_the_Bridge-Linking_to_PortletJSF_Pages_Using_houtputlink"> <title>Linking to Portlet/JSF Pages Using h:outputlink</title> <para> For linking to any JSF/Facelets page within your portlet web application, you can use the following. @@ -218,7 +218,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Developing_Portlets_with_the_Bridge-Redirecting_to_an_External_Page_or_Resource"> + <section id="sect-Reference_Guide-Developing_Portlets_with_the_Bridge-Redirecting_to_an_External_Page_or_Resource"> <title>Redirecting to an External Page or Resource</title> <para> To link to a non JSF view, <emphasis>jboss.org</emphasis> for example, you can use the following parameter. @@ -234,7 +234,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Developing_Portlets_with_the_Bridge-Using_Provided_EL_Variables"> + <section id="sect-Reference_Guide-Developing_Portlets_with_the_Bridge-Using_Provided_EL_Variables"> <title>Using Provided EL Variables</title> <para> All <literal>EL</literal> variables found in the JSR-329 (Portlet 2.0) specification are available in the JBoss Portlet Bridge. For example, you can use the following to edit the portlet preferences on the UI: Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortletDevelopment/PortletBridge.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortletDevelopment/PortletBridge.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortletDevelopment/PortletBridge.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Building_JSF_Portlets"> +<chapter id="chap-Reference_Guide-Building_JSF_Portlets"> <title>Building JSF Portlets</title> <xi:include href="PortletBridge/overview.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> <xi:include href="PortletBridge/gettingstarted.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortletDevelopment/Standard.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortletDevelopment/Standard.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortletDevelopment/Standard.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Portlet_Primer"> +<chapter id="chap-Reference_Guide-Portlet_Primer"> <title>Portlet Primer</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Portlet_Primer-JSR_168_and_JSR_286_overview"> + <section id="sect-Reference_Guide-Portlet_Primer-JSR_168_and_JSR_286_overview"> <title>JSR-168 and JSR-286 overview</title> <para> The Java Community Process (<literal>JCP</literal>) uses Java Specification Requests (<literal>JSR</literal>s) to define proposed specifications and technologies designed for the Java platform. @@ -22,7 +22,7 @@ <para> JBoss Enterprise Portal Platform is fully JSR-286 compliant. Any JSR-168 or JSR-286 portlet operates as it is mandated by the respective specifications inside the portal. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JSR_168_and_JSR_286_overview-Portal_Pages"> + <section id="sect-Reference_Guide-JSR_168_and_JSR_286_overview-Portal_Pages"> <title>Portal Pages</title> <para> A portal can be considered as a series of web pages with different <emphasis>areas</emphasis> within them. Those areas contain different <emphasis>windows</emphasis> and each <emphasis>window</emphasis> contains a <emphasis>portlet</emphasis>: @@ -42,7 +42,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JSR_168_and_JSR_286_overview-Rendering_Modes"> + <section id="sect-Reference_Guide-JSR_168_and_JSR_286_overview-Rendering_Modes"> <title>Rendering Modes</title> <para> A portlet can have different view modes. Three modes are defined by the JSR-286 specification: @@ -83,7 +83,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JSR_168_and_JSR_286_overview-Window_States"> + <section id="sect-Reference_Guide-JSR_168_and_JSR_286_overview-Window_States"> <title>Window States</title> <para> Window states are an indicator of how much page space a portlet consumes on any given page. The three states defined by the JSR-286 specification are: @@ -127,7 +127,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Portlet_Primer-Tutorials"> + <section id="sect-Reference_Guide-Portlet_Primer-Tutorials"> <title>Tutorials</title> <para> The tutorials contained in this chapter are targeted toward portlet developers. It is also recommend that developers read and understand the <ulink url="http://www.jcp.org/en/jsr/detail?id=286"> JSR-286 Portlet Specification </ulink> . @@ -139,7 +139,7 @@ </para> </note> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Tutorials-Deploying_your_first_Portlet"> + <section id="sect-Reference_Guide-Tutorials-Deploying_your_first_Portlet"> <title>Deploying your first Portlet</title> <para> This section describes how to deploy a portlet in JBoss Enterprise Portal Platform. @@ -147,7 +147,7 @@ <para> An example portlet called <filename>SimplestHelloWorld</filename> is available in the <filename>/jboss-epp-<VERSION>-src/portal/examples/portlets/</filename> directory of the JBoss Enterprise Portal Platform sources package or the <filename>jboss-epp-<VERSION>-docs/epp-doc/examples/portlets</filename> directory of the documentation package. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Deploying_your_first_Portlet-Compiling"> + <section id="sect-Reference_Guide-Deploying_your_first_Portlet-Compiling"> <title>Compiling</title> <para> To compile and package the application: @@ -206,7 +206,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Deploying_your_first_Portlet-Package_Structure"> + <section id="sect-Reference_Guide-Deploying_your_first_Portlet-Package_Structure"> <title>Package Structure</title> <para> Like other Java EE applications, JBoss Enterprise Portal Platform portlets are packaged in <literal>WAR</literal> files. A typical portlet <literal>WAR</literal> file can include servlets, resource bundles, images, HTML, JavaServer Pages (JSP), and other static or dynamic files. @@ -216,27 +216,27 @@ </para> <programlistingco> <areaspec> - <area coords="9" id="area-Reference_Guide_eXo_JCR_1.14-Deploying_your_first_Portlet-Package_Structure-javaclass" /> - <area coords="10" id="area-Reference_Guide_eXo_JCR_1.14-Deploying_your_first_Portlet-Package_Structure-portlet" /> - <area coords="11" id="area-Reference_Guide_eXo_JCR_1.14-Deploying_your_first_Portlet-Package_Structure-web" /> + <area coords="9" id="area-Reference_Guide-Deploying_your_first_Portlet-Package_Structure-javaclass" /> + <area coords="10" id="area-Reference_Guide-Deploying_your_first_Portlet-Package_Structure-portlet" /> + <area coords="11" id="area-Reference_Guide-Deploying_your_first_Portlet-Package_Structure-web" /> </areaspec> <programlisting language="Java" role="Java"><xi:include href="../../extras/PortletDevelopment_Standard/default244.java" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> <calloutlist> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Deploying_your_first_Portlet-Package_Structure-javaclass"> + <callout arearefs="area-Reference_Guide-Deploying_your_first_Portlet-Package_Structure-javaclass"> <para> The compiled Java class implementing <emphasis>javax.portlet.Portlet</emphasis> (through <emphasis>javax.portlet.GenericPortlet </emphasis> ) </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Deploying_your_first_Portlet-Package_Structure-portlet"> + <callout arearefs="area-Reference_Guide-Deploying_your_first_Portlet-Package_Structure-portlet"> <para> This is the mandatory descriptor file for portlets. It is used during deployment. </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Deploying_your_first_Portlet-Package_Structure-web"> + <callout arearefs="area-Reference_Guide-Deploying_your_first_Portlet-Package_Structure-web"> <para> This is the mandatory descriptor for web applications. </para> @@ -250,24 +250,24 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Deploying_your_first_Portlet-Portlet_Class"> + <section id="sect-Reference_Guide-Deploying_your_first_Portlet-Portlet_Class"> <title>Portlet Class</title> <para> Below is the Java source for an example portlet named <filename>simplesthelloworld/src/main/java/org/jboss/portal/portlet/samples</filename>: </para> <programlistingco> <areaspec> - <area coords="10" id="area-Reference_Guide_eXo_JCR_1.14-Deploying_your_first_Portlet-Portlet_Class-extends" /> - <area coords="13" id="area-Reference_Guide_eXo_JCR_1.14-Deploying_your_first_Portlet-Portlet_Class-doview" /> - <area coords="15" id="area-Reference_Guide_eXo_JCR_1.14-Deploying_your_first_Portlet-Portlet_Class-writer" /> - <area coords="16" id="area-Reference_Guide_eXo_JCR_1.14-Deploying_your_first_Portlet-Portlet_Class-write" /> - <area coords="17" id="area-Reference_Guide_eXo_JCR_1.14-Deploying_your_first_Portlet-Portlet_Class-close" /> + <area coords="10" id="area-Reference_Guide-Deploying_your_first_Portlet-Portlet_Class-extends" /> + <area coords="13" id="area-Reference_Guide-Deploying_your_first_Portlet-Portlet_Class-doview" /> + <area coords="15" id="area-Reference_Guide-Deploying_your_first_Portlet-Portlet_Class-writer" /> + <area coords="16" id="area-Reference_Guide-Deploying_your_first_Portlet-Portlet_Class-write" /> + <area coords="17" id="area-Reference_Guide-Deploying_your_first_Portlet-Portlet_Class-close" /> </areaspec> <programlisting language="Java" role="Java"><xi:include href="../../extras/PortletDevelopment_Standard/SimplestHelloWorldPortlet.java" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> <calloutlist> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Deploying_your_first_Portlet-Portlet_Class-extends"> + <callout arearefs="area-Reference_Guide-Deploying_your_first_Portlet-Portlet_Class-extends"> <para> All portlets must implement the <literal>javax.portlet.Portlet</literal> interface. The portlet API provides a convenient implementation of this interface. </para> @@ -279,25 +279,25 @@ </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Deploying_your_first_Portlet-Portlet_Class-doview"> + <callout arearefs="area-Reference_Guide-Deploying_your_first_Portlet-Portlet_Class-doview"> <para> If only the <literal>view</literal> mode is required, then only the <literal>doView</literal> method needs to be implemented. The <literal>GenericPortlet</literal> render implementation calls our implementation when the <literal>view</literal> mode is requested. </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Deploying_your_first_Portlet-Portlet_Class-writer"> + <callout arearefs="area-Reference_Guide-Deploying_your_first_Portlet-Portlet_Class-writer"> <para> Use the <emphasis>RenderResponse</emphasis> to obtain a writer to be used to produce content. </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Deploying_your_first_Portlet-Portlet_Class-write"> + <callout arearefs="area-Reference_Guide-Deploying_your_first_Portlet-Portlet_Class-write"> <para> Write the markup to display. </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Deploying_your_first_Portlet-Portlet_Class-close"> + <callout arearefs="area-Reference_Guide-Deploying_your_first_Portlet-Portlet_Class-close"> <para> Closing the writer. </para> @@ -321,7 +321,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Deploying_your_first_Portlet-Application_Descriptors"> + <section id="sect-Reference_Guide-Deploying_your_first_Portlet-Application_Descriptors"> <title>Application Descriptors</title> <para> JBoss Enterprise Portal Platform requires certain descriptors to be included in a portlet <literal>WAR</literal> file. These descriptors are defined by the Java EE (<filename>web.xml</filename>) and Portlet Specification (<filename>portlet.xml</filename>). @@ -331,28 +331,28 @@ </para> <programlistingco> <areaspec> - <area coords="8 70" id="area-Reference_Guide_eXo_JCR_1.14-Deploying_your_first_Portlet-Application_Descriptors-portletname" /> - <area coords="9 70" id="area-Reference_Guide_eXo_JCR_1.14-Deploying_your_first_Portlet-Application_Descriptors-portletclass" /> - <area coords="12 70" id="area-Reference_Guide_eXo_JCR_1.14-Deploying_your_first_Portlet-Application_Descriptors-supports" /> - <area coords="15 70" id="area-Reference_Guide_eXo_JCR_1.14-Deploying_your_first_Portlet-Application_Descriptors-portletinfo" /> + <area coords="8 70" id="area-Reference_Guide-Deploying_your_first_Portlet-Application_Descriptors-portletname" /> + <area coords="9 70" id="area-Reference_Guide-Deploying_your_first_Portlet-Application_Descriptors-portletclass" /> + <area coords="12 70" id="area-Reference_Guide-Deploying_your_first_Portlet-Application_Descriptors-supports" /> + <area coords="15 70" id="area-Reference_Guide-Deploying_your_first_Portlet-Application_Descriptors-portletinfo" /> </areaspec> <programlisting language="XML" role="XML"><xi:include href="../../extras/PortletDevelopment_Standard/default245.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> <calloutlist> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Deploying_your_first_Portlet-Application_Descriptors-portletname"> + <callout arearefs="area-Reference_Guide-Deploying_your_first_Portlet-Application_Descriptors-portletname"> <para> Define the portlet name. It does not have to be the class name. </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Deploying_your_first_Portlet-Application_Descriptors-portletclass"> + <callout arearefs="area-Reference_Guide-Deploying_your_first_Portlet-Application_Descriptors-portletclass"> <para> The Fully Qualified Name (<literal>FQN</literal>) of your portlet class must be declared here. </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Deploying_your_first_Portlet-Application_Descriptors-supports"> + <callout arearefs="area-Reference_Guide-Deploying_your_first_Portlet-Application_Descriptors-supports"> <para> The <literal><supports></literal> element declares all of the markup types that a portlet supports in the <literal>render</literal> method. This is accomplished via the <literal><mime-type></literal> element, which is required for every portlet. </para> @@ -367,7 +367,7 @@ </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Deploying_your_first_Portlet-Application_Descriptors-portletinfo"> + <callout arearefs="area-Reference_Guide-Deploying_your_first_Portlet-Application_Descriptors-portletinfo"> <para> When rendered, the portlet's title is displayed as the header in the portlet window, unless it is overridden programmatically. In the example above the title would be <literal>Simplest Hello World Portlet</literal> . </para> @@ -384,7 +384,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Tutorials-JavaServer_Pages_Portlet_Example"> + <section id="sect-Reference_Guide-Tutorials-JavaServer_Pages_Portlet_Example"> <title>JavaServer Pages Portlet Example</title> <para> This section discusses: @@ -416,7 +416,7 @@ </listitem> </orderedlist> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-JavaServer_Pages_Portlet_Example-Compiling_the_example"> + <formalpara id="form-Reference_Guide-JavaServer_Pages_Portlet_Example-Compiling_the_example"> <title>Compiling the example</title> <para> The example used in this section is available in the <filename>/jboss-epp-<VERSION>-src/portal/examples/portlets/</filename> directory of the JBoss Enterprise Portal Platform sources package or the <filename>/jboss-epp-<VERSION>-docs/epp-doc/examples/portlets</filename> directory of the documentation package. @@ -473,7 +473,7 @@ <para> The <literal>EDIT</literal> button only appears for logged-in users. </para> -</note> --> <section id="sect-Reference_Guide_eXo_JCR_1.14-JavaServer_Pages_Portlet_Example-Package_Structure"> +</note> --> <section id="sect-Reference_Guide-JavaServer_Pages_Portlet_Example-Package_Structure"> <title>Package Structure</title> <para> The package structure in this tutorial does not differ greatly from the previous example, with the exception of adding some JSP files which are detailed later. @@ -486,41 +486,41 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JavaServer_Pages_Portlet_Example-Portlet_Class"> + <section id="sect-Reference_Guide-JavaServer_Pages_Portlet_Example-Portlet_Class"> <title>Portlet Class</title> <para> The code below is from the <filename> jsphellouser/src/main/java/org/jboss/portal/portlet/samples/JSPHelloUserPortlet.java</filename> Java source. It is split in different pieces. </para> <programlistingco> <areaspec> - <area coords="18 80" id="area-Reference_Guide_eXo_JCR_1.14-JavaServer_Pages_Portlet_Example-Portlet_Class-doView" /> - <area coords="21 80" id="area-Reference_Guide_eXo_JCR_1.14-JavaServer_Pages_Portlet_Example-Portlet_Class-renderParameter" /> - <area coords="25 80" id="area-Reference_Guide_eXo_JCR_1.14-JavaServer_Pages_Portlet_Example-Portlet_Class-requestDispatcher" /> - <area coords="26 80" id="area-Reference_Guide_eXo_JCR_1.14-JavaServer_Pages_Portlet_Example-Portlet_Class-include" /> + <area coords="18 80" id="area-Reference_Guide-JavaServer_Pages_Portlet_Example-Portlet_Class-doView" /> + <area coords="21 80" id="area-Reference_Guide-JavaServer_Pages_Portlet_Example-Portlet_Class-renderParameter" /> + <area coords="25 80" id="area-Reference_Guide-JavaServer_Pages_Portlet_Example-Portlet_Class-requestDispatcher" /> + <area coords="26 80" id="area-Reference_Guide-JavaServer_Pages_Portlet_Example-Portlet_Class-include" /> </areaspec> <programlisting language="Java" role="Java"><xi:include href="../../extras/PortletDevelopment_Standard/JSPHelloUserPortlet.java" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> <calloutlist> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-JavaServer_Pages_Portlet_Example-Portlet_Class-doView"> + <callout arearefs="area-Reference_Guide-JavaServer_Pages_Portlet_Example-Portlet_Class-doView"> <para> Override the <emphasis>doView</emphasis> method (as in the first tutorial). </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-JavaServer_Pages_Portlet_Example-Portlet_Class-renderParameter"> + <callout arearefs="area-Reference_Guide-JavaServer_Pages_Portlet_Example-Portlet_Class-renderParameter"> <para> This entry attempts to obtain the value of the render parameter named <literal>yourname</literal>. If defined it should redirect to the <filename>hello.jsp</filename> JSP page, otherwise to the <filename>welcome.jsp</filename> JSP page. </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-JavaServer_Pages_Portlet_Example-Portlet_Class-requestDispatcher"> + <callout arearefs="area-Reference_Guide-JavaServer_Pages_Portlet_Example-Portlet_Class-requestDispatcher"> <para> Get a request dispatcher on a file located within the web archive. </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-JavaServer_Pages_Portlet_Example-Portlet_Class-include"> + <callout arearefs="area-Reference_Guide-JavaServer_Pages_Portlet_Example-Portlet_Class-include"> <para> Perform the inclusion of the markup obtained from the JSP. </para> @@ -553,27 +553,27 @@ </para> <programlistingco> <areaspec> - <area coords="2 100" id="area-Reference_Guide_eXo_JCR_1.14-JavaServer_Pages_Portlet_Example-Portlet_Class-processAction" /> - <area coords="5 80" id="area-Reference_Guide_eXo_JCR_1.14-JavaServer_Pages_Portlet_Example-Portlet_Class-getActionParameter" /> - <area coords="6 80" id="area-Reference_Guide_eXo_JCR_1.14-JavaServer_Pages_Portlet_Example-Portlet_Class-setRenderParameter" /> + <area coords="2 100" id="area-Reference_Guide-JavaServer_Pages_Portlet_Example-Portlet_Class-processAction" /> + <area coords="5 80" id="area-Reference_Guide-JavaServer_Pages_Portlet_Example-Portlet_Class-getActionParameter" /> + <area coords="6 80" id="area-Reference_Guide-JavaServer_Pages_Portlet_Example-Portlet_Class-setRenderParameter" /> </areaspec> <programlisting language="Java" role="Java"><xi:include href="../../extras/PortletDevelopment_Standard/default249.java" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> <calloutlist> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-JavaServer_Pages_Portlet_Example-Portlet_Class-processAction"> + <callout arearefs="area-Reference_Guide-JavaServer_Pages_Portlet_Example-Portlet_Class-processAction"> <para> <literal>processAction</literal> is the method from <literal>GenericPortlet</literal> to override for the <emphasis>action</emphasis> phase. </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-JavaServer_Pages_Portlet_Example-Portlet_Class-getActionParameter"> + <callout arearefs="area-Reference_Guide-JavaServer_Pages_Portlet_Example-Portlet_Class-getActionParameter"> <para> Here the parameter is retrieved through an <emphasis>action URL</emphasis>. </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-JavaServer_Pages_Portlet_Example-Portlet_Class-setRenderParameter"> + <callout arearefs="area-Reference_Guide-JavaServer_Pages_Portlet_Example-Portlet_Class-setRenderParameter"> <para> The value of <literal>yourname</literal> is kept to make it available in the rendering phase. The previous line simply copies an action parameter to a render parameter for this example. </para> @@ -587,7 +587,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JavaServer_Pages_Portlet_Example-JSP_files_and_the_Portlet_Tag_Library"> + <section id="sect-Reference_Guide-JavaServer_Pages_Portlet_Example-JSP_files_and_the_Portlet_Tag_Library"> <title>JSP files and the Portlet Tag Library</title> <para> The <filename>help.jsp</filename> and <filename>edit.jsp</filename> files are very simple. Note that CSS styles are used as defined in the portlet specification. This ensures that the portlet will render well within the theme and across portal vendors. @@ -601,48 +601,48 @@ </para> <programlistingco> <areaspec> - <area coords="1" id="area-Reference_Guide_eXo_JCR_1.14-JavaServer_Pages_Portlet_Example-JSP_files_and_the_Portlet_Tag_Library-taglib" /> - <area coords="13" id="area-Reference_Guide_eXo_JCR_1.14-JavaServer_Pages_Portlet_Example-JSP_files_and_the_Portlet_Tag_Library-method1" /> - <area coords="20" id="area-Reference_Guide_eXo_JCR_1.14-JavaServer_Pages_Portlet_Example-JSP_files_and_the_Portlet_Tag_Library-method2.1" /> - <area coords="24" id="area-Reference_Guide_eXo_JCR_1.14-JavaServer_Pages_Portlet_Example-JSP_files_and_the_Portlet_Tag_Library-method2.2" /> - <area coords="30" id="area-Reference_Guide_eXo_JCR_1.14-JavaServer_Pages_Portlet_Example-JSP_files_and_the_Portlet_Tag_Library-method3.1" /> - <area coords="31" id="area-Reference_Guide_eXo_JCR_1.14-JavaServer_Pages_Portlet_Example-JSP_files_and_the_Portlet_Tag_Library-method3.2" /> + <area coords="1" id="area-Reference_Guide-JavaServer_Pages_Portlet_Example-JSP_files_and_the_Portlet_Tag_Library-taglib" /> + <area coords="13" id="area-Reference_Guide-JavaServer_Pages_Portlet_Example-JSP_files_and_the_Portlet_Tag_Library-method1" /> + <area coords="20" id="area-Reference_Guide-JavaServer_Pages_Portlet_Example-JSP_files_and_the_Portlet_Tag_Library-method2.1" /> + <area coords="24" id="area-Reference_Guide-JavaServer_Pages_Portlet_Example-JSP_files_and_the_Portlet_Tag_Library-method2.2" /> + <area coords="30" id="area-Reference_Guide-JavaServer_Pages_Portlet_Example-JSP_files_and_the_Portlet_Tag_Library-method3.1" /> + <area coords="31" id="area-Reference_Guide-JavaServer_Pages_Portlet_Example-JSP_files_and_the_Portlet_Tag_Library-method3.2" /> </areaspec> <programlisting language="XML" role="XML"><xi:include href="../../extras/PortletDevelopment_Standard/default252.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> <calloutlist> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-JavaServer_Pages_Portlet_Example-JSP_files_and_the_Portlet_Tag_Library-taglib"> + <callout arearefs="area-Reference_Guide-JavaServer_Pages_Portlet_Example-JSP_files_and_the_Portlet_Tag_Library-taglib"> <para> The portlet taglib. This needs to be declared. </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-JavaServer_Pages_Portlet_Example-JSP_files_and_the_Portlet_Tag_Library-method1"> + <callout arearefs="area-Reference_Guide-JavaServer_Pages_Portlet_Example-JSP_files_and_the_Portlet_Tag_Library-method1"> <para> The first method showed here is the simplest one. <literal>portlet:renderURL</literal> will create a URL that calls the render phase of the current portlet and append the result at the place of the markup (within a tag). A parameter is also added directly to the URL. </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-JavaServer_Pages_Portlet_Example-JSP_files_and_the_Portlet_Tag_Library-method2.1"> + <callout arearefs="area-Reference_Guide-JavaServer_Pages_Portlet_Example-JSP_files_and_the_Portlet_Tag_Library-method2.1"> <para> In this method the <literal>var</literal> attribute is used. This avoids having one XML tag within another. Instead of printing the url the <literal>portlet:renderURL</literal> tag will store the result in the referenced variable ( <literal>myRenderURL</literal>). </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-JavaServer_Pages_Portlet_Example-JSP_files_and_the_Portlet_Tag_Library-method2.2"> + <callout arearefs="area-Reference_Guide-JavaServer_Pages_Portlet_Example-JSP_files_and_the_Portlet_Tag_Library-method2.2"> <para> The variable <literal>myRenderURL</literal> is used like any other JSP variable. </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-JavaServer_Pages_Portlet_Example-JSP_files_and_the_Portlet_Tag_Library-method3.1"> + <callout arearefs="area-Reference_Guide-JavaServer_Pages_Portlet_Example-JSP_files_and_the_Portlet_Tag_Library-method3.1"> <para> The third method mixes form submission and action request. Again, a temporary variable is used to put the created URL into. </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-JavaServer_Pages_Portlet_Example-JSP_files_and_the_Portlet_Tag_Library-method3.2"> + <callout arearefs="area-Reference_Guide-JavaServer_Pages_Portlet_Example-JSP_files_and_the_Portlet_Tag_Library-method3.2"> <para> The action URL is used in HTML form. </para> @@ -668,7 +668,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JavaServer_Pages_Portlet_Example-JSF_example_using_the_JBoss_Portlet_Bridge"> + <section id="sect-Reference_Guide-JavaServer_Pages_Portlet_Example-JSF_example_using_the_JBoss_Portlet_Bridge"> <title>JSF example using the JBoss Portlet Bridge</title> <para> In order to write a portlet using JSF a 'bridge' is needed. This software allows developers to write a portlet application as if it was a JSF application. The bridge then negotiates the interactions between the two layers. @@ -689,34 +689,34 @@ </para> <programlistingco> <areaspec> - <area coords="9 80" id="area-Reference_Guide_eXo_JCR_1.14-JavaServer_Pages_Portlet_Example-JSF_example_using_the_JBoss_Portlet_Bridge-portlet" /> - <area coords="21 80" id="area-Reference_Guide_eXo_JCR_1.14-JavaServer_Pages_Portlet_Example-JSF_example_using_the_JBoss_Portlet_Bridge-view" /> - <area coords="26 80" id="area-Reference_Guide_eXo_JCR_1.14-JavaServer_Pages_Portlet_Example-JSF_example_using_the_JBoss_Portlet_Bridge-edit" /> - <area coords="31 80" id="area-Reference_Guide_eXo_JCR_1.14-JavaServer_Pages_Portlet_Example-JSF_example_using_the_JBoss_Portlet_Bridge-help" /> + <area coords="9 80" id="area-Reference_Guide-JavaServer_Pages_Portlet_Example-JSF_example_using_the_JBoss_Portlet_Bridge-portlet" /> + <area coords="21 80" id="area-Reference_Guide-JavaServer_Pages_Portlet_Example-JSF_example_using_the_JBoss_Portlet_Bridge-view" /> + <area coords="26 80" id="area-Reference_Guide-JavaServer_Pages_Portlet_Example-JSF_example_using_the_JBoss_Portlet_Bridge-edit" /> + <area coords="31 80" id="area-Reference_Guide-JavaServer_Pages_Portlet_Example-JSF_example_using_the_JBoss_Portlet_Bridge-help" /> </areaspec> <programlisting language="XML" role="XML"><xi:include href="../../extras/PortletDevelopment_Standard/default254.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> <calloutlist> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-JavaServer_Pages_Portlet_Example-JSF_example_using_the_JBoss_Portlet_Bridge-portlet"> + <callout arearefs="area-Reference_Guide-JavaServer_Pages_Portlet_Example-JSF_example_using_the_JBoss_Portlet_Bridge-portlet"> <para> All JSF portlets define <literal>javax.portlet.faces.GenericFacesPortlet </literal> as portlet class. This class is part of the JBoss Portlet Bridge </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-JavaServer_Pages_Portlet_Example-JSF_example_using_the_JBoss_Portlet_Bridge-view"> + <callout arearefs="area-Reference_Guide-JavaServer_Pages_Portlet_Example-JSF_example_using_the_JBoss_Portlet_Bridge-view"> <para> This is a mandatory parameter to define what's the default page to display. </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-JavaServer_Pages_Portlet_Example-JSF_example_using_the_JBoss_Portlet_Bridge-edit"> + <callout arearefs="area-Reference_Guide-JavaServer_Pages_Portlet_Example-JSF_example_using_the_JBoss_Portlet_Bridge-edit"> <para> This parameter defines which page to display on the 'edit' mode. </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-JavaServer_Pages_Portlet_Example-JSF_example_using_the_JBoss_Portlet_Bridge-help"> + <callout arearefs="area-Reference_Guide-JavaServer_Pages_Portlet_Example-JSF_example_using_the_JBoss_Portlet_Bridge-help"> <para> This parameter defines which page to display on the 'help' mode. </para> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortletDevelopment.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortletDevelopment.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/PortletDevelopment.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE part PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<part id="part-Reference_Guide_eXo_JCR_1.14-Portlet_development"> +<part id="part-Reference_Guide-Portlet_development"> <title>Portlet development</title> <xi:include href="PortletDevelopment/Standard.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> <xi:include href="PortletDevelopment/Global_Portlet.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/RH-WSRP.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/RH-WSRP.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/RH-WSRP.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP"> +<chapter id="chap-Reference_Guide-Web_Services_for_Remote_Portlets_WSRP"> <title><remark>Web Services for Remote Portlets (WSRP)</remark></title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Introduction"> + <section id="sect-Reference_Guide-Web_Services_for_Remote_Portlets_WSRP-Introduction"> <title>Introduction</title> <para> The Web Services for Remote Portlets (WSRP) specification defines a web service interface for accessing and interacting with interactive presentation-oriented web services. @@ -37,7 +37,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Level_of_Support"> + <section id="sect-Reference_Guide-Web_Services_for_Remote_Portlets_WSRP-Level_of_Support"> <title>Level of Support</title> <para> The WSRP Technical Committee defined <ulink url="http://www.oasis-open.org/committees/download.php/3073">WSRP Use Profiles</ulink> to help with WSRP interoperability. Terms defined in that document will be used in this section. @@ -69,14 +69,14 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Deploying_WSRP"> + <section id="sect-Reference_Guide-Web_Services_for_Remote_Portlets_WSRP-Deploying_WSRP"> <title>Deploying WSRP</title> <note> <title>Notational Devices</title> <para> The following list of support files uses the following notational devices: </para> - <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Deploying_WSRP-Notations"> + <variablelist id="vari-Reference_Guide-Deploying_WSRP-Notations"> <title>Notations:</title> <varlistentry> <term><replaceable>JBOSS_HOME</replaceable></term> @@ -131,7 +131,7 @@ <para> The extension itself is composed of the following components: </para> - <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Deploying_WSRP-WSRP_support_files"> + <variablelist id="vari-Reference_Guide-Deploying_WSRP-WSRP_support_files"> <title>WSRP support files</title> <varlistentry> <term><filename>META-INF/</filename></term> @@ -140,7 +140,7 @@ This directory contains files necessary for EAR packaging. The only file that is of interest from a user perspective is <filename>gatein-wsse-consumer.xml</filename> which allows you to configure WS-Security support for the consumer. </para> <para> - Refer to <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-WSRP_and_WS_Security-WS_Security_Configuration" /> section for more details. + Refer to <xref linkend="sect-Reference_Guide-WSRP_and_WS_Security-WS_Security_Configuration" /> section for more details. </para> </listitem> @@ -203,7 +203,7 @@ This file contains the producer-side support for WS-Security. The only file of interest from a user perspective is <filename>gatein-wsse-producer.xml</filename> which allows you to configure WS-Security support for the producer. </para> <para> - Refer to <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-WSRP_and_WS_Security-WS_Security_Configuration" /> for more details. + Refer to <xref linkend="sect-Reference_Guide-WSRP_and_WS_Security-WS_Security_Configuration" /> for more details. </para> </listitem> @@ -211,18 +211,18 @@ </varlistentry> </variablelist> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Deploying_WSRP-Non_default_Ports_or_Hostnames"> + <section id="sect-Reference_Guide-Deploying_WSRP-Non_default_Ports_or_Hostnames"> <title>Non-default Ports or Hostnames</title> <para> JBoss WS (the web service stack that JBoss Enterprise Portal Platform uses) should update the port and host name used in WSDL. Refer to the JBoss WS <ulink url="http://community.jboss.org/wiki/JBossWS-UserGuide#Configuration">user guide</ulink> for more information. </para> <para> - If the host name and port on which the server runs have been modified, the configuration for the Consumer used to consume JBoss Enterprise Portal Platform's "self" Producer will need to be updated. Refer to <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Consuming_Remote_WSRP_Portlets" /> for directions on how to do this. + If the host name and port on which the server runs have been modified, the configuration for the Consumer used to consume JBoss Enterprise Portal Platform's "self" Producer will need to be updated. Refer to <xref linkend="sect-Reference_Guide-Web_Services_for_Remote_Portlets_WSRP-Consuming_Remote_WSRP_Portlets" /> for directions on how to do this. </para> </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Deploying_WSRP-Using_WSRP_with_SSL"> + <section id="sect-Reference_Guide-Deploying_WSRP-Using_WSRP_with_SSL"> <title>Using WSRP with SSL</title> <para> It is possible to use WSRP over SSL for secure exchange of data. Refer to these <ulink url="http://community.jboss.org/wiki/ConfiguringWSRPforuseoverSSL">instructions</ulink> for how to do this. @@ -233,7 +233,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-WSRP_and_WS_Security"> + <section id="sect-Reference_Guide-Web_Services_for_Remote_Portlets_WSRP-WSRP_and_WS_Security"> <title>WSRP and WS-Security</title> <para> Portlets may present different data or options depending on the currently authenticated user. For remote portlets, this means having to propagate the user credentials from the consumer back to the producer in a safe and secure manner. @@ -280,7 +280,7 @@ <para> This community Wiki <ulink url="http://community.jboss.org/wiki/GateInWSRPAndWebServiceSecurity">article</ulink>, also provides a step-by-step example on how to configure WSRP with WS-Security. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-WSRP_and_WS_Security-WS_Security_Configuration"> + <section id="sect-Reference_Guide-WSRP_and_WS_Security-WS_Security_Configuration"> <title>WS-Security Configuration</title> <para> JBoss Enterprise Portal Platform uses <application>JBossWS Native</application> to handle ws-security. @@ -321,7 +321,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-WSRP_and_WS_Security-WS_Security_Producer_Configuration"> + <section id="sect-Reference_Guide-WSRP_and_WS_Security-WS_Security_Producer_Configuration"> <title>WS-Security Producer Configuration</title> <para> Other than the JBossWS configuration file mention above, no other configuration changes should be necessary for the producer. @@ -329,7 +329,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-WSRP_and_WS_Security-WS_Security_Consumer_Configuration"> + <section id="sect-Reference_Guide-WSRP_and_WS_Security-WS_Security_Consumer_Configuration"> <title>WS-Security Consumer Configuration</title> <para> The consumer requires some changes before it will function properly with WS-Security. @@ -337,7 +337,7 @@ <para> The consumer needs access to the current servlet request since this is used to retrieve the currently authenticated user. In order to access this information, the consumer needs a special servlet-filter added to the portal. </para> - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-WS_Security_Consumer_Configuration-Add_the_servlet_filter"> + <procedure id="proc-Reference_Guide-WS_Security_Consumer_Configuration-Add_the_servlet_filter"> <title>Add the servlet-filter</title> <step> <para> @@ -406,7 +406,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Making_a_Portlet_Remotable"> + <section id="sect-Reference_Guide-Web_Services_for_Remote_Portlets_WSRP-Making_a_Portlet_Remotable"> <title>Making a Portlet Remotable</title> <note> <para> @@ -464,13 +464,13 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Consuming_WSRP_portlets_from_a_remote_Consumer"> + <section id="sect-Reference_Guide-Web_Services_for_Remote_Portlets_WSRP-Consuming_WSRP_portlets_from_a_remote_Consumer"> <title>Consuming WSRP portlets from a remote Consumer</title> <para> Configuration is extremely variable between different WSRP Consumers. Most, however, require a specification of the URL for the Producer's WSDL definition. If the JBoss Enterprise Portal Platform Consumer is not being used, refer to the documentation for the Consumer that is in use for specific instructions. </para> <para> - For instructions on how to specify this URL in JBoss Enterprise Portal Platform, refer to <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Consuming_Remote_WSRP_Portlets" />. + For instructions on how to specify this URL in JBoss Enterprise Portal Platform, refer to <xref linkend="sect-Reference_Guide-Web_Services_for_Remote_Portlets_WSRP-Consuming_Remote_WSRP_Portlets" />. </para> <para> JBoss Enterprise Portal Platform's Producer is automatically set up when a portal instance is deployed with the WSRP service. @@ -478,7 +478,7 @@ <para> The WSDL file can be accessed at: </para> - <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Consuming_WSRP_portlets_from_a_remote_Consumer-File_paths"> + <variablelist id="vari-Reference_Guide-Consuming_WSRP_portlets_from_a_remote_Consumer-File_paths"> <title>File paths:</title> <varlistentry> <term>WSRP 1.0:</term> @@ -508,9 +508,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Consuming_Remote_WSRP_Portlets"> + <section id="sect-Reference_Guide-Web_Services_for_Remote_Portlets_WSRP-Consuming_Remote_WSRP_Portlets"> <title>Consuming Remote WSRP Portlets</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Consuming_Remote_WSRP_Portlets-Overview"> + <section id="sect-Reference_Guide-Consuming_Remote_WSRP_Portlets-Overview"> <title>Overview</title> <para> To be able to consume WSRP portlets exposed by a remote producer, JBoss Enterprise Portal Platform's WSRP consumer must be configured to access that remote producer. @@ -528,7 +528,7 @@ --> </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Consuming_Remote_WSRP_Portlets-Configuring_a_Remote_Producer"> + <section id="sect-Reference_Guide-Consuming_Remote_WSRP_Portlets-Configuring_a_Remote_Producer"> <title>Configuring a Remote Producer</title> <para> Access to a remote producer needs to be defined so that portlets can be consumed within JBoss Enterprise Portal Platform. This section will show how to configure access to <emphasis role="bold">NetUnity</emphasis>'s public WSRP producer. @@ -555,7 +555,7 @@ </para> </important> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuring_a_Remote_Producer-The_Configuration_Portlet"> + <section id="sect-Reference_Guide-Configuring_a_Remote_Producer-The_Configuration_Portlet"> <title>The Configuration Portlet</title> <para> JBoss Enterprise Portal Platform provides a graphical portlet to assist with configuring access to, and other facets of, remote WSRP Producers. @@ -569,7 +569,7 @@ <para> Although the Configuration Portlet is installed by default in JBoss Enterprise Portal Platform &VY;., installation instructions are included below should the portlet ever need to be re-installed: </para> - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-The_Configuration_Portlet-Installing_the_configuration_portlet"> + <procedure id="proc-Reference_Guide-The_Configuration_Portlet-Installing_the_configuration_portlet"> <title><emphasis role="bold">Installing the configuration portlet:</emphasis></title> <step> <para> @@ -592,7 +592,7 @@ </procedure> - <section id="sect-Reference_Guide_eXo_JCR_1.14-The_Configuration_Portlet-Using_the_Configuration_portlet"> + <section id="sect-Reference_Guide-The_Configuration_Portlet-Using_the_Configuration_portlet"> <title><emphasis role="bold">Using the Configuration portlet</emphasis></title> <mediaobject> <imageobject role="html"> @@ -618,7 +618,7 @@ <para> To create a new Consumer: </para> - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Using_the_Configuration_portlet-Creating_a_Consumer"> + <procedure id="proc-Reference_Guide-Using_the_Configuration_portlet-Creating_a_Consumer"> <title><emphasis role="bold">Creating a Consumer</emphasis></title> <step> <para> @@ -735,7 +735,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuring_a_Remote_Producer-Using_XML"> + <section id="sect-Reference_Guide-Configuring_a_Remote_Producer-Using_XML"> <title>Using XML</title> <para> Although using the WSRP Configuration portlet to configure Consumers is recommended, the WSRP component provides an alternative way to configure consumers. @@ -756,12 +756,12 @@ </note>  <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Using_XML-The_Consumer_Configuration_file"> + </para> --> <formalpara id="form-Reference_Guide-Using_XML-The_Consumer_Configuration_file"> <title>The Consumer Configuration file</title> <para> It is important to understand how the XML Consumers configuration file is processed. It is read the first time the WSRP service starts and the associated information is then put under control of the JCR (Java Content Repository). @@ -775,12 +775,12 @@ The information defined at the XML level is only processed for producer definition for which no information is already present in the JCR. </para> <para> - Therefore, to delete a Producer configuration, the associated information in the database must be deleted (this can be accomplished using the configuration portlet as shown in <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Configuring_a_Remote_Producer-The_Configuration_Portlet" /> ). + Therefore, to delete a Producer configuration, the associated information in the database must be deleted (this can be accomplished using the configuration portlet as shown in <xref linkend="sect-Reference_Guide-Configuring_a_Remote_Producer-The_Configuration_Portlet" /> ). </para> <para> The associated information in <filename>wsrp-consumers-config.xml</filename> (if such information exists) must also be removed, otherwise the producer will be re-created the next time the WSRP is launched. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Using_XML-Required_Configuration_Information"> + <section id="sect-Reference_Guide-Using_XML-Required_Configuration_Information"> <title>Required Configuration Information</title> <para> The following information needs to be provided to configure access to a remote Producer: @@ -806,12 +806,12 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Using_XML-Optional_Configuration"> + <section id="sect-Reference_Guide-Using_XML-Optional_Configuration"> <title>Optional Configuration</title> <para> It is also possible to provide additional configuration, which, in some cases, might be important to establish a proper connection to the remote producer. </para> - <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Optional_Configuration-Optional_Configurations"> + <variablelist id="vari-Reference_Guide-Optional_Configuration-Optional_Configurations"> <title>Optional Configurations</title> <varlistentry> <term>Caching</term> @@ -881,14 +881,14 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuring_a_Remote_Producer-Examples"> + <section id="sect-Reference_Guide-Configuring_a_Remote_Producer-Examples"> <title>Examples</title> <para> This is the configuration of the <literal>selfv1</literal> and <literal>selfv2</literal> consumers as found in <filename>default-wsrp.xml</filename> with a cache expiring every 500 seconds and with a 50 second timeout for web service operations: </para> <note> <para> - This file contains the default configuration and should not need to be edited. If modifications are required, the recommended practice is to follow the procedure detailed in <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-The_Configuration_Portlet-Using_the_Configuration_portlet" />. + This file contains the default configuration and should not need to be edited. If modifications are required, the recommended practice is to follow the procedure detailed in <xref linkend="sect-Reference_Guide-The_Configuration_Portlet-Using_the_Configuration_portlet" />. </para> </note> @@ -905,7 +905,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Consuming_Remote_WSRP_Portlets-Adding_remote_portlets_to_categories"> + <section id="sect-Reference_Guide-Consuming_Remote_WSRP_Portlets-Adding_remote_portlets_to_categories"> <title>Adding remote portlets to categories</title> <para> Clicking on the Portlet link in the Application Registry will now show the remote portlets in the <emphasis role="bold">REMOTE</emphasis> tab in the left column: @@ -937,11 +937,11 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Consumers_Maintenance"> + <section id="sect-Reference_Guide-Web_Services_for_Remote_Portlets_WSRP-Consumers_Maintenance"> <title>Consumers Maintenance</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Consumers_Maintenance-Modifying_a_Currently_Held_Registration"> + <section id="sect-Reference_Guide-Consumers_Maintenance-Modifying_a_Currently_Held_Registration"> <title>Modifying a Currently Held Registration</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Modifying_a_Currently_Held_Registration-Registration_Modification_for_Service_Upgrade"> + <section id="sect-Reference_Guide-Modifying_a_Currently_Held_Registration-Registration_Modification_for_Service_Upgrade"> <title>Registration Modification for Service Upgrade</title> <para> Producers often offer several levels of service depending on consumers' subscription levels (for example). This is implemented at the WSRP level with the registration concept: producers can assert which level of service to provide to consumers based on the values of given registration properties. @@ -953,7 +953,7 @@ Therefore at times it may be necessary to modify the registration that sets the service agreement between a consumer and a producer. </para> <para> - For example; the producer requiring an email that was configured in <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Configuring_a_Remote_Producer-The_Configuration_Portlet" /> . In that case the producer was requiring registration and required a value to be provided for the <literal>email</literal> property. + For example; the producer requiring an email that was configured in <xref linkend="sect-Reference_Guide-Configuring_a_Remote_Producer-The_Configuration_Portlet" /> . In that case the producer was requiring registration and required a value to be provided for the <literal>email</literal> property. </para> <para> To update the email address that was provided, the remote producer must be informed that some registration data has been modified. @@ -1013,7 +1013,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Modifying_a_Currently_Held_Registration-Registration_Modification_on_Producer_Error"> + <section id="sect-Reference_Guide-Modifying_a_Currently_Held_Registration-Registration_Modification_on_Producer_Error"> <title>Registration Modification on Producer Error</title> <para> If a Producer administrator changes the requirements for registered consumers, invoking operations on the producer may fail with an <exceptionname>OperationFailedFault</exceptionname>. JBoss Enterprise Portal Platform will attempt to assist in these cases. @@ -1085,7 +1085,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Consumers_Maintenance-Consumer_Operations"> + <section id="sect-Reference_Guide-Consumers_Maintenance-Consumer_Operations"> <title>Consumer Operations</title> <para> Several operations are available from the consumer list view of the WSRP configuration portlet: @@ -1155,14 +1155,14 @@ </varlistentry> </variablelist> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Consumer_Operations-Additional_Functionalities_in_WSRP_2.0"> + <formalpara id="form-Reference_Guide-Consumer_Operations-Additional_Functionalities_in_WSRP_2.0"> <title><emphasis role="bold">Additional Functionalities in WSRP 2.0</emphasis></title> <para> In addition to those listed above, the WSRP 2.0 implementation in JBoss Enterprise Portal Platform &VY; also includes the following functions: </para> </formalpara> - <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Consumer_Operations-Additional_Functions"> + <variablelist id="vari-Reference_Guide-Consumer_Operations-Additional_Functions"> <title>Additional Functions:</title> <varlistentry> <term>Export</term> @@ -1186,7 +1186,7 @@ </varlistentry> </variablelist> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Consumer_Operations-Importing_and_Exporting_Portlets"> + <section id="sect-Reference_Guide-Consumer_Operations-Importing_and_Exporting_Portlets"> <title><emphasis role="bold">Importing and Exporting Portlets</emphasis></title> <para> Import and export are new functionalities added in WSRP 2. @@ -1251,7 +1251,7 @@ <para> This screen presents the list of available exports with available operations for each. </para> - <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Importing_and_Exporting_Portlets-Operations"> + <variablelist id="vari-Reference_Guide-Importing_and_Exporting_Portlets-Operations"> <title>Operations:</title> <varlistentry> <term>View</term> @@ -1404,7 +1404,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Consumers_Maintenance-Erasing_Local_Registration_Data"> + <section id="sect-Reference_Guide-Consumers_Maintenance-Erasing_Local_Registration_Data"> <title>Erasing Local Registration Data</title> <para> In rare cases, it may be necessary to erase the local data without being able to de-register first. @@ -1448,9 +1448,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Configuring_the_WSRP_Producer"> + <section id="sect-Reference_Guide-Web_Services_for_Remote_Portlets_WSRP-Configuring_the_WSRP_Producer"> <title>Configuring the WSRP Producer</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuring_the_WSRP_Producer-Overview"> + <section id="sect-Reference_Guide-Configuring_the_WSRP_Producer-Overview"> <title>Overview</title> <para> The behavior of the Portal's WSRP Producer can be configured using the WSRP administration interface, (this is the recommended method), or by editing the <filename><replaceable>WSRP_PATH</replaceable>/lib/gatein.portal.component.wsrp-<replaceable><VERSION></replaceable>-epp-GA.jar/conf/wsrp-producer-config.xml</filename> file. @@ -1467,7 +1467,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuring_the_WSRP_Producer-Default_Configuration"> + <section id="sect-Reference_Guide-Configuring_the_WSRP_Producer-Default_Configuration"> <title>Default Configuration</title> <para> The default producer configuration requires that consumers register with it before providing access to its services. However it does not require any specific registration properties (excepting those mandated by the WSRP standard). @@ -1479,7 +1479,7 @@ The producer also uses the default <classname>RegistrationPolicy</classname> paired with the default <classname>RegistrationPropertyValidator</classname>. </para> <para> - This allows users to customize how Portal's WSRP Producer decides whether a given registration property is valid or not (however property validators are discussed in greater detail in <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Configuring_the_WSRP_Producer-Registration_Configuration" /> ). + This allows users to customize how Portal's WSRP Producer decides whether a given registration property is valid or not (however property validators are discussed in greater detail in <xref linkend="sect-Reference_Guide-Configuring_the_WSRP_Producer-Registration_Configuration" /> ). </para> <para> JBoss Enterprise Portal Platform provides a web interface to configure the producer's behavior. It can be accessed by clicking on the "<emphasis role="bold">Producer Configuration</emphasis>" tab of the "<emphasis role="bold">WSRP</emphasis>" page of the "<emphasis role="bold">admin</emphasis>" portal. @@ -1505,7 +1505,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuring_the_WSRP_Producer-Registration_Configuration"> + <section id="sect-Reference_Guide-Configuring_the_WSRP_Producer-Registration_Configuration"> <title>Registration Configuration</title> <para> In order to have consumers register with Portal's producer the Portal's behavior with respect to registration must be configured. @@ -1552,7 +1552,7 @@ </step> <step> <para> - The fully-qualified name for the <classname>RegistrationPolicy</classname> and <classname>RegistrationPropertyValidator</classname> can be specified here. The default values are acceptable. Refer to <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Registration_Configuration-Customization_of_Registration_Handling_Behavior" /> for more information. + The fully-qualified name for the <classname>RegistrationPolicy</classname> and <classname>RegistrationPropertyValidator</classname> can be specified here. The default values are acceptable. Refer to <xref linkend="sect-Reference_Guide-Registration_Configuration-Customization_of_Registration_Handling_Behavior" /> for more information. </para> </step> @@ -1588,11 +1588,11 @@ </note> <note> <para> - If consumers are already registered with the producer, modifying the configuration of required registration information will trigger the invalidation of held registrations, requiring consumers to modify their registration before being able to access the producer again. The consumer side of that process is documented in <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Modifying_a_Currently_Held_Registration-Registration_Modification_on_Producer_Error" />. + If consumers are already registered with the producer, modifying the configuration of required registration information will trigger the invalidation of held registrations, requiring consumers to modify their registration before being able to access the producer again. The consumer side of that process is documented in <xref linkend="sect-Reference_Guide-Modifying_a_Currently_Held_Registration-Registration_Modification_on_Producer_Error" />. </para> </note> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Registration_Configuration-Customization_of_Registration_Handling_Behavior"> + <section id="sect-Reference_Guide-Registration_Configuration-Customization_of_Registration_Handling_Behavior"> <title>Customization of Registration Handling Behavior</title> <para> Registration handling behavior can be customized by users to suit their Producer needs. This is done with an implementation of the <classname>RegistrationPolicy</classname> interface. @@ -1633,7 +1633,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuring_the_WSRP_Producer-WSRP_Validation_Mode"> + <section id="sect-Reference_Guide-Configuring_the_WSRP_Producer-WSRP_Validation_Mode"> <title>WSRP Validation Mode</title> <para> The lack of conformance kit and the wording of the WSRP specification leaves room for differing interpretations, resulting in interoperability issues. It is therefore possible to encounter issues when using consumers from different vendors. @@ -1653,7 +1653,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Removing_WSRP"> + <section id="sect-Reference_Guide-Web_Services_for_Remote_Portlets_WSRP-Removing_WSRP"> <title>Removing WSRP</title> <para> If you are not going to use WSRP in your JBoss Enterprise Portal Platform instance, the WSRP configuration files may be left in place. They will not adversely affect your installation. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/conversationstate-when-membership-changed.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/conversationstate-when-membership-changed.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/conversationstate-when-membership-changed.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Update_ConversationState_when_users_Membership_changed"> +<section id="sect-Reference_Guide-Update_ConversationState_when_users_Membership_changed"> <title>Update ConversationState when user's Membership changed</title> <para> When a user logged in portal in ConversationRegistry added ConversationSate for this user. ConversationState keeps user's Identity that is actual for logged in time. In this case even user's Membership updated in OrganizationService ConversationState still keeps old (not actual Identity). User must logged out and login in again to update Identity. To fix this issue, need add special listener in configuration of OrganizationServicer. This listener is extended MembershipEventListener. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/core.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/core.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/core.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-eXo_Core"> +<section id="sect-Reference_Guide-eXo_Core"> <title>eXo Core</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-eXo_Core-eXo_Core_introduction"> + <section id="sect-Reference_Guide-eXo_Core-eXo_Core_introduction"> <title>eXo Core introduction</title> <para> The eXo Core is a set of common services that are used by eXo products and modules, it also can be used in the business logic. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/db-configuration-hibernate.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/db-configuration-hibernate.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/db-configuration-hibernate.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,14 +1,14 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Database_Configuration_for_Hibernate"> +<section id="sect-Reference_Guide-Database_Configuration_for_Hibernate"> <title>Database Configuration for Hibernate</title> <para> As usual, it is quite simple to use our configuration XML syntax to configure and parametrize different Databases for eXo tables but also for your own use. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Database_Configuration_for_Hibernate-Generic_configuration"> + <section id="sect-Reference_Guide-Database_Configuration_for_Hibernate-Generic_configuration"> <title>Generic configuration</title> <para> The default DB configuration uses HSQLDB, a Java Database quite useful for demonstrations. @@ -49,7 +49,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Database_Configuration_for_Hibernate-Example_DB_configuration"> + <section id="sect-Reference_Guide-Database_Configuration_for_Hibernate-Example_DB_configuration"> <title>Example DB configuration</title> <para> For MySQL @@ -81,7 +81,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Database_Configuration_for_Hibernate-Registering_custom_Hibernate_XML_files_into_the_service"> + <section id="sect-Reference_Guide-Database_Configuration_for_Hibernate-Registering_custom_Hibernate_XML_files_into_the_service"> <title>Registering custom Hibernate XML files into the service</title> <para> It is possible to use the eXo hibernate service and register your hibernate hbm.xml files to leverage some add-on features of the service such as the table automatic creation as well as the cache of the hibernate session in a ThreadLocal object during all the request lifecycle. To do so, you just have to add a plugin and indicate the location of your files. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/db-creator-service.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/db-creator-service.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/db-creator-service.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Database_Creator"> +<section id="sect-Reference_Guide-Database_Creator"> <title>Database Creator</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Database_Creator-About"> + <section id="sect-Reference_Guide-Database_Creator-About"> <title>About</title> <para> Database creator<envar> DBCreator</envar> is responsible for execution DDL script in runtime. A DDL script may contain templates for database name, user name and password which will be replaced by real values at execution time. @@ -37,7 +37,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Database_Creator-API"> + <section id="sect-Reference_Guide-Database_Creator-API"> <title>API</title> <para> Service provide method for execute script for new database creation. Database name which are passed as parameter will be substituted in DDL script instead of <envar>${database}</envar> template. Returns <envar>DBConnectionInfo</envar> object (with all necessary information of new database's connection) or throws <envar>DBCreatorException</envar> exception if any errors occurs in other case. @@ -57,7 +57,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Database_Creator-A_configuration_examples"> + <section id="sect-Reference_Guide-Database_Creator-A_configuration_examples"> <title>A configuration examples</title> <para> Service's configuration. @@ -174,7 +174,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Database_Creator-An_examples_of_a_DDL_script"> + <section id="sect-Reference_Guide-Database_Creator-An_examples_of_a_DDL_script"> <title>An examples of a DDL script</title> <para> MySQL: Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/db-schema-creator-service.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/db-schema-creator-service.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/db-schema-creator-service.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-DB_Schema_creator_service_JDBC_implementation"> +<section id="sect-Reference_Guide-DB_Schema_creator_service_JDBC_implementation"> <title>DB Schema creator service (JDBC implementation)</title> <para> DB Schema Creator is responsible for creating database schema, using a DDL script inside service configuration or in an external file, calling: Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/digest-auth.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/digest-auth.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/digest-auth.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Digest_Authentication"> +<section id="sect-Reference_Guide-Digest_Authentication"> <title>Digest Authentication</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Digest_Authentication-Overview"> + <section id="sect-Reference_Guide-Digest_Authentication-Overview"> <title>Overview</title> <para> Digest access authentication is one of the agreed methods a web server can use to negotiate credentials with a web user's browser. It uses encryption to send the password over the network which is safer than the Basic access authentication that sends plaintext. @@ -16,12 +16,12 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Digest_Authentication-Server_configuration"> + <section id="sect-Reference_Guide-Digest_Authentication-Server_configuration"> <title>Server configuration</title> <para> To configure you server to use DIGEST authentication we need to edit serverside JAAS module implementation configuration file. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Server_configuration-Tomcat_Server_configuration"> + <section id="sect-Reference_Guide-Server_configuration-Tomcat_Server_configuration"> <title>Tomcat Server configuration</title> <para> You need to fulfill a couple of steps. Firstly change login configuration: @@ -74,7 +74,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Server_configuration-Jetty_server_configuration"> + <section id="sect-Reference_Guide-Server_configuration-Jetty_server_configuration"> <title>Jetty server configuration</title> <para> You need to fulfill a couple of steps. Firstly change login configuration: @@ -124,7 +124,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Server_configuration-JBoss_server_configuration"> + <section id="sect-Reference_Guide-Server_configuration-JBoss_server_configuration"> <title>JBoss server configuration</title> <para> Edit config file located here: exo-jboss/server/default/deploy/exo.jcr.ear.ear/rest.war/WEB-INF/web.xml @@ -181,7 +181,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Digest_Authentication-OrganizationService_implementation_requirements"> + <section id="sect-Reference_Guide-Digest_Authentication-OrganizationService_implementation_requirements"> <title>OrganizationService implementation requirements</title> <para> To make your own <literal>org.exoplatform.services.organization.OrganizationService</literal> implementation able to use DIGEST authentication you need to make your UserHandler implementation also implement <literal>org.exoplatform.services.organization.DigestAuthenticator</literal> interface which provide more flexible authenticate method. As it is called from <literal>org.exoplatform.services.organization.auth.OrganizationAuthenticatorImpl</literal> it receive a <literal>org.exoplatform.services.security.Credential</literal> instances, you can get more information from <literal>org.exoplatform.services.security.PasswordCredential.getPasswordContext()</literal>. It can be used to calculate md5 digest of original password to compare it with received from clientside. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/ldap-configuration.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/ldap-configuration.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/ldap-configuration.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-LDAP_Configuration"> +<section id="sect-Reference_Guide-LDAP_Configuration"> <title>LDAP Configuration</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-LDAP_Configuration-Overview"> + <section id="sect-Reference_Guide-LDAP_Configuration-Overview"> <title>Overview</title> <para> You may decide that you want eXo users to be mapped to an existing directory. eXo provides a flexible implementation of its OrganizationService on top of LDAP. It can be used on any LDAP compliant directory and even Active Directory. This page will guide you how to configure eXo Platform to work with your directory. @@ -13,7 +13,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-LDAP_Configuration-Quickstart"> + <section id="sect-Reference_Guide-LDAP_Configuration-Quickstart"> <title>Quickstart</title> <para> If you just want to have a look at how eXo works with ldap. eXo comes with a predefined ldap configuration. You just need to activate it and eXo will create all it needs to work at startup. @@ -74,7 +74,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-LDAP_Configuration-Configuration"> + <section id="sect-Reference_Guide-LDAP_Configuration-Configuration"> <title>Configuration</title> <para> If you have an existing LDAP server, the eXo predefined settings will likely not match your directory structure. eXo LDAP organization service implementation was written with flexibility in mind and can certainly be configured to meet your requirements. @@ -82,7 +82,7 @@ <para> The configuration is done in <emphasis role="bold">ldap-configuration.xml</emphasis> file, and this chapter will explain the numerous parameters it contains. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuration-Connection_Settings"> + <section id="sect-Reference_Guide-Configuration-Connection_Settings"> <title>Connection Settings</title> <para> Firstly, start by connection settings which will tell eXo how to connect to your directory server. These settings are very close to <ulink url="http://java.sun.com/products/jndi">JNDI API</ulink> context parameters. This configuration is activated by the init-param ldap.config of service LDAPServiceImpl. @@ -176,7 +176,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuration-Organization_Service_Configuration"> + <section id="sect-Reference_Guide-Configuration-Organization_Service_Configuration"> <title>Organization Service Configuration</title> <para> Next, you need to configure the eXo <emphasis role="bold">OrganizationService</emphasis> to tell him how the directory is structured and how to interact with it. This is managed by a couple of init-params : <emphasis role="bold">ldap.userDN.key</emphasis> and <emphasis role="bold">ldap.attribute.mapping</emphasis> in file <emphasis role="bold">ldap-configuration.xml</emphasis> (by default located at portal.war/WEB-INF/conf/organization) @@ -231,9 +231,9 @@ <para> Other parameters are discussed in the following sections. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Organization_Service_Configuration-Users"> + <section id="sect-Reference_Guide-Organization_Service_Configuration-Users"> <title>Users</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Users-Main_parameters"> + <section id="sect-Reference_Guide-Users-Main_parameters"> <title>Main parameters</title> <para> Here are the main parameters to map eXo users to your directory : @@ -314,7 +314,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Users-User_mapping"> + <section id="sect-Reference_Guide-Users-User_mapping"> <title>User mapping</title> <para> The following parameters maps ldap attributes to eXo User java objects attributes. @@ -381,7 +381,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Organization_Service_Configuration-Groups"> + <section id="sect-Reference_Guide-Organization_Service_Configuration-Groups"> <title>Groups</title> <para> eXo groups can be mapped to organizational or applicative groups defined in your directory. @@ -467,7 +467,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Organization_Service_Configuration-Membership_Types"> + <section id="sect-Reference_Guide-Organization_Service_Configuration-Membership_Types"> <title>Membership Types</title> <para> Membership types are the possible roles that can be assigned to users in groups. @@ -542,7 +542,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Organization_Service_Configuration-Memberships"> + <section id="sect-Reference_Guide-Organization_Service_Configuration-Memberships"> <title>Memberships</title> <para> Memberships are used to assign a role within a group. They are entries that are placed under the group entry of their scope group. Users in this role are defined as attributes of the membership entry. @@ -649,7 +649,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Organization_Service_Configuration-User_Profiles"> + <section id="sect-Reference_Guide-Organization_Service_Configuration-User_Profiles"> <title>User Profiles</title> <para> eXo User profiles also have entries in the ldap but the actual storage is still done with the hibernate service. You will need the following parameters: @@ -681,9 +681,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-LDAP_Configuration-Advanced_topics"> + <section id="sect-Reference_Guide-LDAP_Configuration-Advanced_topics"> <title>Advanced topics</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Advanced_topics-Automatic_directory_population"> + <section id="sect-Reference_Guide-Advanced_topics-Automatic_directory_population"> <title>Automatic directory population</title> <para> At startup, eXo can populate the organization model based on @@ -751,7 +751,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Advanced_topics-Active_Directory_sample_configuration"> + <section id="sect-Reference_Guide-Advanced_topics-Active_Directory_sample_configuration"> <title>Active Directory sample configuration</title> <para> Here is an alternative configuration for active directory that you can find in <emphasis role="bold">activedirectory-configuration.xml</emphasis> @@ -822,7 +822,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Advanced_topics-OpenLDAP_dynlist_overlays"> + <section id="sect-Reference_Guide-Advanced_topics-OpenLDAP_dynlist_overlays"> <title>OpenLDAP dynlist overlays</title> <para> If you use OpenLDAP, you may want to use the <ulink url="http://www.openldap.org/faq/data/cache/1169.html">overlays</ulink>. Here is how you can use the <ulink url="http://www.openldap.org/faq/data/cache/1209.html">dynlist overlay</ulink> to have memberships dynamically populated. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/organization-service-initalizer.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/organization-service-initalizer.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/organization-service-initalizer.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Organization_Service_Initializer"> +<section id="sect-Reference_Guide-Organization_Service_Initializer"> <title>Organization Service Initializer</title> <para> Use the Organization Service Initializer to create users, groups and membership types by default. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/organization-service-listener.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/organization-service-listener.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/organization-service-listener.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Organization_Listener"> +<section id="sect-Reference_Guide-Organization_Listener"> <title>Organization Listener</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Organization_Listener-Overview"> + <section id="sect-Reference_Guide-Organization_Listener-Overview"> <title>Overview</title> <para> The Organization Service provides a mechanism to receive notifications when : @@ -58,12 +58,12 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Organization_Listener-Writing_your_own_listeners"> + <section id="sect-Reference_Guide-Organization_Listener-Writing_your_own_listeners"> <title>Writing your own listeners</title> <para> To implement your own listener, you just need to write extend some existing listener classes. These classes define hooks that are invoked before or after operations are performed on organization model. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Writing_your_own_listeners-UserEventListener"> + <section id="sect-Reference_Guide-Writing_your_own_listeners-UserEventListener"> <title>UserEventListener</title> <para> To listen to user changes, you need to extend <>org.exoplatform.services.organization.UserEventListener</> : @@ -91,7 +91,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Writing_your_own_listeners-GroupEventListener"> + <section id="sect-Reference_Guide-Writing_your_own_listeners-GroupEventListener"> <title>GroupEventListener</title> <para> To listen to group changes, you need to extend <>org.exoplatform.services.organization.GroupEventListener</> : @@ -118,7 +118,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Writing_your_own_listeners-MembershipEventListener"> + <section id="sect-Reference_Guide-Writing_your_own_listeners-MembershipEventListener"> <title>MembershipEventListener</title> <para> To listen to membership changes, you need to extend <>org.exoplatform.services.organization.MembershipEventListener</> : @@ -148,10 +148,10 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Organization_Listener-Registering_your_listeners"> + <section id="sect-Reference_Guide-Organization_Listener-Registering_your_listeners"> <title>Registering your listeners</title> <para> - Registering the listeners is then achieved by using the ExoContainer plugin mechanism. Learn more about it on the <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Configuring_Services" />. + Registering the listeners is then achieved by using the ExoContainer plugin mechanism. Learn more about it on the <xref linkend="sect-Reference_Guide-Configuring_Services" />. </para> <para> To effectively register organization service's listeners you simply need to use the <>addListenerPlugin</> seer injector. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/organization-service.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/organization-service.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/organization-service.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Organization_Service"> +<section id="sect-Reference_Guide-Organization_Service"> <title>Organization Service</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Organization_Service-Overview"> + <section id="sect-Reference_Guide-Organization_Service-Overview"> <title>Overview</title> <para> OrganizationService is the service that allows to access the Organization model. This model is composed of : @@ -58,9 +58,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Organization_Service-Organizational_Model"> + <section id="sect-Reference_Guide-Organization_Service-Organizational_Model"> <title>Organizational Model</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Organizational_Model-User"> + <section id="sect-Reference_Guide-Organizational_Model-User"> <title>User</title> <itemizedlist> <listitem> @@ -80,7 +80,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Organizational_Model-Group"> + <section id="sect-Reference_Guide-Organizational_Model-Group"> <title>Group</title> <para> Gather a set of users @@ -115,7 +115,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Organizational_Model-Membership"> + <section id="sect-Reference_Guide-Organizational_Model-Membership"> <title>Membership</title> <itemizedlist> <listitem> @@ -144,7 +144,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Organization_Service-Related_articles_and_how_tos"> + <section id="sect-Reference_Guide-Organization_Service-Related_articles_and_how_tos"> <title>Related articles and how-tos</title> <itemizedlist> <listitem> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/security-service.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/security-service.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/security-service.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Security_Service"> +<section id="sect-Reference_Guide-Security_Service"> <title>Security Service</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Security_Service-a1_Overview"> + <section id="sect-Reference_Guide-Security_Service-a1_Overview"> <title>1 Overview</title> <para> The purpose is to make a simple, unified way for the authentication and the storing/propagation of user sessions through all the eXo components and J2EE containers. JAAS is supposed to be the primary login mechanism but the Security Service framework should not prevent other (custom or standard) mechanisms from being used. You can learn more about JAAS in the <ulink url="http://java.sun.com/j2se/1.5.0/docs/guide/security/jaas/tutorials/General...">Java Tutorial</ulink> @@ -13,7 +13,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Security_Service-a1_Framework"> + <section id="sect-Reference_Guide-Security_Service-a1_Framework"> <title>1 Framework</title> <para> The central point of this framework is the <emphasis role="bold">ConversationState</emphasis> object which stores all information about the state of the current user (very similar to the Session concept). The same ConversationState also stores acquired attributes of an <emphasis role="bold">Identity</emphasis> which is a set of principals to identify a user. @@ -21,7 +21,7 @@ <para> The ConversationState has definite lifetime. This object should be created when the user's identity becomes known by eXo (login procedure) and destroyed when the user leaves an eXo based application (logout procedure). Using JAAS it should happen in LoginModule's login() and logout() methods respectively. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-a1_Framework-a1.1_ConversationState_and_ConversationRegistry"> + <section id="sect-Reference_Guide-a1_Framework-a1.1_ConversationState_and_ConversationRegistry"> <title>1.1 ConversationState and ConversationRegistry</title> <para> The ConversationState can be stored @@ -71,7 +71,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-a1_Framework-a1.1_Authenticator"> + <section id="sect-Reference_Guide-a1_Framework-a1.1_Authenticator"> <title>1.1 Authenticator</title> <para> An Authenticator is responsible for Identity creating, it contains two methods: @@ -129,9 +129,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Security_Service-Usage"> + <section id="sect-Reference_Guide-Security_Service-Usage"> <title>Usage</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Usage-JAAS_login_module"> + <section id="sect-Reference_Guide-Usage-JAAS_login_module"> <title>JAAS login module</title> <para> The framework described is not coupled with any authentication mechanism but the most logical and implemented by default is the JAAS Login module. The typical sequence looks as follows (see org.exoplatform.services.security.jaas.DefaultLoginModule): @@ -217,7 +217,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Usage-a1.1_Predefinded_JAAS_login_modules"> + <section id="sect-Reference_Guide-Usage-a1.1_Predefinded_JAAS_login_modules"> <title>1.1 Predefinded JAAS login modules</title> <para> There are several JAAS Login modules included in eXo Platform sources: @@ -236,7 +236,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Usage-a1.1_J2EE_container_authentication"> + <section id="sect-Reference_Guide-Usage-a1.1_J2EE_container_authentication"> <title>1.1 J2EE container authentication</title> <para> As you know, when a user in JAAS is authenticated, a Subject is created as a result. This Subject represents the authenticated user. It is important to know and follow the rules regarding Subject filling which are specific for each J2EE server, where eXo Platform is deployed. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/spring-security-integration.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/spring-security-integration.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/spring-security-integration.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Spring_Security_Integration"> +<section id="sect-Reference_Guide-Spring_Security_Integration"> <title>Spring Security Integration</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Spring_Security_Integration-Introduction"> + <section id="sect-Reference_Guide-Spring_Security_Integration-Introduction"> <title>Introduction</title> <para> How to Integrate the spring security framework in the eXo portal? @@ -16,7 +16,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Spring_Security_Integration-Installation"> + <section id="sect-Reference_Guide-Spring_Security_Integration-Installation"> <title>Installation</title> <para> This tutorial assumes that you have a working eXo WCM installation running under JBoss 4.2.x. @@ -60,12 +60,12 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Spring_Security_Integration-Configuration"> + <section id="sect-Reference_Guide-Spring_Security_Integration-Configuration"> <title>Configuration</title> <para> To enable spring security in exo we need to go through a few configuration steps: </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuration-JAAS_disabling"> + <section id="sect-Reference_Guide-Configuration-JAAS_disabling"> <title>JAAS disabling</title> <para> First, we need to disable the JAAS security which is the default authentication mechanism in exo. Edit 02portal.war web.xml file and comment out the JAAS configuration related lines: @@ -110,7 +110,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuration-Enabling_spring_security"> + <section id="sect-Reference_Guide-Configuration-Enabling_spring_security"> <title>Enabling spring security</title> <para> To enable spring and set the spring security filter, add the following lines: @@ -154,7 +154,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuration-security_context.xml"> + <section id="sect-Reference_Guide-Configuration-security_context.xml"> <title>security-context.xml</title> <para> We need to configure the spring security filter chain for our purposes. Create a file named security-context.xml in 02portal.war WEB-INF directory containing the following lines: @@ -192,12 +192,12 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Spring_Security_Integration-Login_portlet_example"> + <section id="sect-Reference_Guide-Spring_Security_Integration-Login_portlet_example"> <title>Login portlet example</title> <para> Now that we have successfully installed and configured spring security in exo, we need a login portlet example to capture user credentials and serve as an entry point in the authentication process. The login portlet itself is based on JSF 1.2, Jboss portlet bridge and the spring framework, but you can obviously use whatever web framework you want to achieve the same. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Login_portlet_example-Building_the_portlet"> + <section id="sect-Reference_Guide-Login_portlet_example-Building_the_portlet"> <title>Building the portlet</title> <para> So we need a login form to capture user credentials inputs. The portlet login form consists of the following lines of xml: @@ -272,7 +272,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Login_portlet_example-Setting_up_the_login_portal_page"> + <section id="sect-Reference_Guide-Login_portlet_example-Setting_up_the_login_portal_page"> <title>Setting up the login portal page</title> <para> Now that we have a login portlet available we need to set it up into a portal page. @@ -307,7 +307,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Login_portlet_example-Customization_of_portal_login_and_logout_urls"> + <section id="sect-Reference_Guide-Login_portlet_example-Customization_of_portal_login_and_logout_urls"> <title>Customization of portal login and logout urls</title> <para> In the portal header, there is a login or logout action displayed depending whether you are already logged in or not. We need to customize those actions so that when the user clicks on it she or he will be redirected either to our login page or to the spring security logout url. Edit the article, go to the default.js tab and apply the following changes to the code: @@ -351,7 +351,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Login_portlet_example-A_look_at_the_login_page"> + <section id="sect-Reference_Guide-Login_portlet_example-A_look_at_the_login_page"> <title>A look at the login page</title> <para> Once you are done with all this, just click on the login action and you should be redirect to the login page looking something like that: @@ -368,7 +368,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Spring_Security_Integration-Integration_strategies"> + <section id="sect-Reference_Guide-Spring_Security_Integration-Integration_strategies"> <title>Integration strategies</title> <para> Until now we haven't discussed about any integration strategies concerning a potential existing security realm outside of the eXo platform. To address this problem we have the choice between at least two different strategies: @@ -376,7 +376,7 @@ <para> 1.1.1 <emphasis role="bold">Direct integration</emphasis> We can directly integrate eXo with the external realm. Everything related to organisation and user management in exo is cleanly separated in its own abstraction accessible through the OrganisationService. The authentication process itself is encapsulated in the Authenticator abstraction which sits on top of the organization service. eXo provides several implementations of both. So whether your realm is based on LDAP or JDBC and because the default implementations are generic enough, you will be able to use them and fits them to your needs with a matter of a little configuration. You can even develop a custom implementation to meet your more specific needs. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Integration_strategies-Replication"> + <section id="sect-Reference_Guide-Integration_strategies-Replication"> <title>Replication</title> <para> Or we can go through a replication process between the external realm and the eXo platform realm. This is the strategy that we are going to use to build our login portlet example. Furthermore, the replication will occur dynamically on any user authentication attempt. @@ -387,7 +387,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Spring_Security_Integration-Integration_with_eXo_portal"> + <section id="sect-Reference_Guide-Spring_Security_Integration-Integration_with_eXo_portal"> <title>Integration with eXo portal</title> <para> Being successfully authenticated against an external realm is not sufficient by itself. We also need to propagate the newly created security context to the portal own security mechanism. In eXo portal terminology, it means we have to create an Identity object for the user and register it into the Identity Registry. @@ -473,12 +473,12 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Spring_Security_Integration-Security_context_propagation_to_portlets"> + <section id="sect-Reference_Guide-Spring_Security_Integration-Security_context_propagation_to_portlets"> <title>Security context propagation to portlets</title> <para> Part of the problem is the question of security context propagation between on one side the portal webapp and at the other side the portlets webapps. This means that the security context has to be available in the portlet side allowing the application logic to deal the with current user principal and granted authorities. By default, Spring security uses a thread local variable to partially achieve this. But a problem may arise due to the fact that the portal invokes the portlet through a webapp cross context call. This means that it can lead to a class cast exceptions (two different classloaders involved), or that the security context is simply not propagated at all. To accommodate this, we will need to set up two request filters, one at the portal webapp side and the other at the portlet webapp side and use the http request to propagate the context in between. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Security_context_propagation_to_portlets-Portal_side_filter"> + <section id="sect-Reference_Guide-Security_context_propagation_to_portlets-Portal_side_filter"> <title>Portal side filter</title> <para> We will use the spring security extensible filter chain to plug in our filter. @@ -523,7 +523,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Security_context_propagation_to_portlets-Portlet_side_filter"> + <section id="sect-Reference_Guide-Security_context_propagation_to_portlets-Portlet_side_filter"> <title>Portlet side filter</title> <para> In the portlet webapp we create a regular filter named PortletSideSecurityContextFilter. @@ -601,7 +601,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Spring_Security_Integration-Conclusion"> + <section id="sect-Reference_Guide-Spring_Security_Integration-Conclusion"> <title>Conclusion</title> <para> We are done! Now we know how to integrate the spring security framework in the eXo portal. Thanks to the the great integration capabilities of both eXo portal and Spring framework. You can have a look to the attachment section on this page and get the source code of this tutorial. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/tika-document-reader-service.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/tika-document-reader-service.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core/tika-document-reader-service.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Tika_Document_Reader_Service"> +<section id="sect-Reference_Guide-Tika_Document_Reader_Service"> <title>Tika Document Reader Service</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Tika_Document_Reader_Service-Intro"> + <section id="sect-Reference_Guide-Tika_Document_Reader_Service-Intro"> <title>Intro</title> <para> DocumentReaderService provides API to retrieve DocumentReader by mimetype. @@ -16,7 +16,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Tika_Document_Reader_Service-Architecture"> + <section id="sect-Reference_Guide-Tika_Document_Reader_Service-Architecture"> <title>Architecture</title> <para> Basically, DocumentReaderService is a container for all registered DocumentReaders. So, you can register DocumentReader (method addDocumentReader(ComponentPlugin reader)) and fetch DocumentReader by mimeType (method getDocumentReader(String mimeType)). @@ -36,7 +36,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Tika_Document_Reader_Service-Configuration"> + <section id="sect-Reference_Guide-Tika_Document_Reader_Service-Configuration"> <title>Configuration</title> <para> How TikaDocumentReaderService Impl configuration looks like: @@ -299,7 +299,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Tika_Document_Reader_Service-Old_style_DocumentReaders_and_Tika_Parsers"> + <section id="sect-Reference_Guide-Tika_Document_Reader_Service-Old_style_DocumentReaders_and_Tika_Parsers"> <title>Old-style DocumentReaders and Tika Parsers</title> <para> As you see configuration above, there is both old-style DocumentReaders and new Tika parsers registered. @@ -310,7 +310,7 @@ <para> Old-style DocumentReader registered in configuration become registered into DocumentReaderService. So, mimetypes that is supported by those DocumentReaders will have a registered pair, and user will always fetch this DocumentReaders with getDocumentReader(..) method. Tika configuration will be checked for Parsers only if there is no already registered DocumentReader. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Old_style_DocumentReaders_and_Tika_Parsers-How_to_make_and_register_own_DocumentReader"> + <section id="sect-Reference_Guide-Old_style_DocumentReaders_and_Tika_Parsers-How_to_make_and_register_own_DocumentReader"> <title>How to make and register own DocumentReader</title> <para> You can make you own DocumentReader in two ways. @@ -389,7 +389,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Tika_Document_Reader_Service-TikaDocumentReader_features_and_notes"> + <section id="sect-Reference_Guide-Tika_Document_Reader_Service-TikaDocumentReader_features_and_notes"> <title>TikaDocumentReader features and notes</title> <para> TikaDocumentReader features and notes: Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/core.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-eXoCore"> +<section id="sect-Reference_Guide-eXoCore"> <title>eXoCore</title> <xi:include href="core/core.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> <xi:include href="core/db-creator-service.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/faq/jcr-faq.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/faq/jcr-faq.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/faq/jcr-faq.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_FAQ"> +<section id="sect-Reference_Guide-JCR_FAQ"> <title>JCR FAQ</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_FAQ-Kernel"> + <section id="sect-Reference_Guide-JCR_FAQ-Kernel"> <title>Kernel</title> <variablelist> <title></title> @@ -26,7 +26,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_FAQ-JCR_core"> + <section id="sect-Reference_Guide-JCR_FAQ-JCR_core"> <title>JCR core</title> <variablelist> <title></title> @@ -683,7 +683,7 @@ </variablelist> - </section> --> <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_FAQ-WebDAV"> + </section> --> <section id="sect-Reference_Guide-JCR_FAQ-WebDAV"> <title>WebDAV</title> <variablelist> <title></title> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/faq.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/faq.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/faq.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Frequently_Asked_Question"> +<section id="sect-Reference_Guide-Frequently_Asked_Question"> <title>Frequently Asked Question</title> <xi:include href="faq/jcr-faq.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> </section> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/api-extensions.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/api-extensions.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/api-extensions.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,13 +1,13 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-JCR_API_Extensions"> +<chapter id="chap-Reference_Guide-JCR_API_Extensions"> <title>JCR API Extensions</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_API_Extensions-Lazy_child_nodes_iteration"> + <section id="sect-Reference_Guide-JCR_API_Extensions-Lazy_child_nodes_iteration"> <title>"Lazy" child nodes iteration</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Lazy_child_nodes_iteration-Concept"> + <section id="sect-Reference_Guide-Lazy_child_nodes_iteration-Concept"> <title>Concept</title> <para> eXo JCR implementation offers new extended feature beyond JCR specification. Sometimes it happens that one JCR Node has hundreds or even thousands of child nodes. This situation is highly not recommended for content repository data storage, but some times it occurs. JCR Team is pleased to announce new feature that will help to have a deal with huge child lists. They can be iterated in a "lazy" manner now giving improvement in term of performance and RAM usage. @@ -15,7 +15,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Lazy_child_nodes_iteration-API_and_usage"> + <section id="sect-Reference_Guide-Lazy_child_nodes_iteration-API_and_usage"> <title>API and usage</title> <para> Lazy child nodes iteration feature is accessible via extended interface org.exoplatform.services.jcr.core.ExtendedNode, the inheritor of javax.jcr.Node. It provides a new single method shown below: @@ -39,7 +39,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Lazy_child_nodes_iteration-Configuration"> + <section id="sect-Reference_Guide-Lazy_child_nodes_iteration-Configuration"> <title>Configuration</title> <para> "Lazy" iterator makes ahead reading into memory, though reading the "page". "Page" is a set of nodes read at once. Size of the page by default is 100 nodes and can be configured though workspace container configuration using "lazy-node-iterator-page-size" parameter. I.e.: @@ -60,7 +60,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Lazy_child_nodes_iteration-Implementation_notices"> + <section id="sect-Reference_Guide-Lazy_child_nodes_iteration-Implementation_notices"> <title>Implementation notices</title> <para> Current "lazy" child nodes iterator supports caching, when pages are cached atomically in safe and optimized way. Cache is always kept in consistent state using invalidation if child list changed. Take in account the following difference in getNodes and getNodesLazily. Specification defined getNodes method reads whole list of nodes, so child items added after invocation will never be in results. GetNodesLazily doesn't acquire full list of nodes, so child items added after iterator creation can be found in result. So getNodesLazily can represent some kind of "real-time" results. But it is highly depend on numerous conditions and should not be used as a feature, it more likely implementation specific issue typical for "lazy-pattern". Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/backup/backup-client.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/backup/backup-client.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/backup/backup-client.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-HTTPBackupAgent_and_Backup_Client"> +<chapter id="chap-Reference_Guide-HTTPBackupAgent_and_Backup_Client"> <title><literal>HTTPBackupAgent</literal> and Backup Client</title> <warning> <title>Configuration Persistance</title> @@ -22,7 +22,7 @@ </para> </note> - <section id="sect-Reference_Guide_eXo_JCR_1.14-HTTPBackupAgent_and_Backup_Client-Introduction"> + <section id="sect-Reference_Guide-HTTPBackupAgent_and_Backup_Client-Introduction"> <title>Introduction</title> <para> The <literal>org.exoplatform.services.jcr.ext.backup.server.HTTPBackupAgent</literal> service is REST-based front-end to <literal>rg.exoplatform.services.jcr.ext.backup.BackupManager</literal>. @@ -36,7 +36,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-HTTPBackupAgent_and_Backup_Client-HTTPBackupAgent_"> + <section id="sect-Reference_Guide-HTTPBackupAgent_and_Backup_Client-HTTPBackupAgent_"> <title><literal>HTTPBackupAgent</literal> </title> <para> The <literal>HTTPBackupAgent</literal> is based on REST and uses <literal>POST</literal> and <literal>GET</literal> methods for request. @@ -83,9 +83,9 @@ </listitem> </itemizedlist> - <section id="sect-Reference_Guide_eXo_JCR_1.14-HTTPBackupAgent_-Methods"> + <section id="sect-Reference_Guide-HTTPBackupAgent_-Methods"> <title>Methods</title> - <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Methods-Starting_Backup_Service"> + <variablelist id="vari-Reference_Guide-Methods-Starting_Backup_Service"> <title>Starting Backup Service</title> <varlistentry> <term>/rest/jcr-backup/start/{repo}/{ws}</term> @@ -257,7 +257,7 @@ </varlistentry> </variablelist> - <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Methods-Stopping_Backup_Service"> + <variablelist id="vari-Reference_Guide-Methods-Stopping_Backup_Service"> <title>Stopping Backup Service</title> <varlistentry> <term>/rest/jcr-backup/stop/{id}</term> @@ -330,7 +330,7 @@ </varlistentry> </variablelist> - <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Methods-Backup_Info_Service"> + <variablelist id="vari-Reference_Guide-Methods-Backup_Info_Service"> <title>Backup Info Service</title> <varlistentry> <term>/rest/jcr-backup/info</term> @@ -413,7 +413,7 @@ </varlistentry> </variablelist> - <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Methods-Dropping_Workspace_Service"> + <variablelist id="vari-Reference_Guide-Methods-Dropping_Workspace_Service"> <title>Dropping Workspace Service</title> <varlistentry> <term>/rest/jcr-backup/drop-workspace/{repo}/{ws}/{force-session-close}</term> @@ -492,7 +492,7 @@ </varlistentry> </variablelist> - <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Methods-Backup_Info"> + <variablelist id="vari-Reference_Guide-Methods-Backup_Info"> <title>Backup Info</title> <varlistentry> <term>/rest/jcr-backup/info/backup</term> @@ -608,7 +608,7 @@ </varlistentry> </variablelist> - <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Methods-Current_Backups_Information"> + <variablelist id="vari-Reference_Guide-Methods-Current_Backups_Information"> <title>Current Backups Information</title> <varlistentry> <term>/rest/jcr-backup/info/backup/current</term> @@ -681,7 +681,7 @@ </varlistentry> </variablelist> - <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Methods-Completed_Backups_Information"> + <variablelist id="vari-Reference_Guide-Methods-Completed_Backups_Information"> <title>Completed Backups Information</title> <varlistentry> <term>/rest/jcr-backup/info/backup/completed</term> @@ -754,7 +754,7 @@ </varlistentry> </variablelist> - <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Methods-Workspace_specific_Backup_Information"> + <variablelist id="vari-Reference_Guide-Methods-Workspace_specific_Backup_Information"> <title>Workspace-specific Backup Information</title> <varlistentry> <term>/rest/jcr-backup/info/backup/{repo}/{ws}</term> @@ -830,7 +830,7 @@ </varlistentry> </variablelist> - <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Methods-Single_Backup_Information"> + <variablelist id="vari-Reference_Guide-Methods-Single_Backup_Information"> <title>Single Backup Information</title> <varlistentry> <term>/rest/jcr-backup/info/backup/{id}</term> @@ -948,7 +948,7 @@ </varlistentry> </variablelist> - <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Methods-Restores_on_a_Workspace_Information"> + <variablelist id="vari-Reference_Guide-Methods-Restores_on_a_Workspace_Information"> <title>Restores on a Workspace Information</title> <varlistentry> <term>/rest/jcr-backup/info/restore/{repo}/{ws}</term> @@ -1025,7 +1025,7 @@ </varlistentry> </variablelist> - <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Methods-Restores_Information"> + <variablelist id="vari-Reference_Guide-Methods-Restores_Information"> <title>Restores Information</title> <varlistentry> <term>/rest/jcr-backup/info/restores</term> @@ -1098,7 +1098,7 @@ </varlistentry> </variablelist> - <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Methods-Restoring_Service"> + <variablelist id="vari-Reference_Guide-Methods-Restoring_Service"> <title>Restoring Service</title> <varlistentry> <term>/rest/jcr-backup/restore/{repo}/{id}</term> @@ -1283,7 +1283,7 @@ </varlistentry> </variablelist> - <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Methods-Default_Workspace_Information"> + <variablelist id="vari-Reference_Guide-Methods-Default_Workspace_Information"> <title>Default Workspace Information</title> <varlistentry> <term>/rest/jcr-backup/info/default-ws-config</term> @@ -1452,7 +1452,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-HTTPBackupAgent_-HTTPBackupAgent_Configuration"> + <section id="sect-Reference_Guide-HTTPBackupAgent_-HTTPBackupAgent_Configuration"> <title>HTTPBackupAgent Configuration</title> <para> Add the components <literal>org.exoplatform.services.jcr.ext.backup.server.HTTPBackupAgent</literal> and <literal>org.exoplatform.services.jcr.ext.backup.BackupManager</literal> to services configuration: @@ -1504,7 +1504,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-HTTPBackupAgent_and_Backup_Client-Backup_Client"> + <section id="sect-Reference_Guide-HTTPBackupAgent_and_Backup_Client-Backup_Client"> <title>Backup Client</title> <note> <para> @@ -1584,7 +1584,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-HTTPBackupAgent_and_Backup_Client-Building_and_Running_Application"> + <section id="sect-Reference_Guide-HTTPBackupAgent_and_Backup_Client-Building_and_Running_Application"> <title>Building and Running Application</title> <note> <title>Document Convention</title> @@ -1647,7 +1647,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-HTTPBackupAgent_and_Backup_Client-Starting_Backups"> + <section id="sect-Reference_Guide-HTTPBackupAgent_and_Backup_Client-Starting_Backups"> <title>Starting Backups</title> <para> To start a full backup only on the workspace called "backup", pass the parameter <parameter><bakcup_dir></parameter> (<parameter>../temp/backup</parameter>) to the command: @@ -1748,7 +1748,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-HTTPBackupAgent_and_Backup_Client-Stopping_Backups"> + <section id="sect-Reference_Guide-HTTPBackupAgent_and_Backup_Client-Stopping_Backups"> <title>Stopping Backups</title> <para> Stop an individual backup with the following command: @@ -1765,7 +1765,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-HTTPBackupAgent_and_Backup_Client-Restoring"> + <section id="sect-Reference_Guide-HTTPBackupAgent_and_Backup_Client-Restoring"> <title>Restoring</title> <important> <title>Linebreaks</title> @@ -2014,7 +2014,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-HTTPBackupAgent_and_Backup_Client-Walkthrough_Creating_a_Backup_and_Restoring_a_Workspace"> + <section id="sect-Reference_Guide-HTTPBackupAgent_and_Backup_Client-Walkthrough_Creating_a_Backup_and_Restoring_a_Workspace"> <title>Walkthrough: Creating a Backup and Restoring a Workspace</title> <procedure> <title></title> @@ -2132,7 +2132,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-HTTPBackupAgent_and_Backup_Client-Walkthrough_Creating_a_Backup_and_Restoring_a_Repository"> + <section id="sect-Reference_Guide-HTTPBackupAgent_and_Backup_Client-Walkthrough_Creating_a_Backup_and_Restoring_a_Repository"> <title>Walkthrough: Creating a Backup and Restoring a Repository</title> <note> <title>Default Repository</title> @@ -2152,7 +2152,7 @@ </component></programlisting> </important> - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Walkthrough_Creating_a_Backup_and_Restoring_a_Repository-Backup_and_Restore_a_Repository"> + <procedure id="proc-Reference_Guide-Walkthrough_Creating_a_Backup_and_Restoring_a_Repository-Backup_and_Restore_a_Repository"> <title>Backup and Restore a Repository</title> <step> <title>Creating a backup</title> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/backup/backup-clonsole-dist.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/backup/backup-clonsole-dist.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/backup/backup-clonsole-dist.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Backup_Console_Binary_Distribution"> +<chapter id="chap-Reference_Guide-Backup_Console_Binary_Distribution"> <title>Backup Console Binary Distribution</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Backup_Console_Binary_Distribution-Introduction"> + <section id="sect-Reference_Guide-Backup_Console_Binary_Distribution-Introduction"> <title>Introduction</title> <para> The backup console binary distribution is a script-based front-end to the backup client. It assists you to create backups, restore, get the status of current or completed backup/restore processes. @@ -16,7 +16,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Backup_Console_Binary_Distribution-jcrbackup.cmd_and_jcrbackup.sh"> + <section id="sect-Reference_Guide-Backup_Console_Binary_Distribution-jcrbackup.cmd_and_jcrbackup.sh"> <title><command>jcrbackup.cmd</command> and <command>jcrbackup.sh</command></title> <para> These scripts are flexible for various authentication methods in shell scripts. @@ -83,7 +83,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Backup_Console_Binary_Distribution-exobackup.sh_and_exobackup.cmd"> + <section id="sect-Reference_Guide-Backup_Console_Binary_Distribution-exobackup.sh_and_exobackup.cmd"> <title><command>exobackup.sh</command> and <command>exobackup.cmd</command></title> <para> These scripts are suitable for use with JBoss Enterprise Portal Platform. @@ -143,9 +143,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Backup_Console_Binary_Distribution-Backup_Console_Binary_Distribution_usage"> + <section id="sect-Reference_Guide-Backup_Console_Binary_Distribution-Backup_Console_Binary_Distribution_usage"> <title>Backup Console Binary Distribution usage</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Backup_Console_Binary_Distribution_usage-Building_Application"> + <section id="sect-Reference_Guide-Backup_Console_Binary_Distribution_usage-Building_Application"> <title>Building Application</title> <procedure> <title></title> @@ -169,7 +169,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Backup_Console_Binary_Distribution_usage-Getting_Information_About_Backup_Service"> + <section id="sect-Reference_Guide-Backup_Console_Binary_Distribution_usage-Getting_Information_About_Backup_Service"> <title>Getting Information About Backup Service</title> <para> The context is "<emphasis>portal</emphasis>" by default for <literal>FORM</literal> authentication. @@ -191,7 +191,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Backup_Console_Binary_Distribution_usage-Getting_Information_About_Backup_Service_Not_Using_Default_Context"> + <section id="sect-Reference_Guide-Backup_Console_Binary_Distribution_usage-Getting_Information_About_Backup_Service_Not_Using_Default_Context"> <title>Getting Information About Backup Service Not Using Default Context</title> <para> If the context is "<emphasis>exodms-demo</emphasis>", the command would be: 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-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/backup/exojcr-backup-service.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-eXo_JCR_Backup_Service"> +<chapter id="chap-Reference_Guide-eXo_JCR_Backup_Service"> <title>eXo JCR Backup Service</title> <note> <para> @@ -11,7 +11,7 @@ </para> </note> - <section id="sect-Reference_Guide_eXo_JCR_1.14-eXo_JCR_Backup_Service-Concept"> + <section id="sect-Reference_Guide-eXo_JCR_Backup_Service-Concept"> <title>Concept</title> <para> The main purpose of this feature is to restore data in case of system faults and repository crashes. Also, the backup results may be used as a content history. @@ -61,9 +61,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-eXo_JCR_Backup_Service-How_it_works"> + <section id="sect-Reference_Guide-eXo_JCR_Backup_Service-How_it_works"> <title>How it works</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-How_it_works-Implementation_details"> + <section id="sect-Reference_Guide-How_it_works-Implementation_details"> <title>Implementation details</title> <para> <emphasis>Full</emphasis> backup/restore is implemented using the JCR SysView Export/Import. Workspace data will be exported into Sysview XML data from root node. @@ -87,7 +87,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-How_it_works-Work_basics"> + <section id="sect-Reference_Guide-How_it_works-Work_basics"> <title>Work basics</title> <para> The work of Backup is based on the BackupConfig configuration and the BackupChain logical unit. @@ -134,7 +134,7 @@ <para> <literal>BackupChain</literal> can contain one or more <literal>BackupJobs</literal>. The initial <emphasis>Full</emphasis> job is always there. Each <literal>BackupJobs</literal> has its own unique number which means its Job order in the chain, the initial <emphasis>Full</emphasis> job always has the number <literal>0</literal>. </para> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Work_basics-Backup_process_result_data_and_file_location"> + <formalpara id="form-Reference_Guide-Work_basics-Backup_process_result_data_and_file_location"> <title>Backup process, result data and file location</title> <para> To start the backup process, it is necessary to create the <literal>BackupConfig</literal> and call the <literal>BackupManager.startBackup(BackupConfig)</literal> method. This method will return <literal>BackupChain</literal> created according to the configuration. At the same time, the chain creates a <literal>BackupChainLog</literal> which persists <literal>BackupConfig</literal> content and <literal>BackupChain</literal> operation states to the file in the service working directory (see Configuration). @@ -159,7 +159,7 @@ </para> </note> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Work_basics-Restore_requirements"> + <formalpara id="form-Reference_Guide-Work_basics-Restore_requirements"> <title>Restore requirements</title> <para> As outlined earlier, a Restore operation is a mirror of a Backup. The process is a <emphasis>Full</emphasis> restore of a root node with restoring an additional <emphasis>Incremental</emphasis> backup to reach a desired workspace state. Restoring the workspace <emphasis>Full</emphasis> backup will create a new workspace in the repository using given <literal>RepositoryEntry</literal> of existing repository and given (preconfigured) WorkspaceEntry for a new target workspace. A Restore process will restore a root node from the SysView XML data. @@ -182,7 +182,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-eXo_JCR_Backup_Service-Configuration"> + <section id="sect-Reference_Guide-eXo_JCR_Backup_Service-Configuration"> <title>Configuration</title> <para> As an optional extension, the Backup service is not enabled by default. <emphasis role="bold">You need to enable it via configuration</emphasis>. @@ -192,10 +192,10 @@ </para> <programlistingco> <areaspec> - <area coords="9" id="area-Reference_Guide_eXo_JCR_1.14-eXo_JCR_Backup_Service-Configuration-incremental-backup-type" /> - <area coords="8" id="area-Reference_Guide_eXo_JCR_1.14-eXo_JCR_Backup_Service-Configuration-full-backup-type" /> - <area coords="7" id="area-Reference_Guide_eXo_JCR_1.14-eXo_JCR_Backup_Service-Configuration-default-incremental-job-period" /> - <area coords="10" id="area-Reference_Guide_eXo_JCR_1.14-eXo_JCR_Backup_Service-Configuration-backup-dir" /> + <area coords="9" id="area-Reference_Guide-eXo_JCR_Backup_Service-Configuration-incremental-backup-type" /> + <area coords="8" id="area-Reference_Guide-eXo_JCR_Backup_Service-Configuration-full-backup-type" /> + <area coords="7" id="area-Reference_Guide-eXo_JCR_Backup_Service-Configuration-default-incremental-job-period" /> + <area coords="10" id="area-Reference_Guide-eXo_JCR_Backup_Service-Configuration-backup-dir" /> </areaspec> @@ -209,9 +209,9 @@ </properties-param> </init-params> </component></programlisting> - <calloutlist id="call-Reference_Guide_eXo_JCR_1.14-Configuration-Mandatory_parameter"> + <calloutlist id="call-Reference_Guide-Configuration-Mandatory_parameter"> <title>Mandatory parameter</title> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-eXo_JCR_Backup_Service-Configuration-backup-dir"> + <callout arearefs="area-Reference_Guide-eXo_JCR_Backup_Service-Configuration-backup-dir"> <para> <parameter>backup-dir</parameter> is the path to a working directory where the service will store internal files and chain logs. </para> @@ -219,21 +219,21 @@ </callout> </calloutlist> - <calloutlist id="call-Reference_Guide_eXo_JCR_1.14-Configuration-Optional_parameters"> + <calloutlist id="call-Reference_Guide-Configuration-Optional_parameters"> <title>Optional parameters</title> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-eXo_JCR_Backup_Service-Configuration-incremental-backup-type"> + <callout arearefs="area-Reference_Guide-eXo_JCR_Backup_Service-Configuration-incremental-backup-type"> <para> <parameter>incremental-backup-type</parameter> The FQN of incremental job class. Must implement <literal>org.exoplatform.services.jcr.ext.backup.BackupJob</literal>. By default, <literal>org.exoplatform.services.jcr.ext.backup.impl.fs.FullBackupJob</literal> is used. </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-eXo_JCR_Backup_Service-Configuration-full-backup-type"> + <callout arearefs="area-Reference_Guide-eXo_JCR_Backup_Service-Configuration-full-backup-type"> <para> <parameter>full-backup-type</parameter> is the FQN of the full backup job class. It must implement <literal>org.exoplatform.services.jcr.ext.backup.BackupJob</literal>. By default, <literal>org.exoplatform.services.jcr.ext.backup.impl.rdbms.FullBackupJob</literal> is used. Please, notice that file-system based implementation <literal>org.exoplatform.services.jcr.ext.backup.impl.fs.FullBackupJob</literal> is deprecated and not recommended for use.. </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-eXo_JCR_Backup_Service-Configuration-default-incremental-job-period"> + <callout arearefs="area-Reference_Guide-eXo_JCR_Backup_Service-Configuration-default-incremental-job-period"> <para> <parameter>default-incremental-job-period</parameter> is the period between incremental flushes (in seconds). Default is <literal>3600</literal> seconds. </para> @@ -247,7 +247,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-eXo_JCR_Backup_Service-RDBMS_backup"> + <section id="sect-Reference_Guide-eXo_JCR_Backup_Service-RDBMS_backup"> <title>RDBMS backup</title> <para> RDBMS backup It is the latest, currently supported used by default and recommended implementation of full backup job for BackupManager service. It is useful in case when database is used to store data. @@ -288,9 +288,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-eXo_JCR_Backup_Service-Usage"> + <section id="sect-Reference_Guide-eXo_JCR_Backup_Service-Usage"> <title>Usage</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Usage-Performing_a_Backup"> + <section id="sect-Reference_Guide-Usage-Performing_a_Backup"> <title>Performing a Backup</title> <para> In the following example, we create a <literal>BackupConfig</literal> bean for the <emphasis>Full</emphasis> + <emphasis>Incremental</emphasis>s mode, then we ask the BackupManager to start the backup process. @@ -324,7 +324,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Usage-Performing_a_Restore"> + <section id="sect-Reference_Guide-Usage-Performing_a_Restore"> <title>Performing a Restore</title> <para> Restoration involves reloading the backup file into a <literal>BackupChainLog</literal> and applying appropriate workspace initialization. The following snippet shows the typical sequence for restoring a workspace: @@ -348,7 +348,7 @@ // run restoration backup.restore(bchLog, repositoryEntry, workspaceEntry);</programlisting> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Performing_a_Restore-Restoring_Into_An_Existing_Workspace"> + <section id="sect-Reference_Guide-Performing_a_Restore-Restoring_Into_An_Existing_Workspace"> <title>Restoring Into An Existing Workspace</title> <note> <para> @@ -359,7 +359,7 @@ <para> To restore a backup over an existing workspace, you are required to clear its data. Your backup process should follow these steps: </para> - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Restoring_Into_An_Existing_Workspace-Restore_Over_a_Workspace"> + <procedure id="proc-Reference_Guide-Restoring_Into_An_Existing_Workspace-Restore_Over_a_Workspace"> <title>Restore Over a Workspace</title> <step> <para> @@ -388,7 +388,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Performing_a_Restore-System_workspace"> + <section id="sect-Reference_Guide-Performing_a_Restore-System_workspace"> <title>System workspace</title> <note> <para> @@ -454,7 +454,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Usage-Repository_and_Workspace_Initialization_From_Backup"> + <section id="sect-Reference_Guide-Usage-Repository_and_Workspace_Initialization_From_Backup"> <title>Repository and Workspace Initialization From Backup</title> <para> Repository and Workspace initialization from backup can use the <literal>BackupWorkspaceInitializer</literal>. @@ -516,7 +516,7 @@ </initializer> ... </workspace></programlisting> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Repository_and_Workspace_Initialization_From_Backup-Restore_the_Workspace_over_BackupWorkspaceInitializer"> + <section id="sect-Reference_Guide-Repository_and_Workspace_Initialization_From_Backup-Restore_the_Workspace_over_BackupWorkspaceInitializer"> <title>Restore the Workspace over BackupWorkspaceInitializer</title> <para> Below is an example of configuration initializer to restore the workspace "<emphasis>backup</emphasis>" over <literal>BackupWorkspaceInitializer</literal>: @@ -566,7 +566,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Repository_and_Workspace_Initialization_From_Backup-Restore_the_Repository_over_BackupWorkspaceInitializer"> + <section id="sect-Reference_Guide-Repository_and_Workspace_Initialization_From_Backup-Restore_the_Repository_over_BackupWorkspaceInitializer"> <title>Restore the Repository over BackupWorkspaceInitializer</title> <para> Below is an example of configuration initializers to restore the repository "<emphasis>repository</emphasis>" over <literal>BackupWorkspaceInitializer</literal>: @@ -650,7 +650,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-eXo_JCR_Backup_Service-Scheduling_experimental"> + <section id="sect-Reference_Guide-eXo_JCR_Backup_Service-Scheduling_experimental"> <title>Scheduling (experimental)</title> <para> The Backup service has an additional feature that can be useful for a production level backup implementation. When you need to organize a backup of a repository, it is necessary to have a tool which will be able to create and manage a cycle of <emphasis>Full</emphasis> and <emphasis>Incremental</emphasis> backups in a periodic manner. @@ -661,7 +661,7 @@ <para> For that purpose, <literal>BackupScheduler</literal> has the method: <parameter>BackupScheduler.schedule(backupConfig, startDate, stopDate, chainPeriod, incrementalPeriod)</parameter> </para> - <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Scheduling_experimental-BackupScheduler_Method"> + <variablelist id="vari-Reference_Guide-Scheduling_experimental-BackupScheduler_Method"> <title>BackupScheduler Method</title> <varlistentry> <term>backupConfig</term> @@ -752,7 +752,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-eXo_JCR_Backup_Service-Restore_existing_workspace_or_repository"> + <section id="sect-Reference_Guide-eXo_JCR_Backup_Service-Restore_existing_workspace_or_repository"> <title>Restore existing workspace or repository</title> <para> The resore of existing workspace or repository is available. @@ -873,7 +873,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-eXo_JCR_Backup_Service-Restore_a_workspace_or_a_repository_using_original_configuration"> + <section id="sect-Reference_Guide-eXo_JCR_Backup_Service-Restore_a_workspace_or_a_repository_using_original_configuration"> <title>Restore a workspace or a repository using original configuration</title> <para> The Backup manager allows you to restore a repository or a workspace using the original configuration stored into the backup log: @@ -1015,7 +1015,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-eXo_JCR_Backup_Service-Backup_set_portability"> + <section id="sect-Reference_Guide-eXo_JCR_Backup_Service-Backup_set_portability"> <title>Backup set portability</title> <para> The Backup log is stored during the Backup operation into two different locations: <parameter>backup-dir</parameter> directory of <literal>BackupService</literal> to support interactive operations via Backup API (e.g. console) and backup set files for portability (e.g. on another server). Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/backup/use-external-backup-tool.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/backup/use-external-backup-tool.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/backup/use-external-backup-tool.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Use_External_Backup_Tool"> +<chapter id="chap-Reference_Guide-Use_External_Backup_Tool"> <title>Use External Backup Tool</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Use_External_Backup_Tool-Repository_Suspending"> + <section id="sect-Reference_Guide-Use_External_Backup_Tool-Repository_Suspending"> <title>Repository Suspending</title> <para> To have the repository content consistent with the search index and value storage, the repository should be suspened. This means all working threads are suspended until a resume operation is performed. The index will be flushed. @@ -34,7 +34,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Use_External_Backup_Tool-Backup"> + <section id="sect-Reference_Guide-Use_External_Backup_Tool-Backup"> <title>Backup</title> <para> You can backup your content manually or by using third part software. You should back up: @@ -63,7 +63,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Use_External_Backup_Tool-Repository_Resuming"> + <section id="sect-Reference_Guide-Use_External_Backup_Tool-Repository_Resuming"> <title>Repository Resuming</title> <para> Once a backup is done you need to invoke the <literal>resume()</literal> operation to switch the repository back to online. The returned result will be "<emphasis>online</emphasis>". Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/cluster-config.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/cluster-config.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/cluster-config.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,13 +1,13 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Cluster_Configuration"> +<chapter id="chap-Reference_Guide-Cluster_Configuration">  <title>Cluster Configuration</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Cluster_Configuration-Launching_Cluster"> + <section id="sect-Reference_Guide-Cluster_Configuration-Launching_Cluster"> <title>Launching Cluster</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Launching_Cluster-Deploying_eXo_JCR_to_JBoss_Application_Server"> + <section id="sect-Reference_Guide-Launching_Cluster-Deploying_eXo_JCR_to_JBoss_Application_Server"> <title>Deploying eXo JCR to JBoss Application Server</title> <para> To deploy eXo JCR to the JBoss AS, do the following: @@ -94,22 +94,22 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Launching_Cluster-Configuring_JCR_to_use_external_configuration"> + <section id="sect-Reference_Guide-Launching_Cluster-Configuring_JCR_to_use_external_configuration"> <title>Configuring JCR to use external configuration</title> <itemizedlist> <listitem> <para> - To manually configure a repository, create a new configuration file (<filename>exo-jcr-configuration.xml</filename> for example). For details, see <xref linkend="chap-Reference_Guide_eXo_JCR_1.14-JCR_configuration" />. + To manually configure a repository, create a new configuration file (<filename>exo-jcr-configuration.xml</filename> for example). For details, see <xref linkend="chap-Reference_Guide-JCR_configuration" />. </para> <para> The configuration file must be formatted as follows: </para> <programlistingco> <areaspec> - <area coords="20" id="area-Reference_Guide_eXo_JCR_1.14-Launching_Cluster-Configuring_JCR_to_use_external_configuration-value_storages" /> - <area coords="27" id="area-Reference_Guide_eXo_JCR_1.14-Launching_Cluster-Configuring_JCR_to_use_external_configuration-conf_cache" /> - <area coords="31" id="area-Reference_Guide_eXo_JCR_1.14-Launching_Cluster-Configuring_JCR_to_use_external_configuration-conf_indexer" /> - <area coords="34" id="area-Reference_Guide_eXo_JCR_1.14-Launching_Cluster-Configuring_JCR_to_use_external_configuration-conf_lock_manager" /> + <area coords="20" id="area-Reference_Guide-Launching_Cluster-Configuring_JCR_to_use_external_configuration-value_storages" /> + <area coords="27" id="area-Reference_Guide-Launching_Cluster-Configuring_JCR_to_use_external_configuration-conf_cache" /> + <area coords="31" id="area-Reference_Guide-Launching_Cluster-Configuring_JCR_to_use_external_configuration-conf_indexer" /> + <area coords="34" id="area-Reference_Guide-Launching_Cluster-Configuring_JCR_to_use_external_configuration-conf_lock_manager" /> </areaspec> @@ -160,27 +160,27 @@ </repositories> </repository-service></programlisting> <calloutlist> -  <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Launching_Cluster-Configuring_JCR_to_use_external_configuration-value_storages"> +  <callout arearefs="area-Reference_Guide-Launching_Cluster-Configuring_JCR_to_use_external_configuration-value_storages"> <para> - Refer to <xref linkend="exam-Reference_Guide_eXo_JCR_1.14-Configuration_requirements-Value_Storage_configuration" />. + Refer to <xref linkend="exam-Reference_Guide-Configuration_requirements-Value_Storage_configuration" />. </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Launching_Cluster-Configuring_JCR_to_use_external_configuration-conf_cache"> + <callout arearefs="area-Reference_Guide-Launching_Cluster-Configuring_JCR_to_use_external_configuration-conf_cache"> <para> - Refer to <xref linkend="exam-Reference_Guide_eXo_JCR_1.14-Configuration_requirements-Cache_configuration" />. + Refer to <xref linkend="exam-Reference_Guide-Configuration_requirements-Cache_configuration" />. </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Launching_Cluster-Configuring_JCR_to_use_external_configuration-conf_indexer"> + <callout arearefs="area-Reference_Guide-Launching_Cluster-Configuring_JCR_to_use_external_configuration-conf_indexer"> <para> - Refer to <xref linkend="exam-Reference_Guide_eXo_JCR_1.14-Configuration_requirements-Indexer_configuration" />. + Refer to <xref linkend="exam-Reference_Guide-Configuration_requirements-Indexer_configuration" />. </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Launching_Cluster-Configuring_JCR_to_use_external_configuration-conf_lock_manager"> + <callout arearefs="area-Reference_Guide-Launching_Cluster-Configuring_JCR_to_use_external_configuration-conf_lock_manager"> <para> - Refer to <xref linkend="exam-Reference_Guide_eXo_JCR_1.14-Configuration_requirements-Lock_Manager_configuration" />. + Refer to <xref linkend="exam-Reference_Guide-Configuration_requirements-Lock_Manager_configuration" />. </para> </callout> @@ -217,9 +217,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Cluster_Configuration-Requirements"> + <section id="sect-Reference_Guide-Cluster_Configuration-Requirements"> <title>Requirements</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Requirements-Environment_requirements"> + <section id="sect-Reference_Guide-Requirements-Environment_requirements"> <title>Environment requirements</title> <itemizedlist> <listitem> @@ -238,7 +238,7 @@ <para> The same Clusters on different nodes <emphasis role="bold">must</emphasis> have the same names. </para> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Environment_requirements-Example"> + <example id="exam-Reference_Guide-Environment_requirements-Example"> <title>Example</title> <para> If the <emphasis>Indexer</emphasis> cluster in the <emphasis>production</emphasis> workspace on the first node is named <literal>production_indexer_cluster</literal>, then <emphasis>indexer</emphasis> clusters in the <emphasis>production</emphasis> workspace on all other nodes <emphasis role="bold">must</emphasis> also be named <literal>production_indexer_cluster</literal>. @@ -252,12 +252,12 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Requirements-Configuration_requirements"> + <section id="sect-Reference_Guide-Requirements-Configuration_requirements"> <title>Configuration requirements</title> <para> The configuration of every workspace in the repository must contain the following elements: </para> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Configuration_requirements-Value_Storage_configuration"> + <example id="exam-Reference_Guide-Configuration_requirements-Value_Storage_configuration"> <title>Value Storage configuration</title> <programlisting language="XML" role="XML"><value-storages> @@ -272,7 +272,7 @@ </value-storages></programlisting> </example> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Configuration_requirements-Cache_configuration"> + <example id="exam-Reference_Guide-Configuration_requirements-Cache_configuration"> <title>Cache configuration</title> <programlisting language="XML" role="XML"><cache enabled="true" class="org.exoplatform.services.jcr.impl.dataflow.persistent.jbosscache.JBossCacheWorkspaceStorageCache"> @@ -285,7 +285,7 @@ </cache></programlisting> </example> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Configuration_requirements-Indexer_configuration"> + <example id="exam-Reference_Guide-Configuration_requirements-Indexer_configuration"> <title>Indexer configuration</title> <programlisting language="XML" role="XML"><query-handler class="org.exoplatform.services.jcr.impl.core.query.lucene.SearchIndex"> @@ -300,7 +300,7 @@ </query-handler></programlisting> </example> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Configuration_requirements-Lock_Manager_configuration"> + <example id="exam-Reference_Guide-Configuration_requirements-Lock_Manager_configuration"> <title>Lock Manager configuration</title> <programlisting language="XML" role="XML"><lock-manager class="org.exoplatform.services.jcr.impl.core.lock.jbosscache.CacheableLockManagerImpl"> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/jcr-advantages.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/jcr-advantages.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/jcr-advantages.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Advantages_of_eXo_JCR"> +<chapter id="chap-Reference_Guide-Advantages_of_eXo_JCR"> <title>Advantages of eXo JCR</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Advantages_of_eXo_JCR-Application_Developers"> + <section id="sect-Reference_Guide-Advantages_of_eXo_JCR-Application_Developers"> <title>Application Developers</title> <itemizedlist> <listitem> @@ -37,7 +37,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Advantages_of_eXo_JCR-Managers"> + <section id="sect-Reference_Guide-Advantages_of_eXo_JCR-Managers"> <title>Managers</title> <itemizedlist> <listitem> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/jcr-applications.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/jcr-applications.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/jcr-applications.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-eXo_JCR_Application_Model"> +<chapter id="chap-Reference_Guide-eXo_JCR_Application_Model"> <title>eXo JCR Application Model</title> <para> The following image illustrates the interaction between Applications and JCR: Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/jcr-compatibility-levels.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/jcr-compatibility-levels.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/jcr-compatibility-levels.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Compatibility_Levels"> +<chapter id="chap-Reference_Guide-Compatibility_Levels"> <title>Compatibility Levels</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Compatibility_Levels-Introduction"> + <section id="sect-Reference_Guide-Compatibility_Levels-Introduction"> <title>Introduction</title> <para> The Java Content Repository specification JSR-170 has been split into two compliance levels as well as a set of optional features. <literal>Level 1</literal> defines a read-only repository while <literal>Level 2</literal> defines methods for writing content and bi-directional interaction with the repository. @@ -16,7 +16,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Compatibility_Levels-Level_1"> + <section id="sect-Reference_Guide-Compatibility_Levels-Level_1"> <title>Level 1</title> <para> Level 1 includes read-only functionality for very simple repositories. It is useful to migrate an existing data repository and step through converting it to a more advanced implementation. The JCR uses a well-known Session abstraction to access the repository data. @@ -78,7 +78,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Compatibility_Levels-Level_2"> + <section id="sect-Reference_Guide-Compatibility_Levels-Level_2"> <title>Level 2</title> <para> JCR Level 2 includes reading and writing of content functionality, importing other sources and managing content definition and structuring using extensible node types. @@ -128,7 +128,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Compatibility_Levels-Optional_features"> + <section id="sect-Reference_Guide-Compatibility_Levels-Optional_features"> <title>Optional features</title> <para> On the top of Level 1 or Level 2, a number of optional features are defined for a more advanced repository functionality. This includes functions such as Versioning, (JTA) Transactions, Query using SQL, Explicit Locking and Content Observation. eXo JCR supports all optional features. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/jcr-exo-implementation.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/jcr-exo-implementation.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/jcr-exo-implementation.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Implementation"> +<chapter id="chap-Reference_Guide-Implementation">  <title>Implementation</title> <para> The relationships between the eXo Repository Service components are illustrated below: @@ -14,7 +14,7 @@ </imageobject> </mediaobject> - <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Implementation-Definitions"> + <variablelist id="vari-Reference_Guide-Implementation-Definitions"> <title>Definitions</title> <varlistentry> <term>eXo Container:</term> @@ -75,7 +75,7 @@ <procedure> <step> <para> - Obtaining Repository object by getting <emphasis role="bold">Repository Service</emphasis> via JNDI lookup if eXo repository is bound to the naming context using (see <xref linkend="chap-Reference_Guide_eXo_JCR_1.14-JCR_configuration" /> for details). + Obtaining Repository object by getting <emphasis role="bold">Repository Service</emphasis> via JNDI lookup if eXo repository is bound to the naming context using (see <xref linkend="chap-Reference_Guide-JCR_configuration" /> for details). </para> </step> @@ -88,7 +88,7 @@ </procedure> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Implementation-Workspace_Data_Model"> + <section id="sect-Reference_Guide-Implementation-Workspace_Data_Model"> <title>Workspace Data Model</title> <para> The following diagram explains which components of a eXo JCR implementation are used in a data flow to perform operations specified in the JCR API. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/jcr-extensions.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/jcr-extensions.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/jcr-extensions.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,13 +1,13 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-JCR_Extensions"> +<chapter id="chap-Reference_Guide-JCR_Extensions"> <title>JCR Extensions</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Extensions-JCR_Service_Extensions"> + <section id="sect-Reference_Guide-JCR_Extensions-JCR_Service_Extensions"> <title>JCR Service Extensions</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Service_Extensions-Concept"> + <section id="sect-Reference_Guide-JCR_Service_Extensions-Concept"> <title>Concept</title> <para> eXo JCR supports <emphasis role="bold">observation</emphasis> (JSR-170 8.3), which enables applications to register interest in events that describe changes to a workspace, and then monitor and respond to those events. The standard observation feature allows dispatching events when <emphasis role="bold">persistent change</emphasis> to the workspace is made. @@ -28,7 +28,7 @@ <para> However, if your application logic requires the action to add items to a created or updated item and you save these changes immediately after the JCR API method call is returned, the suggestion with Thread is not applicable for you in this case. </para> - <figure id="figu-Reference_Guide_eXo_JCR_1.14-Concept-Implementation"> + <figure id="figu-Reference_Guide-Concept-Implementation"> <title>Implementation</title> <mediaobject> <imageobject> @@ -41,7 +41,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Service_Extensions-Configuration"> + <section id="sect-Reference_Guide-JCR_Service_Extensions-Configuration"> <title>Configuration</title> <para> Add a <literal>SessionActionCatalog</literal> service and an appropriate <literal>AddActionsPlugin</literal> (see the example below) configuration to your eXo Container configuration. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/jcr-namespace-altering.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/jcr-namespace-altering.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/jcr-namespace-altering.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,14 +1,14 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Namespace_Altering"> +<chapter id="chap-Reference_Guide-Namespace_Altering">  <title>Namespace Altering</title> <para> Since version 1.11, the eXo JCR implementation supports namespaces altering. </para> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Namespace_Altering-Adding_New_Namespace"> + <formalpara id="form-Reference_Guide-Namespace_Altering-Adding_New_Namespace"> <title>Adding New Namespace</title> <para> Add a new namespace with: @@ -18,7 +18,7 @@ <programlisting language="Java" role="Java">ExtendedNamespaceRegistry namespaceRegistry = (ExtendedNamespaceRegistry) workspace.getNamespaceRegistry(); namespaceRegistry.registerNamespace("newMapping", "http://dumb.uri/jcr");</programlisting> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Namespace_Altering-Changing_Existing_Namespace"> + <formalpara id="form-Reference_Guide-Namespace_Altering-Changing_Existing_Namespace"> <title>Changing Existing Namespace</title> <para> Change an existing namespace with: @@ -29,7 +29,7 @@ <programlisting language="Java" role="Java">ExtendedNamespaceRegistry namespaceRegistry = (ExtendedNamespaceRegistry) workspace.getNamespaceRegistry(); namespaceRegistry.registerNamespace("newMapping", "http://dumb.uri/jcr"); namespaceRegistry.registerNamespace("newMapping2", "http://dumb.uri/jcr");</programlisting> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Namespace_Altering-Removing_Existing_Namespace"> + <formalpara id="form-Reference_Guide-Namespace_Altering-Removing_Existing_Namespace"> <title>Removing Existing Namespace</title> <para> Remove an existing namespace with: Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/jcr-registry-service.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/jcr-registry-service.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/jcr-registry-service.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Registry_Service"> +<chapter id="chap-Reference_Guide-Registry_Service"> <title>Registry Service</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Registry_Service-Concept"> + <section id="sect-Reference_Guide-Registry_Service-Concept"> <title>Concept</title> <para> The Registry Service is one of the key parts of the infrastructure built around eXo JCR. Each JCR that is based on services and applications may have its own configuration, settings, and other data that have to be stored persistently and used by the appropriate service or application (referred to as a <emphasis>Consumer</emphasis>). @@ -47,7 +47,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Registry_Service-The_API"> + <section id="sect-Reference_Guide-Registry_Service-The_API"> <title>The API</title> <para> The main functionality of the Registry Service is described in the Registry abstract class as the following: @@ -107,7 +107,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Registry_Service-Configuration"> + <section id="sect-Reference_Guide-Registry_Service-Configuration"> <title>Configuration</title> <para> <literal>RegistryService</literal> has only one optional properties parameter; <parameter>locations</parameter>. It is used to mention where <literal>exo:registry</literal> is placed for each repository. The name of each property is interpreted as a repository name and its value as a workspace name (a system workspace by default). Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/jcr-usage.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/jcr-usage.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/jcr-usage.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Using_The_JCR"> +<chapter id="chap-Reference_Guide-Using_The_JCR"> <title>Using The JCR</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Using_The_JCR-Obtaining_a_Repository_Object"> + <section id="sect-Reference_Guide-Using_The_JCR-Obtaining_a_Repository_Object"> <title>Obtaining a Repository Object</title> <para> A <literal>javax.jcr.Repository</literal> object can be obtained by: @@ -50,7 +50,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Using_The_JCR-JCR_Session_common_considerations"> + <section id="sect-Reference_Guide-Using_The_JCR-JCR_Session_common_considerations"> <title>JCR Session common considerations</title> <para> <itemizedlist> @@ -85,9 +85,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Using_The_JCR-JCR_Application_Practices"> + <section id="sect-Reference_Guide-Using_The_JCR-JCR_Application_Practices"> <title>JCR Application Practices</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Application_Practices-Log_Out_of_All_Open_Sessions"> + <section id="sect-Reference_Guide-JCR_Application_Practices-Log_Out_of_All_Open_Sessions"> <title>Log Out of All Open Sessions</title> <para> Use <literal>org.exoplatform.services.jcr.ext.common.SessionProvider</literal> which is responsible for caching or obtaining your JCR Sessions and closing all opened sessions at once. @@ -151,7 +151,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Application_Practices-Reusing_SessionProvider"> + <section id="sect-Reference_Guide-JCR_Application_Practices-Reusing_SessionProvider"> <title>Reusing SessionProvider</title> <para> Since creating the <literal>SessionProvider</literal> involves multiple steps which may need to be repeated for each JCR session, the <literal>SessionProviderService</literal> assists you to get a <literal>SessionProvider</literal> object. @@ -168,7 +168,7 @@ <para> The main contract of an implemented component is obtaining a <literal>SessionProvider</literal> by key. the eXo JCR provides two implementations: </para> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Reusing_SessionProvider-SessionProvider_implementations"> + <table id="tabl-Reference_Guide-Reusing_SessionProvider-SessionProvider_implementations"> <title>SessionProvider implementations</title> <tgroup cols="3"> <thead> 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-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/nodetype-registration.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-NodeType_Registration"> +<chapter id="chap-Reference_Guide-NodeType_Registration">  <title>NodeType Registration</title> <para> The eXo JCR implementation supports two methods of Nodetypes registration: @@ -11,21 +11,21 @@ <itemizedlist> <listitem> <para> - From a <literal>NodeTypeValue</literal> POJO. Refer to <xref linkend="exam-Reference_Guide_eXo_JCR_1.14-Node_type_registration-Run_time_registration_using_NodeTypeValue" /> + 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_eXo_JCR_1.14-Node_type_registration-Runtime_Registration_From_XML_File" />. + From an XML document. Refer to <xref linkend="exam-Reference_Guide-Node_type_registration-Runtime_Registration_From_XML_File" />. </para> </listitem> </itemizedlist> - <section id="sect-Reference_Guide_eXo_JCR_1.14-NodeType_Registration-Interfaces_and_methods"> + <section id="sect-Reference_Guide-NodeType_Registration-Interfaces_and_methods"> <title>Interfaces and methods</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Interfaces_and_methods-ExtendedNodeTypeManager"> + <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: @@ -80,7 +80,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Interfaces_and_methods-NodeTypeValue"> + <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. @@ -165,7 +165,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Interfaces_and_methods-NodeDefinitionValue"> + <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>. @@ -252,12 +252,12 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Interfaces_and_methods-PropertyDefinitionValue"> + <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_eXo_JCR_1.14-PropertyDefinitionValue-PropertyDefinitionValue"> + <example id="exam-Reference_Guide-PropertyDefinitionValue-PropertyDefinitionValue"> <title><literal>PropertyDefinitionValue</literal></title> <programlisting language="Java" role="Java">/** @@ -301,7 +301,7 @@ public void setValueConstraints(List<String> valueConstraints);</programlisting> </example> - <example id="exam-Reference_Guide_eXo_JCR_1.14-PropertyDefinitionValue-ItemDefinitionValue"> + <example id="exam-Reference_Guide-PropertyDefinitionValue-ItemDefinitionValue"> <title><literal>ItemDefinitionValue</literal></title> <programlisting language="Java" role="Java"> /** @@ -358,12 +358,12 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Interfaces_and_methods-Node_type_registration"> + <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_eXo_JCR_1.14-Node_type_registration-Runtime_Registration_From_XML_File"> + <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() @@ -372,7 +372,7 @@ nodeTypeManager.registerNodeTypes(is,ExtendedNodeTypeManager.IGNORE_IF_EXISTS );</programlisting> </example> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Node_type_registration-Run_time_registration_using_NodeTypeValue"> + <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() @@ -402,7 +402,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Interfaces_and_methods-Changing_Existing_Node_Type"> + <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>. @@ -416,7 +416,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Interfaces_and_methods-Removing_node_type"> + <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. @@ -426,7 +426,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Interfaces_and_methods-Adding_New_PropertyDefinition"> + <section id="sect-Reference_Guide-Interfaces_and_methods-Adding_New_PropertyDefinition"> <title>Adding New <literal>PropertyDefinition</literal></title> <programlisting language="Java" role="Java"> @@ -447,7 +447,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Interfaces_and_methods-Adding_New_Child_NodeDefinition"> + <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>. @@ -470,7 +470,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Interfaces_and_methods-Edit_Existing_PropertyDefinition_or_Child_NodeDefinition"> + <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. @@ -528,7 +528,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Interfaces_and_methods-Changing_The_List_of_Super_Types"> + <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: Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/nodetypes-and-namespaces.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/nodetypes-and-namespaces.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/nodetypes-and-namespaces.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Node_Types_and_Namespaces"> +<chapter id="chap-Reference_Guide-Node_Types_and_Namespaces"> <title>Node Types and Namespaces</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Node_Types_and_Namespaces-Introduction"> + <section id="sect-Reference_Guide-Node_Types_and_Namespaces-Introduction"> <title>Introduction</title> <para> The JSR-170 specification requires support of node types and namespaces. Beyond the methods required by the specification, the eXo JCR has its own API extension for NodeType registration as well as the ability to declaratively define node types in the Repository at the start-up time. @@ -13,7 +13,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Node_Types_and_Namespaces-Node_Types_Definition"> + <section id="sect-Reference_Guide-Node_Types_and_Namespaces-Node_Types_Definition"> <title>Node Types Definition</title> <para> Node type registration extension is declared in <literal>org.exoplatform.services.jcr.core.nodetype.ExtendedNodeTypeManager</literal> interface @@ -122,7 +122,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Node_Types_and_Namespaces-Namespaces_Definition"> + <section id="sect-Reference_Guide-Node_Types_and_Namespaces-Namespaces_Definition"> <title>Namespaces Definition</title> <para> Default namespaces are registered by repository at start up. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/why-jcr.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/why-jcr.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/concepts/why-jcr.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Java_Content_Repository"> +<chapter id="chap-Reference_Guide-Java_Content_Repository"> <title>Java Content Repository</title> <para> A Java Content Repository (<abbrev>JCR</abbrev>) is a java interface used to access contents that are not only web contents, but also other hierarchically stored data. The content is stored in a repository. The repository can be a file system, a relational database or an XML document. The internal structure of JCR data looks similar to an XML document; a document tree with nodes and data, however, in a JCR, the data is stored in <literal>property items</literal>. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/configuration-persister.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/configuration-persister.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/configuration-persister.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,18 +1,18 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-JCR_Configuration_persister"> +<chapter id="chap-Reference_Guide-JCR_Configuration_persister"> <title>JCR Configuration persister</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Configuration_persister-Concept"> + <section id="sect-Reference_Guide-JCR_Configuration_persister-Concept"> <title>Concept</title> <para> The JCR Repository Service uses the <literal>org.exoplatform.services.jcr.config.RepositoryServiceConfiguration</literal> component for its configuration. </para> <programlistingco> <areaspec> - <area coords="8" id="area-Reference_Guide_eXo_JCR_1.14-JCR_Configuration_persister-Concept-config" /> + <area coords="8" id="area-Reference_Guide-JCR_Configuration_persister-Concept-config" /> </areaspec> @@ -28,7 +28,7 @@ </init-params> </component></programlisting> <calloutlist> -  <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-JCR_Configuration_persister-Concept-config"> +  <callout arearefs="area-Reference_Guide-JCR_Configuration_persister-Concept-config"> <para> In this example, the Repository Service will read the configuration from the file <filename>war:/conf/jcr/repository-configuration.xml</filename>. </para> @@ -45,7 +45,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Configuration_persister-Usage"> + <section id="sect-Reference_Guide-JCR_Configuration_persister-Usage"> <title>Usage</title> <para> On start up the <literal>RepositoryServiceConfiguration</literal> component checks if a configuration persister was configured. If one has been, it uses the provided <literal>ConfigurationPersister</literal> implementation class to instantiate the persister object. @@ -55,9 +55,9 @@ </para> <programlistingco> <areaspec> - <area coords="13" id="area-Reference_Guide_eXo_JCR_1.14-JCR_Configuration_persister-Usage-source_name" /> - <area coords="14" id="area-Reference_Guide_eXo_JCR_1.14-JCR_Configuration_persister-Usage-dialect" /> - <area coords="15" id="area-Reference_Guide_eXo_JCR_1.14-JCR_Configuration_persister-Usage-persister_class_name" /> + <area coords="13" id="area-Reference_Guide-JCR_Configuration_persister-Usage-source_name" /> + <area coords="14" id="area-Reference_Guide-JCR_Configuration_persister-Usage-dialect" /> + <area coords="15" id="area-Reference_Guide-JCR_Configuration_persister-Usage-persister_class_name" /> </areaspec> @@ -81,19 +81,19 @@ </component> </programlisting> <calloutlist> -  <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-JCR_Configuration_persister-Usage-source_name"> +  <callout arearefs="area-Reference_Guide-JCR_Configuration_persister-Usage-source_name"> <para> - <parameter><replaceable>source-name</replaceable></parameter>: The JNDI source name is configured in the <literal>InitialContextInitializer</literal> component. This was known as <parameter>sourceName</parameter> in versions prior to 1.9. Refer to <xref linkend="chap-Reference_Guide_eXo_JCR_1.14-JDBC_Data_Container_Config" /> for more information. + <parameter><replaceable>source-name</replaceable></parameter>: The JNDI source name is configured in the <literal>InitialContextInitializer</literal> component. This was known as <parameter>sourceName</parameter> in versions prior to 1.9. Refer to <xref linkend="chap-Reference_Guide-JDBC_Data_Container_Config" /> for more information. </para> </callout> -  <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-JCR_Configuration_persister-Usage-dialect"> +  <callout arearefs="area-Reference_Guide-JCR_Configuration_persister-Usage-dialect"> <para> - <parameter><replaceable>dialect</replaceable></parameter>: The SQL dialect which will be used with the database from <parameter><replaceable>source-name</replaceable></parameter>. Refer to <xref linkend="chap-Reference_Guide_eXo_JCR_1.14-JDBC_Data_Container_Config" /> for more information. + <parameter><replaceable>dialect</replaceable></parameter>: The SQL dialect which will be used with the database from <parameter><replaceable>source-name</replaceable></parameter>. Refer to <xref linkend="chap-Reference_Guide-JDBC_Data_Container_Config" /> for more information. </para> </callout> -  <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-JCR_Configuration_persister-Usage-persister_class_name"> +  <callout arearefs="area-Reference_Guide-JCR_Configuration_persister-Usage-persister_class_name"> <para> <parameter><replaceable>persister-class-name</replaceable></parameter>: The class name of the <literal>ConfigurationPersister</literal> interface implementation. This was known as <parameter>persisterliteral</parameter> in versions prior to 1.9. </para> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/exo-jcr-configuration.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/exo-jcr-configuration.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/exo-jcr-configuration.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,14 +1,14 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-JCR_configuration"> +<chapter id="chap-Reference_Guide-JCR_configuration"> <title>JCR configuration</title> <para> The JCR configuration is defined in an XML file which is constructed as per the DTD below: </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_configuration-Portal_configuration"> + <section id="sect-Reference_Guide-JCR_configuration-Portal_configuration"> <title>Portal configuration</title> <para> JCR services are registered in the Portal container. @@ -18,8 +18,8 @@ </para> <programlistingco> <areaspec> - <area coords="10" id="area-Reference_Guide_eXo_JCR_1.14-JCR_configuration-conf-path" /> - <area coords="15" id="area-Reference_Guide_eXo_JCR_1.14-JCR_configuration-working-conf" /> + <area coords="10" id="area-Reference_Guide-JCR_configuration-conf-path" /> + <area coords="15" id="area-Reference_Guide-JCR_configuration-working-conf" /> </areaspec> @@ -46,13 +46,13 @@ </init-params> </component></programlisting> <calloutlist> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-JCR_configuration-conf-path"> + <callout arearefs="area-Reference_Guide-JCR_configuration-conf-path"> <para> A path to a RepositoryService JCR Configuration. </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-JCR_configuration-working-conf"> + <callout arearefs="area-Reference_Guide-JCR_configuration-working-conf"> <para> JCR configuration persister configuration. If no <parameter>working-conf</parameter> is found, the persister will be disabled. </para> @@ -63,7 +63,7 @@ </programlistingco> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Portal_configuration-JCR_Configuration"> + <section id="sect-Reference_Guide-Portal_configuration-JCR_Configuration"> <title>JCR Configuration</title> <para> The JCR Service can use multiple <emphasis>Repositories</emphasis> and each repository can have multiple <emphasis>Workspaces</emphasis>. @@ -187,115 +187,115 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Portal_configuration-Repository_service_configuration_JCR_repositories_configuration"> + <section id="sect-Reference_Guide-Portal_configuration-Repository_service_configuration_JCR_repositories_configuration"> <title>Repository service configuration (JCR repositories configuration)</title> <programlistingco> <areaspec> -  <area coords="1 60" id="area-Reference_Guide_eXo_JCR_1.14-JCR_configuration-Example_of_the_portal_system_workspace-default-repository" /> -  <area coords="2 60" id="area-Reference_Guide_eXo_JCR_1.14-JCR_configuration-Example_of_the_portal_system_workspace-repositories" /> -  <area coords="3 125" id="area-Reference_Guide_eXo_JCR_1.14-JCR_configuration-Example_of_the_portal_system_workspace-name" /> -  <area coords="3 125" id="area-Reference_Guide_eXo_JCR_1.14-JCR_configuration-Example_of_the_portal_system_workspace-default-workspace" /> -  <area coords="3 125" id="area-Reference_Guide_eXo_JCR_1.14-JCR_configuration-Example_of_the_portal_system_workspace-system-workspace" /> -  <area coords="4 60" id="area-Reference_Guide_eXo_JCR_1.14-JCR_configuration-Example_of_the_portal_system_workspace-security-domain" /> -  <area coords="5 60" id="area-Reference_Guide_eXo_JCR_1.14-JCR_configuration-Example_of_the_portal_system_workspace-access-control" /> -  <area coords="6 165" id="area-Reference_Guide_eXo_JCR_1.14-JCR_configuration-Example_of_the_portal_system_workspace-authentication-policy" /> -  <area coords="9 60" id="area-Reference_Guide_eXo_JCR_1.14-JCR_configuration-Example_of_the_portal_system_workspace-workspaces" /> -  <area coords="13 60" id="area-Reference_Guide_eXo_JCR_1.14-JCR_configuration-Example_of_the_portal_system_workspace-workspace-name" /> -  <area coords="14 165" id="area-Reference_Guide_eXo_JCR_1.14-JCR_configuration-Example_of_the_portal_system_workspace-container" /> -  <area coords="34 165" id="area-Reference_Guide_eXo_JCR_1.14-JCR_configuration-Example_of_the_portal_system_workspace-service_initializer" /> -  <area coords="40 165" id="area-Reference_Guide_eXo_JCR_1.14-JCR_configuration-Example_of_the_portal_system_workspace-service_cache" /> -  <area coords="48 165" id="area-Reference_Guide_eXo_JCR_1.14-JCR_configuration-Example_of_the_portal_system_workspace-service_query-handler" /> -  <area coords="61 60" id="area-Reference_Guide_eXo_JCR_1.14-JCR_configuration-Example_of_the_portal_system_workspace-service_lock-manager-timeout" /> +  <area coords="1 60" id="area-Reference_Guide-JCR_configuration-Example_of_the_portal_system_workspace-default-repository" /> +  <area coords="2 60" id="area-Reference_Guide-JCR_configuration-Example_of_the_portal_system_workspace-repositories" /> +  <area coords="3 125" id="area-Reference_Guide-JCR_configuration-Example_of_the_portal_system_workspace-name" /> +  <area coords="3 125" id="area-Reference_Guide-JCR_configuration-Example_of_the_portal_system_workspace-default-workspace" /> +  <area coords="3 125" id="area-Reference_Guide-JCR_configuration-Example_of_the_portal_system_workspace-system-workspace" /> +  <area coords="4 60" id="area-Reference_Guide-JCR_configuration-Example_of_the_portal_system_workspace-security-domain" /> +  <area coords="5 60" id="area-Reference_Guide-JCR_configuration-Example_of_the_portal_system_workspace-access-control" /> +  <area coords="6 165" id="area-Reference_Guide-JCR_configuration-Example_of_the_portal_system_workspace-authentication-policy" /> +  <area coords="9 60" id="area-Reference_Guide-JCR_configuration-Example_of_the_portal_system_workspace-workspaces" /> +  <area coords="13 60" id="area-Reference_Guide-JCR_configuration-Example_of_the_portal_system_workspace-workspace-name" /> +  <area coords="14 165" id="area-Reference_Guide-JCR_configuration-Example_of_the_portal_system_workspace-container" /> +  <area coords="34 165" id="area-Reference_Guide-JCR_configuration-Example_of_the_portal_system_workspace-service_initializer" /> +  <area coords="40 165" id="area-Reference_Guide-JCR_configuration-Example_of_the_portal_system_workspace-service_cache" /> +  <area coords="48 165" id="area-Reference_Guide-JCR_configuration-Example_of_the_portal_system_workspace-service_query-handler" /> +  <area coords="61 60" id="area-Reference_Guide-JCR_configuration-Example_of_the_portal_system_workspace-service_lock-manager-timeout" /> </areaspec> <programlisting language="XML" role="XML"><xi:include href="../../../../extras/Advanced_Development_JCR_Configuration/orig.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> <calloutlist> -  <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-JCR_configuration-Example_of_the_portal_system_workspace-default-repository"> +  <callout arearefs="area-Reference_Guide-JCR_configuration-Example_of_the_portal_system_workspace-default-repository"> <para> <emphasis>default-repository</emphasis>: The name of a default repository (one returned by <parameter> RepositoryService.getRepository() </parameter> ). </para> </callout> -  <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-JCR_configuration-Example_of_the_portal_system_workspace-repositories"> +  <callout arearefs="area-Reference_Guide-JCR_configuration-Example_of_the_portal_system_workspace-repositories"> <para> <emphasis>repositories</emphasis>: The list of repositories. </para> </callout> -  <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-JCR_configuration-Example_of_the_portal_system_workspace-name"> +  <callout arearefs="area-Reference_Guide-JCR_configuration-Example_of_the_portal_system_workspace-name"> <para> <emphasis>name</emphasis>: The name of a repository. </para> </callout> -  <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-JCR_configuration-Example_of_the_portal_system_workspace-default-workspace"> +  <callout arearefs="area-Reference_Guide-JCR_configuration-Example_of_the_portal_system_workspace-default-workspace"> <para> <emphasis>default-workspace</emphasis>: The name of a workspace obtained using Session's login() or login(Credentials) methods (ones without an explicit workspace name). </para> </callout> -  <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-JCR_configuration-Example_of_the_portal_system_workspace-system-workspace"> +  <callout arearefs="area-Reference_Guide-JCR_configuration-Example_of_the_portal_system_workspace-system-workspace"> <para> <emphasis>system-workspace</emphasis>: The name of workspace where <emphasis>/jcr:system</emphasis> node is placed. </para> </callout> -  <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-JCR_configuration-Example_of_the_portal_system_workspace-security-domain"> +  <callout arearefs="area-Reference_Guide-JCR_configuration-Example_of_the_portal_system_workspace-security-domain"> <para> <emphasis>security-domain</emphasis>: The name of a security domain for JAAS authentication. </para> </callout> -  <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-JCR_configuration-Example_of_the_portal_system_workspace-access-control"> +  <callout arearefs="area-Reference_Guide-JCR_configuration-Example_of_the_portal_system_workspace-access-control"> <para> <emphasis>access-control</emphasis>: The name of an access control policy. There can be 3 types: optional - ACL is created on-demand(default), disable - no access control, mandatory - an ACL is created for each added node(not supported yet). </para> </callout> -  <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-JCR_configuration-Example_of_the_portal_system_workspace-authentication-policy"> +  <callout arearefs="area-Reference_Guide-JCR_configuration-Example_of_the_portal_system_workspace-authentication-policy"> <para> <emphasis>authentication-policy</emphasis>: The name of an authentication policy class. </para> </callout> -  <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-JCR_configuration-Example_of_the_portal_system_workspace-workspaces"> +  <callout arearefs="area-Reference_Guide-JCR_configuration-Example_of_the_portal_system_workspace-workspaces"> <para> <emphasis>workspaces</emphasis>: The list of workspaces. </para> </callout> -  <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-JCR_configuration-Example_of_the_portal_system_workspace-workspace-name"> +  <callout arearefs="area-Reference_Guide-JCR_configuration-Example_of_the_portal_system_workspace-workspace-name"> <para> The name of the workspace. </para> </callout> -  <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-JCR_configuration-Example_of_the_portal_system_workspace-container"> +  <callout arearefs="area-Reference_Guide-JCR_configuration-Example_of_the_portal_system_workspace-container"> <para> Workspace data container (physical storage) configuration. </para> </callout> -  <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-JCR_configuration-Example_of_the_portal_system_workspace-service_initializer"> +  <callout arearefs="area-Reference_Guide-JCR_configuration-Example_of_the_portal_system_workspace-service_initializer"> <para> Workspace initializer configuration. </para> </callout> -  <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-JCR_configuration-Example_of_the_portal_system_workspace-service_cache"> +  <callout arearefs="area-Reference_Guide-JCR_configuration-Example_of_the_portal_system_workspace-service_cache"> <para> Workspace storage cache configuration. </para> </callout> -  <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-JCR_configuration-Example_of_the_portal_system_workspace-service_query-handler"> +  <callout arearefs="area-Reference_Guide-JCR_configuration-Example_of_the_portal_system_workspace-service_query-handler"> <para> Query handler configuration. </para> </callout> -  <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-JCR_configuration-Example_of_the_portal_system_workspace-service_lock-manager-timeout"> +  <callout arearefs="area-Reference_Guide-JCR_configuration-Example_of_the_portal_system_workspace-service_lock-manager-timeout"> <para> The amount of time before the unused global lock is removed. </para> @@ -319,7 +319,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Portal_configuration-Workspace_configuration"> + <section id="sect-Reference_Guide-Portal_configuration-Workspace_configuration"> <title>Workspace configuration:</title> <para> <emphasis>name</emphasis>: The name of a workspace @@ -345,7 +345,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Portal_configuration-Workspace_data_container_configuration"> + <section id="sect-Reference_Guide-Portal_configuration-Workspace_data_container_configuration"> <title>Workspace data container configuration:</title> <para> <emphasis>class:</emphasis> A workspace data container class name. @@ -353,7 +353,7 @@ <para> <emphasis>properties</emphasis>: The list of properties (name-value pairs) for the concrete Workspace data container. </para> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Workspace_data_container_configuration-Parameter_Descriptions"> + <table id="tabl-Reference_Guide-Workspace_data_container_configuration-Parameter_Descriptions"> <title>Parameter Descriptions</title> <tgroup cols="2"> <thead> @@ -423,7 +423,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Portal_configuration-Value_Storage_plugin_configuration_for_data_container"> + <section id="sect-Reference_Guide-Portal_configuration-Value_Storage_plugin_configuration_for_data_container"> <title>Value Storage plugin configuration (for data container):</title> <note> <para> @@ -446,7 +446,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Portal_configuration-Initializer_configuration_optional"> + <section id="sect-Reference_Guide-Portal_configuration-Initializer_configuration_optional"> <title>Initializer configuration (optional):</title> <para> <emphasis>class</emphasis>: Initializer implementation class. @@ -466,7 +466,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Portal_configuration-Cache_configuration"> + <section id="sect-Reference_Guide-Portal_configuration-Cache_configuration"> <title>Cache configuration:</title> <para> <emphasis>enabled</emphasis>: If workspace cache is enabled or not. @@ -522,7 +522,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Portal_configuration-Query_Handler_configuration"> + <section id="sect-Reference_Guide-Portal_configuration-Query_Handler_configuration"> <title>Query Handler configuration:</title> <para> <emphasis>class</emphasis>: A Query Handler class name. @@ -536,7 +536,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Portal_configuration-Lock_Manager_configuration"> + <section id="sect-Reference_Guide-Portal_configuration-Lock_Manager_configuration"> <title>Lock Manager configuration:</title> <para> <emphasis>time-out</emphasis>: Time after which the unused global lock will be removed. @@ -591,7 +591,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Portal_configuration-Help_application_to_prohibit_the_use_of_closed_sessions"> + <section id="sect-Reference_Guide-Portal_configuration-Help_application_to_prohibit_the_use_of_closed_sessions"> <title>Help application to prohibit the use of closed sessions</title> <para> Products that use eXo JCR, sometimes misuse it since they continue to use a session that has been closed through a method call on a node, a property or even the session itself. To prevent bad practices we propose three modes which are the following: Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/external-value-storages.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/external-value-storages.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/external-value-storages.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,17 +1,17 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-External_Value_Storages"> +<chapter id="chap-Reference_Guide-External_Value_Storages"> <title>External Value Storages</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-External_Value_Storages-Introduction"> + <section id="sect-Reference_Guide-External_Value_Storages-Introduction"> <title>Introduction</title> <para> JCR values are stored in the Workspace Data container by default. The eXo JCR offers an additional option of storing JCR values separately from the Workspace Data container which can help keep Binary Large Objects (BLOBs) separate. </para>  <para> Tree-based storage is recommended in most cases. </para> @@ -21,7 +21,7 @@ </para> --> </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-External_Value_Storages-Tree_File_Value_Storage"> + <section id="sect-Reference_Guide-External_Value_Storages-Tree_File_Value_Storage"> <title>Tree File Value Storage</title> <para> Tree File Value Storage holds values in tree-like file system files. <property>Path</property> property points to the root directory to store the files. @@ -34,20 +34,20 @@ </para> <programlistingco> <areaspec> - <area coords="1" id="area-Reference_Guide_eXo_JCR_1.14-External_Value_Storages-Tree_File_Value_Storage-id" /> - <area coords="3" id="area-Reference_Guide_eXo_JCR_1.14-External_Value_Storages-Tree_File_Value_Storage-path" /> + <area coords="1" id="area-Reference_Guide-External_Value_Storages-Tree_File_Value_Storage-id" /> + <area coords="3" id="area-Reference_Guide-External_Value_Storages-Tree_File_Value_Storage-path" /> </areaspec> <programlisting language="XML" role="XML"><xi:include href="../../../../extras/Advanced_Development_JCR_external-value-storages/default25.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> <calloutlist> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-External_Value_Storages-Tree_File_Value_Storage-id"> + <callout arearefs="area-Reference_Guide-External_Value_Storages-Tree_File_Value_Storage-id"> <para> The <emphasis role="bold">id</emphasis> is the value storage unique identifier, used for linking with properties stored in a workspace container </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-External_Value_Storages-Tree_File_Value_Storage-path"> + <callout arearefs="area-Reference_Guide-External_Value_Storages-Tree_File_Value_Storage-path"> <para> <emphasis role="bold">path</emphasis> is a location where value files will be stored. </para> @@ -103,7 +103,7 @@ <filter property-type="Binary" min-value-size="1M"/> </filters> </programlisting> -</section> --> <section id="sect-Reference_Guide_eXo_JCR_1.14-External_Value_Storages-Content_Addressable_Value_storage_CAS_support"> +</section> --> <section id="sect-Reference_Guide-External_Value_Storages-Content_Addressable_Value_storage_CAS_support"> <title>Content Addressable Value storage (CAS) support</title> <para> eXo JCR supports the <phrase>Content-addressable storage</phrase> feature for <phrase>values</phrase> storing. @@ -146,7 +146,7 @@ </para> <programlisting language="XML" role="XML"><xi:include href="../../../../extras/Advanced_Development_JCR_external-value-storages/default28.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Content_Addressable_Value_storage_CAS_support-CAS_Properties"> + <variablelist id="vari-Reference_Guide-Content_Addressable_Value_storage_CAS_support-CAS_Properties"> <title>CAS Properties</title> <varlistentry> <term>digest-algo</term> @@ -196,7 +196,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-External_Value_Storages-Disabling_value_storage"> + <section id="sect-Reference_Guide-External_Value_Storages-Disabling_value_storage"> <title>Disabling value storage</title> <para> The JCR allows you to disable value storage by adding the following property into its configuration. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/jdbc-data-container-config.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/jdbc-data-container-config.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/jdbc-data-container-config.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-JDBC_Data_Container_Config"> +<chapter id="chap-Reference_Guide-JDBC_Data_Container_Config"> <title>JDBC Data Container Config</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JDBC_Data_Container_Config-Introduction"> + <section id="sect-Reference_Guide-JDBC_Data_Container_Config-Introduction"> <title>Introduction</title> <para> eXo JCR persistent data container can work in two configuration modes: @@ -176,7 +176,7 @@ <para> The following tables show the correspondence between the scripts and databases: </para> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Introduction-Single_database"> + <table id="tabl-Reference_Guide-Introduction-Single_database"> <title>Single-database</title> <tgroup cols="2"> <thead> @@ -270,7 +270,7 @@ </tgroup> </table> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Introduction-Multi_database"> + <table id="tabl-Reference_Guide-Introduction-Multi_database"> <title>Multi-database</title> <tgroup cols="2"> <thead> @@ -370,7 +370,7 @@ <para> There are preconfigured configuration files for HSQLDB. Look for these files in /conf/portal and /conf/standalone folders of the jar-file <package>exo.jcr.component.core-XXX.XXX.jar</package> or source-distribution of eXo JCR implementation. </para> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Introduction-Example_Parameter"> + <example id="exam-Reference_Guide-Introduction-Example_Parameter"> <title>Example Parameter</title> <programlisting><code>jdbc:mysql://exoua.dnsalias.net/portal?characterEncoding=utf8</code></programlisting> @@ -380,12 +380,12 @@ The configuration files are located in service jars <filename>/conf/portal/configuration.xml</filename> (eXo services including JCR Repository Service) and <filename>exo-jcr-config.xml</filename> (repositories configuration) by default. In JBoss Enterprise Portal Platform, the JCR is configured in portal web application <filename>portal/WEB-INF/conf/jcr/jcr-configuration.xml</filename> (JCR Repository Service and related services) and <filename>repository-configuration.xml</filename> (repositories configuration). </para> <para> - Read more about <xref linkend="chap-Reference_Guide_eXo_JCR_1.14-JCR_configuration" />. + Read more about <xref linkend="chap-Reference_Guide-JCR_configuration" />. </para> </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JDBC_Data_Container_Config-Multi_database_Configuration"> + <section id="sect-Reference_Guide-JDBC_Data_Container_Config-Multi_database_Configuration"> <title>Multi-database Configuration</title> <para> You need to configure each workspace in a repository as part of multi-database configuration. Databases may reside on remote servers as required. @@ -524,12 +524,12 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JDBC_Data_Container_Config-Single_database_Configuration"> + <section id="sect-Reference_Guide-JDBC_Data_Container_Config-Single_database_Configuration"> <title>Single-database Configuration</title> <para> Configuring a single-database data container is easier than configuring a multi-database data container as only one naming resource must be configured. </para> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Single_database_Configuration-jdbcjcr_Data_Container"> + <example id="exam-Reference_Guide-Single_database_Configuration-jdbcjcr_Data_Container"> <title><parameter>jdbcjcr</parameter> Data Container</title> <programlisting language="XML" role="XML"> @@ -542,7 +542,7 @@ <para> For example (two workspaces <parameter>ws</parameter> - <literal>jdbcjcr</literal>, <parameter>ws1</parameter> - <literal>jdbcjcr</literal>): </para> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Single_database_Configuration-Example"> + <example id="exam-Reference_Guide-Single_database_Configuration-Example"> <title>Example</title> <programlisting language="XML" role="XML"> @@ -552,7 +552,7 @@ <para> This configures two persistent workspaces in one database (PostgreSQL). </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Single_database_Configuration-Configuration_without_DataSource"> + <section id="sect-Reference_Guide-Single_database_Configuration-Configuration_without_DataSource"> <title>Configuration without DataSource</title> <para> It is possible to configure the repository without binding <literal>javax.sql.DataSource</literal> in the JNDI service if you have a dedicated JDBC driver implementation with special features like XA transactions, statements/connections pooling etc: @@ -594,7 +594,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Single_database_Configuration-Dynamic_Workspace_Creation"> + <section id="sect-Reference_Guide-Single_database_Configuration-Dynamic_Workspace_Creation"> <title>Dynamic Workspace Creation</title> <para> Workspaces can be added dynamically during runtime. @@ -625,7 +625,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JDBC_Data_Container_Config-Simple_and_Complex_queries"> + <section id="sect-Reference_Guide-JDBC_Data_Container_Config-Simple_and_Complex_queries"> <title>Simple and Complex queries</title> <para> eXo JCR provides two ways to interact with the database; @@ -678,7 +678,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JDBC_Data_Container_Config-Force_Query_Hints"> + <section id="sect-Reference_Guide-JDBC_Data_Container_Config-Force_Query_Hints"> <title>Force Query Hints</title> <para> Some databases, such as Oracle and MySQL, support hints to increase query performance. The eXo JCR has separate Complex Query implementations for the Orcale database dialect, which uses query hints to increase performance for few important queries. @@ -699,7 +699,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JDBC_Data_Container_Config-Notes_for_Microsoft_Windows_users"> + <section id="sect-Reference_Guide-JDBC_Data_Container_Config-Notes_for_Microsoft_Windows_users"> <title>Notes for Microsoft Windows users</title> <para> The current configuration of eXo JCR uses <ulink url="http://commons.apache.org/dbcp/">Apache DBCP</ulink> connection pool (<literal>org.apache.commons.dbcp.BasicDataSourceFactory</literal>). @@ -730,7 +730,7 @@ </procedure> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Notes_for_Microsoft_Windows_users-Sample_Registry_File"> + <example id="exam-Reference_Guide-Notes_for_Microsoft_Windows_users-Sample_Registry_File"> <title>Sample Registry File</title> <programlisting>Windows Registry Editor Version 5.00 Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/multilanguage-support.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/multilanguage-support.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/multilanguage-support.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Multi_language_Support_the_JCR_RDB"> +<chapter id="chap-Reference_Guide-Multi_language_Support_the_JCR_RDB"> <title>Multi-language Support the JCR RDB</title> <para> Whenever a relational database is used to store multilingual text data in the eXo Java Content Repository the configuration must be adapted to support UTF-8 encoding. Dialect is automatically detected for certified database. You can still enforce it in case of failure, see below. @@ -14,25 +14,25 @@ <itemizedlist> <listitem> <para> - <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Multi_language_Support_the_JCR_RDB-Oracle" /> + <xref linkend="sect-Reference_Guide-Multi_language_Support_the_JCR_RDB-Oracle" /> </para> </listitem> <listitem> <para> - <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Multi_language_Support_the_JCR_RDB-DB2" /> + <xref linkend="sect-Reference_Guide-Multi_language_Support_the_JCR_RDB-DB2" /> </para> </listitem> <listitem> <para> - <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Multi_language_Support_the_JCR_RDB-MySQL" /> + <xref linkend="sect-Reference_Guide-Multi_language_Support_the_JCR_RDB-MySQL" /> </para> </listitem> <listitem> <para> - <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Multi_language_Support_the_JCR_RDB-PostgreSQL" /> + <xref linkend="sect-Reference_Guide-Multi_language_Support_the_JCR_RDB-PostgreSQL" /> </para> </listitem> @@ -56,7 +56,7 @@ </itemizedlist> </note> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Multi_language_Support_the_JCR_RDB-Oracle"> + <section id="sect-Reference_Guide-Multi_language_Support_the_JCR_RDB-Oracle"> <title>Oracle</title> <para> In order to run multilanguage JCR on an Oracle backend Unicode encoding for characters set should be applied to the database. Other Oracle globalization parameters do not have any effect. The property to modify is <literal>NLS_CHARACTERSET</literal>. @@ -100,7 +100,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Multi_language_Support_the_JCR_RDB-DB2"> + <section id="sect-Reference_Guide-Multi_language_Support_the_JCR_RDB-DB2"> <title>DB2</title> <para> DB2 Universal Database (DB2 UDB) supports <ulink url="http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp?topic=/com.i...">UTF-8 and UTF-16/UCS-2</ulink>. When a Unicode database is created, <parameter>CHAR</parameter>, <parameter>VARCHAR</parameter> and <parameter>LONG VARCHAR</parameter> data are stored in UTF-8 form. @@ -125,7 +125,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Multi_language_Support_the_JCR_RDB-MySQL"> + <section id="sect-Reference_Guide-Multi_language_Support_the_JCR_RDB-MySQL"> <title>MySQL</title> <para> Using JCR with a MySQL-back end requires a special dialect <ulink url="http://jira.exoplatform.org/browse/JCR-375">MySQL-UTF8</ulink> to be used for internationalization support. @@ -147,7 +147,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Multi_language_Support_the_JCR_RDB-PostgreSQL"> + <section id="sect-Reference_Guide-Multi_language_Support_the_JCR_RDB-PostgreSQL"> <title>PostgreSQL</title> <para> Multilingual support can be enabled with a PostgreSQL-back end in <ulink url="http://www.postgresql.org/docs/8.3/interactive/charset.html">different ways</ulink>: Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/rest-services-on-groovy.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/rest-services-on-groovy.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/rest-services-on-groovy.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-REST_Services_on_Groovy"> +<chapter id="chap-Reference_Guide-REST_Services_on_Groovy"> <title>REST Services on Groovy</title> <para> Since version 1.9, the JCR Service supports REST services creation from <ulink url="http://groovy.codehaus.org">Groovy script</ulink>. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/search-configuration.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/search-configuration.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/search-configuration.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,15 +1,15 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Search_Configuration"> +<chapter id="chap-Reference_Guide-Search_Configuration"> <title>Search Configuration</title> <para> The search function in JCR can be configured to perform in specific ways. This section will discuss configuring the search function to improve search performance and results. </para> <para> - Below is an example of the configuration file that governs search behaviors. Refer to <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Search_Configuration-Global_Search_Index" /> for how searching operates in JCR and information about customized searches. + Below is an example of the configuration file that governs search behaviors. Refer to <xref linkend="sect-Reference_Guide-Search_Configuration-Global_Search_Index" /> for how searching operates in JCR and information about customized searches. </para> <para> The JCR index configuration file is located at <filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/02portal.war/WEB-INF/conf/jcr/repository-configuration.xml</filename>. @@ -22,7 +22,7 @@ <para> The table below outlines the Configuration Parameters available, their default setting, which version of eXo JCR they were implemented in and other useful information: </para> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Search_Configuration-Configuration_parameters"> + <table id="tabl-Reference_Guide-Search_Configuration-Configuration_parameters">  <title>Configuration parameters</title> <tgroup cols="4"> <colspec colname="1" colwidth="90pt"></colspec> @@ -656,34 +656,34 @@ </tgroup> </table> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Search_Configuration-Global_Search_Index"> + <section id="sect-Reference_Guide-Search_Configuration-Global_Search_Index"> <title>Global Search Index</title> <para> By default eXo JCR uses the Lucene standard Analyzer to index contents. This analyzer uses some standard filters in the method that analyzes the content: </para> <programlistingco> <areaspec> - <area coords="4" id="area-Reference_Guide_eXo_JCR_1.14-Search_Configuration-Global_Search_Index-StandardFilter" /> - <area coords="5" id="area-Reference_Guide_eXo_JCR_1.14-Search_Configuration-Global_Search_Index-LowerCaseFilter" /> - <area coords="6" id="area-Reference_Guide_eXo_JCR_1.14-Search_Configuration-Global_Search_Index-StopFilter" /> + <area coords="4" id="area-Reference_Guide-Search_Configuration-Global_Search_Index-StandardFilter" /> + <area coords="5" id="area-Reference_Guide-Search_Configuration-Global_Search_Index-LowerCaseFilter" /> + <area coords="6" id="area-Reference_Guide-Search_Configuration-Global_Search_Index-StopFilter" /> </areaspec> <programlisting language="Java" role="Java"><xi:include href="../../../../extras/Advanced_Development_JCR_search-configuration/default62.java" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> <calloutlist> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Search_Configuration-Global_Search_Index-StandardFilter"> + <callout arearefs="area-Reference_Guide-Search_Configuration-Global_Search_Index-StandardFilter"> <para> The first filter (StandardFilter) removes possessive apostrophes (<emphasis role="bold">'s</emphasis>) from the end of words and removes periods (<emphasis role="bold">.</emphasis>) from acronyms. </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Search_Configuration-Global_Search_Index-LowerCaseFilter"> + <callout arearefs="area-Reference_Guide-Search_Configuration-Global_Search_Index-LowerCaseFilter"> <para> The second filter (LowerCaseFilter) normalizes token text to lower case. </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Search_Configuration-Global_Search_Index-StopFilter"> + <callout arearefs="area-Reference_Guide-Search_Configuration-Global_Search_Index-StopFilter"> <para> The last filter (StopFilter) removes stop words from a token stream. The stop set is defined in the analyzer. </para> @@ -706,7 +706,7 @@ <para> A customized QueryHandler can also be easily created. </para> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Global_Search_Index-Customized_Search_Indexes_and_Analyzers"> + <formalpara id="form-Reference_Guide-Global_Search_Index-Customized_Search_Indexes_and_Analyzers"> <title>Customized Search Indexes and Analyzers</title> <para> By default Exo JCR uses the Lucene standard Analyzer to index contents. This analyzer uses some standard filters in the method that analyzes the content: @@ -752,7 +752,7 @@ <para> In order to use a different filter, a new analyzer must be created, as well as new search index to use the analyzer. These are packaged into a jar file, which is then deployed with the application. </para> - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Global_Search_Index-Create_a_new_filter_analyzer_and_search_index"> + <procedure id="proc-Reference_Guide-Global_Search_Index-Create_a_new_filter_analyzer_and_search_index"> <title>Create a new filter, analyzer and search index</title> <step> <para> @@ -829,7 +829,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Search_Configuration-IndexingConfiguration"> + <section id="sect-Reference_Guide-Search_Configuration-IndexingConfiguration"> <title>IndexingConfiguration</title> <para> From version 1.9, the default search index implementation in JCR allows user control over which properties of a node are indexed. Different analyzers can also be set for different nodes. @@ -844,7 +844,7 @@ <programlisting language="XML" role="XML"><param name="indexing-configuration-path" value="/indexing_configuration.xml"/> </programlisting> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-IndexingConfiguration-Node_Scope_Limit"> + <formalpara id="form-Reference_Guide-IndexingConfiguration-Node_Scope_Limit"> <title>Node Scope Limit</title> <para> The node scope can be limited so that only certain properties of a node type are indexed. This can optimize the index size. @@ -863,7 +863,7 @@ </para> </note> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-IndexingConfiguration-Indexing_Boost_Value"> + <formalpara id="form-Reference_Guide-IndexingConfiguration-Indexing_Boost_Value"> <title>Indexing Boost Value</title> <para> It is also possible to configure a <phrase>boost value</phrase> for the nodes that match the index rule. The default boost value is 1.0. Higher boost values (a reasonable range is 1.0 - 5.0) will yield a higher score value and appear as more relevant. @@ -877,7 +877,7 @@ </para> <programlisting language="XML" role="XML"><xi:include href="../../../../extras/Advanced_Development_JCR_search-configuration/default73.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-IndexingConfiguration-Conditional_Index_Rules"> + <formalpara id="form-Reference_Guide-IndexingConfiguration-Conditional_Index_Rules"> <title>Conditional Index Rules</title> <para> You may also add a <phrase>condition</phrase> to the index rule and have multiple rules with the same nodeType. The first index rule that matches will apply and all remaining ones are ignored: @@ -899,7 +899,7 @@ </para> <programlisting language="XML" role="XML"><xi:include href="../../../../extras/Advanced_Development_JCR_search-configuration/default76.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-IndexingConfiguration-Exclusion_from_the_Node_Scope_Index"> + <formalpara id="form-Reference_Guide-IndexingConfiguration-Exclusion_from_the_Node_Scope_Index"> <title>Exclusion from the Node Scope Index</title> <para> All configured properties are full-text indexed by default (if they are of type STRING and included in the node scope index). @@ -914,7 +914,7 @@ </para> <programlisting language="XML" role="XML"><xi:include href="../../../../extras/Advanced_Development_JCR_search-configuration/default77.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-IndexingConfiguration-Index_Aggregates"> + <formalpara id="form-Reference_Guide-IndexingConfiguration-Index_Aggregates"> <title>Index Aggregates</title> <para> Sometimes it is useful to include the contents of descendant nodes into a single node to more easily search on content that is scattered across multiple nodes. @@ -944,7 +944,7 @@ </para> <programlisting language="XML" role="XML"><xi:include href="../../../../extras/Advanced_Development_JCR_search-configuration/default81.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-IndexingConfiguration-Property_Level_Analyzers"> + <formalpara id="form-Reference_Guide-IndexingConfiguration-Property_Level_Analyzers"> <title>Property-Level Analyzers</title> <para> How a property has to be analyzed can be defined in the following configuration section. If there is an analyzer configuration for a property, this analyzer is used for indexing and searching of this property. For example: @@ -962,7 +962,7 @@ <para> Using different analyzers for different languages can be particularly useful. </para> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-IndexingConfiguration-Characteristics_of_Node_Scope_Searches"> + <formalpara id="form-Reference_Guide-IndexingConfiguration-Characteristics_of_Node_Scope_Searches"> <title>Characteristics of Node Scope Searches</title> <para> Unexpected behavior may be encountered when using analyzers to search within a <emphasis>property</emphasis> compared to searching within a <emphasis>node scope</emphasis>. This is because the node scope always uses the global analyzer. @@ -1031,7 +1031,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Search_Configuration-Advanced_features"> + <section id="sect-Reference_Guide-Search_Configuration-Advanced_features"> <title>Advanced features</title> <para> eXo JCR supports some advanced features, which are not specified in JSR 170: @@ -1039,25 +1039,25 @@ <itemizedlist> <listitem> <para> - Get a text excerpt with <emphasis role="bold">highlighted words</emphasis> that matches the query: <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Highlighting-DefaultXMLExcerpt" />>. + Get a text excerpt with <emphasis role="bold">highlighted words</emphasis> that matches the query: <xref linkend="sect-Reference_Guide-Highlighting-DefaultXMLExcerpt" />>. </para> </listitem> <listitem> <para> - Search a term and its <emphasis role="bold">synonyms</emphasis>: <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Searching_Repository_Content-SynonymSearch" />. + Search a term and its <emphasis role="bold">synonyms</emphasis>: <xref linkend="sect-Reference_Guide-Searching_Repository_Content-SynonymSearch" />. </para> </listitem> <listitem> <para> - Search <emphasis role="bold">similar</emphasis> nodes: <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Searching_Repository_Content-Similarity" />. + Search <emphasis role="bold">similar</emphasis> nodes: <xref linkend="sect-Reference_Guide-Searching_Repository_Content-Similarity" />. </para> </listitem> <listitem> <para> - Check <emphasis role="bold">spelling</emphasis> of a full text query statement: <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Searching_Repository_Content-SpellChecker" />. + Check <emphasis role="bold">spelling</emphasis> of a full text query statement: <xref linkend="sect-Reference_Guide-Searching_Repository_Content-SpellChecker" />. </para> </listitem> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/workspace-persistence-storage.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/workspace-persistence-storage.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/configuration/workspace-persistence-storage.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Workspace_Data_Container"> +<chapter id="chap-Reference_Guide-Workspace_Data_Container"> <title>Workspace Data Container</title> <para> Each Workspace of the JCR has its own persistent storage to hold that workspace's items data. The eXo JCR can be configured so that it can use one or more workspaces that are logical units of the repository content. @@ -13,14 +13,14 @@ </para> <programlistingco> <areaspec> - <area coords="3" id="area-Reference_Guide_eXo_JCR_1.14-Workspace_Data_Container-source_name" /> - <area coords="4" id="area-Reference_Guide_eXo_JCR_1.14-Workspace_Data_Container-dialect" /> - <area coords="5" id="area-Reference_Guide_eXo_JCR_1.14-Workspace_Data_Container-multidb" /> - <area coords="6" id="area-Reference_Guide_eXo_JCR_1.14-Workspace_Data_Container-maxbuffer" /> - <area coords="7" id="area-Reference_Guide_eXo_JCR_1.14-Workspace_Data_Container-swap" /> - <area coords="8" id="area-Reference_Guide_eXo_JCR_1.14-Workspace_Data_Container-lazy-node-iterator-page-size" /> - <area coords="9" id="area-Reference_Guide_eXo_JCR_1.14-Workspace_Data_Container-acl-bloomfilter-false-positive-probability" /> - <area coords="10" id="area-Reference_Guide_eXo_JCR_1.14-Workspace_Data_Container-acl-bloomfilter-elements-number" /> + <area coords="3" id="area-Reference_Guide-Workspace_Data_Container-source_name" /> + <area coords="4" id="area-Reference_Guide-Workspace_Data_Container-dialect" /> + <area coords="5" id="area-Reference_Guide-Workspace_Data_Container-multidb" /> + <area coords="6" id="area-Reference_Guide-Workspace_Data_Container-maxbuffer" /> + <area coords="7" id="area-Reference_Guide-Workspace_Data_Container-swap" /> + <area coords="8" id="area-Reference_Guide-Workspace_Data_Container-lazy-node-iterator-page-size" /> + <area coords="9" id="area-Reference_Guide-Workspace_Data_Container-acl-bloomfilter-false-positive-probability" /> + <area coords="10" id="area-Reference_Guide-Workspace_Data_Container-acl-bloomfilter-elements-number" /> </areaspec> @@ -36,49 +36,49 @@ <property name="acl-bloomfilter-elements-number" value="1000000"/> </properties></programlisting> <calloutlist> -  <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Workspace_Data_Container-source_name"> +  <callout arearefs="area-Reference_Guide-Workspace_Data_Container-source_name"> <para> <literal>source-name</literal>: The JDBC data source name which is registered in JDNI by InitialContextInitializer. This was known as <literal>sourceName</literal> in versions prior to 1.9. </para> </callout> -  <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Workspace_Data_Container-dialect"> +  <callout arearefs="area-Reference_Guide-Workspace_Data_Container-dialect"> <para> <literal>dialect</literal>: The database dialect. Must be one of the following: <literal>hsqldb</literal>, <literal>mysql</literal>, <literal>mysql-utf8</literal>, <literal>pgsql</literal>, <literal>oracle</literal>, <literal>oracle-oci</literal>, <literal>mssql</literal>, <literal>sybase</literal>, <literal>derby</literal>, <literal>db2</literal> or <literal>db2v8</literal>). </para> </callout> -  <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Workspace_Data_Container-multidb"> +  <callout arearefs="area-Reference_Guide-Workspace_Data_Container-multidb"> <para> <literal>multi-db</literal>: This parameter, if <literal>true</literal>, enables multi-database container. </para> </callout> -  <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Workspace_Data_Container-maxbuffer"> +  <callout arearefs="area-Reference_Guide-Workspace_Data_Container-maxbuffer"> <para> <literal>max-buffer-size</literal>: A threshold in bytes. If a value size is greater than this setting, then it will be spooled to a temporary file. </para> </callout> -  <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Workspace_Data_Container-swap"> +  <callout arearefs="area-Reference_Guide-Workspace_Data_Container-swap"> <para> <literal>swap-directory</literal>: A location where the value will be spooled if no value storage is configured but a <literal>max-buffer-size</literal> is exceeded. </para> </callout> -  <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Workspace_Data_Container-lazy-node-iterator-page-size"> +  <callout arearefs="area-Reference_Guide-Workspace_Data_Container-lazy-node-iterator-page-size"> <para> <emphasis role="bold">lazy-node-iterator-page-size</emphasis>: "Lazy" child nodes iterator settings. Defines size of page, the number of nodes that are retrieved from persistent storage at once. </para> </callout> -  <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Workspace_Data_Container-acl-bloomfilter-false-positive-probability"> +  <callout arearefs="area-Reference_Guide-Workspace_Data_Container-acl-bloomfilter-false-positive-probability"> <para> <emphasis role="bold">acl-bloomfilter-false-positive-probability</emphasis>: ACL Bloom-filter settings. ACL Bloom-filter desired false positive probability. Range [0..1]. Default value 0.1d. </para> </callout> -  <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Workspace_Data_Container-acl-bloomfilter-elements-number"> +  <callout arearefs="area-Reference_Guide-Workspace_Data_Container-acl-bloomfilter-elements-number"> <para> <emphasis role="bold">acl-bloomfilter-elements-number</emphasis>: ACL Bloom-filter settings. Expected number of ACL-elements in the Bloom-filter. Default value 1000000. </para> @@ -112,8 +112,8 @@ </para> <programlistingco> <areaspec> - <area coords="2" id="area-Reference_Guide_eXo_JCR_1.14-Workspace_Data_Container-value_storage" /> - <area coords="6" id="area-Reference_Guide_eXo_JCR_1.14-Workspace_Data_Container-filters" /> + <area coords="2" id="area-Reference_Guide-Workspace_Data_Container-value_storage" /> + <area coords="6" id="area-Reference_Guide-Workspace_Data_Container-filters" /> </areaspec> @@ -128,13 +128,13 @@ ......... </value-storages></programlisting> <calloutlist> -  <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Workspace_Data_Container-value_storage"> +  <callout arearefs="area-Reference_Guide-Workspace_Data_Container-value_storage"> <para> <literal>value-storage</literal> is the subclass of <literal>org.exoplatform.services.jcr.storage.value.ValueStoragePlugin</literal> and <literal>properties</literal> are optional plugin specific parameters. </para> </callout> -  <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Workspace_Data_Container-filters"> +  <callout arearefs="area-Reference_Guide-Workspace_Data_Container-filters"> <para> <literal>filters</literal>: Each file value storage can have the filter(s) for incoming values. If there are several filter criteria, they all have to match (AND-Condition). </para> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/data-container-howto.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/data-container-howto.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/data-container-howto.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,16 +1,16 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-How_to_implement_Workspace_Data_Container"> +<chapter id="chap-Reference_Guide-How_to_implement_Workspace_Data_Container"> <title>How-to implement Workspace Data Container</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-How_to_implement_Workspace_Data_Container-Short_intro_about_Workspace_data_container_implementation_practices"> + <section id="sect-Reference_Guide-How_to_implement_Workspace_Data_Container-Short_intro_about_Workspace_data_container_implementation_practices"> <title>Short intro about Workspace data container implementation practices:</title> <orderedlist> <listitem> <para> - Read a bit about the <xref linkend="chap-Reference_Guide_eXo_JCR_1.14-JCR_Workspace_Data_Container" />. + Read a bit about the <xref linkend="chap-Reference_Guide-JCR_Workspace_Data_Container" />. </para> </listitem> @@ -102,7 +102,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-How_to_implement_Workspace_Data_Container-Notes_on_Value_storage_usage"> + <section id="sect-Reference_Guide-How_to_implement_Workspace_Data_Container-Notes_on_Value_storage_usage"> <title>Notes on Value storage usage:</title> <para> Value storages are pluggable to the container but if they are used, the container implementation should respect set of interfaces and external storage usage principles. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/data-container.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/data-container.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/data-container.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-JCR_Workspace_Data_Container"> +<chapter id="chap-Reference_Guide-JCR_Workspace_Data_Container"> <title>JCR Workspace Data Container</title> <para> The JCR Workspace Data Container: @@ -29,7 +29,7 @@ </listitem> </itemizedlist> - <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-JCR_Workspace_Data_Container-Concepts"> + <variablelist id="vari-Reference_Guide-JCR_Workspace_Data_Container-Concepts"> <title>Concepts</title> <varlistentry> <term>Container and connection</term> @@ -136,12 +136,12 @@ </varlistentry> </variablelist> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Workspace_Data_Container-Requirements"> + <section id="sect-Reference_Guide-JCR_Workspace_Data_Container-Requirements"> <title>Requirements</title> <para> Connection creation and reuse should be a thread safe operation. The connection provides <abbrev>CRUD</abbrev> operations support on the storage. </para> - <itemizedlist id="item-Reference_Guide_eXo_JCR_1.14-Requirements-Read_Operations"> + <itemizedlist id="item-Reference_Guide-Requirements-Read_Operations"> <title>Read Operations</title> <listitem> <para> @@ -205,7 +205,7 @@ </listitem> </itemizedlist> - <itemizedlist id="item-Reference_Guide_eXo_JCR_1.14-Requirements-Write_Operations"> + <itemizedlist id="item-Reference_Guide-Requirements-Write_Operations"> <title>Write Operations</title> <listitem> <para> @@ -293,7 +293,7 @@ </listitem> </itemizedlist> - <itemizedlist id="item-Reference_Guide_eXo_JCR_1.14-Requirements-State_Operations"> + <itemizedlist id="item-Reference_Guide-Requirements-State_Operations"> <title>State Operations</title> <listitem> <para> @@ -306,7 +306,7 @@ </listitem> </itemizedlist> - <itemizedlist id="item-Reference_Guide_eXo_JCR_1.14-Requirements-Validation_of_write_operations"> + <itemizedlist id="item-Reference_Guide-Requirements-Validation_of_write_operations"> <title>Validation of write operations</title> <listitem> <para> @@ -315,7 +315,7 @@ </listitem> <listitem> - <itemizedlist id="item-Reference_Guide_eXo_JCR_1.14-Validation_of_write_operations-On_ADD_errors"> + <itemizedlist id="item-Reference_Guide-Validation_of_write_operations-On_ADD_errors"> <title>On ADD errors</title> <listitem> <itemizedlist> @@ -346,7 +346,7 @@ </listitem> <listitem> - <itemizedlist id="item-Reference_Guide_eXo_JCR_1.14-Validation_of_write_operations-On_DELETE_errors"> + <itemizedlist id="item-Reference_Guide-Validation_of_write_operations-On_DELETE_errors"> <title>On DELETE errors</title> <listitem> <itemizedlist> @@ -371,7 +371,7 @@ </listitem> <listitem> - <itemizedlist id="item-Reference_Guide_eXo_JCR_1.14-Validation_of_write_operations-On_UPDATE_errors"> + <itemizedlist id="item-Reference_Guide-Validation_of_write_operations-On_UPDATE_errors"> <title>On UPDATE errors</title> <listitem> <itemizedlist> @@ -397,7 +397,7 @@ </listitem> </itemizedlist> - <itemizedlist id="item-Reference_Guide_eXo_JCR_1.14-Requirements-Consistency_of_save"> + <itemizedlist id="item-Reference_Guide-Requirements-Consistency_of_save"> <title>Consistency of save</title> <listitem> <para> @@ -407,10 +407,10 @@ </listitem> </itemizedlist> - <itemizedlist id="item-Reference_Guide_eXo_JCR_1.14-Requirements-Value_storages_API"> + <itemizedlist id="item-Reference_Guide-Requirements-Value_storages_API"> <title>Value storages API</title> <listitem> - <itemizedlist id="item-Reference_Guide_eXo_JCR_1.14-Value_storages_API-Storages_provider"> + <itemizedlist id="item-Reference_Guide-Value_storages_API-Storages_provider"> <title>Storages provider:</title> <listitem> <para> @@ -450,7 +450,7 @@ </listitem> <listitem> - <itemizedlist id="item-Reference_Guide_eXo_JCR_1.14-Value_storages_API-Value_storage_plugin"> + <itemizedlist id="item-Reference_Guide-Value_storages_API-Value_storage_plugin"> <title>Value storage plugin</title> <listitem> <para> @@ -496,7 +496,7 @@ </listitem> <listitem> - <itemizedlist id="item-Reference_Guide_eXo_JCR_1.14-Value_storages_API-Value_IO_channel"> + <itemizedlist id="item-Reference_Guide-Value_storages_API-Value_IO_channel"> <title>Value I/O channel</title> <listitem> <para> @@ -542,7 +542,7 @@ </listitem> <listitem> - <itemizedlist id="item-Reference_Guide_eXo_JCR_1.14-Value_storages_API-Transaction_support_via_channel"> + <itemizedlist id="item-Reference_Guide-Value_storages_API-Transaction_support_via_channel"> <title>Transaction support via channel</title> <listitem> <para> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/db-cleaner-service.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/db-cleaner-service.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/db-cleaner-service.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-DBCleanService"> +<chapter id="chap-Reference_Guide-DBCleanService"> <title>DBCleanService</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-DBCleanService-API"> + <section id="sect-Reference_Guide-DBCleanService-API"> <title>API</title> <para> It is special service for removing data from database. @@ -19,7 +19,7 @@ <para> There are three methods of DBCleanerService: </para> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-API-API"> + <table id="tabl-Reference_Guide-API-API"> <title>API</title> <tgroup cols="2"> <tbody> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/intro.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/intro.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/intro.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-eXoJCR-Introduction"> +<chapter id="chap-Reference_Guide-eXoJCR-Introduction"> <title>Introduction</title> <warning> <title>eXo JCR usage</title> @@ -21,7 +21,7 @@ <para> The eXo JCR included with JBoss Enterprise Portal Platform &VY; is a (<ulink type="http" url="http://www.jcp.org/en/jsr/detail?id=170">JSR-170</ulink>) compliant implementation of the JCR 1.0 specification. The JCR provides versioning, textual search, access control, content event monitoring, and is used to storing text and binary data for the portal internal usage. The back-end storage of the JCR is configurable and can be a file system or a database. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Introduction-Concepts"> + <section id="sect-Reference_Guide-Introduction-Concepts"> <title>Concepts</title> <variablelist> <varlistentry> 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-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/jbosscache-configuration-templates.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-JBoss_Cache_configuration"> +<chapter id="chap-Reference_Guide-JBoss_Cache_configuration"> <title>JBoss Cache configuration</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JBoss_Cache_configuration-Indexer_lock_manager_and_data_container_configuration"> + <section id="sect-Reference_Guide-JBoss_Cache_configuration-Indexer_lock_manager_and_data_container_configuration"> <title>Indexer, lock manager and data container configuration</title> <para> Each mentioned component uses instances of the JBoss Cache product for caching in clustered environment. So every element has its own transport and has to be configured correctly. As usual, workspaces have similar configuration differing only in cluster-names (and, possibly, some other parameters). The simplest way to configure them is to define their own configuration files for each component in each workspace: @@ -35,7 +35,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JBoss_Cache_configuration-JGroups_configuration"> + <section id="sect-Reference_Guide-JBoss_Cache_configuration-JGroups_configuration"> <title>JGroups configuration</title> <para> JGroups is used by JBoss Cache for network communications and transport in a clustered environment. If the property is defined in component configuration, it will be injected into the JBoss Cache instance on start up. @@ -57,7 +57,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JBoss_Cache_configuration-Sharing_JBoss_Cache_instances"> + <section id="sect-Reference_Guide-JBoss_Cache_configuration-Sharing_JBoss_Cache_instances"> <title>Sharing JBoss Cache instances</title> <para> As a single JBoss Cache instance can be demanding on resources, and the default setup will have an instance each for the indexer, the lock manager and the data container on each workspace, an environment that uses multiple workspace may benefit from sharing a JBoss Cache instance between several instances of the same type (the lock manager instance, for example). @@ -79,19 +79,19 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JBoss_Cache_configuration-Shipped_JBoss_Cache_configuration_templates"> + <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. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Shipped_JBoss_Cache_configuration_templates-Data_container_template"> + <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>: </para> <programlistingco> <areaspec> - <area coords="7" id="area-Reference_Guide_eXo_JCR_1.14-Shipped_JBoss_Cache_configuration_templates-Data_container_template-jbosscache-cluster-name" /> + <area coords="7" id="area-Reference_Guide-Shipped_JBoss_Cache_configuration_templates-Data_container_template-jbosscache-cluster-name" /> </areaspec> @@ -117,9 +117,9 @@ </default> </eviction> </jbosscache></programlisting> - <calloutlist id="call-Reference_Guide_eXo_JCR_1.14-Data_container_template-Template_variables"> + <calloutlist id="call-Reference_Guide-Data_container_template-Template_variables"> <title>Template variables</title> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Shipped_JBoss_Cache_configuration_templates-Data_container_template-jbosscache-cluster-name"> + <callout arearefs="area-Reference_Guide-Shipped_JBoss_Cache_configuration_templates-Data_container_template-jbosscache-cluster-name"> <para> <replaceable>jbosscache-cluster-name</replaceable>. </para> @@ -133,24 +133,24 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template"> + <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>: </para> <programlistingco> <areaspec> - <area coords="6" id="area-Reference_Guide_eXo_JCR_1.14-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cluster-name" /> - <area coords="18" id="area-Reference_Guide_eXo_JCR_1.14-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cl-cache.jdbc.table.name" /> - <area coords="19" id="area-Reference_Guide_eXo_JCR_1.14-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cl-cache.jdbc.table.create" /> - <area coords="20" id="area-Reference_Guide_eXo_JCR_1.14-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cl-cache.jdbc.table.drop" /> - <area coords="21" id="area-Reference_Guide_eXo_JCR_1.14-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cl-cache.jdbc.table.primarykey" /> - <area coords="22" id="area-Reference_Guide_eXo_JCR_1.14-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cl-cache.jdbc.fqn.column" /> - <area coords="23" id="area-Reference_Guide_eXo_JCR_1.14-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cl-cache.jdbc.fqn.type" /> - <area coords="24" id="area-Reference_Guide_eXo_JCR_1.14-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cl-cache.jdbc.node.column" /> - <area coords="25" id="area-Reference_Guide_eXo_JCR_1.14-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cl-cache.jdbc.node.type" /> - <area coords="26" id="area-Reference_Guide_eXo_JCR_1.14-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cl-cache.jdbc.parent.column" /> - <area coords="27" id="area-Reference_Guide_eXo_JCR_1.14-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cl-cache.jdbc.datasource" /> + <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> @@ -185,69 +185,69 @@ </loader> </loaders> </jbosscache></programlisting> - <calloutlist id="call-Reference_Guide_eXo_JCR_1.14-Lock_manager_template-Template_variables"> + <calloutlist id="call-Reference_Guide-Lock_manager_template-Template_variables"> <title>Template variables</title> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cluster-name"> + <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_eXo_JCR_1.14-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cl-cache.jdbc.table.name"> + <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_eXo_JCR_1.14-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cl-cache.jdbc.table.create"> + <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_eXo_JCR_1.14-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cl-cache.jdbc.table.drop"> + <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_eXo_JCR_1.14-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cl-cache.jdbc.table.primarykey"> + <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_eXo_JCR_1.14-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cl-cache.jdbc.fqn.column"> + <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_eXo_JCR_1.14-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cl-cache.jdbc.fqn.type"> + <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_eXo_JCR_1.14-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cl-cache.jdbc.node.column"> + <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_eXo_JCR_1.14-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cl-cache.jdbc.node.type"> + <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_eXo_JCR_1.14-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cl-cache.jdbc.parent.column"> + <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_eXo_JCR_1.14-Shipped_JBoss_Cache_configuration_templates-Lock_manager_template-jbosscache-cl-cache.jdbc.datasource"> + <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> @@ -261,14 +261,14 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Shipped_JBoss_Cache_configuration_templates-Query_handler_indexer_template"> + <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>: </para> <programlistingco> <areaspec> - <area coords="5" id="area-Reference_Guide_eXo_JCR_1.14-Shipped_JBoss_Cache_configuration_templates-Query_handler_indexer_template-jbosscache-cluster-name" /> + <area coords="5" id="area-Reference_Guide-Shipped_JBoss_Cache_configuration_templates-Query_handler_indexer_template-jbosscache-cluster-name" /> </areaspec> @@ -290,7 +290,7 @@ </eviction> </jbosscache></programlisting> <calloutlist> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Shipped_JBoss_Cache_configuration_templates-Query_handler_indexer_template-jbosscache-cluster-name"> + <callout arearefs="area-Reference_Guide-Shipped_JBoss_Cache_configuration_templates-Query_handler_indexer_template-jbosscache-cluster-name"> <para> <replaceable>jbosscache-cluster-name</replaceable> </para> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/jbossts-transaction-service.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/jbossts-transaction-service.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/jbossts-transaction-service.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-JBossTransactionsService"> +<chapter id="chap-Reference_Guide-JBossTransactionsService"> <title>JBossTransactionsService</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JBossTransactionsService-Introduction"> + <section id="sect-Reference_Guide-JBossTransactionsService-Introduction"> <title>Introduction</title> <para> JBossTransactionsService implements eXo TransactionService and provides access to <ulink url="http://www.jboss.org/jbosstm/">JBoss Transaction Service (JBossTS)</ulink> JTA implementation via eXo container dependency. @@ -16,7 +16,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JBossTransactionsService-Configuration"> + <section id="sect-Reference_Guide-JBossTransactionsService-Configuration"> <title>Configuration</title> <para> Example configuration: Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/jca.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/jca.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/jca.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-The_JCA_Resource_Adapter"> +<chapter id="chap-Reference_Guide-The_JCA_Resource_Adapter"> <title>The <emphasis>JCA</emphasis> Resource Adapter</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-The_JCA_Resource_Adapter-Overview"> + <section id="sect-Reference_Guide-The_JCA_Resource_Adapter-Overview"> <title>Overview</title> <para> eXo JCR supports <emphasis>J2EE Connector Architecture</emphasis> 1.5, thus If you would like to delegate the JCR Session lifecycle to your application server, you can use the JCA Resource Adapter for eXo JCR if your application server supports JCA 1.5. This adapter only supports XA Transaction, in other words you cannot use it for local transactions. Since the JCR Sessions have not been designed to be shareable, the session pooling is simply not covered by the adapter. @@ -13,7 +13,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-The_JCA_Resource_Adapter-The_SessionFactory"> + <section id="sect-Reference_Guide-The_JCA_Resource_Adapter-The_SessionFactory"> <title>The <emphasis>SessionFactory</emphasis></title> <para> The equivalent of the <emphasis>javax.resource.cci.ConnectionFactory</emphasis> in JCA terminology is <emphasis>org.exoplatform.connectors.jcr.adapter.SessionFactory</emphasis> in the context of eXo JCR, the resource that you will get thanks to a JNDI lookup is of type <emphasis>SessionFactory</emphasis> and provides the following methods: @@ -61,9 +61,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-The_JCA_Resource_Adapter-Configuration"> + <section id="sect-Reference_Guide-The_JCA_Resource_Adapter-Configuration"> <title>Configuration</title> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Configuration-Configuration_Properties"> + <table id="tabl-Reference_Guide-Configuration-Configuration_Properties"> <title>Configuration Properties</title> <tgroup cols="2"> <tbody> @@ -94,7 +94,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-The_JCA_Resource_Adapter-Deployment"> + <section id="sect-Reference_Guide-The_JCA_Resource_Adapter-Deployment"> <title>Deployment</title> <para> As the JCR and its dependencies are provided when you use it with gateIn you will need to deploy only the rar file corresponding to the artifactId <emphasis>exo.jcr.connectors.jca</emphasis> and groupId <emphasis>org.exoplatform.jcr</emphasis>. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/jta.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/jta.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/jta.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Java_Transaction_API"> +<chapter id="chap-Reference_Guide-Java_Transaction_API">  <title>Java Transaction API</title> <para> eXo JCR supports the Java Transaction API (<abbrev>JTA</abbrev>) by default. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/lock-manager-config.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/lock-manager-config.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/lock-manager-config.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-LockManager"> +<chapter id="chap-Reference_Guide-LockManager"> <title>LockManager</title> <para> The LockManager stores lock objects. It can lock or release objects as required. It is also responsible for removing stale locks. @@ -19,7 +19,7 @@ </para> <programlisting language="XML" role="XML"><xi:include href="../../../extras/Advanced_Development_JCR_lock-manager-config/default47.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - <section id="sect-Reference_Guide_eXo_JCR_1.14-LockManager-CacheableLockManagerImpl"> + <section id="sect-Reference_Guide-LockManager-CacheableLockManagerImpl"> <title>CacheableLockManagerImpl</title> <para> <classname>CacheableLockManagerImpl</classname> stores lock objects in JBoss-cache (which implements JDBCCacheLoader to store locks in a database). This means its locks are replicable and can affect an entire cluster rather than just a single node. @@ -67,13 +67,13 @@ <itemizedlist> <listitem> <para> - <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-CacheableLockManagerImpl-Simple_JBoss_Cache_Configuration" /> + <xref linkend="sect-Reference_Guide-CacheableLockManagerImpl-Simple_JBoss_Cache_Configuration" /> </para> </listitem> <listitem> <para> - <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-CacheableLockManagerImpl-Template_JBoss_Cache_Configuration" /> + <xref linkend="sect-Reference_Guide-CacheableLockManagerImpl-Template_JBoss_Cache_Configuration" /> </para> </listitem> @@ -82,7 +82,7 @@ <para> Refer to <ulink url="http://community.jboss.org/wiki/JBossCacheJDBCCacheLoader">http://community.jboss.org/wiki/JBossCacheJDBCCacheLoader</ulink> for more information about JBoss Cache and JDBCCacheLoader. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-CacheableLockManagerImpl-Simple_JBoss_Cache_Configuration"> + <section id="sect-Reference_Guide-CacheableLockManagerImpl-Simple_JBoss_Cache_Configuration"> <title>Simple JBoss Cache Configuration</title> <para> One method to configure the LockManager is to put a JBoss Cache configuration file path into <classname>CacheableLockManagerImpl</classname>. @@ -101,13 +101,13 @@ </para> <programlistingco> <areaspec> - <area coords="4 90" id="area-Reference_Guide_eXo_JCR_1.14-CacheableLockManagerImpl-Simple_JBoss_Cache_Configuration-jbosscache-lock-config.xml" /> + <area coords="4 90" id="area-Reference_Guide-CacheableLockManagerImpl-Simple_JBoss_Cache_Configuration-jbosscache-lock-config.xml" /> </areaspec> <programlisting language="XML" role="XML"><xi:include href="../../../extras/Advanced_Development_JCR_lock-manager-config/default49.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> <calloutlist> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-CacheableLockManagerImpl-Simple_JBoss_Cache_Configuration-jbosscache-lock-config.xml"> + <callout arearefs="area-Reference_Guide-CacheableLockManagerImpl-Simple_JBoss_Cache_Configuration-jbosscache-lock-config.xml"> <para> The <replaceable>test-jbosscache-lock-config.xml</replaceable> is shown below. </para> @@ -123,11 +123,11 @@ </para> <programlistingco> <areaspec> - <area coords="6 90" id="area-Reference_Guide_eXo_JCR_1.14-CacheableLockManagerImpl-Simple_JBoss_Cache_Configuration-clusterName" /> - <area coords="41 50" id="area-Reference_Guide_eXo_JCR_1.14-CacheableLockManagerImpl-Simple_JBoss_Cache_Configuration-cache.jdbc.table.name" /> - <areaset coords="" id="area-Reference_Guide_eXo_JCR_1.14-CacheableLockManagerImpl-Simple_JBoss_Cache_Configuration-cache.jdbc.types"> - <area coords="48 50" id="area-Reference_Guide_eXo_JCR_1.14-CacheableLockManagerImpl-Simple_JBoss_Cache_Configuration-cache.jdbc.node.type" /> - <area coords="46 50" id="area-Reference_Guide_eXo_JCR_1.14-CacheableLockManagerImpl-Simple_JBoss_Cache_Configuration-cache.jdbc.fqn.type" /> + <area coords="6 90" id="area-Reference_Guide-CacheableLockManagerImpl-Simple_JBoss_Cache_Configuration-clusterName" /> + <area coords="41 50" id="area-Reference_Guide-CacheableLockManagerImpl-Simple_JBoss_Cache_Configuration-cache.jdbc.table.name" /> + <areaset coords="" id="area-Reference_Guide-CacheableLockManagerImpl-Simple_JBoss_Cache_Configuration-cache.jdbc.types"> + <area coords="48 50" id="area-Reference_Guide-CacheableLockManagerImpl-Simple_JBoss_Cache_Configuration-cache.jdbc.node.type" /> + <area coords="46 50" id="area-Reference_Guide-CacheableLockManagerImpl-Simple_JBoss_Cache_Configuration-cache.jdbc.fqn.type" /> </areaset> @@ -135,19 +135,19 @@ <programlisting language="XML" role="XML"><xi:include href="../../../extras/Advanced_Development_JCR_lock-manager-config/default50.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> <calloutlist> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-CacheableLockManagerImpl-Simple_JBoss_Cache_Configuration-clusterName"> + <callout arearefs="area-Reference_Guide-CacheableLockManagerImpl-Simple_JBoss_Cache_Configuration-clusterName"> <para> The cluster name at <parameter>clustering mode="replication" clusterName="JBoss-Cache-Lock-Cluster_Name"</parameter> must be unique; </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-CacheableLockManagerImpl-Simple_JBoss_Cache_Configuration-cache.jdbc.table.name"> + <callout arearefs="area-Reference_Guide-CacheableLockManagerImpl-Simple_JBoss_Cache_Configuration-cache.jdbc.table.name"> <para> The <parameter>cache.jdbc.table.name</parameter> must be unique per datasource. </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-CacheableLockManagerImpl-Simple_JBoss_Cache_Configuration-cache.jdbc.types"> + <callout arearefs="area-Reference_Guide-CacheableLockManagerImpl-Simple_JBoss_Cache_Configuration-cache.jdbc.types"> <para> The <parameter>cache.jdbc.node.type</parameter> and <parameter>cache.jdbc.fqn.type</parameter> parameters must be configured according to the database in use. </para> @@ -161,7 +161,7 @@ </programlistingco> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Simple_JBoss_Cache_Configuration-Data_Types_in_Different_Databases"> + <table id="tabl-Reference_Guide-Simple_JBoss_Cache_Configuration-Data_Types_in_Different_Databases"> <title>Data Types in Different Databases</title> <tgroup cols="3"> <thead> @@ -285,7 +285,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-CacheableLockManagerImpl-Template_JBoss_Cache_Configuration"> + <section id="sect-Reference_Guide-CacheableLockManagerImpl-Template_JBoss_Cache_Configuration"> <title>Template JBoss Cache Configuration</title> <para> Another method to configure LockManager is to use a JBoss Cache configuration template for all LockManagers. @@ -295,9 +295,9 @@ </para> <programlistingco> <areaspec> - <areaset coords="" id="area-Reference_Guide_eXo_JCR_1.14-CacheableLockManagerImpl-Template_JBoss_Cache_Configuration-cache.jdbc.templates"> - <area coords="24 50" id="area-Reference_Guide_eXo_JCR_1.14-CacheableLockManagerImpl-Template_JBoss_Cache_Configuration-cache.jdbc.table.name" /> - <area coords="35 50" id="area-Reference_Guide_eXo_JCR_1.14-CacheableLockManagerImpl-Template_JBoss_Cache_Configuration-cache.jdbc.datasource" /> + <areaset coords="" id="area-Reference_Guide-CacheableLockManagerImpl-Template_JBoss_Cache_Configuration-cache.jdbc.templates"> + <area coords="24 50" id="area-Reference_Guide-CacheableLockManagerImpl-Template_JBoss_Cache_Configuration-cache.jdbc.table.name" /> + <area coords="35 50" id="area-Reference_Guide-CacheableLockManagerImpl-Template_JBoss_Cache_Configuration-cache.jdbc.datasource" /> </areaset> @@ -305,7 +305,7 @@ <programlisting language="XML" role="XML"><xi:include href="../../../extras/Advanced_Development_JCR_lock-manager-config/you.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> <calloutlist> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-CacheableLockManagerImpl-Template_JBoss_Cache_Configuration-cache.jdbc.templates"> + <callout arearefs="area-Reference_Guide-CacheableLockManagerImpl-Template_JBoss_Cache_Configuration-cache.jdbc.templates"> <para> All the configurable parameters in this file are populated with templates which will be replaced with LockManager's configuration parameters. </para> @@ -321,10 +321,10 @@ </para> <programlistingco> <areaspec> - <area coords="5 90" id="area-Reference_Guide_eXo_JCR_1.14-CacheableLockManagerImpl-Template_JBoss_Cache_Configuration-udp-mux.xml" /> - <areaset coords="" id="area-Reference_Guide_eXo_JCR_1.14-CacheableLockManagerImpl-Template_JBoss_Cache_Configuration-jbosscache-cl-cache.jdbc.parameters"> - <area coords="12 90" id="area-Reference_Guide_eXo_JCR_1.14-CacheableLockManagerImpl-Template_JBoss_Cache_Configuration-jbosscache-cl-cache.jdbc.fqn.column" /> - <area coords="15 90" id="area-Reference_Guide_eXo_JCR_1.14-CacheableLockManagerImpl-Template_JBoss_Cache_Configuration-jbosscache-cl-cache.jdbc.node.type" /> + <area coords="5 90" id="area-Reference_Guide-CacheableLockManagerImpl-Template_JBoss_Cache_Configuration-udp-mux.xml" /> + <areaset coords="" id="area-Reference_Guide-CacheableLockManagerImpl-Template_JBoss_Cache_Configuration-jbosscache-cl-cache.jdbc.parameters"> + <area coords="12 90" id="area-Reference_Guide-CacheableLockManagerImpl-Template_JBoss_Cache_Configuration-jbosscache-cl-cache.jdbc.fqn.column" /> + <area coords="15 90" id="area-Reference_Guide-CacheableLockManagerImpl-Template_JBoss_Cache_Configuration-jbosscache-cl-cache.jdbc.node.type" /> </areaset> @@ -332,7 +332,7 @@ <programlisting language="XML" role="XML"><xi:include href="../../../extras/Advanced_Development_JCR_lock-manager-config/default51.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> <calloutlist> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-CacheableLockManagerImpl-Template_JBoss_Cache_Configuration-udp-mux.xml"> + <callout arearefs="area-Reference_Guide-CacheableLockManagerImpl-Template_JBoss_Cache_Configuration-udp-mux.xml"> <para> The <literal>jgroups-configuration</literal> has been moved to a separate configuration file (<filename>udp-mux.xml</filename>, shown below). </para> @@ -341,12 +341,12 @@ </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-CacheableLockManagerImpl-Template_JBoss_Cache_Configuration-jbosscache-cl-cache.jdbc.parameters"> + <callout arearefs="area-Reference_Guide-CacheableLockManagerImpl-Template_JBoss_Cache_Configuration-jbosscache-cl-cache.jdbc.parameters"> <para> The <parameter>jbosscache-cl-cache.jdbc.fqn.column</parameter> and <parameter>jbosscache-cl-cache.jdbc.node.type</parameter> parameters are not explicitly defined as <parameter>cache.jdbc.fqn.type</parameter> and <parameter>cache.jdbc.node.type</parameter> are defined in the JBoss Cache configuration. </para> <para> - Refer to <xref linkend="tabl-Reference_Guide_eXo_JCR_1.14-Simple_JBoss_Cache_Configuration-Data_Types_in_Different_Databases" /> for information about setting these parameters or set them as <parameter>AUTO</parameter> and the data type will by detected automatically. + Refer to <xref linkend="tabl-Reference_Guide-Simple_JBoss_Cache_Configuration-Data_Types_in_Different_Databases" /> for information about setting these parameters or set them as <parameter>AUTO</parameter> and the data type will by detected automatically. </para> </callout> @@ -363,12 +363,12 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-CacheableLockManagerImpl-Lock_migration_from_1.12.x"> + <section id="sect-Reference_Guide-CacheableLockManagerImpl-Lock_migration_from_1.12.x"> <title>Lock migration from 1.12.x</title> <para> There are three options available: </para> - <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Lock_migration_from_1.12.x-Lock_Migration_Options"> + <variablelist id="vari-Reference_Guide-Lock_migration_from_1.12.x-Lock_Migration_Options"> <title>Lock Migration Options</title> <varlistentry> <term>When new Shareable Cache feature is not going to be used and all locks should be kept after migration.</term> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/other/acl-ext.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/other/acl-ext.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/other/acl-ext.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,19 +1,19 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Access_Control_Extension"> +<chapter id="chap-Reference_Guide-Access_Control_Extension"> <title>Access Control Extension</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Access_Control_Extension-Prerequisites"> + <section id="sect-Reference_Guide-Access_Control_Extension-Prerequisites"> <title>Prerequisites</title> <para> - The Access Control Extension is an extension of eXo JCR Access Control features. Read <xref linkend="chap-Reference_Guide_eXo_JCR_1.14-Access_Control" /> as a primer to the information in this section. + The Access Control Extension is an extension of eXo JCR Access Control features. Read <xref linkend="chap-Reference_Guide-Access_Control" /> as a primer to the information in this section. </para> </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Access_Control_Extension-Overview"> + <section id="sect-Reference_Guide-Access_Control_Extension-Overview"> <title>Overview</title> <para> An extended Access Control system consists of: @@ -42,7 +42,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Access_Control_Extension-Access_Context_Action"> + <section id="sect-Reference_Guide-Access_Control_Extension-Access_Context_Action"> <title>Access Context Action</title> <para> <literal>SetAccessContextAction</literal> implements Action and may be called by <literal>SessionActionInterceptor</literal> as a reaction of some events, usually before writing methods and after reading (<literal>getNode()</literal>, <literal> getProperty()</literal> etc). This <literal>SetAccessContextAction</literal> calls the <literal>AccessManager.setContext(InvocationContext context)</literal> method which sets the ThreadLocal invocation context for the current call. @@ -61,7 +61,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Access_Control_Extension-The_Invocation_Context"> + <section id="sect-Reference_Guide-Access_Control_Extension-The_Invocation_Context"> <title>The Invocation Context</title> <para> The <literal>InvocationContext</literal> contains the current Item, the current ExoContainer and the current EventType is like below: @@ -78,10 +78,10 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Access_Control_Extension-Custom_Extended_Access_Manager"> + <section id="sect-Reference_Guide-Access_Control_Extension-Custom_Extended_Access_Manager"> <title>Custom Extended Access Manager</title> <para> - All Workspaces share an <literal>AccessManager</literal> by default. The <literal>AccessManager</literal> is created by <literal>RepositoryService</literal> at start up and supports access control policy as described in <xref linkend="chap-Reference_Guide_eXo_JCR_1.14-Access_Control" />. + All Workspaces share an <literal>AccessManager</literal> by default. The <literal>AccessManager</literal> is created by <literal>RepositoryService</literal> at start up and supports access control policy as described in <xref linkend="chap-Reference_Guide-Access_Control" />. </para> <para> A Custom Access Control policy can be applied to certain Workspaces by configuring the <parameter>access-manager</parameter> element inside the <parameter>workspace</parameter> element as follows: @@ -113,7 +113,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Access_Control_Extension-Example_of_a_custom_Access_Manager"> + <section id="sect-Reference_Guide-Access_Control_Extension-Example_of_a_custom_Access_Manager"> <title>Example of a custom Access Manager</title> <para> The sample <literal>CustomAccessManagerImpl</literal> below extends the default access manager and uses some <literal>DecisionMakingService</literal> in the overloaded <literal>hasPermission</literal> method to find out if a current user has permission to use current <emphasis role="bold">item, event type, userID</emphasis> and some parameter of AccessManager. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/other/acl.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/other/acl.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/other/acl.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,14 +1,14 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Access_Control"> +<chapter id="chap-Reference_Guide-Access_Control"> <title>Access Control</title> <para> The eXo JCR component is a complete implementation of the standard JSR 170: <ulink url="http://jcp.org/en/jsr/detail?id=170">Content Repository for Java TM Technology API</ulink>, including <emphasis role="bold">Level 1, Level 2 and Additional Features</emphasis> specified in the JCR Specification. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Access_Control-Standard_Action_Permissions"> + <section id="sect-Reference_Guide-Access_Control-Standard_Action_Permissions"> <title>Standard Action Permissions</title> <para> The JCR specification (JSR 170) has few requirements about Access Control. It only requires the implementation of the <literal>Session.checkPermission(String absPath, String actions)</literal> method. This method checks if a current session has permissions to perform some actions on absPath: @@ -114,12 +114,12 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Access_Control-eXo_Access_Control"> + <section id="sect-Reference_Guide-Access_Control-eXo_Access_Control"> <title>eXo Access Control</title> <para> The JSR-170 specification does not define how permissions are managed or checked. Therefore the eXo JCR has a proprietary extension to manage and check permissions on nodes. In essence, this extension uses an <ulink url="http://en.wikipedia.org/wiki/Access_control_list">Access Control List (ACL)</ulink> policy model applied to the eXo Organization model. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-eXo_Access_Control-Principal_and_Identity"> + <section id="sect-Reference_Guide-eXo_Access_Control-Principal_and_Identity"> <title>Principal and Identity</title> <para> The eXo Access Control is built around the notion of the <emphasis role="bold">identity</emphasis> concept. Access to the JCR is made through sessions acquired against a repository. @@ -167,7 +167,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-eXo_Access_Control-ACL"> + <section id="sect-Reference_Guide-eXo_Access_Control-ACL"> <title>ACL</title> <para> An access control list (<abbrev>ACL</abbrev>) is a list of permissions attached to an object. An ACL specifies which users, groups or system processes are granted access to JCR nodes, as well as what operations are allowed to be performed on given objects. @@ -199,7 +199,7 @@ </varlistentry> </variablelist> - <section id="sect-Reference_Guide_eXo_JCR_1.14-ACL-Privilegeable"> + <section id="sect-Reference_Guide-ACL-Privilegeable"> <title>Privilegeable</title> <para> A privilegeable node defines the permissions required for actions on this node. For this purpose, it contains an ACL. @@ -252,7 +252,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-ACL-Ownable"> + <section id="sect-Reference_Guide-ACL-Ownable"> <title>Ownable</title> <para> An ownable node defines an owner identity. The <emphasis role="bold">owner</emphasis> has always <emphasis role="bold">full privileges</emphasis>. These privileges are independent of the permissions set by exo:permissions. At JCR level, the ownership is implemented by an <emphasis role="bold">exo:owneable</emphasis> mixin. This mixin holds an owner property. @@ -272,7 +272,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-ACL-ACL_Inheritance"> + <section id="sect-Reference_Guide-ACL-ACL_Inheritance"> <title>ACL Inheritance</title> <para> To grant or deny access to a node, eXo JCR applies a privilege resolving logic at node access time. @@ -292,7 +292,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-ACL-Default_ACL_of_the_root_node"> + <section id="sect-Reference_Guide-ACL-Default_ACL_of_the_root_node"> <title>Default ACL of the root node</title> <para> When no matching ACL is found in the ancestor hierarchy, the system may end up looking at the root node's ACL. As ACL are optional, even for the root node, if the root node has no ACL, the following rule is ultimately applied to resolve privileges: @@ -312,13 +312,13 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-eXo_Access_Control-Notes"> + <section id="sect-Reference_Guide-eXo_Access_Control-Notes"> <title>Notes</title> <para> <parameter>Access Control nodetypes are not extendible:</parameter> The access control mechanism works for <parameter>exo:owneable</parameter> and <parameter>exo:privilegeable</parameter> nodetypes only, not for their subtypes! So you cannot extend those nodetypes. </para> <para> - <parameter>Autocreation:</parameter> By default, newly created nodes are neither <parameter>exo:privilegeable</parameter> nor <parameter>exo:owneable</parameter> but it is possible to configure the repository to auto-create <parameter>exo:privilegeable</parameter> or/and <parameter>exo:owneable</parameter> thanks to eXo's JCR interceptors extension  + <parameter>Autocreation:</parameter> By default, newly created nodes are neither <parameter>exo:privilegeable</parameter> nor <parameter>exo:owneable</parameter> but it is possible to configure the repository to auto-create <parameter>exo:privilegeable</parameter> or/and <parameter>exo:owneable</parameter> thanks to eXo's JCR interceptors extension  </para> <para> <parameter>OR-based Privilege Inheritance</parameter>: Note, that eXo's Access Control implementation supports a privilege inheritance that follows a strategy of either...or/ and has only an ALLOW privilege mechanism (there is no DENY feature). This means that a session is allowed to perform some operations on some nodes if its identity has an appropriate permission assigned to this node. Only if there is no exo:permission property assigned to the node itself, the permissions of the node's ancestors are used. @@ -326,9 +326,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-eXo_Access_Control-Example"> + <section id="sect-Reference_Guide-eXo_Access_Control-Example"> <title>Example</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Example-XML_Example"> + <section id="sect-Reference_Guide-Example-XML_Example"> <title>XML Example</title> <para> In the following example, you see a node named "<emphasis>Politics</emphasis>" which contains two nodes named "<emphasis>Cats</emphasis>" and "<emphasis>Dogs</emphasis>". @@ -370,7 +370,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Example-Inheritance_Examples"> + <section id="sect-Reference_Guide-Example-Inheritance_Examples"> <title>Inheritance Examples</title> <para> Here is an example showing the accessibility of two nodes (to show inheritance) for two sample users named <emphasis role="bold">manager</emphasis> and <emphasis role="bold">user</emphasis>: @@ -387,7 +387,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Example-Permission_validation"> + <section id="sect-Reference_Guide-Example-Permission_validation"> <title>Permission validation</title> <para> This session describes how permission is validated for different JCR actions. @@ -494,12 +494,12 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-eXo_Access_Control-Java_API"> + <section id="sect-Reference_Guide-eXo_Access_Control-Java_API"> <title>Java API</title> <para> eXo JCR's <literal>ExtendedNode</literal> interface which extends <literal>javax.jcr.Node</literal> interface provides additional methods for Access Control management. </para> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Java_API-Additional_methods"> + <table id="tabl-Reference_Guide-Java_API-Additional_methods"> <title>Additional methods</title> <tgroup cols="2"> <thead> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/other/binary-values-processing.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/other/binary-values-processing.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/other/binary-values-processing.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Binary_Values_Processing"> +<chapter id="chap-Reference_Guide-Binary_Values_Processing"> <title>Binary Values Processing</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Binary_Values_Processing-Configuration"> + <section id="sect-Reference_Guide-Binary_Values_Processing-Configuration"> <title>Configuration</title> <para> Binary large object (<abbrev>BLOB</abbrev>) properties can be stored in two ways in the eXo JCR; in the database with items information or in an external storage on host file system. These options can be configured at workspace in the repository configuration file (<filename>repository-configuration.xml</filename>). The database storage can not be completely disabled. @@ -18,20 +18,20 @@ </para> <note> <para> - The eXo JCR Repository service configuration basics is discussed in <xref linkend="chap-Reference_Guide_eXo_JCR_1.14-JCR_configuration" /> + The eXo JCR Repository service configuration basics is discussed in <xref linkend="chap-Reference_Guide-JCR_configuration" /> </para> <para> - Database and workspace persistence storage configuration is discussed in <xref linkend="chap-Reference_Guide_eXo_JCR_1.14-JDBC_Data_Container_Config" /> + Database and workspace persistence storage configuration is discussed in <xref linkend="chap-Reference_Guide-JDBC_Data_Container_Config" /> </para> <para> - Configuration details for <xref linkend="chap-Reference_Guide_eXo_JCR_1.14-External_Value_Storages" />. + Configuration details for <xref linkend="chap-Reference_Guide-External_Value_Storages" />. </para> </note> </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Binary_Values_Processing-Usage"> + <section id="sect-Reference_Guide-Binary_Values_Processing-Usage"> <title>Usage</title> <para> In both of the cases, a developer can set or update the binary Property via <literal>Node.setProperty(String, InputStream)</literal>, <literal>Property.setValue(InputStream)</literal> as described in the spec JSR-170. Also, there is the setter with a ready Value object obtained from <literal>ValueFactory.createValue(InputStream)</literal>. @@ -113,7 +113,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Binary_Values_Processing-Value_implementations"> + <section id="sect-Reference_Guide-Binary_Values_Processing-Value_implementations"> <title>Value implementations</title> <mediaobject> <imageobject> 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-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/other/jcr-resources.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-JCR_Resources"> +<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> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/other/link-producer.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/other/link-producer.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/other/link-producer.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Link_Producer_Service"> +<chapter id="chap-Reference_Guide-Link_Producer_Service"> <title>Link Producer Service</title> <para> The Link Producer Service is a simple service which generates an file that is compatible with the Microsoft link file format. It is an extension of the REST Framework library and is included into the WebDav service. On dispatching a <literal>GET</literal> request the service generates the content of an <filename>.lnk</filename> file, which points to a JCR resource via WebDav. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/performance-tuning-guide.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/performance-tuning-guide.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/performance-tuning-guide.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-JCR_Performance_Tuning_Guide"> +<chapter id="chap-Reference_Guide-JCR_Performance_Tuning_Guide"> <title>JCR Performance Tuning Guide</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Performance_Tuning_Guide-Introduction"> + <section id="sect-Reference_Guide-JCR_Performance_Tuning_Guide-Introduction"> <title>Introduction</title> <para> This section will show you various ways of improving JCR performance. @@ -16,14 +16,14 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Performance_Tuning_Guide-JCR_Performance_and_Scalability"> + <section id="sect-Reference_Guide-JCR_Performance_Tuning_Guide-JCR_Performance_and_Scalability"> <title>JCR Performance and Scalability</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Performance_and_Scalability-Cluster_configuration"> + <section id="sect-Reference_Guide-JCR_Performance_and_Scalability-Cluster_configuration"> <title>Cluster configuration</title> <para> The table below contains details about the configuration of the cluster used in benchmark testing: </para> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Cluster_configuration-EC2_network_1Gbit"> + <table id="tabl-Reference_Guide-Cluster_configuration-EC2_network_1Gbit"> <title>EC2 network: 1Gbit</title> <tgroup cols="2"> <colspec colname="1"></colspec> @@ -128,7 +128,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Performance_and_Scalability-JCR_Clustered_Performance"> + <section id="sect-Reference_Guide-JCR_Performance_and_Scalability-JCR_Clustered_Performance"> <title>JCR Clustered Performance</title> <para> Benchmark test using WebDAV (Complex read/write load test (benchmark)) with 20K same file. To obtain per-operation results we have used custom output from the test case threads to CSV file. @@ -348,9 +348,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Performance_Tuning_Guide-Performance_Tuning_Guide"> + <section id="sect-Reference_Guide-JCR_Performance_Tuning_Guide-Performance_Tuning_Guide"> <title>Performance Tuning Guide</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Performance_Tuning_Guide-JBoss_AS_Tuning"> + <section id="sect-Reference_Guide-Performance_Tuning_Guide-JBoss_AS_Tuning"> <title>JBoss AS Tuning</title> <para> You can use <parameter>maxThreads</parameter> parameter to increase maximum amount of threads that can be launched in AS instance. This can improve performance if you need a high level of concurrency. also you can use <code>-XX:+UseParallelGC</code> java directory to use parallel garbage collector. @@ -375,7 +375,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Performance_Tuning_Guide-JCR_Cache_Tuning"> + <section id="sect-Reference_Guide-Performance_Tuning_Guide-JCR_Cache_Tuning"> <title>JCR Cache Tuning</title> <para> <citetitle>Cache size</citetitle> @@ -398,7 +398,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Performance_Tuning_Guide-Clustering"> + <section id="sect-Reference_Guide-Performance_Tuning_Guide-Clustering"> <title>Clustering</title> <para> For performance it is better to have loadbalacer, DB server and shared NFS on different computers. If in some reasons you see that one node gets more load than others you can decrease this load using load value in load balancer. 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-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/protocols/ftp.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-FTP"> +<chapter id="chap-Reference_Guide-FTP"> <title>FTP</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-FTP-Introduction"> + <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. @@ -13,9 +13,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-FTP-Configuration_Parameters"> + <section id="sect-Reference_Guide-FTP-Configuration_Parameters"> <title>Configuration Parameters</title> - <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Configuration_Parameters-Parameters"> + <variablelist id="vari-Reference_Guide-Configuration_Parameters-Parameters"> <title>Parameters</title> <varlistentry> <term>command-port:</term> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/protocols/webdav.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/protocols/webdav.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/protocols/webdav.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-WebDAV"> +<chapter id="chap-Reference_Guide-WebDAV">  <title>WebDAV</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-WebDAV-Introduction"> + <section id="sect-Reference_Guide-WebDAV-Introduction"> <title>Introduction</title> <para> The <application>WebDAV</application> protocol enables you to use third party tools to communicate with hierarchical content servers via the HTTP protocol. It is possible to add and remove documents or a set of documents from a path on the server. @@ -42,7 +42,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-WebDAV-WebDAV_Configuration"> + <section id="sect-Reference_Guide-WebDAV-WebDAV_Configuration"> <title>WebDAV Configuration</title> <para> The WebDAV configuration file:  @@ -133,7 +133,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-WebDAV-Corresponding_WebDav_and_JCR_actions"> + <section id="sect-Reference_Guide-WebDAV-Corresponding_WebDav_and_JCR_actions"> <title>Corresponding WebDav and JCR actions</title> <table> <title></title> @@ -331,12 +331,12 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-WebDAV-WebDAV_Considerations"> + <section id="sect-Reference_Guide-WebDAV-WebDAV_Considerations"> <title>WebDAV Considerations</title> <para> There are some restrictions for WebDAV in different operating systems. </para> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-WebDAV_Considerations-Windows_7"> + <formalpara id="form-Reference_Guide-WebDAV_Considerations-Windows_7"> <title>Windows 7</title> <para> When attemping to set up a web folder through <guilabel>Add a Network Location</guilabel> or <guilabel>Map a Network Drive</guilabel> through <guilabel>My Computer</guilabel>, an error message stating <guilabel>The folder you entered does not appear to be valid. Please choose another</guilabel> or <guilabel>Windows cannot access … Check the spelling of the name. Otherwise, there might be …</guilabel> may be encountered. These errors may appear when you are using SSL or non-SSL. @@ -367,7 +367,7 @@ </listitem> </orderedlist> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-WebDAV_Considerations-Microsoft_Office_2010"> + <formalpara id="form-Reference_Guide-WebDAV_Considerations-Microsoft_Office_2010"> <title>Microsoft Office 2010</title> <para> If you have: 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-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/query-handler-config.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-QueryHandler_configuration"> +<chapter id="chap-Reference_Guide-QueryHandler_configuration"> <title>QueryHandler configuration</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-QueryHandler_configuration-Indexing_in_clustered_environment"> + <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. @@ -35,14 +35,14 @@ 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_eXo_JCR_1.14-Search_Configuration" /> . + See more about <xref linkend="chap-Reference_Guide-Search_Configuration" /> . </para> </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-QueryHandler_configuration-Configuration"> + <section id="sect-Reference_Guide-QueryHandler_configuration-Configuration"> <title>Configuration</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuration-Query_handler_configuration_overview"> + <section id="sect-Reference_Guide-Configuration-Query_handler_configuration_overview"> <title>Query-handler configuration overview</title> <para> Configuration example: @@ -67,7 +67,7 @@ </query-handler> </workspace> </programlisting> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Query_handler_configuration_overview-Configuration_properties"> + <table id="tabl-Reference_Guide-Query_handler_configuration_overview-Configuration_properties"> <title>Configuration properties</title> <tgroup cols="2"> <thead> @@ -197,7 +197,7 @@ </tgroup> </table> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Query_handler_configuration_overview-Improving_Query_Performance_With_postgreSQL_and_rdbms_reindexing"> + <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: @@ -227,7 +227,7 @@ </procedure> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Query_handler_configuration_overview-Improving_Query_Performance_With_DB2_and_rdbms_reindexing"> + <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: @@ -250,7 +250,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuration-Cluster_ready_indexing"> + <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. @@ -298,7 +298,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuration-Local_Index_Recovery_Filters"> + <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. @@ -330,7 +330,7 @@ <para> There are multiple filter implementations: </para> - <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Local_Index_Recovery_Filters-org.exoplatform.services.jcr.impl.core.query.lucene.DummyRecoveryFilter"> + <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> @@ -390,12 +390,12 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuration-JBoss_Cache_template_configuration"> + <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_eXo_JCR_1.14-JBoss_Cache_template_configuration-jbosscache_indexer.xml"> + <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"?> @@ -421,7 +421,7 @@ </example> <para> - Read more about template configurations <xref linkend="chap-Reference_Guide_eXo_JCR_1.14-JBoss_Cache_configuration" />. + Read more about template configurations <xref linkend="chap-Reference_Guide-JBoss_Cache_configuration" />. </para> </section> @@ -429,12 +429,12 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-QueryHandler_configuration-Asynchronous_Reindexing"> + <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_eXo_JCR_1.14-Asynchronous_Reindexing-On_startup_indexing"> + <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: @@ -461,7 +461,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Asynchronous_Reindexing-Hot_Asynchronous_Workspace_Reindexing_via_JMX"> + <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"). @@ -487,7 +487,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Asynchronous_Reindexing-Notices"> + <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: @@ -513,9 +513,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-QueryHandler_configuration-Advanced_tuning"> + <section id="sect-Reference_Guide-QueryHandler_configuration-Advanced_tuning"> <title>Advanced tuning</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Advanced_tuning-Lucene_tuning"> + <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. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/repository-check-controller.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/repository-check-controller.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/repository-check-controller.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Checking_repository_integrity_and_consistency"> +<chapter id="chap-Reference_Guide-Checking_repository_integrity_and_consistency"> <title>Checking repository integrity and consistency</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Checking_repository_integrity_and_consistency-JMX_based_consistency_tool"> + <section id="sect-Reference_Guide-Checking_repository_integrity_and_consistency-JMX_based_consistency_tool"> <title>JMX-based consistency tool</title> <para> It is important to check the integrity and consistency of system regularly, especially if there is no, or stale, backups. The JBoss Enterprise Portal Platform JCR implementation offers an innovative JMX-based complex checking tool. @@ -19,7 +19,7 @@ <para> Access to the check tool is exposed via the JMX interface, with the following operations available: </para> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-JMX_based_consistency_tool-Available_methods"> + <table id="tabl-Reference_Guide-JMX_based_consistency_tool-Available_methods"> <title>Available methods</title> <tgroup cols="2"> <tbody> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/repository-creation-service.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/repository-creation-service.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/repository-creation-service.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-RepositoryCreationService"> +<chapter id="chap-Reference_Guide-RepositoryCreationService"> <title><literal>RepositoryCreationService</literal></title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-RepositoryCreationService-Introduction"> + <section id="sect-Reference_Guide-RepositoryCreationService-Introduction"> <title>Introduction</title> <para> The <parameter>RepositoryCreationService</parameter> is the service for creating repositories during runtime. @@ -39,14 +39,14 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-RepositoryCreationService-Configuration"> + <section id="sect-Reference_Guide-RepositoryCreationService-Configuration"> <title>Configuration</title> <para> RepositoryCreationService configuration </para> <programlistingco> <areaspec> - <area coords="63 50" id="area-Reference_Guide_eXo_JCR_1.14-RepositoryCreationService-Configuration-factory-class-name" /> + <area coords="63 50" id="area-Reference_Guide-RepositoryCreationService-Configuration-factory-class-name" /> </areaspec> @@ -115,7 +115,7 @@ </init-params> </component></programlisting> <calloutlist> -  <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-RepositoryCreationService-Configuration-factory-class-name"> +  <callout arearefs="area-Reference_Guide-RepositoryCreationService-Configuration-factory-class-name"> <para> <parameter>factory-class-name</parameter> is not mandatory parameter, indicates what the factory need to use to create DataSource objects </para> @@ -129,7 +129,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-RepositoryCreationService-RepositoryCreationService_Interface"> + <section id="sect-Reference_Guide-RepositoryCreationService-RepositoryCreationService_Interface"> <title>RepositoryCreationService Interface</title> <programlisting language="Java" role="Java">public interface RepositoryCreationService @@ -216,7 +216,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-RepositoryCreationService-Conclusions_and_restrictions"> + <section id="sect-Reference_Guide-RepositoryCreationService-Conclusions_and_restrictions"> <title>Conclusions and restrictions</title> <para> Each datasource in RepositoryEntry of new Repository must have unbinded datasources. That means, such datasource must have not databases behind them. This restriction exists to avoid corruption of existing repositories data. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/aggregation-rule.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/aggregation-rule.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/aggregation-rule.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,14 +1,14 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Finding_a_node_by_content_of_child_node"> +<section id="sect-Reference_Guide-Finding_a_node_by_content_of_child_node"> <title>Finding a node by content of child node</title> <para> The node type <literal>nt:file</literal> represents a file. It requires a single child node, called <literal>jcr:content</literal>. This node type represents images and other binary content. The node type of <literal>jcr:content</literal> is <literal>nt:resource</literal> which represents the actual content of a file. </para> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Finding_a_node_by_content_of_child_node-Task"> + <formalpara id="form-Reference_Guide-Finding_a_node_by_content_of_child_node-Task"> <title>Task:</title> <para> Find node with the primary type <literal>nt:file</literal> and whose <literal>jcr:content</literal> child node contains <emphasis>cats</emphasis>. @@ -38,7 +38,7 @@ <para> Now the content of <literal>nt:file</literal> and <literal>jcr:content</literal> (<literal>nt:resource</literal>) nodes are concatenated in a single Lucene document. Then, a fulltext search query can be based on content of the <literal>nt:file</literal> and this search includes the content of child <literal>jcr:content</literal> node. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Finding_a_node_by_content_of_child_node-Repository_structure"> + <section id="sect-Reference_Guide-Finding_a_node_by_content_of_child_node-Repository_structure"> <title>Repository structure:</title> <para> Repository contains different <literal>nt:file</literal> nodes. @@ -55,9 +55,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Finding_a_node_by_content_of_child_node-Query_execution"> + <section id="sect-Reference_Guide-Finding_a_node_by_content_of_child_node-Query_execution"> <title>Query execution</title> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Finding_a_node_by_content_of_child_node-Query_execution-SQL"> + <example id="exam-Reference_Guide-Finding_a_node_by_content_of_child_node-Query_execution-SQL"> <title>SQL</title> <programlisting language="Java" role="Java">// make SQL query @@ -69,7 +69,7 @@ QueryResult result = query.execute();</programlisting> </example> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Finding_a_node_by_content_of_child_node-Query_execution-XPath"> + <example id="exam-Reference_Guide-Finding_a_node_by_content_of_child_node-Query_execution-XPath"> <title>XPath</title> <programlisting language="Java" role="Java">// make XPath query @@ -84,7 +84,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Finding_a_node_by_content_of_child_node-Fetching_the_result"> + <section id="sect-Reference_Guide-Finding_a_node_by_content_of_child_node-Fetching_the_result"> <title>Fetching the result</title> <para> To fetch the matching nodes: @@ -114,7 +114,7 @@ <para> Table content is: </para> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Finding_a_node_by_content_of_child_node-Fetching_the_result-Table_content"> + <table id="tabl-Reference_Guide-Finding_a_node_by_content_of_child_node-Fetching_the_result-Table_content"> <title>Table content</title> <tgroup cols="2"> <thead> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/and-constraint.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/and-constraint.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/and-constraint.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-AND_Constraint"> +<section id="sect-Reference_Guide-AND_Constraint"> <title>AND Constraint</title> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-AND_Constraint-Task"> + <formalpara id="form-Reference_Guide-AND_Constraint-Task"> <title>Task:</title> <para> To find all <emphasis>fairytales</emphasis> with a page count more than <literal>90</literal> pages. Or, in JCR terms; find all nodes with mixin type <literal>mix:title</literal> where the property <parameter>jcr:description</parameter> equals <emphasis>fairytale</emphasis> and whose <parameter>prop_pagecount</parameter> property value is less than <literal>90</literal>. @@ -14,11 +14,11 @@ </formalpara> <note> <para> - See also <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Multivalue_Property_Comparison" />. + See also <xref linkend="sect-Reference_Guide-Multivalue_Property_Comparison" />. </para> </note> - <section id="sect-Reference_Guide_eXo_JCR_1.14-AND_Constraint-Repository_Structure"> + <section id="sect-Reference_Guide-AND_Constraint-Repository_Structure"> <title>Repository Structure:</title> <para> The repository contains <literal>mix:title</literal> nodes, where <parameter>prop_pagecount</parameter> has different values. @@ -32,9 +32,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-AND_Constraint-Query_execution"> + <section id="sect-Reference_Guide-AND_Constraint-Query_execution"> <title>Query execution</title> - <example id="exam-Reference_Guide_eXo_JCR_1.14-AND_Constraint-Query_execution-SQL"> + <example id="exam-Reference_Guide-AND_Constraint-Query_execution-SQL"> <title>SQL</title> <programlisting language="Java" role="Java">// make SQL query @@ -46,7 +46,7 @@ QueryResult result = query.execute();</programlisting> </example> - <example id="exam-Reference_Guide_eXo_JCR_1.14-AND_Constraint-Query_execution-XPath"> + <example id="exam-Reference_Guide-AND_Constraint-Query_execution-XPath"> <title>XPath</title> <programlisting language="Java" role="Java">// make XPath query @@ -61,7 +61,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-AND_Constraint-Fetching_the_Result"> + <section id="sect-Reference_Guide-AND_Constraint-Fetching_the_Result"> <title>Fetching the Result</title> <para> To fetch the nodes: @@ -90,7 +90,7 @@ }</programlisting> <para> Table content is: - <table id="tabl-Reference_Guide_eXo_JCR_1.14-AND_Constraint-Fetching_the_Result-Table_content"> + <table id="tabl-Reference_Guide-AND_Constraint-Fetching_the_Result-Table_content"> <title>Table content</title> <tgroup cols="5"> <thead> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/child-node-constraint.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/child-node-constraint.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/child-node-constraint.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,18 +1,18 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Child_Node_Constraint"> +<section id="sect-Reference_Guide-Child_Node_Constraint"> <title>Child Node Constraint</title> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Child_Node_Constraint-Task"> + <formalpara id="form-Reference_Guide-Child_Node_Constraint-Task"> <title>Task:</title> <para> To find all nodes with the primary type '<literal>nt:folder</literal>' that are children of node by path "<filename>/root1/root2</filename>". Only find children, do not find further descendants. </para> </formalpara> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Child_Node_Constraint-Repository_Structure"> + <section id="sect-Reference_Guide-Child_Node_Constraint-Repository_Structure"> <title>Repository Structure</title> <para> The repository is filled by "<literal>nt:folder</literal>" nodes. The nodes are placed in a multilayer tree. @@ -28,9 +28,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Child_Node_Constraint-Query_Execution"> + <section id="sect-Reference_Guide-Child_Node_Constraint-Query_Execution"> <title>Query Execution</title> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Child_Node_Constraint-Query_Execution-SQL"> + <example id="exam-Reference_Guide-Child_Node_Constraint-Query_Execution-SQL"> <title>SQL</title> <para> The use of "%" in the LIKE statement includes any string, therefore there is a second LIKE statement that excludes that the string contains "/". This way child nodes are included but descendant nodes are excluded. @@ -45,7 +45,7 @@ QueryResult result = query.execute();</programlisting> </example> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Child_Node_Constraint-Query_Execution-XPath"> + <example id="exam-Reference_Guide-Child_Node_Constraint-Query_Execution-XPath"> <title>XPath</title> <programlisting language="Java" role="Java">// make XPath query @@ -60,7 +60,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Child_Node_Constraint-Fetching_the_Result"> + <section id="sect-Reference_Guide-Child_Node_Constraint-Fetching_the_Result"> <title>Fetching the Result</title> <para> To fetch the nodes: @@ -89,7 +89,7 @@ }</programlisting> <para> The table content is: - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Child_Node_Constraint-Fetching_the_Result-Table_content"> + <table id="tabl-Reference_Guide-Child_Node_Constraint-Fetching_the_Result-Table_content"> <title>Table content</title> <tgroup cols="2"> <thead> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/date-property-comparison.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/date-property-comparison.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/date-property-comparison.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,18 +1,18 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Date_Property_Comparison"> +<section id="sect-Reference_Guide-Date_Property_Comparison"> <title>Date Property Comparison</title> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Date_Property_Comparison-Task"> + <formalpara id="form-Reference_Guide-Date_Property_Comparison-Task"> <title>Task:</title> <para> Find all nodes of primary type <literal>nt:resource</literal> whose <parameter>jcr:lastModified</parameter> property value is greater than <literal>2006-06-04</literal> and less than <literal>2008-06-04</literal>. </para> </formalpara> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Date_Property_Comparison-Repository_Structure"> + <section id="sect-Reference_Guide-Date_Property_Comparison-Repository_Structure"> <title>Repository Structure</title> <para> Repository contains <literal>nt:resource</literal> nodes with different values of <parameter>jcr:lastModified</parameter> property. @@ -29,9 +29,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Date_Property_Comparison-Query_Execution"> + <section id="sect-Reference_Guide-Date_Property_Comparison-Query_Execution"> <title>Query Execution</title> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Date_Property_Comparison-Query_Execution-SQL"> + <example id="exam-Reference_Guide-Date_Property_Comparison-Query_Execution-SQL"> <title>SQL</title> <para> In SQL you have to use the keyword <emphasis>TIMESTAMP</emphasis> for date comparisons. Otherwise, the date would be interpreted as a string. @@ -64,7 +64,7 @@ QueryResult result = query.execute();</programlisting> </example> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Date_Property_Comparison-Query_Execution-XPath"> + <example id="exam-Reference_Guide-Date_Property_Comparison-Query_Execution-XPath"> <title>XPath</title> <para> Compared to the SQL format, you have to use the keyword <emphasis>xs:dateTime</emphasis> and surround the datetime by extra brackets: <literal>xs:dateTime('datetime')</literal>. The actual format of the datetime also conforms with the ISO date standard. @@ -89,7 +89,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Date_Property_Comparison-Fetching_the_result"> + <section id="sect-Reference_Guide-Date_Property_Comparison-Fetching_the_result"> <title>Fetching the result</title> <para> To fetch the nodes: @@ -118,7 +118,7 @@ }</programlisting> <para> The table content is: - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Date_Property_Comparison-Fetching_the_result-Table_content"> + <table id="tabl-Reference_Guide-Date_Property_Comparison-Fetching_the_result-Table_content"> <title>Table content</title> <tgroup cols="3"> <thead> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/escaping-like-statements.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/escaping-like-statements.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/escaping-like-statements.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Escaping_in_LIKE_Statements"> +<section id="sect-Reference_Guide-Escaping_in_LIKE_Statements"> <title>Escaping in LIKE Statements</title> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Escaping_in_LIKE_Statements-Task"> + <formalpara id="form-Reference_Guide-Escaping_in_LIKE_Statements-Task"> <title>Task:</title> <para> Find all nodes with a mixin type 'mix:title' and whose property <literal>jcr:title</literal> starts with <emphasis>P%ri</emphasis>. @@ -23,7 +23,7 @@ <para> XPath does not have any specification for defining escape symbols. The default XPath escape character is the backslash ('<literal>\</literal>'). </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Escaping_in_LIKE_Statements-Repository_structure"> + <section id="sect-Reference_Guide-Escaping_in_LIKE_Statements-Repository_structure"> <title>Repository structure</title> <para> The repository contains <literal>mix:title</literal> nodes, where <parameter>jcr:title</parameter> can have different values. @@ -37,9 +37,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Escaping_in_LIKE_Statements-Query_execution"> + <section id="sect-Reference_Guide-Escaping_in_LIKE_Statements-Query_execution"> <title>Query execution</title> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Escaping_in_LIKE_Statements-Query_execution-SQL"> + <example id="exam-Reference_Guide-Escaping_in_LIKE_Statements-Query_execution-SQL"> <title>SQL</title> <programlisting language="Java" role="Java">// make SQL query @@ -51,7 +51,7 @@ QueryResult result = query.execute();</programlisting> </example> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Escaping_in_LIKE_Statements-Query_execution-XPath"> + <example id="exam-Reference_Guide-Escaping_in_LIKE_Statements-Query_execution-XPath"> <title>XPath</title> <programlisting language="Java" role="Java">// make XPath query @@ -66,7 +66,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Escaping_in_LIKE_Statements-Fetching_result"> + <section id="sect-Reference_Guide-Escaping_in_LIKE_Statements-Fetching_result"> <title>Fetching result</title> <para> To get the matching nodes: @@ -95,7 +95,7 @@ }</programlisting> <para> The table content is - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Escaping_in_LIKE_Statements-Fetching_result-Table_content"> + <table id="tabl-Reference_Guide-Escaping_in_LIKE_Statements-Fetching_result-Table_content"> <title>Table content</title> <tgroup cols="4"> <thead> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/exact-path-constraint.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/exact-path-constraint.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/exact-path-constraint.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,18 +1,18 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Exact_Path_Constraint"> +<section id="sect-Reference_Guide-Exact_Path_Constraint"> <title>Exact Path Constraint</title> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Exact_Path_Constraint-Task"> + <formalpara id="form-Reference_Guide-Exact_Path_Constraint-Task"> <title>Task:</title> <para> Find a node with the primary type <literal>nt:file</literal> that is located on the exact path <filename>/folder1/folder2/document1</filename>. </para> </formalpara> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Exact_Path_Constraint-Repository_Structure"> + <section id="sect-Reference_Guide-Exact_Path_Constraint-Repository_Structure"> <title>Repository Structure</title> <para> Repository filled by different nodes. There are several folders which contain other folders and files. @@ -28,9 +28,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Exact_Path_Constraint-Query_Execution"> + <section id="sect-Reference_Guide-Exact_Path_Constraint-Query_Execution"> <title>Query Execution</title> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Exact_Path_Constraint-Query_Execution-SQL"> + <example id="exam-Reference_Guide-Exact_Path_Constraint-Query_Execution-SQL"> <title>SQL</title> <programlisting language="Java" role="Java">// make SQL query @@ -43,7 +43,7 @@ QueryResult result = query.execute();</programlisting> </example> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Exact_Path_Constraint-Query_Execution-XPath"> + <example id="exam-Reference_Guide-Exact_Path_Constraint-Query_Execution-XPath"> <title>XPath</title> <programlisting language="Java" role="Java">// make SQL query @@ -66,7 +66,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Exact_Path_Constraint-Fetching_the_Result"> + <section id="sect-Reference_Guide-Exact_Path_Constraint-Fetching_the_Result"> <title>Fetching the Result</title> <para> To fetch matching nodes: @@ -95,7 +95,7 @@ }</programlisting> <para> Table content is: - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Exact_Path_Constraint-Fetching_the_Result-Table_content"> + <table id="tabl-Reference_Guide-Exact_Path_Constraint-Fetching_the_Result-Table_content"> <title>Table content</title> <tgroup cols="2"> <thead> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/find-all-descendant-nodes.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/find-all-descendant-nodes.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/find-all-descendant-nodes.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,18 +1,18 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Finding_All_Descendant_Nodes"> +<section id="sect-Reference_Guide-Finding_All_Descendant_Nodes"> <title>Finding All Descendant Nodes</title> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Finding_All_Descendant_Nodes-Task"> + <formalpara id="form-Reference_Guide-Finding_All_Descendant_Nodes-Task"> <title>Task:</title> <para> Find all nodes with the primary type <literal>nt:folder</literal> that are descendants of the node <literal>/folder1/folder2</literal>. </para> </formalpara> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Finding_All_Descendant_Nodes-Repository_Structure"> + <section id="sect-Reference_Guide-Finding_All_Descendant_Nodes-Repository_Structure"> <title>Repository Structure</title> <para> The repository contains <literal>nt:folder</literal> nodes. The nodes are placed in a multilayer tree. @@ -28,9 +28,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Finding_All_Descendant_Nodes-Query_Execution"> + <section id="sect-Reference_Guide-Finding_All_Descendant_Nodes-Query_Execution"> <title>Query Execution</title> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Finding_All_Descendant_Nodes-Query_Execution-SQL"> + <example id="exam-Reference_Guide-Finding_All_Descendant_Nodes-Query_Execution-SQL"> <title>SQL</title> <programlisting language="Java" role="Java">// make SQL query @@ -42,7 +42,7 @@ QueryResult result = query.execute();</programlisting> </example> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Finding_All_Descendant_Nodes-Query_Execution-XPath"> + <example id="exam-Reference_Guide-Finding_All_Descendant_Nodes-Query_Execution-XPath"> <title>XPath</title> <programlisting language="Java" role="Java">// make XPath query @@ -57,7 +57,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Finding_All_Descendant_Nodes-Fetching_the_Result"> + <section id="sect-Reference_Guide-Finding_All_Descendant_Nodes-Fetching_the_Result"> <title>Fetching the Result</title> <para> To fetch the nodes: @@ -86,7 +86,7 @@ }</programlisting> <para> Table content is: - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Finding_All_Descendant_Nodes-Fetching_the_Result-Table_content"> + <table id="tabl-Reference_Guide-Finding_All_Descendant_Nodes-Fetching_the_Result-Table_content"> <title>Table content</title> <tgroup cols="2"> <thead> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/find-all-nodes.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/find-all-nodes.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/find-all-nodes.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Finding_All_Nodes"> +<section id="sect-Reference_Guide-Finding_All_Nodes"> <title>Finding All Nodes</title> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Finding_All_Nodes-Task"> + <formalpara id="form-Reference_Guide-Finding_All_Nodes-Task"> <title>Task:</title> <para> Find all nodes in the repository. @@ -15,11 +15,11 @@ <note> <title>Note</title> <para> - This search will only nodes that the current session has READ access to. See also <xref linkend="chap-Reference_Guide_eXo_JCR_1.14-Access_Control" />. + This search will only nodes that the current session has READ access to. See also <xref linkend="chap-Reference_Guide-Access_Control" />. </para> </note> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Finding_All_Nodes-Repository_structure"> + <section id="sect-Reference_Guide-Finding_All_Nodes-Repository_structure"> <title>Repository structure:</title> <para> Repository contains many different nodes. @@ -35,9 +35,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Finding_All_Nodes-Query_execution"> + <section id="sect-Reference_Guide-Finding_All_Nodes-Query_execution"> <title>Query execution</title> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Finding_All_Nodes-Query_execution-SQL"> + <example id="exam-Reference_Guide-Finding_All_Nodes-Query_execution-SQL"> <title>SQL</title> <programlisting language="Java" role="Java">// make SQL query @@ -49,7 +49,7 @@ QueryResult result = query.execute();</programlisting> </example> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Finding_All_Nodes-Query_execution-XPath"> + <example id="exam-Reference_Guide-Finding_All_Nodes-Query_execution-XPath"> <title>XPath</title> <programlisting language="Java" role="Java">// make XPath query @@ -64,7 +64,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Finding_All_Nodes-Fetching_result"> + <section id="sect-Reference_Guide-Finding_All_Nodes-Fetching_result"> <title>Fetching result</title> <para> To fetch the nodes: @@ -94,7 +94,7 @@ <para> Table content is </para> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Finding_All_Nodes-Fetching_result-Table_content"> + <table id="tabl-Reference_Guide-Finding_All_Nodes-Fetching_result-Table_content"> <title>Table content</title> <tgroup cols="2"> <thead> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/find-nodes-by-mixin-type.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/find-nodes-by-mixin-type.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/find-nodes-by-mixin-type.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,18 +1,18 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Finding_Nodes_by_Mixin_Type"> +<section id="sect-Reference_Guide-Finding_Nodes_by_Mixin_Type"> <title>Finding Nodes by Mixin Type</title> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Finding_Nodes_by_Mixin_Type-Task"> + <formalpara id="form-Reference_Guide-Finding_Nodes_by_Mixin_Type-Task"> <title>Task:</title> <para> Find all nodes in repository, that contain a mixin type <literal>mix:title</literal>. </para> </formalpara> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Finding_Nodes_by_Mixin_Type-Repository_structure"> + <section id="sect-Reference_Guide-Finding_Nodes_by_Mixin_Type-Repository_structure"> <title>Repository structure:</title> <para> The repository contains nodes with different primary types and mixin types. @@ -26,9 +26,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Finding_Nodes_by_Mixin_Type-Query_execution"> + <section id="sect-Reference_Guide-Finding_Nodes_by_Mixin_Type-Query_execution"> <title>Query execution</title> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Finding_Nodes_by_Mixin_Type-Query_execution-SQL"> + <example id="exam-Reference_Guide-Finding_Nodes_by_Mixin_Type-Query_execution-SQL"> <title>SQL</title> <programlisting language="Java" role="Java">// make SQL query @@ -40,7 +40,7 @@ QueryResult result = query.execute();</programlisting> </example> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Finding_Nodes_by_Mixin_Type-Query_execution-XPath"> + <example id="exam-Reference_Guide-Finding_Nodes_by_Mixin_Type-Query_execution-XPath"> <title>XPath</title> <programlisting language="Java" role="Java">// make XPath query @@ -55,7 +55,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Finding_Nodes_by_Mixin_Type-Fetching_result"> + <section id="sect-Reference_Guide-Finding_Nodes_by_Mixin_Type-Fetching_result"> <title>Fetching result</title> <para> To the fetch the nodes: @@ -84,7 +84,7 @@ }</programlisting> <para> Table content is - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Finding_Nodes_by_Mixin_Type-Fetching_result-Table_content"> + <table id="tabl-Reference_Guide-Finding_Nodes_by_Mixin_Type-Fetching_result-Table_content"> <title>Table content</title> <tgroup cols="4"> <thead> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/find-nodes-by-primary-type.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/find-nodes-by-primary-type.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/find-nodes-by-primary-type.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,18 +1,18 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Finding_Nodes_by_Primary_Type"> +<section id="sect-Reference_Guide-Finding_Nodes_by_Primary_Type"> <title>Finding Nodes by Primary Type</title> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Finding_Nodes_by_Primary_Type-Task"> + <formalpara id="form-Reference_Guide-Finding_Nodes_by_Primary_Type-Task"> <title>Task:</title> <para> Find all nodes whose primary type is <literal>nt:file</literal>. </para> </formalpara> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Finding_Nodes_by_Primary_Type-Repository_structure"> + <section id="sect-Reference_Guide-Finding_Nodes_by_Primary_Type-Repository_structure"> <title>Repository structure:</title> <para> The repository contains nodes with different primary types and mixin types. @@ -26,9 +26,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Finding_Nodes_by_Primary_Type-Query_execution"> + <section id="sect-Reference_Guide-Finding_Nodes_by_Primary_Type-Query_execution"> <title>Query execution</title> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Finding_Nodes_by_Primary_Type-Query_execution-SQL"> + <example id="exam-Reference_Guide-Finding_Nodes_by_Primary_Type-Query_execution-SQL"> <title>SQL</title> <programlisting language="Java" role="Java">// make SQL query @@ -40,7 +40,7 @@ QueryResult result = query.execute();</programlisting> </example> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Finding_Nodes_by_Primary_Type-Query_execution-XPath"> + <example id="exam-Reference_Guide-Finding_Nodes_by_Primary_Type-Query_execution-XPath"> <title>XPath</title> <programlisting language="Java" role="Java">// make XPath query @@ -55,7 +55,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Finding_Nodes_by_Primary_Type-Fetching_result"> + <section id="sect-Reference_Guide-Finding_Nodes_by_Primary_Type-Fetching_result"> <title>Fetching result</title> <para> To fetch the matching nodes: @@ -84,7 +84,7 @@ }</programlisting> <para> The table content is - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Finding_Nodes_by_Primary_Type-Fetching_result-Table_content"> + <table id="tabl-Reference_Guide-Finding_Nodes_by_Primary_Type-Fetching_result-Table_content"> <title>Table content</title> <tgroup cols="2"> <thead> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/find-nodes-case-insensitive.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/find-nodes-case-insensitive.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/find-nodes-case-insensitive.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,18 +1,18 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Finding_Nodes_in_a_Case_Insensitive_Way"> +<section id="sect-Reference_Guide-Finding_Nodes_in_a_Case_Insensitive_Way"> <title>Finding Nodes in a Case-Insensitive Way</title> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Finding_Nodes_in_a_Case_Insensitive_Way-Task"> + <formalpara id="form-Reference_Guide-Finding_Nodes_in_a_Case_Insensitive_Way-Task"> <title>Task:</title> <para> Find all nodes with a mixin type <literal>mix:title</literal> and where the property <parameter>jcr:title</parameter> equals <literal>casesensitive</literal> in lower or upper case. </para> </formalpara> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Finding_Nodes_in_a_Case_Insensitive_Way-Repository_Structure"> + <section id="sect-Reference_Guide-Finding_Nodes_in_a_Case_Insensitive_Way-Repository_Structure"> <title>Repository Structure</title> <para> The repository contains <literal>mix:title</literal> nodes, whose <literal>jcr:title</literal> properties have different values. @@ -26,9 +26,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Finding_Nodes_in_a_Case_Insensitive_Way-Query_Execution"> + <section id="sect-Reference_Guide-Finding_Nodes_in_a_Case_Insensitive_Way-Query_Execution"> <title>Query Execution</title> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Finding_Nodes_in_a_Case_Insensitive_Way-Query_Execution-SQL_Uppercase"> + <example id="exam-Reference_Guide-Finding_Nodes_in_a_Case_Insensitive_Way-Query_Execution-SQL_Uppercase"> <title>SQL- Uppercase</title> <programlisting language="Java" role="Java">// make SQL query @@ -40,7 +40,7 @@ QueryResult result = query.execute();</programlisting> </example> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Finding_Nodes_in_a_Case_Insensitive_Way-Query_Execution-XPath_Upper_Case"> + <example id="exam-Reference_Guide-Finding_Nodes_in_a_Case_Insensitive_Way-Query_Execution-XPath_Upper_Case"> <title>XPath - Upper Case</title> <programlisting language="Java" role="Java">// make XPath query @@ -52,7 +52,7 @@ QueryResult result = query.execute();</programlisting> </example> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Finding_Nodes_in_a_Case_Insensitive_Way-Query_Execution-SQL_Lower_Case"> + <example id="exam-Reference_Guide-Finding_Nodes_in_a_Case_Insensitive_Way-Query_Execution-SQL_Lower_Case"> <title>SQL - Lower Case</title> <programlisting language="Java" role="Java">// make SQL query @@ -64,7 +64,7 @@ QueryResult result = query.execute();</programlisting> </example> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Finding_Nodes_in_a_Case_Insensitive_Way-Query_Execution-XPath_Lower_Case"> + <example id="exam-Reference_Guide-Finding_Nodes_in_a_Case_Insensitive_Way-Query_Execution-XPath_Lower_Case"> <title>XPath - Lower Case</title> <programlisting language="Java" role="Java">// make XPath query @@ -79,7 +79,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Finding_Nodes_in_a_Case_Insensitive_Way-Fetching_the_Result"> + <section id="sect-Reference_Guide-Finding_Nodes_in_a_Case_Insensitive_Way-Fetching_the_Result"> <title>Fetching the Result</title> <para> To fetch the nodes: @@ -108,7 +108,7 @@ }</programlisting> <para> Table content is: - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Finding_Nodes_in_a_Case_Insensitive_Way-Fetching_the_Result-Table_content"> + <table id="tabl-Reference_Guide-Finding_Nodes_in_a_Case_Insensitive_Way-Fetching_the_Result-Table_content"> <title>Table content</title> <tgroup cols="3"> <thead> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/find-similar-nodes.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/find-similar-nodes.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/find-similar-nodes.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Finding_Similar_Nodes"> +<section id="sect-Reference_Guide-Finding_Similar_Nodes"> <title>Finding Similar Nodes</title> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Finding_Similar_Nodes-Task"> + <formalpara id="form-Reference_Guide-Finding_Similar_Nodes-Task"> <title>Task:</title> <para> To find nodes similar to a nominated node at: <literal>/baseFile/jcr:content</literal>. @@ -18,7 +18,7 @@ <note> <title>Reference</title> <para> - Refer to <xref linkend="chap-Reference_Guide_eXo_JCR_1.14-Searching_Repository_Content" /> for information about Similarity and configuration. + Refer to <xref linkend="chap-Reference_Guide-Searching_Repository_Content" /> for information about Similarity and configuration. </para> </note> @@ -33,17 +33,17 @@ ... </properties> </query-handler></programlisting> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Finding_Similar_Nodes-Repository_structure"> + <section id="sect-Reference_Guide-Finding_Similar_Nodes-Repository_structure"> <title>Repository structure:</title> <para> Repository contains many nt:file nodes" </para> <programlistingco> <areaspec> - <area coords="2" id="area-Reference_Guide_eXo_JCR_1.14-Finding_Similar_Nodes-Repository_structure-baseFile" /> - <area coords="3" id="area-Reference_Guide_eXo_JCR_1.14-Finding_Similar_Nodes-Repository_structure-target1" /> - <area coords="4" id="area-Reference_Guide_eXo_JCR_1.14-Finding_Similar_Nodes-Repository_structure-target2" /> - <area coords="5" id="area-Reference_Guide_eXo_JCR_1.14-Finding_Similar_Nodes-Repository_structure-target3" /> + <area coords="2" id="area-Reference_Guide-Finding_Similar_Nodes-Repository_structure-baseFile" /> + <area coords="3" id="area-Reference_Guide-Finding_Similar_Nodes-Repository_structure-target1" /> + <area coords="4" id="area-Reference_Guide-Finding_Similar_Nodes-Repository_structure-target2" /> + <area coords="5" id="area-Reference_Guide-Finding_Similar_Nodes-Repository_structure-target3" /> </areaspec> @@ -54,25 +54,25 @@ └── target3 (nt:file) </programlisting> <calloutlist> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Finding_Similar_Nodes-Repository_structure-baseFile"> + <callout arearefs="area-Reference_Guide-Finding_Similar_Nodes-Repository_structure-baseFile"> <para> jcr:content (nt:resource) jcr:data="Similarity is determined by looking up <emphasis role="bold">terms</emphasis> that are common to nodes. There are some conditions that must be met for a <emphasis role="bold">term</emphasis> to be considered. This is required to limit the number possibly relevant <emphasis role="bold">terms</emphasis>. Only <emphasis role="bold">terms</emphasis> with at least 4 characters are considered. Only <emphasis role="bold">terms</emphasis> that occur at least 2 times in the source node are considered. Only <emphasis role="bold">terms</emphasis> that occur in at least 5 nodes are considered." </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Finding_Similar_Nodes-Repository_structure-target1"> + <callout arearefs="area-Reference_Guide-Finding_Similar_Nodes-Repository_structure-target1"> <para> jcr:content (nt:resource) jcr:data="Similarity is determined by looking up <emphasis role="bold">terms</emphasis> that are common to nodes." </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Finding_Similar_Nodes-Repository_structure-target2"> + <callout arearefs="area-Reference_Guide-Finding_Similar_Nodes-Repository_structure-target2"> <para> jcr:content (nt:resource) jcr:data="There is no you know what" </para> </callout> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Finding_Similar_Nodes-Repository_structure-target3"> + <callout arearefs="area-Reference_Guide-Finding_Similar_Nodes-Repository_structure-target3"> <para> jcr:content (nt:resource) jcr:data=" <emphasis role="bold">Terms</emphasis> occurs here" </para> @@ -86,9 +86,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Finding_Similar_Nodes-Query_execution"> + <section id="sect-Reference_Guide-Finding_Similar_Nodes-Query_execution"> <title>Query execution</title> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Finding_Similar_Nodes-Query_execution-SQL"> + <example id="exam-Reference_Guide-Finding_Similar_Nodes-Query_execution-SQL"> <title>SQL</title> <programlisting language="Java" role="Java">// make SQL query @@ -100,7 +100,7 @@ QueryResult result = query.execute();</programlisting> </example> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Finding_Similar_Nodes-Query_execution-XPath"> + <example id="exam-Reference_Guide-Finding_Similar_Nodes-Query_execution-XPath"> <title>XPath</title> <programlisting language="Java" role="Java">// make XPath query @@ -115,7 +115,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Finding_Similar_Nodes-Fetching_results"> + <section id="sect-Reference_Guide-Finding_Similar_Nodes-Fetching_results"> <title>Fetching results</title> <para> To fetch nodes: @@ -148,7 +148,7 @@ <para> The table content is: </para> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Finding_Similar_Nodes-Fetching_results-Table_content"> + <table id="tabl-Reference_Guide-Finding_Similar_Nodes-Fetching_results-Table_content"> <title>Table content</title> <tgroup cols="3"> <thead> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/fulltext-search-and-settings.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/fulltext-search-and-settings.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/fulltext-search-and-settings.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,18 +1,18 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Fulltext_Search_And_Affecting_Settings"> +<chapter id="chap-Reference_Guide-Fulltext_Search_And_Affecting_Settings"> <title>Fulltext Search And Affecting Settings</title> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Fulltext_Search_And_Affecting_Settings-Property_content_indexing"> + <formalpara id="form-Reference_Guide-Fulltext_Search_And_Affecting_Settings-Property_content_indexing"> <title>Property content indexing</title> <para> Each property of a node (if it is indexable) is processed with the Lucene analyzer and stored in the Lucene index. This is called indexing of a property. It allows fulltext searching of these indexed properties. </para> </formalpara> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Fulltext_Search_And_Affecting_Settings-Lucene_Analyzers"> + <section id="sect-Reference_Guide-Fulltext_Search_And_Affecting_Settings-Lucene_Analyzers"> <title>Lucene Analyzers</title> <para> The purpose of analyzers is to transform all strings stored in the index into a well-defined condition. The same analyzer(s) is/are used when searching in order to adapt the query string to the index reality. @@ -23,7 +23,7 @@ <para> The example below illustrates how the same string is transformed by different analyzers. </para> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Lucene_Analyzers-The_quick_brown_fox_jumped_over_the_lazy_dogs"> + <table id="tabl-Reference_Guide-Lucene_Analyzers-The_quick_brown_fox_jumped_over_the_lazy_dogs"> <title>"The quick brown fox jumped over the lazy dogs"</title> <tgroup cols="2"> <thead> @@ -99,7 +99,7 @@ </tgroup> </table> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Lucene_Analyzers-XYampZ_Corporation_xyz..."> + <table id="tabl-Reference_Guide-Lucene_Analyzers-XYampZ_Corporation_xyzexample.com"> <title>"XY&Z Corporation - xyz(a)example.com"</title> <tgroup cols="2"> <thead> @@ -182,12 +182,12 @@ </note> <para> - You can assign your analyzer as described in <xref linkend="chap-Reference_Guide_eXo_JCR_1.14-Search_Configuration" />. + You can assign your analyzer as described in <xref linkend="chap-Reference_Guide-Search_Configuration" />. </para> </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Fulltext_Search_And_Affecting_Settings-Property_Indexing"> + <section id="sect-Reference_Guide-Fulltext_Search_And_Affecting_Settings-Property_Indexing"> <title>Property Indexing</title> <para> Different properties are indexed in different ways and this affects whether it can be searched via fulltext by property or not. @@ -195,7 +195,7 @@ <para> Only two property types are indexed as fulltext searcheable: <parameter>STRING</parameter> and <parameter>BINARY</parameter>. </para> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Property_Indexing-Fulltext_search_by_different_properties"> + <table id="tabl-Reference_Guide-Property_Indexing-Fulltext_search_by_different_properties"> <title>Fulltext search by different properties</title> <tgroup cols="3"> <thead> @@ -260,7 +260,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Fulltext_Search_And_Affecting_Settings-Different_Analyzers"> + <section id="sect-Reference_Guide-Fulltext_Search_And_Affecting_Settings-Different_Analyzers"> <title>Different Analyzers</title> <para> First of all, we will fill repository by nodes with mixin type 'mix:title' and different values of 'jcr:description' property. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/fulltext-search-by-all-properties.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/fulltext-search-by-all-properties.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/fulltext-search-by-all-properties.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Fulltext_Search_by_All_Properties_in_Node"> +<section id="sect-Reference_Guide-Fulltext_Search_by_All_Properties_in_Node"> <title>Fulltext Search by All Properties in Node</title> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Fulltext_Search_by_All_Properties_in_Node-Task"> + <formalpara id="form-Reference_Guide-Fulltext_Search_by_All_Properties_in_Node-Task"> <title>Task:</title> <para> Find nodes with mixin type <literal>mix:title</literal> where any property contains <literal>break</literal> string. @@ -15,7 +15,7 @@ <para> </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Fulltext_Search_by_All_Properties_in_Node-Repository_structure"> + <section id="sect-Reference_Guide-Fulltext_Search_by_All_Properties_in_Node-Repository_structure"> <title>Repository structure:</title> <para> The repository filled with different nodes with mixin type <literal>mix:title</literal> and different values of <literal>jcr:title</literal> and <literal>jcr:description</literal> properties. @@ -29,9 +29,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Fulltext_Search_by_All_Properties_in_Node-Query_execution"> + <section id="sect-Reference_Guide-Fulltext_Search_by_All_Properties_in_Node-Query_execution"> <title>Query execution</title> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Fulltext_Search_by_All_Properties_in_Node-Query_execution-SQL"> + <example id="exam-Reference_Guide-Fulltext_Search_by_All_Properties_in_Node-Query_execution-SQL"> <title>SQL</title> <programlisting language="Java" role="Java">// make SQL query @@ -43,7 +43,7 @@ QueryResult result = query.execute();</programlisting> </example> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Fulltext_Search_by_All_Properties_in_Node-Query_execution-XPath"> + <example id="exam-Reference_Guide-Fulltext_Search_by_All_Properties_in_Node-Query_execution-XPath"> <title>XPath</title> <programlisting language="Java" role="Java">// make SQL query @@ -59,7 +59,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Fulltext_Search_by_All_Properties_in_Node-Fetching_result"> + <section id="sect-Reference_Guide-Fulltext_Search_by_All_Properties_in_Node-Fetching_result"> <title>Fetching result</title> <para> To fetch matching nodes: @@ -89,7 +89,7 @@ <para> Table content is: </para> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Fulltext_Search_by_All_Properties_in_Node-Fetching_result-Table_content"> + <table id="tabl-Reference_Guide-Fulltext_Search_by_All_Properties_in_Node-Fetching_result-Table_content"> <title>Table content</title> <tgroup cols="4"> <thead> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/fulltext-search-by-property.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/fulltext-search-by-property.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/fulltext-search-by-property.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Fulltext_Search_by_Property"> +<section id="sect-Reference_Guide-Fulltext_Search_by_Property"> <title>Fulltext Search by Property</title> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Fulltext_Search_by_Property-Task"> + <formalpara id="form-Reference_Guide-Fulltext_Search_by_Property-Task"> <title>Task:</title> <para> Find all nodes containing a mixin type <literal>mix:title</literal> and whose <literal>jcr:description</literal> contains the string; <emphasis>forest</emphasis>. @@ -15,7 +15,7 @@ <para> </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Fulltext_Search_by_Property-Repository_Structure"> + <section id="sect-Reference_Guide-Fulltext_Search_by_Property-Repository_Structure"> <title>Repository Structure</title> <para> The repository is filled with nodes of the mixin type <literal>mix:title</literal> and different values of the <literal>jcr:description</literal> property. @@ -30,10 +30,10 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Fulltext_Search_by_Property-Query_Execution"> + <section id="sect-Reference_Guide-Fulltext_Search_by_Property-Query_Execution"> <title>Query Execution</title> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Fulltext_Search_by_Property-Query_Execution-SQL"> + <example id="exam-Reference_Guide-Fulltext_Search_by_Property-Query_Execution-SQL"> <title>SQL</title> <programlisting language="Java" role="Java">// make SQL query @@ -46,7 +46,7 @@ QueryResult result = query.execute();</programlisting> </example> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Fulltext_Search_by_Property-Query_Execution-XPath"> + <example id="exam-Reference_Guide-Fulltext_Search_by_Property-Query_Execution-XPath"> <title>XPath</title> <programlisting language="Java" role="Java">// make SQL query @@ -62,7 +62,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Fulltext_Search_by_Property-Fetching_the_Result"> + <section id="sect-Reference_Guide-Fulltext_Search_by_Property-Fetching_the_Result"> <title>Fetching the Result</title> <para> To fetch the appropriate nodes: @@ -92,7 +92,7 @@ <para> Table content is: </para> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Fulltext_Search_by_Property-Fetching_the_Result-Table_content"> + <table id="tabl-Reference_Guide-Fulltext_Search_by_Property-Fetching_the_Result-Table_content"> <title>Table content</title> <tgroup cols="3"> <thead> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/higlight.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/higlight.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/higlight.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,12 +1,12 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Highlighting_Results_of_Fulltext_Search"> +<section id="sect-Reference_Guide-Highlighting_Results_of_Fulltext_Search"> <title>Highlighting Results of Fulltext Search</title> <para> - The highlighting functionality is also called excerption (refer to the Excerpt configuration information in <xref linkend="chap-Reference_Guide_eXo_JCR_1.14-Search_Configuration" />). + The highlighting functionality is also called excerption (refer to the Excerpt configuration information in <xref linkend="chap-Reference_Guide-Search_Configuration" />). </para> <para> This query will find and highlight instances of <emphasis>eXo</emphasis> and <emphasis>implementation</emphasis> within fulltext search results. @@ -34,7 +34,7 @@ <property useInExcerpt="false">title</property> <property>text</property> </index-rule></programlisting> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Highlighting_Results_of_Fulltext_Search-Repository_structure"> + <section id="sect-Reference_Guide-Highlighting_Results_of_Fulltext_Search-Repository_structure"> <title>Repository structure:</title> <para> The repository contains a single node with the primary type <literal>nt:unstructured</literal>: @@ -48,9 +48,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Highlighting_Results_of_Fulltext_Search-Query_execution"> + <section id="sect-Reference_Guide-Highlighting_Results_of_Fulltext_Search-Query_execution"> <title>Query execution</title> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Highlighting_Results_of_Fulltext_Search-Query_execution-SQL"> + <example id="exam-Reference_Guide-Highlighting_Results_of_Fulltext_Search-Query_execution-SQL"> <title>SQL</title> <programlisting language="Java" role="Java">// make SQL query @@ -62,7 +62,7 @@ QueryResult result = query.execute();</programlisting> </example> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Highlighting_Results_of_Fulltext_Search-Query_execution-XPath"> + <example id="exam-Reference_Guide-Highlighting_Results_of_Fulltext_Search-Query_execution-XPath"> <title>XPath</title> <programlisting language="Java" role="Java">// make XPath query @@ -77,7 +77,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Highlighting_Results_of_Fulltext_Search-Fetching_result"> + <section id="sect-Reference_Guide-Highlighting_Results_of_Fulltext_Search-Fetching_result"> <title>Fetching result</title> <para> Below is the result table: @@ -94,7 +94,7 @@ <para> Table content is </para> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Highlighting_Results_of_Fulltext_Search-Fetching_result-Table_content"> + <table id="tabl-Reference_Guide-Highlighting_Results_of_Fulltext_Search-Fetching_result-Table_content"> <title>Table content</title> <tgroup cols="3"> <thead> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/ignore-accent-symbols.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/ignore-accent-symbols.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/ignore-accent-symbols.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Ignoring_Accent_Symbols"> +<section id="sect-Reference_Guide-Ignoring_Accent_Symbols"> <title>Ignoring Accent Symbols</title> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Ignoring_Accent_Symbols-Task"> + <formalpara id="form-Reference_Guide-Ignoring_Accent_Symbols-Task"> <title>Task:</title> <para> Create a new Analyzer to normalize accented characters (such as; é,è,à), set the new Analyzer in QueryHandler configuration, and create a query to check it. @@ -18,7 +18,7 @@ <orderedlist> <listitem> <para> - Create a descendant class of SearchIndex with the new Analyzer (refer to <xref linkend="chap-Reference_Guide_eXo_JCR_1.14-Search_Configuration" /> for more infomation). + Create a descendant class of SearchIndex with the new Analyzer (refer to <xref linkend="chap-Reference_Guide-Search_Configuration" /> for more infomation). </para> </listitem> @@ -30,7 +30,7 @@ </listitem> </orderedlist> - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Ignoring_Accent_Symbols-Creating_and_Registering_a_New_Analyzer"> + <procedure id="proc-Reference_Guide-Ignoring_Accent_Symbols-Creating_and_Registering_a_New_Analyzer"> <title>Creating and Registering a New Analyzer</title> <step> <para> @@ -82,7 +82,7 @@ </procedure> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Ignoring_Accent_Symbols-Repository_structure"> + <section id="sect-Reference_Guide-Ignoring_Accent_Symbols-Repository_structure"> <title>Repository structure:</title> <para> Repository filled by nodes with mixin type <literal>mix:title</literal> and different values of <parameter>jcr:title</parameter> property. @@ -95,9 +95,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Ignoring_Accent_Symbols-Query_execution"> + <section id="sect-Reference_Guide-Ignoring_Accent_Symbols-Query_execution"> <title>Query execution</title> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Ignoring_Accent_Symbols-Query_execution-SQL"> + <example id="exam-Reference_Guide-Ignoring_Accent_Symbols-Query_execution-SQL"> <title>SQL</title> <programlisting language="Java" role="Java">// make SQL query @@ -109,7 +109,7 @@ QueryResult result = query.execute();</programlisting> </example> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Ignoring_Accent_Symbols-Query_execution-XPath"> + <example id="exam-Reference_Guide-Ignoring_Accent_Symbols-Query_execution-XPath"> <title>XPath</title> <programlisting language="Java" role="Java">// make SQL query @@ -124,7 +124,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Ignoring_Accent_Symbols-Fetching_result"> + <section id="sect-Reference_Guide-Ignoring_Accent_Symbols-Fetching_result"> <title>Fetching result</title> <para> To fetch applicable nodes: @@ -154,7 +154,7 @@ <para> Table content is </para> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Ignoring_Accent_Symbols-Fetching_result-Table_content"> + <table id="tabl-Reference_Guide-Ignoring_Accent_Symbols-Fetching_result-Table_content"> <title>Table content</title> <tgroup cols="3"> <thead> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/index-boost-value.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/index-boost-value.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/index-boost-value.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Changing_Priority_of_Node"> +<section id="sect-Reference_Guide-Changing_Priority_of_Node"> <title>Changing Priority of Node</title> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Changing_Priority_of_Node-Task"> + <formalpara id="form-Reference_Guide-Changing_Priority_of_Node-Task"> <title>Task:</title> <para> Set different boost values for predefined nodes, and check the effect of this change by selecting those nodes and order them by <literal>jcr:score</literal>. @@ -16,14 +16,14 @@ The default boost value is <literal>1.0</literal>. Higher boost values (a reasonable range is between <literal>1.0</literal> and <literal>5.0</literal>) will yield a higher score value and appear as more relevant. </para> <para> - Refer to <xref linkend="chap-Reference_Guide_eXo_JCR_1.14-Search_Configuration" /> for more information. + Refer to <xref linkend="chap-Reference_Guide-Search_Configuration" /> for more information. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Changing_Priority_of_Node-Indexing_configuration"> + <section id="sect-Reference_Guide-Changing_Priority_of_Node-Indexing_configuration"> <title>Indexing configuration</title> <para> In this configuration the boost values for <literal>nt:unstructured</literal> nodes <emphasis>text</emphasis> property will be increased. </para> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Indexing_configuration-indexing_config.xml"> + <example id="exam-Reference_Guide-Indexing_configuration-indexing_config.xml"> <title>indexing-config.xml:</title> <programlisting language="XML" role="XML">   <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Query_Usecases-Query_Examples"> + </section> --> <section id="sect-Reference_Guide-JCR_Query_Usecases-Query_Examples"> <title>Query Examples</title> <xi:include href="offset-and-limit.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> <xi:include href="find-all-nodes.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> @@ -357,7 +357,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-JCR_Query_Usecases-Tips_and_tricks"> + <section id="sect-Reference_Guide-JCR_Query_Usecases-Tips_and_tricks"> <title>Tips and tricks</title> <xi:include href="tip-nodename-with-number.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/like-constraint.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/like-constraint.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/like-constraint.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-LIKE_Constraint"> +<section id="sect-Reference_Guide-LIKE_Constraint"> <title>LIKE Constraint</title> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-LIKE_Constraint-Task"> + <formalpara id="form-Reference_Guide-LIKE_Constraint-Task"> <title>Task:</title> <para> Find all nodes with mixin type <literal>mix:title</literal> and where the property <parameter>jcr:title</parameter> starts with <literal>P</literal>. @@ -14,11 +14,11 @@ </formalpara> <note> <para> - Further useful information can be found in <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-NOT_Constraint" />. + Further useful information can be found in <xref linkend="sect-Reference_Guide-NOT_Constraint" />. </para> </note> - <section id="sect-Reference_Guide_eXo_JCR_1.14-LIKE_Constraint-Repository_structure"> + <section id="sect-Reference_Guide-LIKE_Constraint-Repository_structure"> <title>Repository structure:</title> <para> The repository contains three mix:title nodes, where each jcr:title has a different value. @@ -32,9 +32,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-LIKE_Constraint-Query_execution"> + <section id="sect-Reference_Guide-LIKE_Constraint-Query_execution"> <title>Query execution</title> - <example id="exam-Reference_Guide_eXo_JCR_1.14-LIKE_Constraint-Query_execution-SQL"> + <example id="exam-Reference_Guide-LIKE_Constraint-Query_execution-SQL"> <title>SQL</title> <programlisting language="Java" role="Java">// make SQL query @@ -46,7 +46,7 @@ QueryResult result = query.execute();</programlisting> </example> - <example id="exam-Reference_Guide_eXo_JCR_1.14-LIKE_Constraint-Query_execution-XPath"> + <example id="exam-Reference_Guide-LIKE_Constraint-Query_execution-XPath"> <title>XPath</title> <programlisting language="Java" role="Java">// make XPath query @@ -61,7 +61,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-LIKE_Constraint-Fetching_result"> + <section id="sect-Reference_Guide-LIKE_Constraint-Fetching_result"> <title>Fetching result</title> <para> To fetch matching nodes: @@ -90,7 +90,7 @@ }</programlisting> <para> The table content is - <table id="tabl-Reference_Guide_eXo_JCR_1.14-LIKE_Constraint-Fetching_result-Table_content"> + <table id="tabl-Reference_Guide-LIKE_Constraint-Fetching_result-Table_content"> <title>Table content</title> <tgroup cols="4"> <thead> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/multivalue-property-comparison.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/multivalue-property-comparison.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/multivalue-property-comparison.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,18 +1,18 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Multivalue_Property_Comparison"> +<section id="sect-Reference_Guide-Multivalue_Property_Comparison"> <title>Multivalue Property Comparison</title> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Multivalue_Property_Comparison-Task"> + <formalpara id="form-Reference_Guide-Multivalue_Property_Comparison-Task"> <title>Task:</title> <para> To find all nodes with the primary type <literal>nt:unstructured</literal> whose property <parameter>multiprop</parameter> contains both values <emphasis>one</emphasis> and <emphasis>two</emphasis>. </para> </formalpara> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Multivalue_Property_Comparison-Repository_Structure"> + <section id="sect-Reference_Guide-Multivalue_Property_Comparison-Repository_Structure"> <title>Repository Structure</title> <para> The repository contains nt:unstructured nodes with different 'multiprop' properties. @@ -26,9 +26,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Multivalue_Property_Comparison-Query_Execution"> + <section id="sect-Reference_Guide-Multivalue_Property_Comparison-Query_Execution"> <title>Query Execution</title> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Multivalue_Property_Comparison-Query_Execution-SQL"> + <example id="exam-Reference_Guide-Multivalue_Property_Comparison-Query_Execution-SQL"> <title>SQL</title> <programlisting language="Java" role="Java">// make SQL query @@ -40,7 +40,7 @@ QueryResult result = query.execute();</programlisting> </example> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Multivalue_Property_Comparison-Query_Execution-XPath"> + <example id="exam-Reference_Guide-Multivalue_Property_Comparison-Query_Execution-XPath"> <title>XPath</title> <programlisting language="Java" role="Java">// make XPath query @@ -55,7 +55,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Multivalue_Property_Comparison-Fetching_the_Result"> + <section id="sect-Reference_Guide-Multivalue_Property_Comparison-Fetching_the_Result"> <title>Fetching the Result</title> <para> To fetch nodes: @@ -84,7 +84,7 @@ }</programlisting> <para> The table content is: - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Multivalue_Property_Comparison-Fetching_the_Result-Table_content"> + <table id="tabl-Reference_Guide-Multivalue_Property_Comparison-Fetching_the_Result-Table_content"> <title>Table content</title> <tgroup cols="3"> <thead> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/node-name-constraint.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/node-name-constraint.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/node-name-constraint.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Node_Name_Constraint"> +<section id="sect-Reference_Guide-Node_Name_Constraint"> <title>Node Name Constraint</title> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Node_Name_Constraint-Task"> + <formalpara id="form-Reference_Guide-Node_Name_Constraint-Task"> <title>Task:</title> <para> Find all nodes with primary type <literal>nt:file</literal> whose node name is <parameter>document</parameter>. The node name is accessible by a function called <code>fn:name()</code>. @@ -19,7 +19,7 @@ </para> </note> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Node_Name_Constraint-Repository_Structure"> + <section id="sect-Reference_Guide-Node_Name_Constraint-Repository_Structure"> <title>Repository Structure</title> <para> The repository contains nt:file nodes with different names. @@ -33,9 +33,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Node_Name_Constraint-Query_execution"> + <section id="sect-Reference_Guide-Node_Name_Constraint-Query_execution"> <title>Query execution</title> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Node_Name_Constraint-Query_execution-SQL"> + <example id="exam-Reference_Guide-Node_Name_Constraint-Query_execution-SQL"> <title>SQL</title> <programlisting language="Java" role="Java">// make SQL query @@ -47,7 +47,7 @@ QueryResult result = query.execute();</programlisting> </example> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Node_Name_Constraint-Query_execution-XPath"> + <example id="exam-Reference_Guide-Node_Name_Constraint-Query_execution-XPath"> <title>XPath</title> <programlisting language="Java" role="Java">// make XPath query @@ -62,7 +62,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Node_Name_Constraint-Fetching_the_Result"> + <section id="sect-Reference_Guide-Node_Name_Constraint-Fetching_the_Result"> <title>Fetching the Result</title> <para> To fetch appropriate nodes: @@ -91,7 +91,7 @@ }</programlisting> <para> Table content is: - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Node_Name_Constraint-Fetching_the_Result-Table_content"> + <table id="tabl-Reference_Guide-Node_Name_Constraint-Fetching_the_Result-Table_content"> <title>Table content</title> <tgroup cols="2"> <thead> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/node-scope-index.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/node-scope-index.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/node-scope-index.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Removing_Nodes_Property_From_Indexing_Scope"> +<section id="sect-Reference_Guide-Removing_Nodes_Property_From_Indexing_Scope"> <title>Removing Nodes Property From Indexing Scope</title> <para> This example will cover excluding a <emphasis>text</emphasis> property of <literal>nt:unstructured</literal> nodes from being indexed. This means the node will not be found by a search for the content of this property, even if it accepts all constraints. @@ -22,9 +22,9 @@ <property nodeScopeIndex="false">text</property> </index-rule></programlisting> <para> - Refer to <xref linkend="chap-Reference_Guide_eXo_JCR_1.14-Search_Configuration" /> for more details. + Refer to <xref linkend="chap-Reference_Guide-Search_Configuration" /> for more details. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Removing_Nodes_Property_From_Indexing_Scope-Repository_structure"> + <section id="sect-Reference_Guide-Removing_Nodes_Property_From_Indexing_Scope-Repository_structure"> <title>Repository structure</title> <para> The repository contains <literal>nt:unstructured</literal> nodes, with same <emphasis>text</emphasis> property and different <emphasis>rule</emphasis> properties. @@ -38,9 +38,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Removing_Nodes_Property_From_Indexing_Scope-Query_execution"> + <section id="sect-Reference_Guide-Removing_Nodes_Property_From_Indexing_Scope-Query_execution"> <title>Query execution</title> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Removing_Nodes_Property_From_Indexing_Scope-Query_execution-SQL"> + <example id="exam-Reference_Guide-Removing_Nodes_Property_From_Indexing_Scope-Query_execution-SQL"> <title>SQL</title> <programlisting language="Java" role="Java">// make SQL query @@ -52,7 +52,7 @@ QueryResult result = query.execute();</programlisting> </example> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Removing_Nodes_Property_From_Indexing_Scope-Query_execution-XPath"> + <example id="exam-Reference_Guide-Removing_Nodes_Property_From_Indexing_Scope-Query_execution-XPath"> <title>XPath</title> <programlisting language="Java" role="Java">// make XPath query @@ -67,7 +67,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Removing_Nodes_Property_From_Indexing_Scope-Fetching_result"> + <section id="sect-Reference_Guide-Removing_Nodes_Property_From_Indexing_Scope-Fetching_result"> <title>Fetching result</title> <para> To fetch nodes: @@ -97,7 +97,7 @@ <para> Table content is: </para> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Removing_Nodes_Property_From_Indexing_Scope-Fetching_result-Table_content"> + <table id="tabl-Reference_Guide-Removing_Nodes_Property_From_Indexing_Scope-Fetching_result-Table_content"> <title>Table content</title> <tgroup cols="3"> <thead> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/not-constraint.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/not-constraint.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/not-constraint.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,18 +1,18 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-NOT_Constraint"> +<section id="sect-Reference_Guide-NOT_Constraint"> <title>NOT Constraint</title> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-NOT_Constraint-Task"> + <formalpara id="form-Reference_Guide-NOT_Constraint-Task"> <title>Task:</title> <para> Find all nodes with a mixin type <literal>mix:title</literal> and where the property <parameter>jcr:title</parameter> does <emphasis role="bold">not</emphasis> start with a <literal>P</literal> symbol. </para> </formalpara> - <section id="sect-Reference_Guide_eXo_JCR_1.14-NOT_Constraint-Repository_Structure"> + <section id="sect-Reference_Guide-NOT_Constraint-Repository_Structure"> <title>Repository Structure</title> <para> The repository contains a mix:title nodes, where the jcr:title has different values. @@ -26,9 +26,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-NOT_Constraint-Query_execution"> + <section id="sect-Reference_Guide-NOT_Constraint-Query_execution"> <title>Query execution</title> - <example id="exam-Reference_Guide_eXo_JCR_1.14-NOT_Constraint-Query_execution-SQL"> + <example id="exam-Reference_Guide-NOT_Constraint-Query_execution-SQL"> <title>SQL</title> <programlisting language="Java" role="Java">// make SQL query @@ -40,7 +40,7 @@ QueryResult result = query.execute();</programlisting> </example> - <example id="exam-Reference_Guide_eXo_JCR_1.14-NOT_Constraint-Query_execution-XPath"> + <example id="exam-Reference_Guide-NOT_Constraint-Query_execution-XPath"> <title>XPath</title> <programlisting language="Java" role="Java">// make XPath query @@ -55,7 +55,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-NOT_Constraint-Fetching_the_result"> + <section id="sect-Reference_Guide-NOT_Constraint-Fetching_the_result"> <title>Fetching the result</title> <para> To fetch the matching nodes: @@ -84,7 +84,7 @@ }</programlisting> <para> Table content is - <table id="tabl-Reference_Guide_eXo_JCR_1.14-NOT_Constraint-Fetching_the_result-Table_content"> + <table id="tabl-Reference_Guide-NOT_Constraint-Fetching_the_result-Table_content"> <title>Table content</title> <tgroup cols="4"> <thead> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/offset-and-limit.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/offset-and-limit.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/offset-and-limit.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,18 +1,18 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-SetOffset_and_SetLimit"> +<section id="sect-Reference_Guide-SetOffset_and_SetLimit"> <title><literal>SetOffset</literal> and <literal>SetLimit</literal></title> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-SetOffset_and_SetLimit-Task"> + <formalpara id="form-Reference_Guide-SetOffset_and_SetLimit-Task"> <title>Task:</title> <para> Select all nodes with primary type <literal>nt:unstructured</literal> and return only three nodes starting with the second node in the list. </para> </formalpara> - <section id="sect-Reference_Guide_eXo_JCR_1.14-SetOffset_and_SetLimit-Common_information"> + <section id="sect-Reference_Guide-SetOffset_and_SetLimit-Common_information"> <title>Common information</title> <para> <literal>QueryImpl</literal> class has two methods; one to indicate how many results shall be returned at most, and another to fix the starting position. @@ -44,7 +44,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-SetOffset_and_SetLimit-Repository_structure"> + <section id="sect-Reference_Guide-SetOffset_and_SetLimit-Repository_structure"> <title>Repository structure</title> <para> The repository contains <literal>mix:title</literal> nodes, where <literal>jcr:title</literal> has different values. @@ -61,9 +61,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-SetOffset_and_SetLimit-Query_execution"> + <section id="sect-Reference_Guide-SetOffset_and_SetLimit-Query_execution"> <title>Query execution</title> - <example id="exam-Reference_Guide_eXo_JCR_1.14-SetOffset_and_SetLimit-Query_execution-SQL"> + <example id="exam-Reference_Guide-SetOffset_and_SetLimit-Query_execution-SQL"> <title>SQL</title> <programlisting language="Java" role="Java">// make SQL query @@ -82,7 +82,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-SetOffset_and_SetLimit-Fetching_result"> + <section id="sect-Reference_Guide-SetOffset_and_SetLimit-Fetching_result"> <title>Fetching result</title> <para> To fetch the matching nodes: Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/or-constraint.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/or-constraint.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/or-constraint.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,18 +1,18 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-OR_Constraint"> +<section id="sect-Reference_Guide-OR_Constraint"> <title>OR Constraint</title> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-OR_Constraint-Task"> + <formalpara id="form-Reference_Guide-OR_Constraint-Task"> <title>Task:</title> <para> Find all documents whose title is <emphasis>Cinderella</emphasis> OR whose description is <emphasis>novel</emphasis>. In JCR terms this would be; find all nodes with a mixin type <literal>mix:title</literal> whose property <parameter>jcr:title</parameter> equals <emphasis>Cinderella</emphasis> or whose <parameter>jcr:description</parameter> property value is <emphasis>novel</emphasis>. </para> </formalpara> - <section id="sect-Reference_Guide_eXo_JCR_1.14-OR_Constraint-Repository_Structure"> + <section id="sect-Reference_Guide-OR_Constraint-Repository_Structure"> <title>Repository Structure</title> <para> The repository contains mix:title nodes, where jcr:title and jcr:description have different values. @@ -26,9 +26,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-OR_Constraint-Query_Execution"> + <section id="sect-Reference_Guide-OR_Constraint-Query_Execution"> <title>Query Execution</title> - <example id="exam-Reference_Guide_eXo_JCR_1.14-OR_Constraint-Query_Execution-SQL"> + <example id="exam-Reference_Guide-OR_Constraint-Query_Execution-SQL"> <title>SQL</title> <programlisting language="Java" role="Java">// make SQL query @@ -40,7 +40,7 @@ QueryResult result = query.execute();</programlisting> </example> - <example id="exam-Reference_Guide_eXo_JCR_1.14-OR_Constraint-Query_Execution-XPath"> + <example id="exam-Reference_Guide-OR_Constraint-Query_Execution-XPath"> <title>XPath</title> <programlisting language="Java" role="Java">// make XPath query @@ -55,7 +55,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-OR_Constraint-Fetching_the_Result"> + <section id="sect-Reference_Guide-OR_Constraint-Fetching_the_Result"> <title>Fetching the Result</title> <para> To fetch matching nodes: @@ -84,7 +84,7 @@ }</programlisting> <para> Table content is: - <table id="tabl-Reference_Guide_eXo_JCR_1.14-OR_Constraint-Fetching_the_Result-Table_content"> + <table id="tabl-Reference_Guide-OR_Constraint-Fetching_the_Result-Table_content"> <title>Table content</title> <tgroup cols="4"> <thead> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/order-by-descendant.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/order-by-descendant.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/order-by-descendant.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Ordering_by_Descendant_Nodes_Property_XPath_only"> +<section id="sect-Reference_Guide-Ordering_by_Descendant_Nodes_Property_XPath_only"> <title>Ordering by Descendant Nodes Property (XPath only)</title> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Ordering_by_Descendant_Nodes_Property_XPath_only-Task"> + <formalpara id="form-Reference_Guide-Ordering_by_Descendant_Nodes_Property_XPath_only-Task"> <title>Task:</title> <para> Find all nodes with the primary type <literal>nt:unstructured</literal> and sort them by the property value of descendant nodes with the relative path <literal>/a/b</literal>. @@ -19,7 +19,7 @@ </para> </note> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Ordering_by_Descendant_Nodes_Property_XPath_only-Repository_structure"> + <section id="sect-Reference_Guide-Ordering_by_Descendant_Nodes_Property_XPath_only-Repository_structure"> <title>Repository structure</title> <programlisting>root @@ -38,9 +38,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Ordering_by_Descendant_Nodes_Property_XPath_only-Query_Execution"> + <section id="sect-Reference_Guide-Ordering_by_Descendant_Nodes_Property_XPath_only-Query_Execution"> <title>Query Execution</title> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Ordering_by_Descendant_Nodes_Property_XPath_only-Query_Execution-XPath"> + <example id="exam-Reference_Guide-Ordering_by_Descendant_Nodes_Property_XPath_only-Query_Execution-XPath"> <title>XPath</title> <programlisting language="Java" role="Java">// make XPath query @@ -55,7 +55,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Ordering_by_Descendant_Nodes_Property_XPath_only-Fetching_the_Result"> + <section id="sect-Reference_Guide-Ordering_by_Descendant_Nodes_Property_XPath_only-Fetching_the_Result"> <title>Fetching the Result</title> <para> To fetch the nodes: @@ -85,7 +85,7 @@ <para> Table content is: </para> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Ordering_by_Descendant_Nodes_Property_XPath_only-Fetching_the_Result-Table_content"> + <table id="tabl-Reference_Guide-Ordering_by_Descendant_Nodes_Property_XPath_only-Fetching_the_Result-Table_content"> <title>Table content</title> <tgroup cols="3"> <thead> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/order-by-path-or-name.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/order-by-path-or-name.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/order-by-path-or-name.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Ordering_by_Path_or_Name"> +<section id="sect-Reference_Guide-Ordering_by_Path_or_Name"> <title>Ordering by Path or Name</title> <warning> <para> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/order-by-property.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/order-by-property.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/order-by-property.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,18 +1,18 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Sorting_Nodes_by_Property"> +<section id="sect-Reference_Guide-Sorting_Nodes_by_Property"> <title>Sorting Nodes by Property</title> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Sorting_Nodes_by_Property-Task"> + <formalpara id="form-Reference_Guide-Sorting_Nodes_by_Property-Task"> <title>Task:</title> <para> Select all nodes with the mixin type <literal>mix:title</literal> and order them by the <parameter>prop_pagecount</parameter> property. </para> </formalpara> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Sorting_Nodes_by_Property-Repository_Structure"> + <section id="sect-Reference_Guide-Sorting_Nodes_by_Property-Repository_Structure"> <title>Repository Structure</title> <para> The repository contains several <literal>mix:title</literal> nodes, where <parameter>prop_pagecount</parameter> has different values. @@ -26,9 +26,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Sorting_Nodes_by_Property-Query_Execution"> + <section id="sect-Reference_Guide-Sorting_Nodes_by_Property-Query_Execution"> <title>Query Execution</title> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Sorting_Nodes_by_Property-Query_Execution-SQL"> + <example id="exam-Reference_Guide-Sorting_Nodes_by_Property-Query_Execution-SQL"> <title>SQL</title> <programlisting language="Java" role="Java">// make SQL query @@ -40,7 +40,7 @@ QueryResult result = query.execute();</programlisting> </example> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Sorting_Nodes_by_Property-Query_Execution-XPath"> + <example id="exam-Reference_Guide-Sorting_Nodes_by_Property-Query_Execution-XPath"> <title>XPath</title> <programlisting language="Java" role="Java">// make XPath query @@ -55,7 +55,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Sorting_Nodes_by_Property-Fetching_the_Result"> + <section id="sect-Reference_Guide-Sorting_Nodes_by_Property-Fetching_the_Result"> <title>Fetching the Result</title> <para> To fetch nodes: @@ -85,7 +85,7 @@ <para> Table content is: </para> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Sorting_Nodes_by_Property-Fetching_the_Result-Table_content"> + <table id="tabl-Reference_Guide-Sorting_Nodes_by_Property-Fetching_the_Result-Table_content"> <title>Table content</title> <tgroup cols="5"> <thead> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/order-by-score.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/order-by-score.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/order-by-score.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Ordering_by_Score"> +<section id="sect-Reference_Guide-Ordering_by_Score"> <title>Ordering by Score</title> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Ordering_by_Score-Task"> + <formalpara id="form-Reference_Guide-Ordering_by_Score-Task"> <title>Task:</title> <para> Select all nodes with the mixin type <literal>mix:title</literal> containing any word from the set {<emphasis>brown</emphasis>, <emphasis>fox</emphasis>, <emphasis>jumps</emphasis>}. Then, sort the results by their score in ascending node. This way nodes that are a closer match to the query statement are in the last positions in the result list. @@ -15,7 +15,7 @@ <para> </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Ordering_by_Score-Info"> + <section id="sect-Reference_Guide-Ordering_by_Score-Info"> <title>Info</title> <para> SQL and XPath queries both support score constructions <literal>jcr:score</literal> and <literal>jcr:score()</literal>. @@ -39,7 +39,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Ordering_by_Score-Repository_Structure"> + <section id="sect-Reference_Guide-Ordering_by_Score-Repository_Structure"> <title>Repository Structure</title> <para> The repository contains mix:title nodes, where the jcr:description has different values. @@ -53,9 +53,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Ordering_by_Score-Query_Execution"> + <section id="sect-Reference_Guide-Ordering_by_Score-Query_Execution"> <title>Query Execution</title> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Ordering_by_Score-Query_Execution-SQL"> + <example id="exam-Reference_Guide-Ordering_by_Score-Query_Execution-SQL"> <title>SQL</title> <programlisting language="Java" role="Java">// make SQL query @@ -67,7 +67,7 @@ QueryResult result = query.execute();</programlisting> </example> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Ordering_by_Score-Query_Execution-XPath"> + <example id="exam-Reference_Guide-Ordering_by_Score-Query_Execution-XPath"> <title>XPath</title> <programlisting language="Java" role="Java">// make XPath query @@ -82,7 +82,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Ordering_by_Score-Fetching_the_Result"> + <section id="sect-Reference_Guide-Ordering_by_Score-Fetching_the_Result"> <title>Fetching the Result</title> <para> To fetch the nodes: @@ -112,7 +112,7 @@ <para> Table content is: </para> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Ordering_by_Score-Fetching_the_Result-Table_content"> + <table id="tabl-Reference_Guide-Ordering_by_Score-Fetching_the_Result-Table_content"> <title>Table content</title> <tgroup cols="4"> <thead> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/property-comparison.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/property-comparison.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/property-comparison.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,18 +1,18 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Property_Comparison"> +<section id="sect-Reference_Guide-Property_Comparison"> <title>Property Comparison</title> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Property_Comparison-Task"> + <formalpara id="form-Reference_Guide-Property_Comparison-Task"> <title>Task:</title> <para> To find all nodes with mixin type <literal>mix:title</literal> where the <parameter>prop_pagecount</parameter> property contains a value less than <literal>90</literal>. Only select the title of each node. </para> </formalpara> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Property_Comparison-Repository_structure"> + <section id="sect-Reference_Guide-Property_Comparison-Repository_structure"> <title>Repository structure:</title> <para> Repository contains several <literal>mix:title</literal> nodes, where each <parameter>prop_pagecount</parameter> contains a different value. @@ -26,9 +26,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Property_Comparison-Query_execution"> + <section id="sect-Reference_Guide-Property_Comparison-Query_execution"> <title>Query execution</title> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Property_Comparison-Query_execution-SQL"> + <example id="exam-Reference_Guide-Property_Comparison-Query_execution-SQL"> <title>SQL</title> <programlisting language="Java" role="Java">// make SQL query @@ -40,7 +40,7 @@ QueryResult result = query.execute();</programlisting> </example> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Property_Comparison-Query_execution-XPath"> + <example id="exam-Reference_Guide-Property_Comparison-Query_execution-XPath"> <title>XPath</title> <programlisting language="Java" role="Java">// make XPath query @@ -55,7 +55,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Property_Comparison-Fetching_result"> + <section id="sect-Reference_Guide-Property_Comparison-Fetching_result"> <title>Fetching result</title> <para> To fetch nodes: @@ -84,7 +84,7 @@ }</programlisting> <para> The table content is: - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Property_Comparison-Fetching_result-Table_Content"> + <table id="tabl-Reference_Guide-Property_Comparison-Fetching_result-Table_Content"> <title>Table Content</title> <tgroup cols="3"> <thead> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/property-existance-constraint.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/property-existance-constraint.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/property-existance-constraint.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Property_Existence_Constraint"> +<section id="sect-Reference_Guide-Property_Existence_Constraint"> <title>Property Existence Constraint</title> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Property_Existence_Constraint-Task"> + <formalpara id="form-Reference_Guide-Property_Existence_Constraint-Task"> <title>Task:</title> <para> Find all nodes with a mixin type '<literal>mix:title</literal>' where the property <parameter>jcr:description</parameter> does not exist (is null). @@ -15,7 +15,7 @@ <para> </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Property_Existence_Constraint-Repository_Structure"> + <section id="sect-Reference_Guide-Property_Existence_Constraint-Repository_Structure"> <title>Repository Structure</title> <para> The repository contains <literal>mix:title</literal> nodes, in one of these nodes the <literal>jcr:description</literal> property is null. @@ -29,9 +29,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Property_Existence_Constraint-Query_Execution"> + <section id="sect-Reference_Guide-Property_Existence_Constraint-Query_Execution"> <title>Query Execution</title> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Property_Existence_Constraint-Query_Execution-SQL"> + <example id="exam-Reference_Guide-Property_Existence_Constraint-Query_Execution-SQL"> <title>SQL</title> <programlisting language="Java" role="Java">// make SQL query @@ -42,7 +42,7 @@ // execute query and fetch result QueryResult result = query.execute();</programlisting> </example> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Property_Existence_Constraint-Query_Execution-XPath"> + <example id="exam-Reference_Guide-Property_Existence_Constraint-Query_Execution-XPath"> <title>XPath</title> <programlisting language="Java" role="Java">// make XPath query @@ -56,7 +56,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Property_Existence_Constraint-Fetching_the_Result"> + <section id="sect-Reference_Guide-Property_Existence_Constraint-Fetching_the_Result"> <title>Fetching the Result</title> <para> To fetch the nodes: @@ -85,7 +85,7 @@ }</programlisting> <para> Table content is: - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Property_Existence_Constraint-Fetching_the_Result-Table_content"> + <table id="tabl-Reference_Guide-Property_Existence_Constraint-Fetching_the_Result-Table_content"> <title>Table content</title> <tgroup cols="4"> <thead> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/regexp-indexing-rule.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/regexp-indexing-rule.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/regexp-indexing-rule.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Regular_Expression_as_Property_Name_in_Indexing_Rules"> +<section id="sect-Reference_Guide-Regular_Expression_as_Property_Name_in_Indexing_Rules"> <title>Regular Expression as Property Name in Indexing Rules</title> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Regular_Expression_as_Property_Name_in_Indexing_Rules-Task"> + <formalpara id="form-Reference_Guide-Regular_Expression_as_Property_Name_in_Indexing_Rules-Task"> <title>Task:</title> <para> To configure indexing so that all properties of <literal>nt:unstructured</literal> nodes must be excluded from searches, except properties with names ending with a particular <emphasis>Text</emphasis> string. @@ -20,9 +20,9 @@ <property isRegexp="true">.*Text</property> </index-rule></programlisting> <para> - See <xref linkend="chap-Reference_Guide_eXo_JCR_1.14-Search_Configuration" /> for more information. + See <xref linkend="chap-Reference_Guide-Search_Configuration" /> for more information. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Regular_Expression_as_Property_Name_in_Indexing_Rules-Repository_structure"> + <section id="sect-Reference_Guide-Regular_Expression_as_Property_Name_in_Indexing_Rules-Repository_structure"> <title>Repository structure:</title> <para> The repository contains <literal>nt:unstructured</literal> nodes, with different <parameter>text</parameter>-based properties: @@ -36,9 +36,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Regular_Expression_as_Property_Name_in_Indexing_Rules-Query_execution"> + <section id="sect-Reference_Guide-Regular_Expression_as_Property_Name_in_Indexing_Rules-Query_execution"> <title>Query execution</title> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Regular_Expression_as_Property_Name_in_Indexing_Rules-Query_execution-SQL"> + <example id="exam-Reference_Guide-Regular_Expression_as_Property_Name_in_Indexing_Rules-Query_execution-SQL"> <title>SQL</title> <programlisting language="Java" role="Java">// make SQL query @@ -50,7 +50,7 @@ QueryResult result = query.execute();</programlisting> </example> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Regular_Expression_as_Property_Name_in_Indexing_Rules-Query_execution-XPath"> + <example id="exam-Reference_Guide-Regular_Expression_as_Property_Name_in_Indexing_Rules-Query_execution-XPath"> <title>XPath</title> <programlisting language="Java" role="Java">// make XPath query @@ -65,7 +65,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Regular_Expression_as_Property_Name_in_Indexing_Rules-Fetching_result"> + <section id="sect-Reference_Guide-Regular_Expression_as_Property_Name_in_Indexing_Rules-Fetching_result"> <title>Fetching result</title> <para> To fetch the nodes: @@ -95,7 +95,7 @@ <para> Table content is: </para> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Regular_Expression_as_Property_Name_in_Indexing_Rules-Fetching_result-Table_content"> + <table id="tabl-Reference_Guide-Regular_Expression_as_Property_Name_in_Indexing_Rules-Fetching_result-Table_content"> <title>Table content</title> <tgroup cols="3"> <thead> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/searching-repository-content.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/searching-repository-content.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/searching-repository-content.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,22 +1,22 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Searching_Repository_Content"> +<chapter id="chap-Reference_Guide-Searching_Repository_Content"> <title>Searching Repository Content</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Searching_Repository_Content-Introduction"> + <section id="sect-Reference_Guide-Searching_Repository_Content-Introduction"> <title>Introduction</title> <para> You can find the JCR configuration file here: <filename><replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/02portal.war/portal/WEB-INF/conf/jcr/repository-configuration.xml</filename>. </para> <para> - Please refer to <xref linkend="chap-Reference_Guide_eXo_JCR_1.14-Search_Configuration" /> for more information about index configuration. + Please refer to <xref linkend="chap-Reference_Guide-Search_Configuration" /> for more information about index configuration. </para> </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Searching_Repository_Content-Bi_directional_RangeIterator"> + <section id="sect-Reference_Guide-Searching_Repository_Content-Bi_directional_RangeIterator"> <title>Bi-directional RangeIterator</title> <para> <literal>QueryResult.getNodes()</literal> will return bi-directional <literal>NodeIterator</literal> implementation. @@ -71,7 +71,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Searching_Repository_Content-Fuzzy_Searches"> + <section id="sect-Reference_Guide-Searching_Repository_Content-Fuzzy_Searches"> <title>Fuzzy Searches</title> <para> The JBoss Enterprise Portal Platform JCR supports features such as Lucene Fuzzy Searches. To perform a fuzzy search, form your query like the one below: @@ -83,7 +83,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Searching_Repository_Content-SynonymSearch"> + <section id="sect-Reference_Guide-Searching_Repository_Content-SynonymSearch"> <title>SynonymSearch</title> <para> Searching with synonyms is integrated in the <literal>jcr:contains()</literal> function and uses the same syntax as synonym searches in web search engines (Google, for example). If a search term is prefixed by a tilde symbol ( ~ ), synonyms of the search term are taken into consideration. For example: @@ -131,7 +131,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Searching_Repository_Content-Highlighting"> + <section id="sect-Reference_Guide-Searching_Repository_Content-Highlighting"> <title>Highlighting</title> <para> An <literal>ExcerptProvider</literal> retrieves text excerpts for a node in the query result and marks up the words in the text that match the query terms. @@ -149,7 +149,7 @@ </para> <programlisting language="XML" role="XML"><param name="excerptprovider-class" value="org.exoplatform.services.jcr.impl.core.query.lucene.DefaultXMLExcerpt"/></programlisting> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Highlighting-DefaultXMLExcerpt"> + <section id="sect-Reference_Guide-Highlighting-DefaultXMLExcerpt"> <title>DefaultXMLExcerpt</title> <para> This excerpt provider creates an XML fragment of the following form: @@ -168,7 +168,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Highlighting-DefaultHTMLExcerpt"> + <section id="sect-Reference_Guide-Highlighting-DefaultHTMLExcerpt"> <title>DefaultHTMLExcerpt</title> <para> This excerpt provider creates an HTML fragment of the following form: @@ -187,7 +187,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Highlighting-Usage"> + <section id="sect-Reference_Guide-Highlighting-Usage"> <title>Usage</title> <para> If you are using XPath, you must use the <code>rep:excerpt()</code> function in the last location step, just like you would select properties: @@ -227,13 +227,13 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Searching_Repository_Content-SpellChecker"> + <section id="sect-Reference_Guide-Searching_Repository_Content-SpellChecker"> <title>SpellChecker</title> <para> The lucene based query handler implementation supports a pluggable spell-checker mechanism. By default, spell checking is not available, it must be configured first. </para> <para> - Information about the <parameter>spellCheckerClass</parameter> parameter is available in <xref linkend="chap-Reference_Guide_eXo_JCR_1.14-Search_Configuration" />. + Information about the <parameter>spellCheckerClass</parameter> parameter is available in <xref linkend="chap-Reference_Guide-Search_Configuration" />. </para> <para> The JCR currently provides an implementation class which uses the <ulink url="http://wiki.apache.org/jakarta-lucene/SpellChecker">lucene-spellchecker</ulink>. @@ -295,7 +295,7 @@ <para> The spell checker dictionary is stored as a lucene index under <filename><index-dir>/spellchecker</filename>. If this index does not exist, a background thread will create it on start up. Similarly, the dictionary refresh is also done in a background thread so as not to block regular queries. </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-SpellChecker-Usage"> + <section id="sect-Reference_Guide-SpellChecker-Usage"> <title>Usage</title> <para> You can spell check a fulltext statement either with an XPath or a SQL query: @@ -337,7 +337,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Searching_Repository_Content-Similarity"> + <section id="sect-Reference_Guide-Searching_Repository_Content-Similarity"> <title>Similarity</title> <para> Starting with version, 1.12 JCR allows you to search for nodes that are similar to an existing node. @@ -412,7 +412,7 @@ </para> </warning> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Similarity-Example"> + <example id="exam-Reference_Guide-Similarity-Example"> <title>Example</title> <programlisting>//element(*, nt:resource)[rep:similar(., '/parentnode/node.txt/jcr:content')]</programlisting> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/spell-checker.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/spell-checker.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/spell-checker.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Checking_the_spelling_of_Phrase"> +<section id="sect-Reference_Guide-Checking_the_spelling_of_Phrase"> <title>Checking the spelling of Phrase</title> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Checking_the_spelling_of_Phrase-Task"> + <formalpara id="form-Reference_Guide-Checking_the_spelling_of_Phrase-Task"> <title>Task:</title> <para> Check the correct spelling of phrase '<emphasis>quik OR (-foo bar)</emphasis>' according to data already stored in index. @@ -14,14 +14,14 @@ </formalpara> <note> <para> - Refer to <xref linkend="chap-Reference_Guide_eXo_JCR_1.14-Searching_Repository_Content" /> for information about SpellChecker configuration. + Refer to <xref linkend="chap-Reference_Guide-Searching_Repository_Content" /> for information about SpellChecker configuration. </para> </note> <para> The SpellChecker must be set in query-handler configuration. </para> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Checking_the_spelling_of_Phrase-test_jcr_config.xml"> + <example id="exam-Reference_Guide-Checking_the_spelling_of_Phrase-test_jcr_config.xml"> <title>test-jcr-config.xml:</title> <programlisting language="XML" role="XML"><query-handler class="org.exoplatform.services.jcr.impl.core.query.lucene.SearchIndex"> @@ -32,7 +32,7 @@ </properties> </query-handler></programlisting> </example> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Checking_the_spelling_of_Phrase-Repository_structure"> + <section id="sect-Reference_Guide-Checking_the_spelling_of_Phrase-Repository_structure"> <title>Repository structure:</title> <para> Repository contains node, with string property "The quick brown fox jumps over the lazy dog." @@ -44,12 +44,12 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Checking_the_spelling_of_Phrase-Query_execution"> + <section id="sect-Reference_Guide-Checking_the_spelling_of_Phrase-Query_execution"> <title>Query execution</title> <para> The query looks only for the <literal>root</literal> node, because the spell checker looks for suggestions by full index. Therefore a complicated query is unecessary. </para> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Checking_the_spelling_of_Phrase-Query_execution-SQL"> + <example id="exam-Reference_Guide-Checking_the_spelling_of_Phrase-Query_execution-SQL"> <title>SQL</title> <programlisting language="Java" role="Java">// make SQL query @@ -60,7 +60,7 @@ // execute query and fetch result QueryResult result = query.execute();</programlisting> </example> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Checking_the_spelling_of_Phrase-Query_execution-XPath"> + <example id="exam-Reference_Guide-Checking_the_spelling_of_Phrase-Query_execution-XPath"> <title>XPath</title> <programlisting language="Java" role="Java">// make XPath query @@ -74,7 +74,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Checking_the_spelling_of_Phrase-Fetching_result"> + <section id="sect-Reference_Guide-Checking_the_spelling_of_Phrase-Fetching_result"> <title>Fetching result</title> <para> To get suggestions of the correct spelling of the nominated phrase: Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/synonim-provider.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/synonim-provider.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/synonim-provider.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Searching_By_Synonym"> +<section id="sect-Reference_Guide-Searching_By_Synonym"> <title>Searching By Synonym</title> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Searching_By_Synonym-Task"> + <formalpara id="form-Reference_Guide-Searching_By_Synonym-Task"> <title>Task:</title> <para> Find all <literal>mix:title</literal> nodes whose title contains a synonym for the term <emphasis>fast</emphasis>. @@ -14,7 +14,7 @@ </formalpara> <note> <para> - Refer to <xref linkend="chap-Reference_Guide_eXo_JCR_1.14-Searching_Repository_Content" /> for information about synonym provider configuration + Refer to <xref linkend="chap-Reference_Guide-Searching_Repository_Content" /> for information about synonym provider configuration </para> </note> @@ -33,14 +33,14 @@ <para> The <filename>synonym.properties</filename> file contains the synonyms list: </para> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Searching_By_Synonym-Example_Synonym_List"> + <example id="exam-Reference_Guide-Searching_By_Synonym-Example_Synonym_List"> <title>Example Synonym List</title> <programlisting>ASF=Apache Software Foundation quick=fast sluggish=lazy</programlisting> </example> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Searching_By_Synonym-Repository_structure"> + <section id="sect-Reference_Guide-Searching_By_Synonym-Repository_structure"> <title>Repository structure:</title> <para> the repository contains <literal>mix:title</literal> nodes, where <literal>jcr:title</literal> has different values. @@ -52,9 +52,9 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Searching_By_Synonym-Query_execution"> + <section id="sect-Reference_Guide-Searching_By_Synonym-Query_execution"> <title>Query execution</title> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Searching_By_Synonym-Query_execution-SQL"> + <example id="exam-Reference_Guide-Searching_By_Synonym-Query_execution-SQL"> <title>SQL</title> <programlisting language="Java" role="Java">// make SQL query @@ -65,7 +65,7 @@ // execute query and fetch result QueryResult result = query.execute();</programlisting> </example> - <example id="exam-Reference_Guide_eXo_JCR_1.14-Searching_By_Synonym-Query_execution-XPath"> + <example id="exam-Reference_Guide-Searching_By_Synonym-Query_execution-XPath"> <title>XPath</title> <programlisting language="Java" role="Java">// make XPath query @@ -79,7 +79,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Searching_By_Synonym-Fetching_result"> + <section id="sect-Reference_Guide-Searching_By_Synonym-Fetching_result"> <title>Fetching result</title> <para> To fetch nodes: Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/tip-nodename-with-number.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/tip-nodename-with-number.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/searching/tip-nodename-with-number.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-XPath_queries_containing_node_names_starting_with_a_number"> +<section id="sect-Reference_Guide-XPath_queries_containing_node_names_starting_with_a_number"> <title>XPath queries containing node names starting with a number</title> <para> If you execute an XPath request like this... 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-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/statistics.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-eXo_JCR_statistics"> +<chapter id="chap-Reference_Guide-eXo_JCR_statistics"> <title>eXo JCR statistics</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-eXo_JCR_statistics-Statistics_on_the_Database_Access_Layer"> + <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. @@ -64,7 +64,7 @@ <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_eXo_JCR_1.14-Statistics_on_the_Database_Access_Layer-Method_Alias"> + <table id="tabl-Reference_Guide-Statistics_on_the_Database_Access_Layer-Method_Alias"> <title>Method Alias</title> <tgroup cols="2"> <tbody> @@ -248,7 +248,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-eXo_JCR_statistics-Statistics_on_the_JCR_API_accesses"> + <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. @@ -345,7 +345,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-eXo_JCR_statistics-Statistics_Manager"> + <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. @@ -354,7 +354,7 @@ 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_eXo_JCR_1.14-Statistics_Manager-Metric_Alias"> + <table id="tabl-Reference_Guide-Statistics_Manager-Metric_Alias"> <title>Metric Alias</title> <tgroup cols="2"> <tbody> @@ -418,7 +418,7 @@ You can also access to the statistics via JMX. The available methods are: </para> <para> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Statistics_Manager-JMX_Methods"> + <table id="tabl-Reference_Guide-Statistics_Manager-JMX_Methods"> <title>JMX Methods</title> <tgroup cols="2"> <tbody> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/transaction-manager-lookup.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/transaction-manager-lookup.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr/transaction-manager-lookup.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-TransactionManagerLookup"> +<chapter id="chap-Reference_Guide-TransactionManagerLookup"> <title>TransactionManagerLookup</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-TransactionManagerLookup-Configuration"> + <section id="sect-Reference_Guide-TransactionManagerLookup-Configuration"> <title>Configuration</title> <para> <literal>TransactionManagerLookup</literal> is a JBossCache class registered as an eXo container component in the <filename>configuration.xml</filename> file. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr-with-gatein.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr-with-gatein.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr-with-gatein.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-eXo_JCR_with_GateIn"> +<chapter id="chap-Reference_Guide-eXo_JCR_with_GateIn"> <title>eXo JCR with GateIn</title>  <xi:include href="jcr-with-gtn/managed-datasources-under-jboss-as.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> </chapter> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr-with-gtn/managed-datasources-under-jboss-as.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr-with-gtn/managed-datasources-under-jboss-as.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/jcr-with-gtn/managed-datasources-under-jboss-as.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,13 +1,13 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-How_to_use_AS_Managed_DataSource_under_JBoss_AS"> +<section id="sect-Reference_Guide-How_to_use_AS_Managed_DataSource_under_JBoss_AS"> <title>How to use AS Managed DataSource under JBoss AS</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-How_to_use_AS_Managed_DataSource_under_JBoss_AS-Configurations_Steps"> + <section id="sect-Reference_Guide-How_to_use_AS_Managed_DataSource_under_JBoss_AS-Configurations_Steps"> <title>Configurations Steps</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configurations_Steps-Declaring_the_datasources_in_the_AS"> + <section id="sect-Reference_Guide-Configurations_Steps-Declaring_the_datasources_in_the_AS"> <title>Declaring the datasources in the AS</title> <para> To declare the datasources using a JBoss application server, deploy a <literal>ds</literal> file (<filename><replaceable>XXX</replaceable>-ds.xml</filename>) into the <emphasis>deploy</emphasis> directory of the appropriate server profile (<filename>\server\<replaceable><PROFILE></replaceable>\deploy</filename>, for example). @@ -59,7 +59,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configurations_Steps-Do_not_bind_datasources_explicitly"> + <section id="sect-Reference_Guide-Configurations_Steps-Do_not_bind_datasources_explicitly"> <title>Do not bind datasources explicitly</title> <para> Do not let the portal explicitly bind datasources. Edit the <filename><replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/conf/gatein/configuration.properties</filename> and comment out the following rows in the JCR section: Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/ws/framework-for-cross-domain-ajax.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/ws/framework-for-cross-domain-ajax.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/ws/framework-for-cross-domain-ajax.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,14 +1,14 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Framework_for_cross_domain_AJAX"> +<chapter id="chap-Reference_Guide-Framework_for_cross_domain_AJAX"> <title>Framework for cross-domain AJAX</title> <para> (<ulink url="https://anonsvn.jboss.org/repos/exo-jcr/ws/trunk/exo.ws.frameworks.javasc...">https://anonsvn.jboss.org/repos/exo-jcr/ws/trunk/exo.ws.frameworks.javasc...</ulink>) </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Framework_for_cross_domain_AJAX-Motivation"> + <section id="sect-Reference_Guide-Framework_for_cross_domain_AJAX-Motivation"> <title>Motivation</title> <para> XmlHttpRequest objects are bound by the same origin security policy of browsers, which prevents a page from accessing data from another server. This has put a serious limitation on Ajax developers: you can use XmlHttpRequests to make background calls to a server, but it has to be the same server that served up the current page. For more details, you can visit <ulink url="http://www.mozilla.org/projects/security/components/same-origin.html">http://www.mozilla.org/projects/security/components/same-origin.html</ulink>. @@ -25,7 +25,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Framework_for_cross_domain_AJAX-Scheme_how_it_works"> + <section id="sect-Reference_Guide-Framework_for_cross_domain_AJAX-Scheme_how_it_works"> <title>Scheme (how it works)</title> <para> To describe our method for cross-domain AJAX solution, let's consider the following scheme contains of 3 components: @@ -48,7 +48,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Framework_for_cross_domain_AJAX-A_Working_Sequence"> + <section id="sect-Reference_Guide-Framework_for_cross_domain_AJAX-A_Working_Sequence"> <title>A Working Sequence:</title> <para> 1) A Browser requests the Start page from the ServerA @@ -74,7 +74,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Framework_for_cross_domain_AJAX-How_to_use_it"> + <section id="sect-Reference_Guide-Framework_for_cross_domain_AJAX-How_to_use_it"> <title>How to use it</title> <para> 1). Place the file client.html and xda.js on the serverA. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/ws/groovy-scripts-as-rest-services.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/ws/groovy-scripts-as-rest-services.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/ws/groovy-scripts-as-rest-services.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Groovy_Scripts_as_REST_Services"> +<chapter id="chap-Reference_Guide-Groovy_Scripts_as_REST_Services"> <title>Groovy Scripts as REST Services</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Groovy_Scripts_as_REST_Services-Overview"> + <section id="sect-Reference_Guide-Groovy_Scripts_as_REST_Services-Overview"> <title>Overview</title> <para> This article describes how to use Groovy scripts as REST services. We are going to consider these operations: @@ -49,7 +49,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Groovy_Scripts_as_REST_Services-Loading_script_and_save_it_in_JCR"> + <section id="sect-Reference_Guide-Groovy_Scripts_as_REST_Services-Loading_script_and_save_it_in_JCR"> <title>Loading script and save it in JCR</title> <para> There are two ways to save a script in JCR. The first way is to save it at server startup time by using configuration.xml and the second way is to upload the script via HTTP. @@ -115,7 +115,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Groovy_Scripts_as_REST_Services-Instantiation"> + <section id="sect-Reference_Guide-Groovy_Scripts_as_REST_Services-Instantiation"> <title>Instantiation</title> <para> org.exoplatform.services.script.groovy.GroovyScriptInstantiator is part of project exo.core.component.script.groovy. GroovyScriptInstantiator can load script from specified URL and parse stream that contains Groovy source code. It has possibility inject component from Container in Groovy Class constructor. Configuration example: @@ -127,7 +127,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Groovy_Scripts_as_REST_Services-Deploying_newly_created_Class_as_RESTful_service"> + <section id="sect-Reference_Guide-Groovy_Scripts_as_REST_Services-Deploying_newly_created_Class_as_RESTful_service"> <title>Deploying newly created Class as RESTful service</title> <para> To deploy script automatically at server startup time, its property exo:autoload must be set as true. org.exoplatform.services.jcr.ext.script.groovy.GroovyScript2RestLoader check JCR workspaces which were specified in configuration and deploy all auto-loadable scripts. @@ -162,7 +162,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Groovy_Scripts_as_REST_Services-Script_Lifecycle_Management"> + <section id="sect-Reference_Guide-Groovy_Scripts_as_REST_Services-Script_Lifecycle_Management"> <title>Script Lifecycle Management</title> <para> If GroovyScript2RestLoader configured as was decribed in the previous section, then all "autoload" scripts deployed. In the first section, we added script from file /home/andrew/JcrGroovyTest.groovy to JCR node /script/groovy/JcrGroovyTest.groovy, repository repository, workspace production. In section "Load script via HTTP", it was referred about load scripts via HTTP, there is an opportunity to manage the life cycle of script. @@ -236,7 +236,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Groovy_Scripts_as_REST_Services-Getting_node_UUID_example"> + <section id="sect-Reference_Guide-Groovy_Scripts_as_REST_Services-Getting_node_UUID_example"> <title>Getting node UUID example</title> <para> Now we are going to try simple example of Groovy RESTfull service. There is one limitation, even if we use groovy, we should use Java style code and decline to use dynamic types, but of course we can use it in private methods and fields. Create file JcrGroovyTest.groovy, in this example I save it in my home directory /home/andrew/JcrGroovyTest.groovy. Then, configure GroovyScript2RestLoaderPlugin as described in section Load script at startup time. @@ -365,7 +365,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Groovy_Scripts_as_REST_Services-Groovy_script_restrictions"> + <section id="sect-Reference_Guide-Groovy_Scripts_as_REST_Services-Groovy_script_restrictions"> <title>Groovy script restrictions</title> <para> You should keep one class per one groovy file. The same actually for interface and it implementation. It's limitation of groovy parser that does not have type Class[] parseClass(InputStream) or Collection parseClass(InputStream) but only Class parseClass(InputStream) instead. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/ws/introduction-to-rest.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/ws/introduction-to-rest.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/ws/introduction-to-rest.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Introduction_to_the_Representational_State_Transfer_REST"> +<chapter id="chap-Reference_Guide-Introduction_to_the_Representational_State_Transfer_REST"> <title>Introduction to the Representational State Transfer (REST)</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Introduction_to_the_Representational_State_Transfer_REST-Introduction"> + <section id="sect-Reference_Guide-Introduction_to_the_Representational_State_Transfer_REST-Introduction"> <title>Introduction</title> <para> <command>Representational State Transfer (REST)</command> is a style of software architecture for distributed hypermedia systems such as the World Wide Web. The term was introduced in the doctoral dissertation in 2000 by Roy Fielding, one of the principal authors of the Hypertext Transfer Protocol (HTTP) specification, and has come into widespread use in the networking community. @@ -22,7 +22,7 @@ <para> REST components perform actions with a resource by using a <command>representation</command> to capture the current or intended state of that resource and transferring that representation between components. A representation is a sequence of bytes, plus <command>representation metadata </command>to describe those bytes. Other commonly used but less precise names for a representation include: <command>document, file, and HTTP message entity, instance, or variant</command>. A representation consists of data, metadata describing the data, and, on occasion, metadata to describe the metadata (usually for the purpose of verifying message integrity). Metadata are in the form of name-value pairs, where the name corresponds to a standard that defines the value's structure and semantics. The data format of a representation is known as a media type. </para> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Introduction-REST_Data_Elements"> + <table id="tabl-Reference_Guide-Introduction-REST_Data_Elements"> <title>REST Data Elements</title> <tgroup cols="2"> <thead> @@ -101,7 +101,7 @@ <para> REST uses various <command>connector</command> types to encapsulate the activities of accessing resources and transferring resource representations. The connectors present an abstract interface for component communication, enhancing simplicity by providing a complete separation of concepts and hiding the underlying implementation of resources and communication mechanisms. </para> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Introduction-REST_Connectors"> + <table id="tabl-Reference_Guide-Introduction-REST_Connectors"> <title>REST Connectors</title> <tgroup cols="2"> <thead> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/ws/overwrite-default-providers.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/ws/overwrite-default-providers.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/ws/overwrite-default-providers.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-OverwriteDefaultProviders"> +<chapter id="chap-Reference_Guide-OverwriteDefaultProviders"> <title>OverwriteDefaultProviders</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-OverwriteDefaultProviders-Motivation"> + <section id="sect-Reference_Guide-OverwriteDefaultProviders-Motivation"> <title>Motivation</title> <para> There is set of providers embedded in eXo JAX-RS implementation. @@ -16,7 +16,7 @@ <para> The next set of media and Java types processed automatically, thanks to embedded Readers (Writers). </para> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-Motivation-Embedded_Reader_and_Writers_of_message_body"> + <table id="tabl-Reference_Guide-Motivation-Embedded_Reader_and_Writers_of_message_body"> <title>Embedded Reader and Writers of message body</title> <tgroup cols="2"> <colspec align="center"></colspec> @@ -180,7 +180,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-OverwriteDefaultProviders-Usage"> + <section id="sect-Reference_Guide-OverwriteDefaultProviders-Usage"> <title>Usage</title> <para> To be able overwrite default JAX-RS provider(s) developer need: @@ -209,7 +209,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-OverwriteDefaultProviders-Example"> + <section id="sect-Reference_Guide-OverwriteDefaultProviders-Example"> <title>Example</title> <para> In example below see how to use Jackson JSON provider instead of embedded in eXo RESTful framework. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/ws/restservicelist-service.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/ws/restservicelist-service.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/ws/restservicelist-service.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-RestServicesList_Service"> +<chapter id="chap-Reference_Guide-RestServicesList_Service"> <title>RestServicesList Service</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-RestServicesList_Service-Overview."> + <section id="sect-Reference_Guide-RestServicesList_Service-Overview."> <title>Overview.</title> <para> RestServicesList service is intended to provide information about rest services deployed to the application server. @@ -37,7 +37,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-RestServicesList_Service-Usage"> + <section id="sect-Reference_Guide-RestServicesList_Service-Usage"> <title>Usage</title> <note> <para> @@ -45,7 +45,7 @@ </para> </note> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Usage-HTML_format"> + <section id="sect-Reference_Guide-Usage-HTML_format"> <title>HTML format</title> <para> To get the list of services in HTML format use listHTML() method: @@ -108,7 +108,7 @@ <para> If you perform the same request with your browser, you'll see the table with the list of deployed services like this: </para> - <table id="tabl-Reference_Guide_eXo_JCR_1.14-HTML_format-Root_resources"> + <table id="tabl-Reference_Guide-HTML_format-Root_resources"> <title>Root resources</title> <tgroup cols="3"> <thead> @@ -196,7 +196,7 @@ </section> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Usage-JSON_format"> + <section id="sect-Reference_Guide-Usage-JSON_format"> <title>JSON format</title> <para> To get the list of services in HTML format use listJSON() method: Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/ws/ws.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/ws/ws.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/ws/ws.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,11 +1,11 @@ <?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 "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-eXo_Web_Services"> +<chapter id="chap-Reference_Guide-eXo_Web_Services"> <title>eXo Web Services</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-eXo_Web_Services-eXo_Web_Services_introduction"> + <section id="sect-Reference_Guide-eXo_Web_Services-eXo_Web_Services_introduction"> <title>eXo Web Services introduction</title> <para> The Web Services module allows eXo technology to integrate with external products and services. Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/ws.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/ws.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR/ws.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-eXoWS"> +<section id="sect-Reference_Guide-eXoWS"> <title>eXoWS</title> <xi:include href="ws/ws.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> <xi:include href="ws/introduction-to-rest.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> Modified: epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR.xml 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/eXoJCR.xml 2011-11-25 01:13:48 UTC (rev 8142) @@ -1,9 +1,9 @@ <?xml version='1.0' encoding='utf-8' ?> <!DOCTYPE part PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide.ent"> %BOOK_ENTITIES; ]> -<part id="part-Reference_Guide_eXo_JCR_1.14-The_Java_Content_Repository_"> +<part id="part-Reference_Guide-The_Java_Content_Repository_"> <title><remark>The Java Content Repository</remark> </title>  <xi:include href="eXoJCR/jcr/intro.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> Modified: epp/docs/branches/5.2/Reference_Guide/publican.cfg =================================================================== --- epp/docs/branches/5.2/Reference_Guide/publican.cfg 2011-11-25 00:48:53 UTC (rev 8141) +++ epp/docs/branches/5.2/Reference_Guide/publican.cfg 2011-11-25 01:13:48 UTC (rev 8142) @@ -4,7 +4,7 @@ cvs_root: ":ext:cvs.devel.redhat.com:/cvs/dist" cvs_branch: "DOCS-RHEL-6" show_remarks: 1 -cvs_pkg: "JBoss_Enterprise_Portal_Platform-Reference_Guide_eXo_JCR_1.14-5.2-web-__LANG__" +cvs_pkg: "JBoss_Enterprise_Portal_Platform-Reference_Guide-5.2-web-__LANG__" xml_lang: "en-US" brand: JBoss debug: 1

13 years, 1 month

1
0
0 / 0

gatein SVN: r8141 - in epp/docs/branches/5.2: Reference_Guide/en-US and 4 other directories.

by do-not-reply＠jboss.org

Author: smumford Date: 2011-11-24 19:48:53 -0500 (Thu, 24 Nov 2011) New Revision: 8141 Added: epp/docs/branches/5.2/Reference_Guide/ epp/docs/branches/5.2/Reference_Guide/en-US/Author_Group.xml epp/docs/branches/5.2/Reference_Guide/en-US/Book_Info.xml epp/docs/branches/5.2/Reference_Guide/en-US/Revision_History.xml epp/docs/branches/5.2/Reference_Guide/en-US/images/WSRP/config_self.png epp/docs/branches/5.2/Reference_Guide/en-US/images/WSRP/modify_reg_end.png epp/docs/branches/5.2/Reference_Guide/en-US/images/WSRP/modify_reg_self_end.png 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/RH-WSRP.xml epp/docs/branches/5.2/Reference_Guide/en-US/modules/WSRP.xml Removed: epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/ epp/docs/branches/5.2/Reference_Guide/en-US/Author_Group.xml epp/docs/branches/5.2/Reference_Guide/en-US/Book_Info.xml epp/docs/branches/5.2/Reference_Guide/en-US/Revision_History.xml epp/docs/branches/5.2/Reference_Guide/en-US/images/WSRP/config_self.png epp/docs/branches/5.2/Reference_Guide/en-US/images/WSRP/modify_reg_end.png epp/docs/branches/5.2/Reference_Guide/en-US/images/WSRP/modify_reg_self_end.png 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/WSRP.xml Log: Moving Ref_Guide_eXo to Ref_Guide Deleted: epp/docs/branches/5.2/Reference_Guide/en-US/Author_Group.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/Author_Group.xml 2011-11-24 17:26:22 UTC (rev 8138) +++ epp/docs/branches/5.2/Reference_Guide/en-US/Author_Group.xml 2011-11-25 00:48:53 UTC (rev 8141) @@ -1,57 +0,0 @@ -<?xml version='1.0' encoding='utf-8' ?> -<!DOCTYPE authorgroup PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> -%BOOK_ENTITIES; -]> -<authorgroup> - <editor> - <firstname>Luc</firstname> - <surname>Texier</surname> - <affiliation> - <shortaffil>Red Hat</shortaffil> - <orgdiv>JBoss Engineering</orgdiv> - - </affiliation> - - </editor> - <editor> - <firstname>Thomas</firstname> - <surname>Heute</surname> - <affiliation> - <shortaffil>Red Hat</shortaffil> - <orgdiv>JBoss Engineering</orgdiv> - - </affiliation> - - </editor> - <editor> - <firstname>Wesley</firstname> - <surname>Hales</surname> - <affiliation> - <shortaffil>Red Hat</shortaffil> - <orgdiv>JBoss Engineering</orgdiv> - - </affiliation> - - </editor> - <editor> - <firstname>Scott</firstname> - <surname>Mumford</surname> - <affiliation> - <shortaffil>Red Hat</shortaffil> - <orgdiv>Engineering Content Services</orgdiv> - - </affiliation> - - </editor> - <othercredit> - <affiliation> - <orgname><emphasis role="bold"><ulink type="http" url="http://www.jboss.org/gatein/">GateIn</ulink></emphasis> and <emphasis role="bold"><ulink type="http" url="http://www.exoplatform.com">eXo Platform</ulink></emphasis></orgname> - <orgdiv>Documentation Teams</orgdiv> - - </affiliation> - <contrib>Based on original product documentation by:</contrib> - - </othercredit> -</authorgroup> - Copied: epp/docs/branches/5.2/Reference_Guide/en-US/Author_Group.xml (from rev 8139, epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/Author_Group.xml) =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/Author_Group.xml (rev 0) +++ epp/docs/branches/5.2/Reference_Guide/en-US/Author_Group.xml 2011-11-25 00:48:53 UTC (rev 8141) @@ -0,0 +1,67 @@ +<?xml version='1.0' encoding='utf-8' ?> +<!DOCTYPE authorgroup PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +%BOOK_ENTITIES; +]> +<authorgroup> + <editor> + <firstname>Luc</firstname> + <surname>Texier</surname> + <affiliation> + <shortaffil>Red Hat</shortaffil> + <orgdiv>JBoss Engineering</orgdiv> + + </affiliation> + + </editor> + <editor> + <firstname>Thomas</firstname> + <surname>Heute</surname> + <affiliation> + <shortaffil>Red Hat</shortaffil> + <orgdiv>JBoss Engineering</orgdiv> + + </affiliation> + + </editor> + <editor> + <firstname>Wesley</firstname> + <surname>Hales</surname> + <affiliation> + <shortaffil>Red Hat</shortaffil> + <orgdiv>JBoss Engineering</orgdiv> + + </affiliation> + + </editor> + <editor> + <firstname>Chris</firstname> + <surname>Laprun</surname> + <affiliation> + <shortaffil>Red Hat</shortaffil> + <orgdiv>JBoss Engineering</orgdiv> + + </affiliation> + + </editor> + <editor> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <affiliation> + <shortaffil>Red Hat</shortaffil> + <orgdiv>Engineering Content Services</orgdiv> + + </affiliation> + + </editor> + <othercredit> + <affiliation> + <orgname><emphasis role="bold"><ulink type="http" url="http://www.jboss.org/gatein/">GateIn</ulink></emphasis> and <emphasis role="bold"><ulink type="http" url="http://www.exoplatform.com">eXo Platform</ulink></emphasis></orgname> + <orgdiv>Documentation Teams</orgdiv> + + </affiliation> + <contrib>Based on original product documentation by:</contrib> + + </othercredit> +</authorgroup> + Deleted: epp/docs/branches/5.2/Reference_Guide/en-US/Book_Info.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/Book_Info.xml 2011-11-24 17:26:22 UTC (rev 8138) +++ epp/docs/branches/5.2/Reference_Guide/en-US/Book_Info.xml 2011-11-25 00:48:53 UTC (rev 8141) @@ -1,33 +0,0 @@ -<?xml version='1.0' encoding='utf-8' ?> -<!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> -%BOOK_ENTITIES; -]> -<bookinfo id="book-Reference_Guide_eXo_JCR_1.14-Reference_Guide_eXo_JCR_1.14"> - <title>Reference Guide eXo JCR 1.14</title> - <subtitle>An in-depth guide to Enterprise Portal Platform &VZ;</subtitle> - <productname>JBoss Enterprise Portal Platform</productname> - <productnumber>5.2</productnumber> - <edition>5.2.0</edition> - <pubsnumber>7</pubsnumber> - <abstract> - <para> - This Reference Guide is a high-level usage document. It deals with more advanced topics than the Installation and User Guides, adding new content or taking concepts discussed in the earlier documents further. It aims to provide supporting documentation for advanced users of the JBoss Enterprise Portal Platform product. Its primary focus is on advanced use of the product and it assumes an intermediate or advanced knowledge of the technology and terms. - </para> - - </abstract> - <corpauthor> - <inlinemediaobject> - <imageobject> - <imagedata fileref="Common_Content/images/title_logo.svg" format="SVG" /> - </imageobject> - - </inlinemediaobject> - - </corpauthor> -  <xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude">  <xi:fallback xmlns:xi="http://www.w3.org/2001/XInclude"> <xi:include href="fallback_content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - </xi:fallback> - </xi:include> - <xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -</bookinfo> - Copied: epp/docs/branches/5.2/Reference_Guide/en-US/Book_Info.xml (from rev 8139, epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/Book_Info.xml) =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/Book_Info.xml (rev 0) +++ epp/docs/branches/5.2/Reference_Guide/en-US/Book_Info.xml 2011-11-25 00:48:53 UTC (rev 8141) @@ -0,0 +1,33 @@ +<?xml version='1.0' encoding='utf-8' ?> +<!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +%BOOK_ENTITIES; +]> +<bookinfo id="book-Reference_Guide_eXo_JCR_1.14-Reference_Guide_eXo_JCR_1.14"> + <title>Reference Guide eXo JCR 1.14</title> + <subtitle>An in-depth guide to Enterprise Portal Platform &VZ;</subtitle> + <productname>JBoss Enterprise Portal Platform</productname> + <productnumber>5.2</productnumber> + <edition>5.2.0</edition> + <pubsnumber>9</pubsnumber> + <abstract> + <para> + This Reference Guide is a high-level usage document. It deals with more advanced topics than the Installation and User Guides, adding new content or taking concepts discussed in the earlier documents further. It aims to provide supporting documentation for advanced users of the JBoss Enterprise Portal Platform product. Its primary focus is on advanced use of the product and it assumes an intermediate or advanced knowledge of the technology and terms. + </para> + + </abstract> + <corpauthor> + <inlinemediaobject> + <imageobject> + <imagedata fileref="Common_Content/images/title_logo.svg" format="SVG" /> + </imageobject> + + </inlinemediaobject> + + </corpauthor> +  <xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude">  <xi:fallback xmlns:xi="http://www.w3.org/2001/XInclude"> <xi:include href="fallback_content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> + </xi:fallback> + </xi:include> + <xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> +</bookinfo> + Deleted: epp/docs/branches/5.2/Reference_Guide/en-US/Revision_History.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/Revision_History.xml 2011-11-24 17:26:22 UTC (rev 8138) +++ epp/docs/branches/5.2/Reference_Guide/en-US/Revision_History.xml 2011-11-25 00:48:53 UTC (rev 8141) @@ -1,141 +0,0 @@ -<?xml version='1.0' encoding='utf-8' ?> -<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> -%BOOK_ENTITIES; -]> -<appendix id="appe-Reference_Guide_eXo_JCR_1.14-Revision_History"> - <title>Revision History</title> - <simpara> - <revhistory> - <revision> - <revnumber>5.2.0-6</revnumber> - <date>Thu Nov 17 2011</date> - <author> - <firstname>Scott</firstname> - <surname>Mumford</surname> - <email></email> - - </author> - <revdescription> - <simplelist> - <member>Incorporated GateIn SSO updates.</member> - - </simplelist> - - </revdescription> - - </revision> - <revision> - <revnumber>5.2.0-5</revnumber> - <date>Tue Nov 15 2011</date> - <author> - <firstname>Scott</firstname> - <surname>Mumford</surname> - <email></email> - - </author> - <revdescription> - <simplelist> - <member>Staging for beta release.</member> - - </simplelist> - - </revdescription> - - </revision> - <revision> - <revnumber>5.2.0-4</revnumber> - <date>Wed Nov 9 2011</date> - <author> - <firstname>Scott</firstname> - <surname>Mumford</surname> - <email></email> - - </author> - <revdescription> - <simplelist> - <member>Republished for review/feedback.</member> - - </simplelist> - - </revdescription> - - </revision> - <revision> - <revnumber>5.2.0-3</revnumber> - <date>Wed Nov 2 2011</date> - <author> - <firstname>Scott</firstname> - <surname>Mumford</surname> - <email></email> - - </author> - <revdescription> - <simplelist> - <member>Staged for review of updated Foundations and eXo JCR content.</member> - - </simplelist> - - </revdescription> - - </revision> - <revision> - <revnumber>5.2.0-2</revnumber> - <date>Tue Sep 27 2011</date> - <author> - <firstname>Scott</firstname> - <surname>Mumford</surname> - <email></email> - - </author> - <revdescription> - <simplelist> - <member>Incorporated eXo JCR 1.14 documentation.</member> - - </simplelist> - - </revdescription> - - </revision> - <revision> - <revnumber>5.2.0-5</revnumber> - <date>Wed Sep 14 2011</date> - <author> - <firstname>Scott</firstname> - <surname>Mumford</surname> - <email></email> - - </author> - <revdescription> - <simplelist> - <member>Added Global Portlet Data section.</member> - - </simplelist> - - </revdescription> - - </revision> - <revision> - <revnumber>5.2.0-1</revnumber> - <date>Mon Aug 29 2011</date> - <author> - <firstname>Scott</firstname> - <surname>Mumford</surname> - <email></email> - - </author> - <revdescription> - <simplelist> - <member>Updating version and resetting pubs/ed numbers.</member> - - </simplelist> - - </revdescription> - - </revision> - - </revhistory> - - </simpara> -</appendix> - Copied: epp/docs/branches/5.2/Reference_Guide/en-US/Revision_History.xml (from rev 8139, epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/Revision_History.xml) =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/Revision_History.xml (rev 0) +++ epp/docs/branches/5.2/Reference_Guide/en-US/Revision_History.xml 2011-11-25 00:48:53 UTC (rev 8141) @@ -0,0 +1,171 @@ +<?xml version='1.0' encoding='utf-8' ?> +<!DOCTYPE appendix PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +%BOOK_ENTITIES; +]> +<appendix id="appe-Reference_Guide_eXo_JCR_1.14-Revision_History"> + <title>Revision History</title> + <simpara> + <revhistory> + <revision> + <revnumber>5.2.0-9</revnumber> + <date>Fri Nov 25 2011</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email></email> + </author> + <revdescription> + <simplelist> + <member>Ported latest community WSRP content.</member> + </simplelist> + </revdescription> + </revision> + <revision> + <revnumber>5.2.0-8</revnumber> + <date>Thu Nov 24 2011</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email></email> + </author> + <revdescription> + <simplelist> + <member>Finalized first edit pass of eXoJCR content.</member> + <member>Moved eXoJCR section to Part IV.</member> + <member>Clean element ids and fix broken linkends.</member> + </simplelist> + </revdescription> + </revision> + <revision> + <revnumber>5.2.0-6</revnumber> + <date>Thu Nov 17 2011</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email></email> + + </author> + <revdescription> + <simplelist> + <member>Incorporated GateIn SSO updates.</member> + + </simplelist> + + </revdescription> + + </revision> + <revision> + <revnumber>5.2.0-5</revnumber> + <date>Tue Nov 15 2011</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email></email> + + </author> + <revdescription> + <simplelist> + <member>Staging for beta release.</member> + + </simplelist> + + </revdescription> + + </revision> + <revision> + <revnumber>5.2.0-4</revnumber> + <date>Wed Nov 9 2011</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email></email> + + </author> + <revdescription> + <simplelist> + <member>Republished for review/feedback.</member> + + </simplelist> + + </revdescription> + + </revision> + <revision> + <revnumber>5.2.0-3</revnumber> + <date>Wed Nov 2 2011</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email></email> + + </author> + <revdescription> + <simplelist> + <member>Staged for review of updated Foundations and eXo JCR content.</member> + + </simplelist> + + </revdescription> + + </revision> + <revision> + <revnumber>5.2.0-2</revnumber> + <date>Tue Sep 27 2011</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email></email> + + </author> + <revdescription> + <simplelist> + <member>Incorporated eXo JCR 1.14 documentation.</member> + + </simplelist> + + </revdescription> + + </revision> + <revision> + <revnumber>5.2.0-5</revnumber> + <date>Wed Sep 14 2011</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email></email> + + </author> + <revdescription> + <simplelist> + <member>Added Global Portlet Data section.</member> + + </simplelist> + + </revdescription> + + </revision> + <revision> + <revnumber>5.2.0-1</revnumber> + <date>Mon Aug 29 2011</date> + <author> + <firstname>Scott</firstname> + <surname>Mumford</surname> + <email></email> + + </author> + <revdescription> + <simplelist> + <member>Updating version and resetting pubs/ed numbers.</member> + + </simplelist> + + </revdescription> + + </revision> + + </revhistory> + + </simpara> +</appendix> + Deleted: epp/docs/branches/5.2/Reference_Guide/en-US/images/WSRP/config_self.png =================================================================== (Binary files differ) Copied: epp/docs/branches/5.2/Reference_Guide/en-US/images/WSRP/config_self.png (from rev 8139, epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/images/WSRP/config_self.png) =================================================================== (Binary files differ) Deleted: epp/docs/branches/5.2/Reference_Guide/en-US/images/WSRP/modify_reg_end.png =================================================================== (Binary files differ) Copied: epp/docs/branches/5.2/Reference_Guide/en-US/images/WSRP/modify_reg_end.png (from rev 8139, epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/images/WSRP/modify_reg_end.png) =================================================================== (Binary files differ) Deleted: epp/docs/branches/5.2/Reference_Guide/en-US/images/WSRP/modify_reg_self_end.png =================================================================== (Binary files differ) Copied: epp/docs/branches/5.2/Reference_Guide/en-US/images/WSRP/modify_reg_self_end.png (from rev 8139, epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/images/WSRP/modify_reg_self_end.png) =================================================================== (Binary files differ) Deleted: epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Configuring_Services.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations/Configuring_Services.xml 2011-11-24 17:26:22 UTC (rev 8138) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Configuring_Services.xml 2011-11-25 00:48:53 UTC (rev 8141) @@ -1,913 +0,0 @@ -<?xml version='1.0' encoding='utf-8' ?> -<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> -%BOOK_ENTITIES; -]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-Configuring_Services"> - <title>Configuring Services</title> - <para> - The eXo Kernel uses dependency injection to create services based on <filename>configuration.xml</filename> configuration files. The location of the configuration files determines if services are placed into the <literal>RootContainer</literal> scope, or into the <literal>PortalContainer</literal> scope. - </para> - <para> - When creating a service, you also should declare its existence to the <emphasis role="bold">Container</emphasis>, therefore you create a first simple configuration file. Copy the following code to a file called "configuration.xml" and place this file in a /conf subdirectory of your service base folder. As you already know the container looks for a "/conf/configuration.xml" file in each jar-file. - </para> - <para> - All <filename>configuration.xml</filename> files located at <filename>conf/configuration.xml</filename> in the classpath (any directory, or any jar in the classpath) will have their services configured in the <literal>RootContainer</literal> scope. All <filename>configuration.xml</filename> files located at <filename>conf/portal/configuration.xml</filename> in the classpath will have their services configured at the <literal>PortalContainer</literal> scope. - </para> - <para> - Additionally, <emphasis role="bold">portal extensions</emphasis> can contain configuration in <filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/02portal.war/WEB-INF/conf/configuration.xml</filename>, and will also have their services configured in the <literal>PortalContainer</literal> scope. - </para> - <para> - When eXo kernel reads a configuration, it loads the file from the kernel jar using the classloader and does not use an internet connection to resolve the file. - </para> - <note> - <para> - <emphasis role="bold">Portal extensions</emphasis> are described later in this document. - </para> - - </note> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuring_Services-Configuration_syntax"> - <title>Configuration syntax</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuration_syntax-Components"> - <title>Components</title> - <para> - A service component is defined in <filename>configuration.xml</filename> by using a <emphasis role="bold"><component></emphasis> element. - </para> - <para> - Only one piece of information is required when defining a service; the service implementation class. This is specified using <literal><type></literal> - </para> - <para> - Every component has a <literal><key></literal> that identifies it. If not explicitly set, a key defaults to the value of <literal><type></literal>. If a key can be loaded as a class, a class object is used as a key, otherwise a string is used. - </para> - <para> - The usual approach is to specify an interface as a key. - </para> - -<programlisting language="XML" role="XML"><xi:include href="../../../extras/Advanced_Development_Foundations/default.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - <para> - The configuration you find inside the jar file is considered as the default configuration. If you want to override this default configuration you can do it in different places outside the jar. When the container finds several configurations for the same service, the configuration which is found later replaces completely the one found previously. Let's call this the <emphasis>configuration override mechanism</emphasis>. - </para> - <para> - After deploying you find the configuration.xml file in webapps/portal/WEB-INF/conf Use component registration tags. Let's look at the key tag that defines the interface and the type tag that defines the implementation. Note that the key tag is not mandatory, but it improves performance. - </para> - -<programlisting language="XML" role="XML"> - <component> - <key>org.exoplatform.services.portletcontainer.persistence.PortletPreferencesPersister</key> - <type>org.exoplatform.services.portal.impl.PortletPreferencesPersisterImpl</type> - </component></programlisting> - <para> - Register plugins that can act as listeners or external plugin to bundle some plugin classes in other jar modules. The usual example is the hibernate service to which we can add hbm mapping files even if those are deployed in an other maven artifact. - </para> - -<programlisting language="XML" role="XML"><external-component-plugins> - <target-component>org.exoplatform.services.database.HibernateService</target-component> - <component-plugin> - <name>add.hibernate.mapping</name> - <set-method>addPlugin</set-method> - <type>org.exoplatform.services.database.impl.AddHibernateMappingPlugin</type> - <init-params> - <values-param> - <name>hibernate.mapping</name> - <value>org/exoplatform/services/portal/impl/PortalConfigData.hbm.xml</value> - <value>org/exoplatform/services/portal/impl/PageData.hbm.xml</value> - <value>org/exoplatform/services/portal/impl/NodeNavigationData.hbm.xml</value> - </values-param> - </init-params> - </component-plugin> -</external-component-plugins></programlisting> - <para> - In that sample we target the HibernateService and we will call its addPlugin() method with an argument of the type AddHibernateMappingPlugin. That object will first have been filled with the init parameters. - </para> - <para> - Therefore, it is possible to define services that will be able to receive plugins without implementing any framework interface. - </para> - <para> - Another example of use is the case of listeners as in the following code where a listener is added to the OrganisationService and will be called each time a new user is created: - </para> - -<programlisting language="XML" role="XML"><external-component-plugins> - <target-component>org.exoplatform.services.organization.OrganizationService</target-component> - <component-plugin> - <name>portal.new.user.event.listener</name> - <set-method>addListenerPlugin</set-method> - <type>org.exoplatform.services.portal.impl.PortalUserEventListenerImpl</type> - <description>this listener create the portal configuration for the new user</description> - <init-params> - <object-param> - <name>configuration</name> - <description>description</description> - <object type="org.exoplatform.services.portal.impl.NewPortalConfig"> - <field name="predefinedUser"> - <collection type="java.util.HashSet"> - <value><string>admin</string></value> - <value><string>exo</string></value> - <value><string>company</string></value> - <value><string>community</string></value> - <value><string>portal</string></value> - <value><string>exotest</string></value> - </collection> - </field> - <field name="templateUser"><string>template</string></field> - <field name="templateLocation"><string>war:/conf/users</string></field> - </object> - </object-param> - </init-params> - </component-plugin> -...</programlisting> - <para> - In the previous XML configuration, we refer the organization service and we will call its method addListenerPlugin with an object of type PortalUserEventListenerImpl. Each time a new user will be created (apart the predefined ones in the list above) methods of the PortalUserEventListenerImpl will be called by the service. - </para> - <para> - As you can see, there are several types of init parameters, from a simple value param which binds a key with a value to a more complex object mapping that fills a JavaBean with the info defined in the XML. - </para> - <para> - Many other examples exist such as for the Scheduler Service where you can add a job with a simple XML configuration or the JCR Service where you can add a NodeType from your own configuration.xml file. - </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Components-RootContainer"> - <title>RootContainer</title> - <para> - As PortalContainer depends on the RootContainer, we will start by looking into this one. - </para> - <para> - The retrieval sequence in short: - </para> - <orderedlist> - <listitem> - <para> - Services default <classname>RootContainer</classname> configurations from JAR files <emphasis>/conf/configuration.xml</emphasis> - </para> - - </listitem> - <listitem> - <para> - External <classname>RootContainer</classname> configuration, to be found at <emphasis>exo-tomcat/exo-conf/configuration.xml</emphasis> - </para> - - </listitem> - - </orderedlist> - <note> - <para> - Naturally you always have to replace <parameter>exo-tomcat</parameter> by your own folder name. - </para> - - </note> - <para> - <emphasis role="bold">HashTable</emphasis> The <classname>RootContainer</classname> creates a java <classname>HashTable</classname> which contains key-value pairs for the services. The qualified interface name of each service is used as key for the hashtable. Hopefully you still remember that the <parameter><key></parameter> tag of the configuration file contains the interface name? The value of each hashtable pair is an object that contains the service configuration (yes, this means the whole structure between the <parameter><component></parameter> tags of your <filename>configuration.xml</filename> file). - </para> - <para> - The <classname>RootContainer</classname> runs over all jar files you find in <emphasis>exo-tomcat/lib</emphasis> and looks if there is a configuration file at <emphasis>/conf/configuration.xml</emphasis>, the services configured in this file are added to the hashtable. That way - at the end of this process - the default configurations for all services are stored in the hashtable. - </para> - <note> - <para> - What happens if the same service - recognized by the same qualified interface name - is configured in different jars? As the service only can exist one time the configuration of the jar found later overrides the previous configuration. You know that the loading <emphasis role="bold">order of the jars is unpredictable</emphasis> you <emphasis role="bold">must not depend on this</emphasis>. - </para> - - </note> - <para> - If you wish to provide your own configurations for one or several services, you can do it in a general configuration file that has to be placed at <emphasis>exo-tomcat/exo-conf/configuration.xml</emphasis>. Do not search for such a file on your computer - you won't find one, because this option is not used in the default installation. Here again the same rule applies: <emphasis>The posterior configuration replaces the previous one</emphasis>. - </para> - <para> - The further configuration retrieval depends on the container type. - </para> - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Components-PortalContainer"> - <title>PortalContainer</title> - <para> - The PortalContainer takes the hashtable filled by the RootContainer and continues to look in some more places. Here you get the opportunity to replace RootContainer configurations by those which are specific to your portal. Again, the configurations are overridden whenever necessary. - </para> - <para> - In short PortalContainer configurations are retrieved in the following lookup sequence : - </para> - <orderedlist> - <listitem> - <para> - Take over the configurations of the RootContainer - </para> - - </listitem> - <listitem> - <para> - Default PortalContainer configurations from all JAR files (folder <emphasis>/conf/portal/configuration.xml</emphasis>) - </para> - - </listitem> - <listitem> - <para> - Web application configurations from the portal.war file - or the <emphasis>portal</emphasis> weppapp (folder <emphasis>/WEB-INF/conf/configuration.xml</emphasis>) - </para> - - </listitem> - <listitem> - <para> - External configuration for services of a named portal, it will be found at <emphasis>exo-tomcat/exo-conf/portal/$portal_name/configuration.xml</emphasis> (as of Portal 2.5) - </para> - - </listitem> - - </orderedlist> - <para> - 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>. - </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. - </para> - - </note> - <note> - <para> - Under <emphasis role="bold">JBoss</emphasis> application server <emphasis>exo-conf</emphasis> will be looked up in directory described by JBoss System property <emphasis>jboss.server.config.url</emphasis>. If the property is not found or empty <emphasis>exo-jboss/exo-conf</emphasis> will be asked (since kernel 2.0.4). - </para> - - </note> - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Components-External_Plug_ins"> - <title>External Plug-ins</title> - <para> - The eXo Kernel supports non-component objects that can be configured, instantiated, and injected into registered components using method calls. This '<emphasis>plugin</emphasis>' method allows portal extensions to add additional configurations to core services. - </para> - <para> - An external plugin is defined by using the <literal><external-component-plugin></literal> wrapper element which contains one or more <literal><component-plugin></literal> definitions. - </para> - <para> - The <literal><external-component-plugin></literal> element uses <literal><target-component></literal> to specify a target service component that will receive injected objects. - </para> - <para> - Every <literal><component-plugin></literal> defines an implementation type, and a method on the target component to use for injection (<literal><set-method></literal>). - </para> - <para> - A plugin implementation class has to implement the <emphasis role="bold">org.exoplatform.container.component. ComponentPlugin</emphasis> interface. - </para> - <para> - In the following example the <literal>PortalContainerDefinitionPlugin</literal> implements the <literal>ComponentPlugin</literal>: - </para> - -<programlisting language="XML" role="XML"><xi:include href="../../../extras/Advanced_Development_Foundations/default1.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - <para> - The <emphasis role="bold"><target-component></emphasis> defines the service for which the plugin is defined. The configuration is injected by the container using a method that is defined in <emphasis role="bold"><set-method></emphasis>. The method has exactly one argument of the type org.exoplatform.services.cms.categories.impl.TaxonomyPlugin: - </para> - <itemizedlist> - <listitem> - <para> - addTaxonomyPlugin(org.exoplatform.services.cms.categories.impl.TaxonomyPlugin plugin) - </para> - - </listitem> - - </itemizedlist> - <para> - The content of <emphasis role="bold"><init-params></emphasis> corresponds to the structure of the TaxonomyPlugin object. - </para> - <note> - <para> - You can configure the component CategoriesService using the addTaxonomyPlugin as often as you wish, you can also call addTaxonomyPlugin in different configuration files. The method addTaxonomyPlugin is then called several times, everything else depends on the implementation of the method. - </para> - - </note> - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Components-Service_instantiation"> - <title>Service instantiation</title> - <para> - As you have already learned the services are all singletons, so that the container creates only one single instance of each container. The services are created by calling the constructors (called <emphasis>constructor injection</emphasis>). If there are only zero-arguments constructors (<code>Foo public Foo(){}</code>) there are no problems to be expected. That's easy. - </para> - <para> - But now look at <ulink url="https://anonsvn.jboss.org/repos/exo-jcr/core/trunk/exo.core.component.org...">https://anonsvn.jboss.org/repos/exo-jcr/core/trunk/exo.core.component.org...</ulink> - </para> - <para> - This JDBC implementation of BaseOrganizationService interface has only one constructor: - </para> - -<programlisting language="Java" role="Java">public OrganizationServiceImpl(ListenerService listenerService, DatabaseService dbService);</programlisting> - <para> - You see this service depends on two other services. In order to be able to call this constructor the container first needs a <classname>ListenerService</classname> and a <classname>DatabaseService</classname>. Therefore these services must be instantiated before <classname>BaseOrganizationService</classname>, because <classname>BaseOrganizationService</classname> depends on them. - </para> - <para> - For this purpose the container first looks at the constructors of all services and creates a matrix of service dependencies in order to call the services in a proper order. If for any reason there are interdependencies or circular dependencies you will get a java <classname>Exception</classname>. <emphasis>In this way the dependencies are injected by the container</emphasis>. - </para> - <note> - <para> - What happens if one service has more than one constructor? The container always tries first to use the constructor with a maximum of arguments, if this is not possible the container continues step by step with constructors that have less arguments until arriving at the zero-argument constructor (if there is one). - </para> - - </note> - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Components-Service_Access"> - <title>Service Access</title> - <para> - As you want to follow the principle of <emphasis role="bold">Inversion of Control,</emphasis> you <emphasis role="bold">must not</emphasis> access the service directly. You need a <emphasis role="bold">Container</emphasis> to access the service. - </para> - <para> - With this command you get your current container: - </para> - <itemizedlist> - <listitem> - <para> - <emphasis role="bold">ExoContainer myContainer = ExoContainerContext.getCurrentContainer();</emphasis> - </para> - - </listitem> - - </itemizedlist> - <para> - Whenever you need one of the services that you have configured use the method: - </para> - <itemizedlist> - <listitem> - <para> - <emphasis role="bold">myContainer.getComponentInstance(class)</emphasis> - </para> - - </listitem> - - </itemizedlist> - <para> - In our case: - </para> - <itemizedlist> - <listitem> - <para> - <emphasis role="bold">ArticleStatsService statsService = (ArticleStatsService) myContainer.getComponentInstance(ArticleStatsService.class);</emphasis> - </para> - - </listitem> - - </itemizedlist> - <para> - Recapitulation: - </para> - -<programlisting language="Java" role="Java">package com.laverdad.common; - -import org.exoplatform.container.ExoContainer; -import org.exoplatform.container.ExoContainerContext; -import com.laverdad.services.*; - -public class Statistics { - - public int makeStatistics(String articleText) { - ExoContainer myContainer = ExoContainerContext.getCurrentContainer(); - ArticleStatsService statsService = (ArticleStatsService) - myContainer.getComponentInstance(ArticleStatsService.class); - int numberOfSentences = statsService.calcSentences(articleText); - return numberOfSentences; - } - - public static void main( String args[]) { - Statistics stats = new Statistics(); - String newText = "This is a normal text. The method only counts the number of periods. " - + "You can implement your own implementation with a more exact counting. " - + "Let`s make a last sentence."; - System.out.println("Number of sentences: " + stats.makeStatistics(newText)); - } -}</programlisting> - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Components-Includes_and_special_URLs"> - <title>Includes, and special URLs</title> - <para> - It is possible to divide the <filename>configuration.xml</filename> file into many smaller files, which are then included into the main configuration file. - </para> - <para> - The included files must be valid xml files; they cannot be fragments of text. - </para> - <para> - Below is an example <filename>configuration.xml</filename> that 'outsources' its content into several files: - </para> - <programlistingco> - <areaspec> - <area coords="6" id="area-Reference_Guide_eXo_JCR_1.14-Components-Includes_and_special_URLs-url_schema" /> - - </areaspec> - -<programlisting language="XML" role="XML"><xi:include href="../../../extras/Advanced_Development_Foundations/default2.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - <calloutlist> - <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Components-Includes_and_special_URLs-url_schema"> - <para> - This line is being used to reference another configuration file. The <code>war:</code> URL schema indicates that the following path is to be resolved relative to the current <literal>PortalContainer</literal>'s servlet context resource path, starting with <emphasis role="bold">WEB-INF</emphasis> as a root. - </para> - - </callout> - - </calloutlist> - - </programlistingco> - - <note> - <para> - The current <literal>PortalContainer</literal> is really a newly created <literal>PortalContainer</literal>, as <code>war:</code> URLs only make sense for <literal>PortalContainer</literal> scoped configuration. - </para> - - </note> - <para> - Through the extension mechanism the servlet context used for resource loading is a <emphasis role="bold">unified servlet context</emphasis> (this is explained in a later section). - </para> - <para> - To have an 'include' path resolved relative to current classpath (context classloader), use a <code>'jar:'</code> URL schema. - </para> - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Components-Special_variables"> - <title>Special variables</title> - <para> - Configuration files may contain a <emphasis role="bold">special variable</emphasis> reference <emphasis>${container.name.suffix}</emphasis>. This variable resolves to the name of the current portal container, prefixed by underscore (_). - </para> - <para> - This facilitates reuse of configuration files in situations where portal-specific unique names need to be assigned to some resources; JNDI names, Database/DataSource names and JCR repository names, for example. - </para> - <para> - This variable is only defined when there is a current <literal>PortalContainer</literal> available and is only available for <literal>PortalContainer</literal> scoped services. - </para> - <para> - A good example of this is the <emphasis role="bold">HibernateService</emphasis>: - </para> - -<programlisting language="XML" role="XML"><xi:include href="../../../extras/Advanced_Development_Foundations/default3.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - - </section> - - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuration_syntax-InitParams_configuration_element"> - <title>InitParams configuration element</title> - <para> - <parameter>InitParams</parameter> is a configuration element that is essentially a map of key-value pairs, where <emphasis role="bold">key</emphasis> is always a <literal>String</literal>, and <emphasis role="bold">value</emphasis> can be any type that can be described using the kernel XML configuration. - </para> - <para> - Service components that form the JBoss Enterprise Portal Platform infrastructure use <parameter>InitParams</parameter> elements to configure themselves. A component can have one instance of <parameter>InitParams</parameter> injected at most. - </para> - <para> - If the service component's constructor takes <parameter>InitParams</parameter> as any of the parameters it will automatically be injected at component instantiation time. - </para> - <para> - The XML configuration for a service component that expects an <parameter>InitParams</parameter> element must have an <parameter><init-params></parameter> element present, however this element can be left empty. - </para> - <para> - Below is an example of how the kernel XML configuration syntax looks when creating <parameter>InitParams</parameter> instances: - </para> - -<programlisting language="XML" role="XML"><xi:include href="../../../extras/Advanced_Development_Foundations/default4.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - <para> - An <parameter>InitParams</parameter> element description begins with an <parameter><init-params></parameter> element. - </para> - <para> - It can have zero or more children elements, each of which is one of the following: - </para> - <itemizedlist> - <listitem> - <para> - <parameter><value-param></parameter> - </para> - - </listitem> - <listitem> - <para> - <parameter><values-param></parameter> - </para> - - </listitem> - <listitem> - <para> - <parameter><properties-param></parameter> - </para> - - </listitem> - - </itemizedlist> - <para> - or - </para> - <itemizedlist> - <listitem> - <para> - <parameter><object-param></parameter> - </para> - - </listitem> - - </itemizedlist> - <para> - Each of these child elements takes a <parameter><name></parameter> that serves as a map entry key, and an optional <parameter><description></parameter>. It also takes a type-specific <emphasis role="bold">value</emphasis> specification. - </para> - <para> - The value specification for the <parameter><properties-param></parameter> defines one or more <parameter><property></parameter> elements, each of which specifies two strings; a property name and a property value. This is evident in the two previous examples. - </para> - <para> - Each <parameter><properties-params></parameter> defines one <literal>java.util.Properties</literal> instance. - </para> - <para> - The value specification for <parameter><value-param></parameter> elements is a <parameter><value></parameter> element which defines a <literal>String</literal> instance. - </para> - -<programlisting language="XML" role="XML"><xi:include href="../../../extras/Advanced_Development_Foundations/default5.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - <para> - The value specification for <parameter><values-param></parameter> requires one or more <parameter><value></parameter> elements. Each <parameter><value></parameter> represents one <literal>String</literal> instance. All <literal>String</literal> values are then collected into a <literal>java.util.List</literal> instance. - </para> - -<programlisting language="XML" role="XML"><xi:include href="../../../extras/Advanced_Development_Foundations/default6.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - <para> - For <parameter><object-param></parameter> entries, the value specification consists of an <parameter><object></parameter> element which is used for plain Java style object specification (specifying an implementation <emphasis>class - <parameter><type></parameter></emphasis>, and <emphasis>property values - <parameter><field></parameter></emphasis>). - </para> - <para> - The following section has an example of specifying a field of with a <literal>Collection</literal> type. - </para> - <para> - The <parameter>InitParams</parameter> structure (the names and types of entries) is specific for each service, as it is the code inside a service components' class that defines which entry names to look up and what types it expects to find. - </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-InitParams_configuration_element-Value_Param"> - <title>Value-Param</title> - <para> - There is an value-param example: - </para> - -<programlisting language="XML" role="XML"> <component> - <key>org.exoplatform.portal.config.UserACL</key> - <type>org.exoplatform.portal.config.UserACL</type> - <init-params> -... - <value-param> - <name>access.control.workspace</name> - <description>groups with memberships that have the right to access the User Control Workspace</description> - <value>*:/platform/administrators,*:/organization/management/executive-board</value> - </value-param> -... - </component></programlisting> - <para> - The UserACL class accesses to the <emphasis role="bold">value-param</emphasis> in its constructor. - </para> - -<programlisting language="Java" role="Java">package org.exoplatform.portal.config; -public class UserACL { - - public UserACL(InitParams params) { - UserACLMetaData md = new UserACLMetaData(); - ValueParam accessControlWorkspaceParam = params.getValueParam("access.control.workspace"); - if(accessControlWorkspaceParam != null) md.setAccessControlWorkspace(accessControlWorkspaceParam.getValue()); -...</programlisting> - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-InitParams_configuration_element-Properties_Param"> - <title>Properties-Param</title> - <para> - Properties are name-value pairs. Both the name and the value are Java Strings. - </para> - <para> - Here you see the hibernate configuration example: - </para> - -<programlisting language="XML" role="XML"> <component> - <key>org.exoplatform.services.database.HibernateService</key> - <type>org.exoplatform.services.database.impl.HibernateServiceImpl</type> - <init-params> - <properties-param> - <name>hibernate.properties</name> - <description>Default Hibernate Service</description> - <property name="hibernate.show_sql" value="false"/> - <property name="hibernate.cglib.use_reflection_optimizer" value="true"/> - <property name="hibernate.connection.url" value="jdbc:hsqldb:file:../temp/data/exodb"/> - <property name="hibernate.connection.driver_class" value="org.hsqldb.jdbcDriver"/> -... - </properties-param> - </init-params> - </component></programlisting> - <para> - In the org.exoplatform.services.database.impl.HibernateServiceImpl you will find that the name "hibernate.properties" of the properties-param is used to access the properties. - </para> - -<programlisting language="Java" role="Java">package org.exoplatform.services.database.impl; - -public class HibernateServiceImpl implements HibernateService, ComponentRequestLifecycle { - public HibernateServiceImpl(InitParams initParams, CacheService cacheService) { - PropertiesParam param = initParams.getPropertiesParam("hibernate.properties"); -... -}</programlisting> - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-InitParams_configuration_element-Object_Param"> - <title>Object-Param</title> - <para> - Let's have a look at the configuration of the LDAPService. It's not important to know LDAP, we only discuss the parameters. - </para> - -<programlisting language="XML" role="XML"><component> - <key>org.exoplatform.services.ldap.LDAPService</key> - <type>org.exoplatform.services.ldap.impl.LDAPServiceImpl</type> - <init-params> - <object-param> - <name>ldap.config</name> - <description>Default ldap config</description> - <object type="org.exoplatform.services.ldap.impl.LDAPConnectionConfig"> - <field name="providerURL"><string>ldaps://10.0.0.3:636</string></field> - <field name="rootdn"><string>CN=Administrator,CN=Users,DC=exoplatform,DC=org</string></field> - <field name="password"><string>exo</string></field> - <field name="version"><string>3</string></field> - <field name="minConnection"><int>5</int></field> - <field name="maxConnection"><int>10</int></field> - <field name="referralMode"><string>ignore</string></field> - <field name="serverName"><string>active.directory</string></field> - </object> - </object-param> - </init-params> -</component></programlisting> - <para> - You see here an <emphasis role="bold">object-param</emphasis> is being used to pass the parameters inside an object (actually a java bean). It consists of a <emphasis role="bold">name</emphasis>, a <emphasis role="bold">description</emphasis> and exactly one <emphasis role="bold">object</emphasis>. The object defines the <emphasis role="bold">type</emphasis> and a number of <emphasis role="bold">fields</emphasis>. - </para> - <para> - Here you see how the service accesses the object: - </para> - -<programlisting language="Java" role="Java">package org.exoplatform.services.ldap.impl; - -public class LDAPServiceImpl implements LDAPService { -... - public LDAPServiceImpl(InitParams params) { - LDAPConnectionConfig config = (LDAPConnectionConfig) params.getObjectParam("ldap.config") - .getObject(); -...</programlisting> - <para> - The passed object is LDAPConnectionConfig which is a classic <emphasis role="bold">java bean</emphasis>. It contains all fields and also the appropriate getters and setters (not listed here). You also can provide default values. The container creates a new instance of your bean and calls all setters whose values are configured in the configuration file. - </para> - -<programlisting language="Java" role="Java">package org.exoplatform.services.ldap.impl; - -public class LDAPConnectionConfig { - private String providerURL = "ldap://127.0.0.1:389"; - private String rootdn; - private String password; - private String version; - private String authenticationType = "simple"; - private String serverName = "default"; - private int minConnection; - private int maxConnection; - private String referralMode = "follow"; -...</programlisting> - <para> - You see that the types (String, int) of the fields in the configuration correspond with the bean. A short glance in the kernel_1_2.xsd file let us discover more simple types: - </para> - <itemizedlist> - <listitem> - <para> - <emphasis role="bold">string, int, long, boolean, date, double</emphasis> - </para> - - </listitem> - - </itemizedlist> - <para> - Have a look on this type test xml file: <ulink url="https://anonsvn.jboss.org/repos/exo-jcr/kernel/trunk/exo.kernel.container...">https://anonsvn.jboss.org/repos/exo-jcr/kernel/trunk/exo.kernel.container...</ulink>. - </para> - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-InitParams_configuration_element-Collection"> - <title>Collection</title> - <para> - You also can use java collections to configure your service. In order to see an example, let's open the database-organization-configuration.xml file. This file defines a default user organization (users, groups, memberships/roles) of your portal. They use component-plugins which are explained later. You will see that object-param is used again. - </para> - <para> - There are two collections: The first collection is an <emphasis role="bold">ArrayList</emphasis>. This ArrayList contains only one value, but there could be more. The only value is an object which defines the field of the NewUserConfig$JoinGroup bean. - </para> - <para> - The second collection is a <emphasis role="bold">HashSet</emphasis> that is a set of strings. - </para> - -<programlisting language="XML" role="XML"> <component-plugin> - <name>new.user.event.listener</name> - <set-method>addListenerPlugin</set-method> - <type>org.exoplatform.services.organization.impl.NewUserEventListener</type> - <description>this listener assign group and membership to a new created user</description> - <init-params> - <object-param> - <name>configuration</name> - <description>description</description> - <object type="org.exoplatform.services.organization.impl.NewUserConfig"> - <field name="group"> - <collection type="java.util.ArrayList"> - <value> - <object type="org.exoplatform.services.organization.impl.NewUserConfig$JoinGroup"> - <field name="groupId"><string>/platform/users</string></field> - <field name="membership"><string>member</string></field> - </object> - </value> - </collection> - </field> - <field name="ignoredUser"> - <collection type="java.util.HashSet"> - <value><string>root</string></value> - <value><string>john</string></value> - <value><string>marry</string></value> - <value><string>demo</string></value> - <value><string>james</string></value> - </collection> - </field> - </object> - </object-param> - </init-params> - </component-plugin></programlisting> - <para> - Let's look at the org.exoplatform.services.organization.impl.NewUserConfig bean: - </para> - -<programlisting language="Java" role="Java">public class NewUserConfig { - private List role; - private List group; - private HashSet ignoredUser; - - ... - - public void setIgnoredUser(String user) { - ignoredUser.add(user); - - ... - - static public class JoinGroup { - public String groupId; - public String membership; - ... -}</programlisting> - <para> - You see the values of the HashSet are set one by one by the container, and it's the responsibility of the bean to add these values to its HashSet. - </para> - <para> - The JoinGroup object is just an inner class and implements a bean of its own. It can be accessed like any other inner class using NewUserConfig.JoinGroup. - </para> - - </section> - - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuration_syntax-Component_Plugin_Priority"> - <title>Component Plugin Priority</title> - <para> - Since kernel version 2.0.6 it is possible to setup order of loading for ComponentPlugin. Use the ' <emphasis role="bold">priority</emphasis>' tag to define plugin's load priority. By <emphasis role="bold">default</emphasis> all plugins get <emphasis role="bold">priority '0'</emphasis>; they will be loaded in the container's natural way. If you want one plugin to be loaded later than the others then just set priority for it <emphasis role="bold">higher than zero</emphasis>. - </para> - <para> - Simple example of fragment of a <emphasis role="bold">configuration.xml</emphasis>. - </para> - -<programlisting language="XML" role="XML">... -<component> - <type>org.exoplatform.services.Component1</type> -</component> - -<external-component-plugins> - <target-component>org.exoplatform.services.Component1</target-component> - - <component-plugin> - <name>Plugin1</name> - <set-method>addPlugin</set-method> - <type>org.exoplatform.services.plugins.Plugin1</type> - <description>description</description> - <priority>1</priority> - </component-plugin> - - <component-plugin> - <name>Plugin2</name> - <set-method>addPlugin</set-method> - <type>org.exoplatform.services.plugins.Plugin2</type> - <description>description</description> - <priority>2</priority> - </component-plugin> - -</external-component-plugins> - -<external-component-plugins> - <target-component>org.exoplatform.services.Component1</target-component> - <component-plugin> - <name>Plugin3</name> - <set-method>addPlugin</set-method> - <type>org.exoplatform.services.plugins.Plugin3</type> - <description>description</description> - </component-plugin> -</external-component-plugins> -...</programlisting> - <para> - In the above example plugin 'Plugin3' will be loaded first because it has the default priority '0'. Then, plugin 'Plugin1' will be loaded and last one is plugin 'Plugin2'. - </para> - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuration_syntax-Configuration_Logging"> - <title>Configuration Logging</title> - <para> - In case you need to solve problems with your service configuration, you have to know from which JAR/WAR causes your troubles. Add the JVM system property <parameter>org.exoplatform.container.configuration.debug</parameter> to your eXo.bat or eXo.sh file (exo-tomcat/bin/). - </para> - -<programlisting>set EXO_CONFIG_OPTS="-Dorg.exoplatform.container.configuration.debug"</programlisting> - <para> - If this property is set the container configuration manager reports during startup the configuration retrieval process to the standard output (System.out). - </para> - -<programlisting>...... -Add configuration jar:file:/D:/Projects/eXo/dev/exo-working/exo-tomcat/lib/exo.kernel.container-trunk.jar!/conf/portal/configuration.xml -Add configuration jar:file:/D:/Projects/eXo/dev/exo-working/exo-tomcat/lib/exo.kernel.component.cache-trunk.jar!/conf/portal/configuration.xml -Add configuration jndi:/localhost/portal/WEB-INF/conf/configuration.xml import jndi:/localhost/portal/WEB-INF/conf/common/common-configuration.xml -import jndi:/localhost/portal/WEB-INF/conf/database/database-configuration.xml import jndi:/localhost/portal/WEB-INF/conf/ecm/jcr-component-plugins-configuration.xml -import jndi:/localhost/portal/WEB-INF/conf/jcr/jcr-configuration.xml -......</programlisting> - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuration_syntax-Import"> - <title>Import</title> - <para> - The import tag allows to link to other configuration files. These imported files can be placed anywhere. If you write a default configuration which is part of your jar file you should not import files from outside your jar. - </para> - <itemizedlist> - <listitem> - <para> - <emphasis role="bold">war</emphasis>: Imports from <emphasis role="bold">portal.war/WEB-INF</emphasis> - </para> - - </listitem> - <listitem> - <para> - <emphasis role="bold">jar</emphasis> or <emphasis role="bold">classpath</emphasis>: Uses the <emphasis role="bold">classloader</emphasis>, you can use this prefix in the default configuration for importing an other configuration file which is accessible by the classloader. - </para> - - </listitem> - <listitem> - <para> - <emphasis role="bold">file</emphasis>: Uses an <emphasis role="bold">absolute path</emphasis>, you also can put a <emphasis role="bold">URL</emphasis>. - </para> - - </listitem> - <listitem> - <para> - <emphasis role="bold">without any prefix</emphasis>: - </para> - - </listitem> - - </itemizedlist> - <para> - If you open the "portal/trunk/web/portal/src/main/webapp/WEB-INF/conf.configuration.xml" you will see that it consists only of imports: - </para> - -<programlisting language="XML" role="XML"><import>war:/conf/common/common-configuration.xml</import> -<import>war:/conf/common/logs-configuration.xml</import> -<import>war:/conf/database/database-configuration.xml</import> -<import>war:/conf/jcr/jcr-configuration.xml</import> -<import>war:/conf/common/portlet-container-configuration.xml</import> -...</programlisting> - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuration_syntax-System_properties"> - <title>System properties</title> - <para> - Since kernel 2.0.7 and 2.1, it is possible to use system properties in literal values of component configuration meta data. This makes it possible to resolve properties at runtime instead of providing a value at packaging time. - </para> - <para> - In portal/trunk/web/portal/src/main/webapp/WEB-INF/conf/database/database-configuration.tmpl.xml you find an example for system properties: - </para> - -<programlisting language="XML" role="XML"> <component> - <key>org.exoplatform.services.database.HibernateService</key> - <jmx-name>database:type=HibernateService</jmx-name> - <type>org.exoplatform.services.database.impl.HibernateServiceImpl</type> - <init-params> - <properties-param> - <name>hibernate.properties</name> - <description>Default Hibernate Service</description> -... - <property name="hibernate.connection.url" value="${connectionUrl}"/> - <property name="hibernate.connection.driver_class" value="${driverClass}"/> - <property name="hibernate.connection.username" value="${username}"/> - <property name="hibernate.connection.password" value="${password}"/> - <property name="hibernate.dialect" value="${dialect}"/> -... - </properties-param> - </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> - </para> - - </section> - - - </section> - - -</section> - - Copied: epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Configuring_Services.xml (from rev 8139, epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/Advanced/Foundations/Configuring_Services.xml) =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Configuring_Services.xml (rev 0) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/Advanced/Foundations/Configuring_Services.xml 2011-11-25 00:48:53 UTC (rev 8141) @@ -0,0 +1,919 @@ +<?xml version='1.0' encoding='utf-8' ?> +<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +%BOOK_ENTITIES; +]> +<section id="sect-Reference_Guide_eXo_JCR_1.14-Configuring_Services"> + <title>Configuring Services</title> + <para> + The eXo Kernel uses dependency injection to create services based on <filename>configuration.xml</filename> configuration files. The location of the configuration files determines if services are placed into the <literal>RootContainer</literal> scope, or into the <literal>PortalContainer</literal> scope. + </para> + <para> + When creating a service, you also should declare its existence to the <emphasis role="bold">Container</emphasis>. This fan be done by creating a simple configuration file. + </para> + <para> + Copy the following code to a <filename>configuration.xml</filename> file and save this file in a <filename>/conf</filename> subdirectory of your service base folder. The container looks for a <filename>/conf/configuration.xml</filename> file in each jar-file. + </para> + <para> + All <filename>configuration.xml</filename> files located at <filename>conf/configuration.xml</filename> in the classpath (any directory, or any jar in the classpath) will have their services configured in the <literal>RootContainer</literal> scope. + </para> + <para> + All <filename>configuration.xml</filename> files located at <filename>conf/portal/configuration.xml</filename> in the classpath will have their services configured at the <literal>PortalContainer</literal> scope. + </para> + <para> + Additionally, <emphasis role="bold">portal extensions</emphasis> can use configuration information stored in <filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/02portal.war/WEB-INF/conf/configuration.xml</filename>, and will also have their services configured in the <literal>PortalContainer</literal> scope. + </para> + <para> + When eXo kernel reads a configuration, it loads the file from the kernel jar using the classloader and does not use an internet connection to resolve the file. + </para> + <note> + <para> + <emphasis role="bold">Portal extensions</emphasis> are described later in this document. + </para> + + </note> + <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuring_Services-Configuration_syntax"> + <title>Configuration syntax</title> + <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuration_syntax-Components"> + <title>Components</title> + <para> + A service component is defined in <filename>configuration.xml</filename> by using a <emphasis role="bold"><component></emphasis> element. + </para> + <para> + Only one piece of information is required when defining a service; the service implementation class. This is specified using <literal><type></literal> + </para> + <para> + Every component has a <literal><key></literal> that identifies it. If not explicitly set, a key defaults to the value of <literal><type></literal>. If a key can be loaded as a class, a class object is used as a key, otherwise a string is used. + </para> + <para> + The usual approach is to specify an interface as a key. + </para> + +<programlisting language="XML" role="XML"><xi:include href="../../../extras/Advanced_Development_Foundations/default.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> + <para> + The configuration found inside the jar file is considered as the default configuration. If you want to override this default configuration you can do it in different places outside the jar. When the container finds several configurations for the same service, the configuration which is found later replaces completely the one found previously. Let's call this the <emphasis>configuration override mechanism</emphasis>. + </para> + <para> + After deploying you find the configuration.xml file in webapps/portal/WEB-INF/conf Use component registration tags. Let's look at the key tag that defines the interface and the type tag that defines the implementation. Note that the key tag is not mandatory, but it improves performance. + </para> + +<programlisting language="XML" role="XML"> + <component> + <key>org.exoplatform.services.portletcontainer.persistence.PortletPreferencesPersister</key> + <type>org.exoplatform.services.portal.impl.PortletPreferencesPersisterImpl</type> + </component></programlisting> + <para> + Register plugins that can act as listeners or external plugin to bundle some plugin classes in other jar modules. The usual example is the hibernate service to which we can add hbm mapping files even if those are deployed in an other maven artifact. + </para> + +<programlisting language="XML" role="XML"><external-component-plugins> + <target-component>org.exoplatform.services.database.HibernateService</target-component> + <component-plugin> + <name>add.hibernate.mapping</name> + <set-method>addPlugin</set-method> + <type>org.exoplatform.services.database.impl.AddHibernateMappingPlugin</type> + <init-params> + <values-param> + <name>hibernate.mapping</name> + <value>org/exoplatform/services/portal/impl/PortalConfigData.hbm.xml</value> + <value>org/exoplatform/services/portal/impl/PageData.hbm.xml</value> + <value>org/exoplatform/services/portal/impl/NodeNavigationData.hbm.xml</value> + </values-param> + </init-params> + </component-plugin> +</external-component-plugins></programlisting> + <para> + In that sample we target the HibernateService and we will call its addPlugin() method with an argument of the type AddHibernateMappingPlugin. That object will first have been filled with the init parameters. + </para> + <para> + Therefore, it is possible to define services that will be able to receive plugins without implementing any framework interface. + </para> + <para> + Another example of use is the case of listeners as in the following code where a listener is added to the OrganisationService and will be called each time a new user is created: + </para> + +<programlisting language="XML" role="XML"><external-component-plugins> + <target-component>org.exoplatform.services.organization.OrganizationService</target-component> + <component-plugin> + <name>portal.new.user.event.listener</name> + <set-method>addListenerPlugin</set-method> + <type>org.exoplatform.services.portal.impl.PortalUserEventListenerImpl</type> + <description>this listener create the portal configuration for the new user</description> + <init-params> + <object-param> + <name>configuration</name> + <description>description</description> + <object type="org.exoplatform.services.portal.impl.NewPortalConfig"> + <field name="predefinedUser"> + <collection type="java.util.HashSet"> + <value><string>admin</string></value> + <value><string>exo</string></value> + <value><string>company</string></value> + <value><string>community</string></value> + <value><string>portal</string></value> + <value><string>exotest</string></value> + </collection> + </field> + <field name="templateUser"><string>template</string></field> + <field name="templateLocation"><string>war:/conf/users</string></field> + </object> + </object-param> + </init-params> + </component-plugin> +...</programlisting> + <para> + In the previous XML configuration, we refer the organization service and we will call its method addListenerPlugin with an object of type PortalUserEventListenerImpl. Each time a new user will be created (apart the predefined ones in the list above) methods of the PortalUserEventListenerImpl will be called by the service. + </para> + <para> + As you can see, there are several types of init parameters, from a simple value param which binds a key with a value to a more complex object mapping that fills a JavaBean with the info defined in the XML. + </para> + <para> + Many other examples exist such as for the Scheduler Service where you can add a job with a simple XML configuration or the JCR Service where you can add a NodeType from your own configuration.xml file. + </para> + <section id="sect-Reference_Guide_eXo_JCR_1.14-Components-RootContainer"> + <title>RootContainer</title> + <para> + As PortalContainer depends on the RootContainer, we will start by looking into this one. + </para> + <para> + The retrieval sequence in short: + </para> + <orderedlist> + <listitem> + <para> + Services default <classname>RootContainer</classname> configurations from JAR files <emphasis>/conf/configuration.xml</emphasis> + </para> + + </listitem> + <listitem> + <para> + External <classname>RootContainer</classname> configuration, to be found at <emphasis>exo-tomcat/exo-conf/configuration.xml</emphasis> + </para> + + </listitem> + + </orderedlist> + <note> + <para> + Naturally you always have to replace <parameter>exo-tomcat</parameter> by your own folder name. + </para> + + </note> + <para> + <emphasis role="bold">HashTable</emphasis> The <classname>RootContainer</classname> creates a java <classname>HashTable</classname> which contains key-value pairs for the services. The qualified interface name of each service is used as key for the hashtable. Hopefully you still remember that the <parameter><key></parameter> tag of the configuration file contains the interface name? The value of each hashtable pair is an object that contains the service configuration (yes, this means the whole structure between the <parameter><component></parameter> tags of your <filename>configuration.xml</filename> file). + </para> + <para> + The <classname>RootContainer</classname> runs over all jar files you find in <emphasis>exo-tomcat/lib</emphasis> and looks if there is a configuration file at <emphasis>/conf/configuration.xml</emphasis>, the services configured in this file are added to the hashtable. That way - at the end of this process - the default configurations for all services are stored in the hashtable. + </para> + <note> + <para> + What happens if the same service - recognized by the same qualified interface name - is configured in different jars? As the service only can exist one time the configuration of the jar found later overrides the previous configuration. You know that the loading <emphasis role="bold">order of the jars is unpredictable</emphasis> you <emphasis role="bold">must not depend on this</emphasis>. + </para> + + </note> + <para> + If you wish to provide your own configurations for one or several services, you can do it in a general configuration file that has to be placed at <emphasis>exo-tomcat/exo-conf/configuration.xml</emphasis>. Do not search for such a file on your computer - you won't find one, because this option is not used in the default installation. Here again the same rule applies: <emphasis>The posterior configuration replaces the previous one</emphasis>. + </para> + <para> + The further configuration retrieval depends on the container type. + </para> + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Components-PortalContainer"> + <title>PortalContainer</title> + <para> + The PortalContainer takes the hashtable filled by the RootContainer and continues to look in some more places. Here you get the opportunity to replace RootContainer configurations by those which are specific to your portal. Again, the configurations are overridden whenever necessary. + </para> + <para> + In short PortalContainer configurations are retrieved in the following lookup sequence : + </para> + <orderedlist> + <listitem> + <para> + Take over the configurations of the RootContainer + </para> + + </listitem> + <listitem> + <para> + Default PortalContainer configurations from all JAR files (folder <emphasis>/conf/portal/configuration.xml</emphasis>) + </para> + + </listitem> + <listitem> + <para> + Web application configurations from the portal.war file - or the <emphasis>portal</emphasis> weppapp (folder <emphasis>/WEB-INF/conf/configuration.xml</emphasis>) + </para> + + </listitem> + <listitem> + <para> + External configuration for services of a named portal, it will be found at <emphasis>exo-tomcat/exo-conf/portal/$portal_name/configuration.xml</emphasis> (as of Portal 2.5) + </para> + + </listitem> + + </orderedlist> + <para> + 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>. + </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. + </para> + + </note> + <note> + <para> + Under <emphasis role="bold">JBoss</emphasis> application server <emphasis>exo-conf</emphasis> will be looked up in directory described by JBoss System property <emphasis>jboss.server.config.url</emphasis>. If the property is not found or empty <emphasis>exo-jboss/exo-conf</emphasis> will be asked (since kernel 2.0.4). + </para> + + </note> + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Components-External_Plug_ins"> + <title>External Plug-ins</title> + <para> + The eXo Kernel supports non-component objects that can be configured, instantiated, and injected into registered components using method calls. This '<emphasis>plugin</emphasis>' method allows portal extensions to add additional configurations to core services. + </para> + <para> + An external plugin is defined by using the <literal><external-component-plugin></literal> wrapper element which contains one or more <literal><component-plugin></literal> definitions. + </para> + <para> + The <literal><external-component-plugin></literal> element uses <literal><target-component></literal> to specify a target service component that will receive injected objects. + </para> + <para> + Every <literal><component-plugin></literal> defines an implementation type, and a method on the target component to use for injection (<literal><set-method></literal>). + </para> + <para> + A plugin implementation class has to implement the <emphasis role="bold">org.exoplatform.container.component. ComponentPlugin</emphasis> interface. + </para> + <para> + In the following example the <literal>PortalContainerDefinitionPlugin</literal> implements the <literal>ComponentPlugin</literal>: + </para> + +<programlisting language="XML" role="XML"><xi:include href="../../../extras/Advanced_Development_Foundations/default1.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> + <para> + The <emphasis role="bold"><target-component></emphasis> defines the service for which the plugin is defined. The configuration is injected by the container using a method that is defined in <emphasis role="bold"><set-method></emphasis>. The method has exactly one argument of the type org.exoplatform.services.cms.categories.impl.TaxonomyPlugin: + </para> + <itemizedlist> + <listitem> + <para> + addTaxonomyPlugin(org.exoplatform.services.cms.categories.impl.TaxonomyPlugin plugin) + </para> + + </listitem> + + </itemizedlist> + <para> + The content of <emphasis role="bold"><init-params></emphasis> corresponds to the structure of the TaxonomyPlugin object. + </para> + <note> + <para> + You can configure the component CategoriesService using the addTaxonomyPlugin as often as you wish, you can also call addTaxonomyPlugin in different configuration files. The method addTaxonomyPlugin is then called several times, everything else depends on the implementation of the method. + </para> + + </note> + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Components-Service_instantiation"> + <title>Service instantiation</title> + <para> + As you have already learned the services are all singletons, so that the container creates only one single instance of each container. The services are created by calling the constructors (called <emphasis>constructor injection</emphasis>). If there are only zero-arguments constructors (<code>Foo public Foo(){}</code>) there are no problems to be expected. That's easy. + </para> + <para> + But now look at <ulink url="https://anonsvn.jboss.org/repos/exo-jcr/core/trunk/exo.core.component.org...">https://anonsvn.jboss.org/repos/exo-jcr/core/trunk/exo.core.component.org...</ulink> + </para> + <para> + This JDBC implementation of BaseOrganizationService interface has only one constructor: + </para> + +<programlisting language="Java" role="Java">public OrganizationServiceImpl(ListenerService listenerService, DatabaseService dbService);</programlisting> + <para> + You see this service depends on two other services. In order to be able to call this constructor the container first needs a <classname>ListenerService</classname> and a <classname>DatabaseService</classname>. Therefore these services must be instantiated before <classname>BaseOrganizationService</classname>, because <classname>BaseOrganizationService</classname> depends on them. + </para> + <para> + For this purpose the container first looks at the constructors of all services and creates a matrix of service dependencies in order to call the services in a proper order. If for any reason there are interdependencies or circular dependencies you will get a java <classname>Exception</classname>. <emphasis>In this way the dependencies are injected by the container</emphasis>. + </para> + <note> + <para> + What happens if one service has more than one constructor? The container always tries first to use the constructor with a maximum of arguments, if this is not possible the container continues step by step with constructors that have less arguments until arriving at the zero-argument constructor (if there is one). + </para> + + </note> + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Components-Service_Access"> + <title>Service Access</title> + <para> + As you want to follow the principle of <emphasis role="bold">Inversion of Control,</emphasis> you <emphasis role="bold">must not</emphasis> access the service directly. You need a <emphasis role="bold">Container</emphasis> to access the service. + </para> + <para> + With this command you get your current container: + </para> + <itemizedlist> + <listitem> + <para> + <emphasis role="bold">ExoContainer myContainer = ExoContainerContext.getCurrentContainer();</emphasis> + </para> + + </listitem> + + </itemizedlist> + <para> + Whenever you need one of the services that you have configured use the method: + </para> + <itemizedlist> + <listitem> + <para> + <emphasis role="bold">myContainer.getComponentInstance(class)</emphasis> + </para> + + </listitem> + + </itemizedlist> + <para> + In our case: + </para> + <itemizedlist> + <listitem> + <para> + <emphasis role="bold">ArticleStatsService statsService = (ArticleStatsService) myContainer.getComponentInstance(ArticleStatsService.class);</emphasis> + </para> + + </listitem> + + </itemizedlist> + <para> + Recapitulation: + </para> + +<programlisting language="Java" role="Java">package com.laverdad.common; + +import org.exoplatform.container.ExoContainer; +import org.exoplatform.container.ExoContainerContext; +import com.laverdad.services.*; + +public class Statistics { + + public int makeStatistics(String articleText) { + ExoContainer myContainer = ExoContainerContext.getCurrentContainer(); + ArticleStatsService statsService = (ArticleStatsService) + myContainer.getComponentInstance(ArticleStatsService.class); + int numberOfSentences = statsService.calcSentences(articleText); + return numberOfSentences; + } + + public static void main( String args[]) { + Statistics stats = new Statistics(); + String newText = "This is a normal text. The method only counts the number of periods. " + + "You can implement your own implementation with a more exact counting. " + + "Let`s make a last sentence."; + System.out.println("Number of sentences: " + stats.makeStatistics(newText)); + } +}</programlisting> + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Components-Includes_and_special_URLs"> + <title>Includes, and special URLs</title> + <para> + It is possible to divide the <filename>configuration.xml</filename> file into many smaller files, which are then included into the main configuration file. + </para> + <para> + The included files must be valid xml files; they cannot be fragments of text. + </para> + <para> + Below is an example <filename>configuration.xml</filename> that 'outsources' its content into several files: + </para> + <programlistingco> + <areaspec> + <area coords="6" id="area-Reference_Guide_eXo_JCR_1.14-Components-Includes_and_special_URLs-url_schema" /> + + </areaspec> + +<programlisting language="XML" role="XML"><xi:include href="../../../extras/Advanced_Development_Foundations/default2.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> + <calloutlist> + <callout arearefs="area-Reference_Guide_eXo_JCR_1.14-Components-Includes_and_special_URLs-url_schema"> + <para> + This line is being used to reference another configuration file. The <code>war:</code> URL schema indicates that the following path is to be resolved relative to the current <literal>PortalContainer</literal>'s servlet context resource path, starting with <emphasis role="bold">WEB-INF</emphasis> as a root. + </para> + + </callout> + + </calloutlist> + + </programlistingco> + + <note> + <para> + The current <literal>PortalContainer</literal> is really a newly created <literal>PortalContainer</literal>, as <code>war:</code> URLs only make sense for <literal>PortalContainer</literal> scoped configuration. + </para> + + </note> + <para> + Through the extension mechanism the servlet context used for resource loading is a <emphasis role="bold">unified servlet context</emphasis> (this is explained in a later section). + </para> + <para> + To have an 'include' path resolved relative to current classpath (context classloader), use a <code>'jar:'</code> URL schema. + </para> + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Components-Special_variables"> + <title>Special variables</title> + <para> + Configuration files may contain a <emphasis role="bold">special variable</emphasis> reference <emphasis>${container.name.suffix}</emphasis>. This variable resolves to the name of the current portal container, prefixed by underscore (_). + </para> + <para> + This facilitates reuse of configuration files in situations where portal-specific unique names need to be assigned to some resources; JNDI names, Database/DataSource names and JCR repository names, for example. + </para> + <para> + This variable is only defined when there is a current <literal>PortalContainer</literal> available and is only available for <literal>PortalContainer</literal> scoped services. + </para> + <para> + A good example of this is the <emphasis role="bold">HibernateService</emphasis>: + </para> + +<programlisting language="XML" role="XML"><xi:include href="../../../extras/Advanced_Development_Foundations/default3.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> + + </section> + + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuration_syntax-InitParams_configuration_element"> + <title>InitParams configuration element</title> + <para> + <parameter>InitParams</parameter> is a configuration element that is essentially a map of key-value pairs, where <emphasis role="bold">key</emphasis> is always a <literal>String</literal>, and <emphasis role="bold">value</emphasis> can be any type that can be described using the kernel XML configuration. + </para> + <para> + Service components that form the JBoss Enterprise Portal Platform infrastructure use <parameter>InitParams</parameter> elements to configure themselves. A component can have one instance of <parameter>InitParams</parameter> injected at most. + </para> + <para> + If the service component's constructor takes <parameter>InitParams</parameter> as any of the parameters it will automatically be injected at component instantiation time. + </para> + <para> + The XML configuration for a service component that expects an <parameter>InitParams</parameter> element must have an <parameter><init-params></parameter> element present, however this element can be left empty. + </para> + <para> + Below is an example of how the kernel XML configuration syntax looks when creating <parameter>InitParams</parameter> instances: + </para> + +<programlisting language="XML" role="XML"><xi:include href="../../../extras/Advanced_Development_Foundations/default4.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> + <para> + An <parameter>InitParams</parameter> element description begins with an <parameter><init-params></parameter> element. + </para> + <para> + It can have zero or more children elements, each of which is one of the following: + </para> + <itemizedlist> + <listitem> + <para> + <parameter><value-param></parameter> + </para> + + </listitem> + <listitem> + <para> + <parameter><values-param></parameter> + </para> + + </listitem> + <listitem> + <para> + <parameter><properties-param></parameter> + </para> + + </listitem> + + </itemizedlist> + <para> + or + </para> + <itemizedlist> + <listitem> + <para> + <parameter><object-param></parameter> + </para> + + </listitem> + + </itemizedlist> + <para> + Each of these child elements takes a <parameter><name></parameter> that serves as a map entry key, and an optional <parameter><description></parameter>. It also takes a type-specific <emphasis role="bold">value</emphasis> specification. + </para> + <para> + The value specification for the <parameter><properties-param></parameter> defines one or more <parameter><property></parameter> elements, each of which specifies two strings; a property name and a property value. This is evident in the two previous examples. + </para> + <para> + Each <parameter><properties-params></parameter> defines one <literal>java.util.Properties</literal> instance. + </para> + <para> + The value specification for <parameter><value-param></parameter> elements is a <parameter><value></parameter> element which defines a <literal>String</literal> instance. + </para> + +<programlisting language="XML" role="XML"><xi:include href="../../../extras/Advanced_Development_Foundations/default5.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> + <para> + The value specification for <parameter><values-param></parameter> requires one or more <parameter><value></parameter> elements. Each <parameter><value></parameter> represents one <literal>String</literal> instance. All <literal>String</literal> values are then collected into a <literal>java.util.List</literal> instance. + </para> + +<programlisting language="XML" role="XML"><xi:include href="../../../extras/Advanced_Development_Foundations/default6.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> + <para> + For <parameter><object-param></parameter> entries, the value specification consists of an <parameter><object></parameter> element which is used for plain Java style object specification (specifying an implementation <emphasis>class - <parameter><type></parameter></emphasis>, and <emphasis>property values - <parameter><field></parameter></emphasis>). + </para> + <para> + The following section has an example of specifying a field of with a <literal>Collection</literal> type. + </para> + <para> + The <parameter>InitParams</parameter> structure (the names and types of entries) is specific for each service, as it is the code inside a service components' class that defines which entry names to look up and what types it expects to find. + </para> + <section id="sect-Reference_Guide_eXo_JCR_1.14-InitParams_configuration_element-Value_Param"> + <title>Value-Param</title> + <para> + There is an value-param example: + </para> + +<programlisting language="XML" role="XML"> <component> + <key>org.exoplatform.portal.config.UserACL</key> + <type>org.exoplatform.portal.config.UserACL</type> + <init-params> +... + <value-param> + <name>access.control.workspace</name> + <description>groups with memberships that have the right to access the User Control Workspace</description> + <value>*:/platform/administrators,*:/organization/management/executive-board</value> + </value-param> +... + </component></programlisting> + <para> + The UserACL class accesses to the <emphasis role="bold">value-param</emphasis> in its constructor. + </para> + +<programlisting language="Java" role="Java">package org.exoplatform.portal.config; +public class UserACL { + + public UserACL(InitParams params) { + UserACLMetaData md = new UserACLMetaData(); + ValueParam accessControlWorkspaceParam = params.getValueParam("access.control.workspace"); + if(accessControlWorkspaceParam != null) md.setAccessControlWorkspace(accessControlWorkspaceParam.getValue()); +...</programlisting> + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-InitParams_configuration_element-Properties_Param"> + <title>Properties-Param</title> + <para> + Properties are name-value pairs. Both the name and the value are Java Strings. + </para> + <para> + Here you see the hibernate configuration example: + </para> + +<programlisting language="XML" role="XML"> <component> + <key>org.exoplatform.services.database.HibernateService</key> + <type>org.exoplatform.services.database.impl.HibernateServiceImpl</type> + <init-params> + <properties-param> + <name>hibernate.properties</name> + <description>Default Hibernate Service</description> + <property name="hibernate.show_sql" value="false"/> + <property name="hibernate.cglib.use_reflection_optimizer" value="true"/> + <property name="hibernate.connection.url" value="jdbc:hsqldb:file:../temp/data/exodb"/> + <property name="hibernate.connection.driver_class" value="org.hsqldb.jdbcDriver"/> +... + </properties-param> + </init-params> + </component></programlisting> + <para> + In the org.exoplatform.services.database.impl.HibernateServiceImpl you will find that the name "hibernate.properties" of the properties-param is used to access the properties. + </para> + +<programlisting language="Java" role="Java">package org.exoplatform.services.database.impl; + +public class HibernateServiceImpl implements HibernateService, ComponentRequestLifecycle { + public HibernateServiceImpl(InitParams initParams, CacheService cacheService) { + PropertiesParam param = initParams.getPropertiesParam("hibernate.properties"); +... +}</programlisting> + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-InitParams_configuration_element-Object_Param"> + <title>Object-Param</title> + <para> + Let's have a look at the configuration of the LDAPService. It's not important to know LDAP, we only discuss the parameters. + </para> + +<programlisting language="XML" role="XML"><component> + <key>org.exoplatform.services.ldap.LDAPService</key> + <type>org.exoplatform.services.ldap.impl.LDAPServiceImpl</type> + <init-params> + <object-param> + <name>ldap.config</name> + <description>Default ldap config</description> + <object type="org.exoplatform.services.ldap.impl.LDAPConnectionConfig"> + <field name="providerURL"><string>ldaps://10.0.0.3:636</string></field> + <field name="rootdn"><string>CN=Administrator,CN=Users,DC=exoplatform,DC=org</string></field> + <field name="password"><string>exo</string></field> + <field name="version"><string>3</string></field> + <field name="minConnection"><int>5</int></field> + <field name="maxConnection"><int>10</int></field> + <field name="referralMode"><string>ignore</string></field> + <field name="serverName"><string>active.directory</string></field> + </object> + </object-param> + </init-params> +</component></programlisting> + <para> + You see here an <emphasis role="bold">object-param</emphasis> is being used to pass the parameters inside an object (actually a java bean). It consists of a <emphasis role="bold">name</emphasis>, a <emphasis role="bold">description</emphasis> and exactly one <emphasis role="bold">object</emphasis>. The object defines the <emphasis role="bold">type</emphasis> and a number of <emphasis role="bold">fields</emphasis>. + </para> + <para> + Here you see how the service accesses the object: + </para> + +<programlisting language="Java" role="Java">package org.exoplatform.services.ldap.impl; + +public class LDAPServiceImpl implements LDAPService { +... + public LDAPServiceImpl(InitParams params) { + LDAPConnectionConfig config = (LDAPConnectionConfig) params.getObjectParam("ldap.config") + .getObject(); +...</programlisting> + <para> + The passed object is LDAPConnectionConfig which is a classic <emphasis role="bold">java bean</emphasis>. It contains all fields and also the appropriate getters and setters (not listed here). You also can provide default values. The container creates a new instance of your bean and calls all setters whose values are configured in the configuration file. + </para> + +<programlisting language="Java" role="Java">package org.exoplatform.services.ldap.impl; + +public class LDAPConnectionConfig { + private String providerURL = "ldap://127.0.0.1:389"; + private String rootdn; + private String password; + private String version; + private String authenticationType = "simple"; + private String serverName = "default"; + private int minConnection; + private int maxConnection; + private String referralMode = "follow"; +...</programlisting> + <para> + You see that the types (String, int) of the fields in the configuration correspond with the bean. A short glance in the kernel_1_2.xsd file let us discover more simple types: + </para> + <itemizedlist> + <listitem> + <para> + <emphasis role="bold">string, int, long, boolean, date, double</emphasis> + </para> + + </listitem> + + </itemizedlist> + <para> + Have a look on this type test xml file: <ulink url="https://anonsvn.jboss.org/repos/exo-jcr/kernel/trunk/exo.kernel.container...">https://anonsvn.jboss.org/repos/exo-jcr/kernel/trunk/exo.kernel.container...</ulink>. + </para> + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-InitParams_configuration_element-Collection"> + <title>Collection</title> + <para> + You also can use java collections to configure your service. In order to see an example, let's open the database-organization-configuration.xml file. This file defines a default user organization (users, groups, memberships/roles) of your portal. They use component-plugins which are explained later. You will see that object-param is used again. + </para> + <para> + There are two collections: The first collection is an <emphasis role="bold">ArrayList</emphasis>. This ArrayList contains only one value, but there could be more. The only value is an object which defines the field of the NewUserConfig$JoinGroup bean. + </para> + <para> + The second collection is a <emphasis role="bold">HashSet</emphasis> that is a set of strings. + </para> + +<programlisting language="XML" role="XML"> <component-plugin> + <name>new.user.event.listener</name> + <set-method>addListenerPlugin</set-method> + <type>org.exoplatform.services.organization.impl.NewUserEventListener</type> + <description>this listener assign group and membership to a new created user</description> + <init-params> + <object-param> + <name>configuration</name> + <description>description</description> + <object type="org.exoplatform.services.organization.impl.NewUserConfig"> + <field name="group"> + <collection type="java.util.ArrayList"> + <value> + <object type="org.exoplatform.services.organization.impl.NewUserConfig$JoinGroup"> + <field name="groupId"><string>/platform/users</string></field> + <field name="membership"><string>member</string></field> + </object> + </value> + </collection> + </field> + <field name="ignoredUser"> + <collection type="java.util.HashSet"> + <value><string>root</string></value> + <value><string>john</string></value> + <value><string>marry</string></value> + <value><string>demo</string></value> + <value><string>james</string></value> + </collection> + </field> + </object> + </object-param> + </init-params> + </component-plugin></programlisting> + <para> + Let's look at the org.exoplatform.services.organization.impl.NewUserConfig bean: + </para> + +<programlisting language="Java" role="Java">public class NewUserConfig { + private List role; + private List group; + private HashSet ignoredUser; + + ... + + public void setIgnoredUser(String user) { + ignoredUser.add(user); + + ... + + static public class JoinGroup { + public String groupId; + public String membership; + ... +}</programlisting> + <para> + You see the values of the HashSet are set one by one by the container, and it's the responsibility of the bean to add these values to its HashSet. + </para> + <para> + The JoinGroup object is just an inner class and implements a bean of its own. It can be accessed like any other inner class using NewUserConfig.JoinGroup. + </para> + + </section> + + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuration_syntax-Component_Plugin_Priority"> + <title>Component Plugin Priority</title> + <para> + Since kernel version 2.0.6 it is possible to setup order of loading for ComponentPlugin. Use the ' <emphasis role="bold">priority</emphasis>' tag to define plugin's load priority. By <emphasis role="bold">default</emphasis> all plugins get <emphasis role="bold">priority '0'</emphasis>; they will be loaded in the container's natural way. If you want one plugin to be loaded later than the others then just set priority for it <emphasis role="bold">higher than zero</emphasis>. + </para> + <para> + Simple example of fragment of a <emphasis role="bold">configuration.xml</emphasis>. + </para> + +<programlisting language="XML" role="XML">... +<component> + <type>org.exoplatform.services.Component1</type> +</component> + +<external-component-plugins> + <target-component>org.exoplatform.services.Component1</target-component> + + <component-plugin> + <name>Plugin1</name> + <set-method>addPlugin</set-method> + <type>org.exoplatform.services.plugins.Plugin1</type> + <description>description</description> + <priority>1</priority> + </component-plugin> + + <component-plugin> + <name>Plugin2</name> + <set-method>addPlugin</set-method> + <type>org.exoplatform.services.plugins.Plugin2</type> + <description>description</description> + <priority>2</priority> + </component-plugin> + +</external-component-plugins> + +<external-component-plugins> + <target-component>org.exoplatform.services.Component1</target-component> + <component-plugin> + <name>Plugin3</name> + <set-method>addPlugin</set-method> + <type>org.exoplatform.services.plugins.Plugin3</type> + <description>description</description> + </component-plugin> +</external-component-plugins> +...</programlisting> + <para> + In the above example plugin 'Plugin3' will be loaded first because it has the default priority '0'. Then, plugin 'Plugin1' will be loaded and last one is plugin 'Plugin2'. + </para> + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuration_syntax-Configuration_Logging"> + <title>Configuration Logging</title> + <para> + In case you need to solve problems with your service configuration, you have to know from which JAR/WAR causes your troubles. Add the JVM system property <parameter>org.exoplatform.container.configuration.debug</parameter> to your eXo.bat or eXo.sh file (exo-tomcat/bin/). + </para> + +<programlisting>set EXO_CONFIG_OPTS="-Dorg.exoplatform.container.configuration.debug"</programlisting> + <para> + If this property is set the container configuration manager reports during startup the configuration retrieval process to the standard output (System.out). + </para> + +<programlisting>...... +Add configuration jar:file:/D:/Projects/eXo/dev/exo-working/exo-tomcat/lib/exo.kernel.container-trunk.jar!/conf/portal/configuration.xml +Add configuration jar:file:/D:/Projects/eXo/dev/exo-working/exo-tomcat/lib/exo.kernel.component.cache-trunk.jar!/conf/portal/configuration.xml +Add configuration jndi:/localhost/portal/WEB-INF/conf/configuration.xml import jndi:/localhost/portal/WEB-INF/conf/common/common-configuration.xml +import jndi:/localhost/portal/WEB-INF/conf/database/database-configuration.xml import jndi:/localhost/portal/WEB-INF/conf/ecm/jcr-component-plugins-configuration.xml +import jndi:/localhost/portal/WEB-INF/conf/jcr/jcr-configuration.xml +......</programlisting> + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuration_syntax-Import"> + <title>Import</title> + <para> + The import tag allows to link to other configuration files. These imported files can be placed anywhere. If you write a default configuration which is part of your jar file you should not import files from outside your jar. + </para> + <itemizedlist> + <listitem> + <para> + <emphasis role="bold">war</emphasis>: Imports from <emphasis role="bold">portal.war/WEB-INF</emphasis> + </para> + + </listitem> + <listitem> + <para> + <emphasis role="bold">jar</emphasis> or <emphasis role="bold">classpath</emphasis>: Uses the <emphasis role="bold">classloader</emphasis>, you can use this prefix in the default configuration for importing an other configuration file which is accessible by the classloader. + </para> + + </listitem> + <listitem> + <para> + <emphasis role="bold">file</emphasis>: Uses an <emphasis role="bold">absolute path</emphasis>, you also can put a <emphasis role="bold">URL</emphasis>. + </para> + + </listitem> + <listitem> + <para> + <emphasis role="bold">without any prefix</emphasis>: + </para> + + </listitem> + + </itemizedlist> + <para> + If you open the "portal/trunk/web/portal/src/main/webapp/WEB-INF/conf.configuration.xml" you will see that it consists only of imports: + </para> + +<programlisting language="XML" role="XML"><import>war:/conf/common/common-configuration.xml</import> +<import>war:/conf/common/logs-configuration.xml</import> +<import>war:/conf/database/database-configuration.xml</import> +<import>war:/conf/jcr/jcr-configuration.xml</import> +<import>war:/conf/common/portlet-container-configuration.xml</import> +...</programlisting> + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuration_syntax-System_properties"> + <title>System properties</title> + <para> + Since kernel 2.0.7 and 2.1, it is possible to use system properties in literal values of component configuration meta data. This makes it possible to resolve properties at runtime instead of providing a value at packaging time. + </para> + <para> + In portal/trunk/web/portal/src/main/webapp/WEB-INF/conf/database/database-configuration.tmpl.xml you find an example for system properties: + </para> + +<programlisting language="XML" role="XML"> <component> + <key>org.exoplatform.services.database.HibernateService</key> + <jmx-name>database:type=HibernateService</jmx-name> + <type>org.exoplatform.services.database.impl.HibernateServiceImpl</type> + <init-params> + <properties-param> + <name>hibernate.properties</name> + <description>Default Hibernate Service</description> +... + <property name="hibernate.connection.url" value="${connectionUrl}"/> + <property name="hibernate.connection.driver_class" value="${driverClass}"/> + <property name="hibernate.connection.username" value="${username}"/> + <property name="hibernate.connection.password" value="${password}"/> + <property name="hibernate.dialect" value="${dialect}"/> +... + </properties-param> + </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> + </para> + + </section> + + + </section> + + +</section> + + Deleted: epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/AuthenticationAndIdentity/SSO.xml 2011-11-24 17:26:22 UTC (rev 8138) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml 2011-11-25 00:48:53 UTC (rev 8141) @@ -1,1695 +0,0 @@ -<?xml version='1.0' encoding='utf-8' ?> -<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ -<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> -%BOOK_ENTITIES; -]> -<section id="sect-Reference_Guide_eXo_JCR_1.14-SSO_Single_Sign_On_"> - <title><remark>SSO - Single Sign On</remark> - </title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-SSO_Single_Sign_On_-Overview"> - <title>Overview</title> - <para> - JBoss Enterprise Portal Platform provides an implementation of Single Sign On (<literal>SSO</literal>) as an integration and aggregation platform. - </para> - <para> - When logging into the portal users can access many systems through portlets using a single identity. In many cases, however, the portal infrastructure must be integrated with other SSO enabled systems. - </para> - <para> - There are many different Identity Management solutions available. In most cases each SSO framework provides a unique way to plug into a Java EE application. - </para> - <para> - This section will cover the implementation of four different SSO plug-ins with JBoss Enterprise Portal Platform: - </para> - <itemizedlist> - <listitem> - <para> - <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-SSO_Single_Sign_On_-Central_Authentication_Service" /> - </para> - - </listitem> - <listitem> - <para> - <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-SSO_Single_Sign_On_-Java_Open_Single_Sign_On_Project" /> - </para> - - </listitem> - <listitem> - <para> - <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-SSO_Single_Sign_On_-OpenSSO" /> - </para> - - </listitem> - <listitem> - <para> - <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-SSO_Single_Sign_On_-SPNEGO_Simple_and_Protected_GSSAPI_Negotiation_Mechanism" /> - </para> - - </listitem> - - </itemizedlist> - <note> - <title>Prerequisites</title> - <para> - In this tutorial, the SSO server is being installed in a Tomcat environment. Tomcat can be obtained from <ulink type="http" url="http://tomcat.apache.org"> http://tomcat.apache.org </ulink> . - </para> - - </note> - <para> - All the packages required for SSO setup can be found in a zip file located in the <filename>jboss-epp-<replaceable>VERSION</replaceable>/gatein-sso</filename> directory of the JBoss Enterprise Portal Platform binary package. - </para> - <para> - In the following scenarios this directory will be referred to as <replaceable>PORTAL_SSO</replaceable>. - </para> - <warning> - <para> - Users are advised to not run any portal extensions that could override the data when manipulating the <filename>gatein.ear</filename> file directly. - </para> -  - </warning> - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-SSO_Single_Sign_On_-Enabling_SSO_using_JBoss_SSO_Valve"> - <title>Enabling SSO using JBoss SSO Valve</title> -  <para> - The JBoss SSO valve is useful to authenticate a user on one JBoss Enterprise Portal Platform node in a cluster and have that authentication automatically carry across to other nodes in the cluster. - </para> - <para> - This authentication can also be used in any other web applications which may require authentication, <emphasis role="bold">provided that these applications use same roles as the main portal instance</emphasis>. Attempting to use an SSO authentication in an application that uses different roles may create authorization errors (<emphasis role="bold">403</emphasis> errors, for example). - </para> - <note> - <title>Reauthentication</title> - <para> - This behavior is coming from the fact that same JAAS principal is added by SSO valve to all HTTP requests, even to other web applications. - </para> - <para> - So the same roles are required because of it. There is an alternative that allows you to configure the SSO valve with the <parameter>requireReauthentication=true</parameter> parameter, which will force the SSO valve to perform reauthentication with saved credentials in each HTTP request against security domain of particular web application where the request is coming. - </para> - <para> - This will ensure that a new principal for that web application will be created with updated roles for that web application. - </para> - <para> - In other words; when <parameter>requireReauthentication</parameter> is <emphasis role="bold">false</emphasis> (the default state), you need to have the same roles among web applications. When <parameter>requireReauthentication</parameter> is <emphasis role="bold">true</emphasis> you need to have same username and passwords. - </para> - - </note> - <para> - More info about the JBoss SSO valve can be found at <ulink type="http" url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Web_Platform/5/html/Ad..." />. - </para> - <para> - To successfully implement SSO integration, do the following: - </para> - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Enabling_SSO_using_JBoss_SSO_Valve-SSO_Integration"> - <title>SSO Integration</title> - <step> - <para> - Open the <filename>/<replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/jbossweb.sar/server.xml</filename> file and uncomment one of the two <parameter>Valve</parameter> entries: - </para> - <itemizedlist> - <listitem> - <para> - For a <emphasis>non-clustered</emphasis> implementation, uncomment: - </para> - -<programlisting language="XML" role="XML"><Valve className="org.apache.catalina.authenticator.SingleSignOn" /> -</programlisting> - - </listitem> - <listitem> - <para> - For a <emphasis>clustered</emphasis> implementation, uncomment: - </para> - -<programlisting language="XML" role="XML"><Valve className="org.jboss.web.tomcat.service.sso.ClusteredSingleSignOn" /></programlisting> - - </listitem> - - </itemizedlist> - - </step> - <step> - <para> - For implementation of the SSO valve among the different nodes of cluster, all the nodes must share the same domain (<emphasis>node1.yourdomain.com</emphasis> and <emphasis>node2.yourdomain.com</emphasis>, for example). - </para> - <para> - This domain needs to be configured in the SSO valve parameter <parameter>cookieDomain</parameter>. This is required because the SSO valve adds the cookie <emphasis role="bold">JSESSIONIDSSO</emphasis>, which is, by default bound only to the host where the request is originating. - </para> - <para> - When the <parameter>cookieDomain</parameter> parameter is used, the cookie is bound to the domain (like <emphasis>yourdomain.com</emphasis>), which will ensure that it is shared among both hosts <emphasis>node1.yourdomain.com</emphasis> and <emphasis>node2.yourdomain.com</emphasis>. - </para> - <para> - So in this case, the valve configuration would be: - </para> - -<programlisting language="XML" role="XML"><Valve className="org.jboss.web.tomcat.service.sso.ClusteredSingleSignOn" -cookieDomain="yourdomain.com" /> -</programlisting> - - </step> - <step> - <para> - Another important thing is that both cluster nodes needs to be on same cluster (using same parameter <emphasis role="bold">-g</emphasis> and same parameter <emphasis role="bold">-u</emphasis> and also using parameter <emphasis role="bold">-Dexo.profiles=cluster</emphasis>). - </para> - <para> - They must also share the same NFS directory and the same database and apply all the configuration needed for JBoss Enterprise Portal Platform cluster. - </para> - - </step> - - </procedure> - - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Enabling_SSO_using_JBoss_SSO_Valve-Testing_SSO_in_a_physical_cluster"> - <title>Testing SSO in a physical cluster</title> - <para> - In this example, we will try to simulate testing on more physical machines by simply using virtual hosts on single machine. - </para> - - </formalpara> - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Enabling_SSO_using_JBoss_SSO_Valve-Testing_the_SSO_Valve"> - <title>Testing the SSO Valve</title> - <step> - <para> - If you are using a Linux system, you can configure file <emphasis role="bold">/etc/hosts</emphasis> to contain these lines: - </para> - -<programlisting> -127.0.1.1 machine1.yourdomain.com -127.0.1.2 machine2.yourdomain.com -</programlisting> - - </step> - <step> - <para> - Open the <filename><replaceable><JBOSS_HOME></replaceable>/server/all/deploy/jbossweb.sar/server.xml</filename> file. - </para> - - </step> - <step> - <para> - Uncomment the line: - </para> - -<programlisting language="XML" role="XML"> -</programlisting> - - </step> - <step> - <para> - And edit it to match the following: - </para> - -<programlisting language="XML" role="XML"><Valve className="org.jboss.web.tomcat.service.sso.ClusteredSingleSignOn" -cookieDomain="yourdomain.com" /> -</programlisting> - <para> - This will ensure the <literal>JSESSIONIDSSO</literal> cookie is used in the correct domain, allowing the SSO authentication to occur. - </para> - - </step> - <step> - <para> - Copy server configuration <emphasis role="bold">all</emphasis> and create another two configurations <emphasis role="bold">node1</emphasis> and <emphasis role="bold">node2</emphasis> from it. - </para> - - </step> - <step> - <para> - Start both cluster nodes with commands: - </para> - -<programlisting> -./run.sh -c node1 -b machine1.yourdomain.com -Dexo.profiles=cluster -Djboss.messaging.ServerPeerID=0 & -./run.sh -c node2 -b machine2.yourdomain.com -Dexo.profiles=cluster -Djboss.messaging.ServerPeerID=1 & -</programlisting> - - </step> - <step> - <para> - Go to <ulink type="http" url="http://machine1.yourdomain.com:8080/portal">http://machine1.yourdomain.com:8080/portal</ulink> and login as a user. - </para> - - </step> - <step> - <para> - Access a private URL on the second host, such as <ulink type="http" url="http://machine2.yourdomain.com:8080/portal/dologin">http://machine2.yourdomain.com:8080/portal/dologin</ulink>, for example. - </para> - <para> - Now you should be logged directly into <literal>machine2</literal> thanks to SSO valve. - </para> - - </step> - <step> - <para> - Logout from SSO initiating machine1.yourdomain.com should also logged you out from other cluster nodes. So you should be logout directly from machine2 as well. - </para> - - </step> - - </procedure> - - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Enabling_SSO_using_JBoss_SSO_Valve-Enabling_SSO_with_Other_Web_Applications"> - <title>Enabling SSO with Other Web Applications</title> - <para> - As mentioned earlier, in order to use SSO authentication between JBoss Enterprise Portal Platform instances and other web applications, the roles defined in the web application must match those used in the portal instance (unless you have the <parameter>requireReauthentication</parameter> parameter set to <literal>true</literal>). - </para> - - </formalpara> - <para> - As an example, to use the SSO Valve to authenticate a user in both a portal instance and the JMX Console, the following actions would be required: - </para> - <procedure> - <title></title> - <step> - <para> - Open the <filename><replaceable><JBOSS_HOME></replaceable>/server/node1/deploy/jmx-console.war/WEB-INF/web.xml</filename> file and edit it as follows: - </para> - <substeps> - <step> - <para> - Change the <parameter><role-name></parameter> entry in the <parameter><auth-constraint></parameter> element (line <literal>110</literal>) from <literal>JBossAdmin</literal> to <literal>users</literal>: - </para> - -<programlisting language="XML" role="XML"><auth-constraint> -  - <role-name>users</role-name> -</auth-constraint></programlisting> - - </step> - <step> - <para> - Change the <parameter><role-name></parameter> entry in the <parameter><security-role></parameter> element (line <literal>120</literal>) from <literal>JBossAdmin</literal> to <literal>users</literal> - </para> - -<programlisting language="XML" role="XML"><security-role> -  - <role-name>users</role-name> -</security-role></programlisting> - - </step> - - </substeps> - - </step> - - </procedure> - - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Enabling_SSO_using_JBoss_SSO_Valve-Testing_SSO_With_Other_Web_Applications"> - <title>Testing SSO With Other Web Applications</title> - <para> - To test that SSO authentication is enabled from portal instances to other web applications (in this case, the JMX Console), do the following: - </para> - - </formalpara> - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Enabling_SSO_using_JBoss_SSO_Valve-Test_SSO_Between_Portal_and_JMX_Console"> - <title>Test SSO Between Portal and JMX Console</title> - <step> - <para> - Start a portal instance on one node: - </para> - -<programlisting>./run.sh -c node1 -b machine1.yourdomain.com -Dexo.profiles=cluster -Djboss.messaging.ServerPeerID=0 & -</programlisting> - - </step> - <step> - <para> - Navigate to <ulink type="http" url="http://machine1.yourdomain.com:8080/portal/private/classic" /> and authenticate with the pre-configured user account "<systemitem>root</systemitem>" (password "<systemitem>gtn </systemitem>"). - </para> - - </step> - <step> - <para> - Navigate to <ulink type="http" url="http://machine1.yourdomain.com:8080/jmx-console" />. You should be automatically authenticated into the JMX Console. - </para> - - </step> - - </procedure> - - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Enabling_SSO_using_JBoss_SSO_Valve-Using_SSO_to_Authenticate_From_the_Public_Page"> - <title>Using SSO to Authenticate From the Public Page</title> - <para> - The previous configuration changes in this section are useful if a user is using a secured URL (<ulink type="http" url="http://localhost:8080/portal/private/classic" />, for example) to log in to the portal instance. - </para> - - </formalpara> - <para> - Further changes are needed however, if SSO authentication is required to work with the <guilabel>Sign In</guilabel> button on the front page of the portal (<ulink type="http" url="http://localhost:8080/portal/classic" />). - </para> - <para> - To enable this functionality, the <guilabel>Sign In</guilabel> link must redirect to some secured URL, which will ensure that JAAS authentication will be enforced directly without showing login dialog. - </para> - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Enabling_SSO_using_JBoss_SSO_Valve-Redirect_to_Use_SSO_Valve_Authentication"> - <title>Redirect to Use SSO Valve Authentication</title> - <step> - <para> - Open the <filename><replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/web.war/groovy/groovy/webui/component/UIBannerPortlet.gtml</filename> file and edit the line: - </para> - -<programlisting language="Java" role="java"><a class="Login" onclick="$signInAction"><%=_ctx.appRes("UILoginForm.label.Signin")%></a> -</programlisting> - <para> - To read: - </para> - -<programlisting language="Java" role="java"><a class="Login" href="/portal/private/classic"><%=_ctx.appRes("UILoginForm.label.Signin")%></a> -</programlisting> - - </step> - <step> - <para> - Open the <filename><replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/web.war/groovy/portal/webui/component/UILogoPortlet.gtmpl</filename> file and change the line: - </para> - -<programlisting language="Java" role="java"><a onclick="$signInAction"><%=_ctx.appRes("UILogoPortlet.action.signin")%></a> -</programlisting> - <para> - To read: - </para> - -<programlisting language="Java" role="java"><a href="/portal/private/classic"><%=_ctx.appRes("UILogoPortlet.action.signin")%></a> -</programlisting> - - </step> - - </procedure> - - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-SSO_Single_Sign_On_-Central_Authentication_Service"> - <title>Central Authentication Service</title> - <para> - This Single Sign On plugin enables seamless integration between JBoss Enterprise Portal Platform and the Central Authentication Service (<emphasis role="bold">CAS</emphasis>) Single Sign On Framework. Details about CAS can be found <ulink url="http://www.ja-sig.org/cas/"> here </ulink> . - </para> - <para> - The integration consists of two parts; the first part consists of installing or configuring a CAS server, the second part consists of setting up the portal to use the CAS server. - </para> - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Central_Authentication_Service-CAS_server"> - <title>CAS server</title> - <step> - <para> - Set up the server to authenticate against the portal login module. - </para> - - </step> - <step> - <para> - Downloaded CAS from <ulink type="http" url="http://www.jasig.org/cas/download"> http://www.jasig.org/cas/download </ulink> . - </para> - <para> - The version, tested with these instructions is <emphasis role="bold">CAS 3.3.5</emphasis>. Other versions may work. - </para> - - </step> - <step> - <para> - Extract the downloaded file into a suitable location. This location will be referred to as <replaceable>CAS_DIR</replaceable> in the following example. - </para> - - </step> - - </procedure> - - <para> - The simplest way to configure the web archive is to make the necessary changes directly into the CAS codebase. - </para> - <note> - <para> - To perform the final build step and complete these instructions you will need the Apache Maven 2. Download it from <ulink type="http" url="http://maven.apache.org/download.html"> here </ulink> . - </para> - - </note> - <para> - Change the default authentication handler with the one provided by JBoss Enterprise Portal Platform. - </para> - <para> - The CAS Server Plugin makes secure callbacks to a RESTful service installed on the remote JBoss Enterprise Portal Platform 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 controlled by the <filename>cas.war/WEB-INF/deployerConfigContext.xml </filename> file. - </para> - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Central_Authentication_Service-Modifying_CAS_server"> - <title>Modifying CAS server</title> - <step> - <para> - Open <filename><replaceable>CAS_DIR</replaceable>/cas-server-webapp/src/main/webapp/WEB-INF/deployerConfigContext.xml</filename> - </para> - - </step> - <step> - <para> - Replace this code: - </para> - -<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default102.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - <para> - with the following (ensure you set the host, port and context with the values corresponding to your portal). Also available in <filename>GATEIN_SSO_HOME/cas/plugin/WEB-INF/deployerConfigContext.xml</filename>.): - </para> - -<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default103.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - - </step> - <step> - <para> - Copy <filename><replaceable>PORTAL_SSO</replaceable>/cas/plugin/WEB-INF/lib/sso-cas-plugin-<VERSION>.jar</filename> and <filename><replaceable>PORTAL_SSO</replaceable>/cas/plugin/WEB-INF/lib/commons-httpclient-<VERSION>.jar</filename> into the <filename><replaceable>CAS_DIR</replaceable>/cas-server-webapp/src/main/webapp/WEB-INF/lib</filename> created directory. - </para> - - </step> - <step> - <para> - If you have not already done so, download an instance of Tomcat and extract it into a suitable location (which will be called <filename>TOMCAT_HOME</filename> for these instructions). - </para> - - </step> - <step> - <para> - Edit <filename>TOMCAT_HOME/conf/server.xml</filename> and change the 8080 port to 8888 to avoid a conflict with the default JBoss Enterprise Portal Platform. - </para> - <note> - <para> - If JBoss Enterprise Portal Platform is running on the same machine as Tomcat other ports will need to be changed in addition to 8080 in order to avoid conflicts. They can be changed to any free port. For example; you can change the admin port from 8005 to 8805 and the AJP port from 8009 to 8809. - </para> - - </note> - - </step> - <step> - <para> - Navigate locally to the <filename><replaceable>CAS_DIR</replaceable>/cas-server-webapp</filename> directory and execute the following command: - </para> - -<programlisting>mvn install -</programlisting> - - </step> - <step> - <para> - Copy the <filename><replaceable>CAS_DIR</replaceable>/cas-server-webapp/target/cas.war</filename> file into the <filename>TOMCAT_HOME/webapps</filename> directory. - </para> - <para> - Tomcat should start without issue and should be accessible at <ulink type="http" url="http://localhost:8888/cas"> http://localhost:8888/cas </ulink> . - </para> - <note> - <para> - At this stage the login functionality will not be available. - </para> - - </note> - <mediaobject> - <imageobject> - <imagedata fileref="images/AuthenticationAndIdentity/SSO/cas.png" format="PNG" scale="100" width="444" /> - </imageobject> - - </mediaobject> - - </step> - - </procedure> - - <note> - <para> - On logout, the CAS server will display the CAS logout page with a link to return to the portal. To make the CAS server redirect to the portal page after a logout, modify the <filename>cas.war/WEB-INF/cas-servlet.xml</filename> to include the follow line : - </para> - -<programlisting> -<bean id="logoutController" class="org.jasig.cas.web.LogoutController" - p:centralAuthenticationService-ref="centralAuthenticationService" - p:logoutView="casLogoutView" - p:warnCookieGenerator-ref="warnCookieGenerator" - p:ticketGrantingTicketCookieGenerator-ref="ticketGrantingTicketCookieGenerator" - p:followServiceRedirects="true"/> -</programlisting> - - </note> - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Central_Authentication_Service-Setup_the_CAS_client"> - <title>Setup the CAS client</title> - <step> - <para> - Copy all the libraries from the <filename><replaceable>PORTAL_SSO</replaceable>/cas/gatein.ear/lib</filename> directory into the <filename>JBOSS_HOME/server/default/deploy/gatein.ear/lib</filename>) directory. - </para> - - </step> - <step> - <para> - Edit the <filename>jboss-as/server/<replaceable>PROFILE</replaceable>/deploy/gatein.ear/META-INF/gatein-jboss-beans.xml</filename> and uncomment this section: - </para> - -<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default105.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - <para> - There's a line comment already in this source file to assist you. - </para> -  - </step> - <step> - <para> - The installation can be tested at this point (assuming the CAS server on Tomcat is running): - </para> - <procedure> - <step> - <para> - Start (or restart) JBoss Enterprise Portal Platform and direct your web browser to <ulink type="http" url="http://localhost:8888/cas"> http://localhost:8888/cas </ulink> . - </para> - - </step> - <step> - <para> - Login with the username <literal>root</literal> and the password <literal>gtn</literal> (or any other account created through the portal). - </para> - - </step> - - </procedure> - - - </step> - - </procedure> - - <para> - To utilize the Central Authentication Service, JBoss Enterprise Portal Platform needs to redirect all user authentication to the CAS server. - </para> - <para> - Information about where the CAS is hosted must be properly configured within the JBoss Enterprise Portal Platform instance. The required configuration is done by modifying three files. - </para> - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Central_Authentication_Service-Redirect_to_CAS"> - <title>Redirect to CAS</title> - <step> - <para> - Modify the '<emphasis role="bold">Sign In</emphasis>' link in the <filename><replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/web.war/groovy/groovy/webui/component/UIBannerPortlet.gtml</filename> file as follows: - </para> - -<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default106.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - - </step> - <step> - <para> - Modify the '<emphasis role="bold">Sign In</emphasis>' link in the <filename><replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/web.war/groovy/portal/webui/component/UILogoPortlet.gtmpl</filename> file as follows: - </para> - -<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default107.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - - </step> - <step> - <para> - Replace the entire contents of <filename>gatein.ear/02portal.war/login/jsp/login.jsp</filename> with: - </para> - -<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default108.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - - </step> - <step> - <para> - Add the following Filters at the top of the filter chain in <filename>gatein.ear/02portal.war/WEB-INF/web.xml</filename>: - </para> - -<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default109.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - - </step> - - </procedure> - - <para> - Once these changes have been made, all links to the user authentication pages will redirect to the CAS centralized authentication form and CAS can be used as an SSO implementation in your portal. - </para> - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-SSO_Single_Sign_On_-Java_Open_Single_Sign_On_Project"> - <title>Java Open Single Sign-On Project</title> - <para> - This Single Sign On plugin enables seamless integration between JBoss Enterprise Portal Platform and the Java Open Single Sign-On Project (<emphasis role="bold">JOSSO</emphasis>) Single Sign On Framework. Details about JOSSO can be found at <ulink url="http://www.josso.org"> www.josso.org </ulink> . - </para> - <para> - This section details setting up the JOSSO server to authenticate against the JBoss Enterprise Portal Platform login module. - </para> - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Java_Open_Single_Sign_On_Project-JOSSO_server"> - <title>JOSSO server</title> - <step> - <para> - Download JOSSO from <ulink type="http" url="http://sourceforge.net/projects/josso/files/"> http://sourceforge.net/projects/josso/files/ </ulink> . - </para> - <note> - <para> - Use the package that embeds Apache Tomcat. The integration was tested with JOSSO-1.8.1. - </para> - - </note> - - </step> - <step> - <para> - Extract the package into what will be called <filename>JOSSO_HOME</filename> in this example. - </para> - - </step> - - </procedure> - - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Java_Open_Single_Sign_On_Project-Modifying_JOSSO_server"> - <title>Modifying JOSSO server</title> - <step> - <para> - Copy the files from <filename><replaceable>PORTAL_SSO</replaceable>/josso/plugin</filename> into the <filename>JOSSO_HOME</filename> directory created in the last step. - </para> - <para> - This action should replace or add the following files to the <filename>JOSSO_HOME/webapps/josso/WEB-INF/lib</filename> directory: - </para> - <itemizedlist> - <listitem> - <para> - <filename>JOSSO_HOME/lib/josso-gateway-config.xml</filename> - </para> - - </listitem> - <listitem> - <para> - <filename>JOSSO_HOME/lib/josso-gateway-gatein-stores.xml</filename> - </para> - - </listitem> - <listitem> - <para> - <filename>JOSSO_HOME/webapps/josso/WEB-INF/classes/gatein.properties</filename> - </para> - - </listitem> - - </itemizedlist> - - </step> - <step> - <para> - Edit <filename>TOMCAT_HOME/conf/server.xml</filename> file and change the 8080 port to 8888 to avoid a conflict with the default JBoss Enterprise Portal Platform port. - <note> - <title>Port Conflicts</title> - <para> - If JBoss Enterprise Portal Platform is running on the same machine as Tomcat, other ports need to be changed in addition to 8080 in order 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> - - </para> - - </step> - <step> - <para> - Tomcat will start and allow access to <ulink type="http" url="http://localhost:8888/josso/signon/login.do"> http://localhost:8888/josso/signon/login.do </ulink> but at this stage login will not be available. - </para> - <mediaobject> - <imageobject> - <imagedata fileref="images/AuthenticationAndIdentity/SSO/opensso.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - - </step> - - </procedure> - - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Java_Open_Single_Sign_On_Project-Setup_the_JOSSO_client"> - <title>Setup the JOSSO client</title> - <step> - <para> - Copy the library files from <filename><replaceable>PORTAL_SSO</replaceable>/josso/gatein.ear/lib</filename> into <filename>gatein.ear/lib</filename> (or into <filename>GATEIN_HOME/lib</filename> if the product is running in Tomcat). - </para> - - </step> - <step> - <para> - Copy the <filename><replaceable>PORTAL_SSO</replaceable>/josso/gatein.ear/portal.war/WEB-INF/classes/josso-agent-config.xml</filename> file into the <filename>gatein.ear/02portal.war/WEB-INF/classes</filename> directory (or into <filename>JBOSS_HOME/webapps/portal.war/WEB-INF/classes</filename>, or <filename>GATEIN_HOME/conf</filename> if the product is running in Tomcat). - </para> - - </step> - <step> - <para> - Edit <filename>jboss-as/server/<replaceable>PROFILE</replaceable>/deploy/gatein.ear/META-INF/gatein-jboss-beans.xml</filename> and uncomment this section: - </para> - -<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default111.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - - </step> - <step> - <para> - In Tomcat, edit <filename>JBOSS_HOME/conf/jaas.conf</filename> and uncomment this section: - </para> - -<programlisting>org.gatein.sso.agent.login.SSOLoginModule required; -org.exoplatform.services.security.j2ee.TomcatLoginModule requiredtm -portalContainerName=portal -realmName=gatein-domain; -</programlisting> - - </step> - <step> - <para> - The installation can be tested at this point. - </para> - <substeps> - <step> - <para> - Start (or restart) JBoss Enterprise Portal Platform, and (assuming the JOSSO server on Tomcat is running) direct your browser to <ulink type="http" url="http://localhost:8888/josso/signon/login.do"> http://localhost:8888/josso/signon/login.do </ulink> . - </para> - - </step> - <step> - <para> - Login with the username <literal>root</literal> and the password <literal>gtn</literal> or any account created through the portal. - </para> - - </step> - - </substeps> - - </step> - - </procedure> - - <para> - The next part of the process is to redirect all user authentication to the JOSSO server. - </para> - <para> - Information about where the JOSSO server is hosted must be properly configured within the JBoss Enterprise Portal Platform instance. The required configuration is done by modifying four files: - </para> - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Java_Open_Single_Sign_On_Project-Setup_the_portal_to_redirect_to_JOSSO"> - <title>Setup the portal to redirect to JOSSO</title> - <step> - <para> - In the <filename><replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/web.war/groovy/groovy/webui/component/UIBannerPortlet.gtml</filename> file modify the 'Sign In' link as follows: - </para> - -<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default112.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - - </step> - <step> - <para> - Modify the '<emphasis role="bold">Sign In</emphasis>' link in the <filename>gatein.ear/web.war/groovy/portal/webui/component/UILogoPortlet.gtmpl</filename> file as follows: - </para> - -<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default113.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - - </step> - <step> - <para> - Replace the entire contents of <filename>gatein.ear/02portal.war/login/jsp/login.jsp</filename> with: - </para> - -<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default114.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - - </step> - <step> - <para> - Add the following Filters to the top of the filter chain in <filename>gatein.ear/02portal.war/WEB-INF/web.xml</filename>: - </para> - -<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default115.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - - </step> - - </procedure> - - <para> - From now on, all links redirecting to the user authentication pages will redirect to the JOSSO centralized authentication form. - </para> - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-SSO_Single_Sign_On_-OpenSSO"> - <title>OpenSSO</title> - <para> - This section details the setting up of OpenSSO server to authenticate against the JBoss Enterprise Portal Platform login module. - </para> - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-OpenSSO-Obtaining_OpenSSO"> - <title>Obtaining OpenSSO</title> - <step> - <para> - OpenSSO must be purchased from <ulink type="http" url="http://www.oracle.com/technetwork/middleware/id-mgmt/overview/index.html"> Oracle </ulink> . - </para> - <para> - For testing purpose, use OpenSSO_80U2, which can be downloaded from <ulink type="http" url="http://download.oracle.com/otn/nt/middleware/11g/oracle_opensso_80U2.zip"> Oracle </ulink> . - </para> - - </step> - <step> - <para> - Extract the package into a suitable location. This location will be referred to as <filename>OPENSSO_HOME</filename> in this example. - </para> - - </step> - - </procedure> - - <note> - <para> - It is also possible to use OpenAM instead of OpenSSO server. OpenAM is free and the integration steps between Enterprise Portal Platform and OpenAM are very similar as with OpenSSO. More info is available <ulink type="http" url="http://community.jboss.org/wiki/GateInAndOpenAMIntegration"> here </ulink> . - </para> - - </note> - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-SSO_Single_Sign_On_-Modifying_the_OpenSSO_server"> - <title>Modifying the OpenSSO server</title> - <para> - To configure the web server as required, it is simpler to directly modify the source files. - </para> - <para> - The first step is to add the JBoss Enterprise Portal Platform Authentication Plugin. - </para> - <para> - The plugin makes secure callbacks to a RESTful service installed on the remote JBoss Enterprise Portal Platform 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. - </para> - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Modifying_the_OpenSSO_server-Modifying_OpenSSO_server"> - <title>Modifying OpenSSO server</title> - <step> - <para> - Obtain a copy of Tomcat and extract it into a suitable location. This location will be referred to as <filename>TOMCAT_HOME</filename> in this example. - </para> - - </step> - <step> - <para> - Edit <filename>TOMCAT_HOME/conf/server.xml</filename> and change the 8080 port to 8888 to avoid a conflict with the default JBoss Enterprise Portal Platform port. - <note> - <para> - If JBoss Enterprise Portal Platform is running on the same machine as Tomcat, other ports need to be changed in addition to 8080 in order to avoid port conflicts. They can be changed to any free port. For example, you can change the admin port from 8005 to 8805 and the AJP port from 8009 to 8809. - </para> - - </note> - - </para> - - </step> - <step> - <para> - Ensure the <filename>TOMCAT_HOME/webapps/opensso/config/auth/default/AuthenticationPlugin.xml</filename> file matches the following: - </para> - -<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default117.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - - </step> - <step> - <para> - Copy the following files into the Tomcat directory at <filename>TOMCAT_HOME/webapps/opensso/WEB-INF/lib</filename>: - </para> - <itemizedlist> - <listitem> - <para> - <filename><replaceable>PORTAL_SSO</replaceable>/opensso/plugin/WEB-INF/lib/sso-opensso-plugin-<VERSION>.jar</filename> - </para> - - </listitem> - <listitem> - <para> - <filename><replaceable>PORTAL_SSO</replaceable>/opensso/plugin/WEB-INF/lib/commons-httpclient-<VERSION>.jar</filename> - </para> - - </listitem> - <listitem> - <para> - <filename><replaceable>PORTAL_SSO</replaceable>/opensso/plugin/WEB-INF/lib/commons-logging-<VERSION>.jar</filename> - </para> - - </listitem> - - </itemizedlist> - - </step> - <step> - <para> - Copy the <filename><replaceable>PORTAL_SSO</replaceable>/opensso/plugin/WEB-INF/classes/gatein.properties</filename> file into the <filename>TOMCAT_HOME/webapps/opensso/WEB-INF/classes</filename> directory. - </para> - - </step> - <step> - <para> - Tomcat should start and be able to access <ulink type="http" url="http://localhost:8888/opensso/UI/Login?realm=gatein"> http://localhost:8888/opensso/UI/Login?realm=gatein </ulink> . - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/AuthenticationAndIdentity/SSO/opensso-shot.png" format="PNG" scale="110" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="150mm" fileref="images/AuthenticationAndIdentity/SSO/opensso-shot.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - <note> - <para> - Login will not be available at this point. - </para> - - </note> - - </step> - - </procedure> - - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Modifying_the_OpenSSO_server-Configure_the_gatein_realm"> - <title>Configure the "gatein" realm</title> - <step> - <para> - Direct your browser to <ulink type="http" url="http://localhost:8888/opensso"> http://localhost:8888/opensso </ulink> - </para> - - </step> - <step> - <para> - Create a default configuration. - </para> - - </step> - <step> - <para> - Login as <literal>amadmin</literal>. - </para> - <important> - <para> - Go to <menuchoice><guimenu>Configuration</guimenu> <guimenuitem> Authentication </guimenuitem> </menuchoice> and follow the link to <guilabel>Core</guilabel> - </para> - <para> - Add a new value with the class name <literal>org.gatein.sso.opensso.plugin.AuthenticationPlugin</literal>. - </para> - <para> - If this is not done <literal>AuthenticationPlugin</literal> is not available among other OpenSSO authentication modules. - </para> - - </important> - - </step> - <step> - <para> - Go to the <guilabel>Access control</guilabel> tab and create new realm called <literal>gatein</literal>. - </para> - - </step> - <step> - <substeps> - <step> - <para> - Go to the new <literal>gatein</literal> realm and click on the <guilabel>Authentication</guilabel> tab. - </para> - - </step> - <step> - <para> - Click on <guilabel>ldapService</guilabel> (at the bottom in the <guilabel>Authentication chaining</guilabel> section). - </para> - - </step> - <step> - <para> - Change the selection from <literal>Datastore</literal>, which is the default module in the authentication chain, to <literal>AuthenticationPlugin</literal>. - </para> - - </step> - - </substeps> - <para> - These changes enable authentication of the <literal>gatein</literal> realm using the <literal>GateIn REST</literal> service instead of the OpenSSO LDAP server. - </para> - - </step> - <step> - <para> - Go to <guilabel>Advanced properties</guilabel> and change <literal>UserProfile</literal> from <parameter>Required</parameter> to <parameter>Dynamic</parameter> to ensure all new users are automatically created in the OpenSSO datastore after successful authentication. - </para> - - </step> - <step> - <para> - Increase the user privileges to allow REST access with the following procedure: - </para> - <substeps> - <step> - <para> - Go to <menuchoice><guimenu>Access control</guimenu> <guimenuitem> Top level realm </guimenuitem> <guimenuitem> Privileges </guimenuitem> <guimenuitem> All authenticated users </guimenuitem> </menuchoice>. - </para> - - </step> - <step> - <para> - Check the last two checkboxes: - </para> - <itemizedlist> - <listitem> - <para> - Read and write access only for policy properties - </para> - - </listitem> - <listitem> - <para> - Read and write access to all realm and policy properties - </para> - - </listitem> - - </itemizedlist> - - </step> - - </substeps> - - </step> - <step> - <para> - Repeat step 7 for the '<literal>gatein</literal>' realm as well. - </para> - - </step> - - </procedure> - - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-SSO_Single_Sign_On_-Setup_the_OpenSSO_Client"> - <title>Setup the OpenSSO Client</title> - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Setup_the_OpenSSO_Client-Setup_the_OpenSSO_client"> - <title>Setup the OpenSSO client</title> - <step> - <para> - Copy all libraries from the <filename><replaceable>PORTAL_SSO</replaceable>/opensso/gatein.ear/lib</filename> directory into the <filename>JBOSS_HOME/server/default/deploy/gatein.ear/lib</filename> directory. - </para> - <para> - Alternatively, in a Tomcat environment, copy the libraries into the <filename>JBOSS_HOME/lib</filename> directory. - </para> - - </step> - <step> - <para> - Edit the <filename>jboss-as/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/META-INF/gatein-jboss-beans.xml</filename> and uncomment this section: - </para> - -<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default118.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - - </step> -  <step> - <para> - Test the installation: - </para> - <procedure> - <step> - <para> - Access JBoss Enterprise Portal Platform by going to <ulink type="http" url="http://localhost:8888/opensso/UI/Login?realm=gatein"> http://localhost:8888/opensso/UI/Login?realm=gatein </ulink> (assuming that the OpenSSO server using Tomcat is still running). - </para> - - </step> - <step> - <para> - Login with the username <literal>root</literal> and the password <literal>gtn</literal> or any account created through the portal. - </para> - - </step> - - </procedure> - - - </step> - - </procedure> - - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-SSO_Single_Sign_On_-Setup_the_portal_to_redirect_to_OpenSSO"> - <title>Setup the portal to redirect to OpenSSO</title> - <para> - The next part of the process is to redirect all user authentication to the OpenSSO server. - </para> - <para> - Information about where the OpenSSO server is hosted must be properly configured within the Enterprise Portal Platform instance. The required configuration is done by modifying three files: - </para> - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Setup_the_portal_to_redirect_to_OpenSSO-Setup_the_portal_to_redirect_to_OpenSSO"> - <title>Setup the portal to redirect to OpenSSO</title> - <step> - <para> - Modify the '<emphasis role="bold">Sign In</emphasis>' link in the <filename><replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/web.war/groovy/groovy/webui/component/UIBannerPortlet.gtml</filename> file as follows: - </para> - -<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default119.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - - </step> - <step> - <para> - Modify the '<emphasis role="bold">Sign In</emphasis>' link in the <filename>gatein.ear/web.war/groovy/portal/webui/component/UILogoPortlet.gtmpl</filename> file as follows: - </para> - -<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default120.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - - </step> - <step> - <para> - Replace the entire contents of <filename>gatein.ear/02portal.war/login/jsp/login.jsp</filename> with: - </para> - -<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default121.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - - </step> - <step> - <para> - Add the following Filters to the top of the filter chain in <filename>gatein.ear/02portal.war/WEB-INF/web.xml</filename>: - </para> - -<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default122.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - - </step> - - </procedure> - - <para> - From now on, all links redirecting to the user authentication pages will redirect to the OpenSSO centralized authentication form. - </para> - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-SSO_Single_Sign_On_-SPNEGO_Simple_and_Protected_GSSAPI_Negotiation_Mechanism"> - <title>SPNEGO - Simple and Protected GSSAPI Negotiation Mechanism</title> - <para> - The Simple and Protected GSSAPI Negotiation Mechanism (<emphasis role="bold">SPNEGO</emphasis>) uses desktop credentials provided during a desktop login to transparently authenticate a portal user through a web browser. - </para> - <para> - For illustrative purposes; a typical use case would be: - </para> - <procedure> - <step> - <para> - A user logs into their desktop computer with a login that is governed by an Active Directory domain. - </para> - - </step> - <step> - <para> - The user then launches a web browser to access a web application (that uses JBoss Negotiation) hosted on JBoss Enterprise Portal Platform. - </para> - - </step> - <step> - <para> - The browser transfers the desktop credentials to the web application. - </para> - - </step> - <step> - <para> - JBoss EAP/AS uses background GSS messages with the Active Directory (or any Kerberos Server) to validate the Kerberos ticket from user. - </para> - - </step> - <step> - <para> - The user experiences a seamless single sign on (SSO) into the web application. - </para> - - </step> - - </procedure> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-SPNEGO_Simple_and_Protected_GSSAPI_Negotiation_Mechanism-SPNEGO_Server_Configuration"> - <title>SPNEGO Server Configuration</title> - <para> - In this section, we will describe some necessary steps for setup Kerberos server on Linux. This server will then be used for SPNEGO authentication against JBoss Enterprise Portal Platform. - </para> - <note> - <title>SPNEGO Basics</title> - <para> - The procedure below only describes the basic steps to configure the SPNEGO server in a Linux environment. If you are already familiar with SPNEGO, or if you are using Windows and Active Directory domain, you can jump to the <xref linkend="proc-Reference_Guide_eXo_JCR_1.14-JBoss_Enterprise_Portal_Platform_Configuration-Advanced_SPNEGO_Configuration" /> to see how to integrate SPNEGO with JBoss Enterprise Portal Platform. - </para> - <para> - Please note that Kerberos setup is also dependent on your Linux distribution and so steps can be slightly different in your environment. - </para> - - </note> - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-SPNEGO_Server_Configuration-SPNEGO_Basics"> - <title>SPNEGO Basics</title> - <step> - <para> - Correct the setup of network on the machine. For example, if you are using the "server.local.network" domain as your machine where Kerberos and JBoss Enterprise Portal Platform are localed, add the line containing the machine's IP address to the <emphasis role="bold">/etc/host </emphasis> file. - </para> - -<programlisting> -192.168.1.88 server.local.network -</programlisting> - <note> - <para> - It is not recommended you use loopback addresses. - </para> - - </note> - - </step> - <step> - <para> - Install Kerberos with these packages: krb5-admin-server, krb5-kdc, krb5-config, krb5-user, krb5-clients, and krb5-rsh-server. - </para> - - </step> - <step> - <para> - Edit the Kerberos configuration file at <emphasis role="bold">/etc/krb5.config</emphasis>, including: - </para> - <itemizedlist> - <listitem> - <para> - Uncomment on these lines: - </para> - -<programlisting> -default_tgs_enctypes = des3-hmac-sha1 -default_tkt_enctypes = des3-hmac-sha1 -permitted_enctypes = des3-hmac-sha1 -</programlisting> - - </listitem> - <listitem> - <para> - Add <emphasis role="bold">local.network</emphasis> as a default realm and it is also added to the list of realms and remove the remains of realms. The content looks like: - </para> - -<programlisting> -[libdefaults] - default_realm = LOCAL.NETWORK - -# The following krb5.conf variables are only for MIT Kerberos. - krb4_config = /etc/krb.conf - krb4_realms = /etc/krb.realms - kdc_timesync = 1 - ccache_type = 4 - forwardable = true - proxiable = true - -# The following encryption type specification will be used by MIT Kerberos -# if uncommented. In general, the defaults in the MIT Kerberos code are -# correct and overriding these specifications only serves to disable new -# encryption types as they are added, creating interoperability problems. -# -# Thie only time when you might need to uncomment these lines and change -# the enctypes is if you have local software that will break on ticket -# caches containing ticket encryption types it doesn't know about (such as -# old versions of Sun Java). - - default_tgs_enctypes = des3-hmac-sha1 - default_tkt_enctypes = des3-hmac-sha1 - permitted_enctypes = des3-hmac-sha1 - -# The following libdefaults parameters are only for Heimdal Kerberos. - v4_instance_resolve = false - v4_name_convert = { - host = { - rcmd = host - ftp = ftp - } - plain = { - something = something-else - } - } - fcc-mit-ticketflags = true - -[realms] - LOCAL.NETWORK = { - kdc = server.local.network - admin_server = server.local.network - } - -[domain_realm] - .local.network = LOCAL.NETWORK - local.network = LOCAL.NETWORK - -[login] - krb4_convert = true - krb4_get_tickets = false -</programlisting> - - </listitem> - - </itemizedlist> - - </step> - <step> - <para> - Edit the KDC configuraton file at <emphasis role="bold">/etc/krb5kdc/kdc.conf</emphasis> that looks like. - </para> - -<programlisting> -[kdcdefaults] - kdc_ports = 750,88 - -[realms] - LOCAL.NETWORK = { - database_name = /home/gatein/krb5kdc/principal - admin_keytab = FILE:/home/gatein/krb5kdc/kadm5.keytab - acl_file = /home/gatein/krb5kdc/kadm5.acl - key_stash_file = /home/gatein/krb5kdc/stash - kdc_ports = 750,88 - max_life = 10h 0m 0s - max_renewable_life = 7d 0h 0m 0s - master_key_type = des3-hmac-sha1 - supported_enctypes = aes256-cts:normal arcfour-hmac:normal des3-hmac-sha1:normal des-cbc-crc:normal des:normal des:v4 des:norealm des:onlyrealm des:afs3 - default_principal_flags = +preauth - } - -[logging] - kdc = FILE:/home/gatein/krb5logs/kdc.log - admin_server = FILE:/home/gatein/krb5logs/kadmin.log -</programlisting> - <itemizedlist> - <listitem> - <para> - Create krb5kdc and krb5logs directory for Kerberos database as shown in the configuration file above. - </para> - - </listitem> - <listitem> - <para> - Next, create a KDC database using the following command. - </para> - -<programlisting> -sudo krb5_newrealm -</programlisting> - - </listitem> - <listitem> - <para> - Start the KDC and Kerberos admin servers using these commands: - </para> - -<programlisting> -sudo /etc/init.d/krb5-kdc restart -sudo /etc/init.d/krb-admin-server restart -</programlisting> - - </listitem> - - </itemizedlist> - - </step> - <step> - <para> - Add Principals and create Keys. - </para> - <itemizedlist> - <listitem> - <para> - Start an interactive 'kadmin' session and create the necessary Principals. - </para> - -<programlisting> -sudo kadmin.local -</programlisting> - - </listitem> - <listitem> - <para> - Add the JBoss Enterprise Portal Platform machine and keytab file that need to be authenticated. - </para> - -<programlisting> -addprinc -randkey HTTP/server.local.network(a)LOCAL.NETWORK -ktadd HTTP/server.local.network(a)LOCAL.NETWORK -</programlisting> - - </listitem> - <listitem> - <para> - Add the default JBoss Enterprise Portal Platform user accounts and enter the password for each created user that will be authenticated. - </para> - -<programlisting> -addprinc john -addprinc demo -addprinc root -</programlisting> - - </listitem> - - </itemizedlist> - - </step> - <step> - <para> - Test your changed setup by using the command. - </para> - -<programlisting> -kinit -A demo -</programlisting> - <itemizedlist> - <listitem> - <para> - If the setup works well, you are required to enter the password created for this user in Step 5. Without the -A, the kerberos ticket validation involved reverse DNS lookups, which can get very cumbersome to debug if your network's DNS setup is not great. This is a production level security feature, which is not necessary in this development setup. In production environment, it will be better to avoid -A option. - </para> - - </listitem> - <listitem> - <para> - After successful login to Kerberos, you can see your Kerberos ticket when using this command. - </para> - -<programlisting> -klist -</programlisting> - - </listitem> - <listitem> - <para> - If you want to logout and destroy your ticket, use this command. - </para> - -<programlisting> -kdestroy -</programlisting> - - </listitem> - - </itemizedlist> - - </step> - - </procedure> - - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-SPNEGO_Simple_and_Protected_GSSAPI_Negotiation_Mechanism-SPNEGO_Server_Configuration-Clients"> - <title>Clients</title> - <para> - After performing all configurations above, you need to enable the <emphasis role="bold">Negotiate authentication </emphasis> of Firefox in client machines so that clients could be authenticated by JBoss Enterprise Portal Platform as follows: - </para> - <procedure> - <step> - <para> - Start Firefox, then enter the command: <emphasis role="bold">about:config </emphasis> into the address field. - </para> - - </step> - <step> - <para> - Enter <emphasis role="bold">network.negotiate-auth</emphasis> and set the value as below: - </para> - -<programlisting> -network.negotiate-auth.allow-proxies = true -network.negotiate-auth.delegation-uris = .local.network -network.negotiate-auth.gsslib (no-value) -network.negotiate-auth.trusted-uris = .local.network -network.negotiate-auth.using-native-gsslib = true -</programlisting> - - </step> - - </procedure> - - <note> - <para> - Consult documentation of your OS or web browser if using different browser than Firefox. - </para> - - </note> - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-SPNEGO_Simple_and_Protected_GSSAPI_Negotiation_Mechanism-JBoss_Enterprise_Portal_Platform_Configuration"> - <title>JBoss Enterprise Portal Platform Configuration</title> - <para> - JBoss Enterprise Portal Platform uses JBoss Negotiation to enable SPNEGO-based desktop SSO for the portal. Here are the steps to integrate SPNEGO with JBoss Enterprise Portal Platform. - </para> - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-JBoss_Enterprise_Portal_Platform_Configuration-Advanced_SPNEGO_Configuration"> - <title>Advanced SPNEGO Configuration</title> - <step> - <para> - Activate the Host authentication. Add the following host login module to the <filename>jboss-as/server/<replaceable>PROFILE</replaceable>/conf/login-config.xml</filename>: - </para> - -<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default124.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - <para> - The '<literal>keyTab</literal>' value should point to the keytab file that was generated by the <literal>kadmin</literal> Kerberos tool. When using Kerberos on Linux, it should be value of parameter <emphasis role="bold">admin_keytab</emphasis> from kdc.conf file. See the <xref linkend="proc-Reference_Guide_eXo_JCR_1.14-SPNEGO_Server_Configuration-SPNEGO_Basics" /> for more details. - </para> - - </step> - <step> - <para> - Extend the core authentication mechanisms to support SPNEGO. Under <filename>deployers/jbossweb.deployer/META-INF/war-deployers-jboss-beans.xml</filename>, add a '<literal>SPNEGO</literal>' authenticators property - </para> - -<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default125.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - - </step> - <step> - <para> - Add the GateIn SSO module binaries by copying <emphasis role="bold">GATEIN_SSO_HOME/spnego/gatein.ear/lib/sso-agent-VERSION.jar</emphasis> to the <emphasis role="bold">JBOSS_HOME/server/default/deploy/gatein.ear/lib</emphasis> directory. File <emphasis role="bold">GATEIN_SSO_HOME/spnego/gatein.ear/lib/spnego-VERSION.jar</emphasis> needs to be copied to the <emphasis role="bold">JBOSS_HOME/server/default/lib</emphasis> directory. - </para> - - </step> -  <step> - <para> - Modify the <filename>deploy/gatein.ear/META-INF/gatein-jboss-beans.xml</filename> file to match the following: - </para> - -<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default126.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - <para> - This activates SPNEGO LoginModules with fallback to FORM authentication. When SPNEGO is not available and it needs to fallback to FORM, it will use <emphasis role="bold">gatein-form-auth-domain</emphasis> security domain. - </para> - - </step> - <step> - <para> - Modify <filename>gatein.ear/02portal.war/WEB-INF/web.xml</filename> to match: - </para> - -<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default127.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - <para> - Integrate the request pre-processing needed for SPNEGO via filters by adding the following filters to the <emphasis role="bold">JBOSS_HOME/server/default/deploy/gatein.ear/02portal.war/WEB-INF/web.xml</emphasis> at the top of the Filter chain. - </para> - -<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default128.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - <para> - This integrates request pre-processing needed for SPNEGO. - </para> - - </step> - <step> - <para> - Edit the '<emphasis role="bold">Sign In</emphasis>' link in <filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable>PROFILE</replaceable>/deploy/gatein.ear/web.war/groovy/groovy/webui/component/UIBannerPortlet.gtmpl</filename> to match the following: - </para> - -<programlisting language="Java" role="Java"><xi:include href="../../extras/Authentication_Identity_SSO/default129.java" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - - </step> - <step> - <para> - Start the JBoss Enterprise Portal Platform; - </para> - -<programlisting language="Java" role="Java"><xi:include href="../../extras/Authentication_Identity_SSO/default130.java" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - <para> - The <replaceable>PROFILE</replaceable> parameter in the above command should be replaced with the server profile modified with the above configuration. - </para> - - </step> - <step> - <para> - Login to Kerberos: - </para> - -<programlisting>kinit -A demo -</programlisting> - - </step> - - </procedure> - - <para> - Clicking the 'Sign In' link on the JBoss Enterprise Portal Platform should automatically sign the 'demo' user into the portal. - </para> - <para> - If you destroy your kerberos ticket with command <command>kdestroy</command>, then try to login again, you will directed to the login screen of JBoss Enterprise Portal Product because you don't have active Kerberos ticket. You can login with predefined account and password "demo"/"gtn" . - </para> - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-SPNEGO_Simple_and_Protected_GSSAPI_Negotiation_Mechanism-JBoss_Enterprise_Portal_Platform_Configuration-Clients"> - <title>Clients</title> - <para> - After performing all configurations above, you need to enable the <emphasis role="bold">Negotiate authentication </emphasis> of Firefox in clients so that clients can be authenticated by JBoss Enterprise Portal Platform as follows: - </para> - <procedure> - <step> - <para> - Start Firefox, then enter the command: <emphasis role="bold">about:config </emphasis> into the address field. - </para> - - </step> - <step> - <para> - Enter <emphasis role="bold">network.negotiate-auth</emphasis> and set the value as below: - </para> - -<programlisting> -network.negotiate-auth.allow-proxies = true -network.negotiate-auth.delegation-uris = .local.network -network.negotiate-auth.gsslib (no-value) -network.negotiate-auth.trusted-uris = .local.network -network.negotiate-auth.using-native-gsslib = true -</programlisting> - - </step> - - </procedure> - - - </section> - - - </section> - - -</section> - - Copied: epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml (from rev 8139, epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/AuthenticationAndIdentity/SSO.xml) =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml (rev 0) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/AuthenticationAndIdentity/SSO.xml 2011-11-25 00:48:53 UTC (rev 8141) @@ -0,0 +1,1695 @@ +<?xml version='1.0' encoding='utf-8' ?> +<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +<!ENTITY % BOOK_ENTITIES SYSTEM "Reference_Guide_eXo_JCR_1.14.ent"> +%BOOK_ENTITIES; +]> +<section id="sect-Reference_Guide_eXo_JCR_1.14-SSO_Single_Sign_On_"> + <title><remark>SSO - Single Sign On</remark> + </title> + <section id="sect-Reference_Guide_eXo_JCR_1.14-SSO_Single_Sign_On_-Overview"> + <title>Overview</title> + <para> + JBoss Enterprise Portal Platform provides an implementation of Single Sign On (<literal>SSO</literal>) as an integration and aggregation platform. + </para> + <para> + When logging into the portal users can access many systems through portlets using a single identity. In many cases, however, the portal infrastructure must be integrated with other SSO enabled systems. + </para> + <para> + There are many different Identity Management solutions available. In most cases each SSO framework provides a unique way to plug into a Java EE application. + </para> + <para> + This section will cover the implementation of four different SSO plug-ins with JBoss Enterprise Portal Platform: + </para> + <itemizedlist> + <listitem> + <para> + <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-SSO_Single_Sign_On_-Central_Authentication_Service" /> + </para> + + </listitem> + <listitem> + <para> + <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-SSO_Single_Sign_On_-Java_Open_Single_Sign_On_Project" /> + </para> + + </listitem> + <listitem> + <para> + <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-SSO_Single_Sign_On_-OpenSSO" /> + </para> + + </listitem> + <listitem> + <para> + <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-SSO_Single_Sign_On_-SPNEGO_Simple_and_Protected_GSSAPI_Negotiation_Mechanism" /> + </para> + + </listitem> + + </itemizedlist> + <note> + <title>Prerequisites</title> + <para> + In this tutorial, the SSO server is being installed in a Tomcat environment. Tomcat can be obtained from <ulink type="http" url="http://tomcat.apache.org"> http://tomcat.apache.org </ulink> . + </para> + + </note> + <para> + All the packages required for SSO setup can be found in a zip file located in the <filename>jboss-epp-<replaceable>VERSION</replaceable>/gatein-sso</filename> directory of the JBoss Enterprise Portal Platform binary package. + </para> + <para> + In the following scenarios this directory will be referred to as <replaceable>PORTAL_SSO</replaceable>. + </para> + <warning> + <para> + Users are advised to not run any portal extensions that could override the data when manipulating the <filename>gatein.ear</filename> file directly. + </para> +  + </warning> + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-SSO_Single_Sign_On_-Enabling_SSO_using_JBoss_SSO_Valve"> + <title>Enabling SSO using JBoss SSO Valve</title> +  <para> + The JBoss SSO valve is useful to authenticate a user on one JBoss Enterprise Portal Platform node in a cluster and have that authentication automatically carry across to other nodes in the cluster. + </para> + <para> + This authentication can also be used in any other web applications which may require authentication, <emphasis role="bold">provided that these applications use same roles as the main portal instance</emphasis>. Attempting to use an SSO authentication in an application that uses different roles may create authorization errors (<emphasis role="bold">403</emphasis> errors, for example). + </para> + <note> + <title>Reauthentication</title> + <para> + This behavior is coming from the fact that same JAAS principal is added by SSO valve to all HTTP requests, even to other web applications. + </para> + <para> + So the same roles are required because of it. There is an alternative that allows you to configure the SSO valve with the <parameter>requireReauthentication=true</parameter> parameter, which will force the SSO valve to perform reauthentication with saved credentials in each HTTP request against security domain of particular web application where the request is coming. + </para> + <para> + This will ensure that a new principal for that web application will be created with updated roles for that web application. + </para> + <para> + In other words; when <parameter>requireReauthentication</parameter> is <emphasis role="bold">false</emphasis> (the default state), you need to have the same roles among web applications. When <parameter>requireReauthentication</parameter> is <emphasis role="bold">true</emphasis> you need to have same username and passwords. + </para> + + </note> + <para> + More info about the JBoss SSO valve can be found at <ulink type="http" url="http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Web_Platform/5/html/Ad..." />. + </para> + <para> + To successfully implement SSO integration, do the following: + </para> + <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Enabling_SSO_using_JBoss_SSO_Valve-SSO_Integration"> + <title>SSO Integration</title> + <step> + <para> + Open the <filename><replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/jbossweb.sar/server.xml</filename> file and uncomment one of the two <parameter>Valve</parameter> entries: + </para> + <itemizedlist> + <listitem> + <para> + For a <emphasis>non-clustered</emphasis> implementation, uncomment: + </para> + +<programlisting language="XML" role="XML"><Valve className="org.apache.catalina.authenticator.SingleSignOn" /> +</programlisting> + + </listitem> + <listitem> + <para> + For a <emphasis>clustered</emphasis> implementation, uncomment: + </para> + +<programlisting language="XML" role="XML"><Valve className="org.jboss.web.tomcat.service.sso.ClusteredSingleSignOn" /></programlisting> + + </listitem> + + </itemizedlist> + + </step> + <step> + <para> + For implementation of the SSO valve among the different nodes of cluster, all the nodes must share the same domain (<emphasis>node1.yourdomain.com</emphasis> and <emphasis>node2.yourdomain.com</emphasis>, for example). + </para> + <para> + This domain needs to be configured in the SSO valve parameter <parameter>cookieDomain</parameter>. This is required because the SSO valve adds the cookie <emphasis role="bold">JSESSIONIDSSO</emphasis>, which is, by default bound only to the host where the request is originating. + </para> + <para> + When the <parameter>cookieDomain</parameter> parameter is used, the cookie is bound to the domain (like <emphasis>yourdomain.com</emphasis>), which will ensure that it is shared among both hosts <emphasis>node1.yourdomain.com</emphasis> and <emphasis>node2.yourdomain.com</emphasis>. + </para> + <para> + So in this case, the valve configuration would be: + </para> + +<programlisting language="XML" role="XML"><Valve className="org.jboss.web.tomcat.service.sso.ClusteredSingleSignOn" +cookieDomain="yourdomain.com" /> +</programlisting> + + </step> + <step> + <para> + Another important thing is that both cluster nodes needs to be on same cluster (using same parameter <emphasis role="bold">-g</emphasis> and same parameter <emphasis role="bold">-u</emphasis> and also using parameter <emphasis role="bold">-Dexo.profiles=cluster</emphasis>). + </para> + <para> + They must also share the same NFS directory and the same database and apply all the configuration needed for JBoss Enterprise Portal Platform cluster. + </para> + + </step> + + </procedure> + + <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Enabling_SSO_using_JBoss_SSO_Valve-Testing_SSO_in_a_physical_cluster"> + <title>Testing SSO in a physical cluster</title> + <para> + In this example, we will try to simulate testing on more physical machines by simply using virtual hosts on single machine. + </para> + + </formalpara> + <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Enabling_SSO_using_JBoss_SSO_Valve-Testing_the_SSO_Valve"> + <title>Testing the SSO Valve</title> + <step> + <para> + If you are using a Linux system, you can configure file <emphasis role="bold">/etc/hosts</emphasis> to contain these lines: + </para> + +<programlisting> +127.0.1.1 machine1.yourdomain.com +127.0.1.2 machine2.yourdomain.com +</programlisting> + + </step> + <step> + <para> + Open the <filename><replaceable><JBOSS_HOME></replaceable>/server/all/<replaceable><PROFILE></replaceable>/jbossweb.sar/server.xml</filename> file. + </para> + + </step> + <step> + <para> + Uncomment the line: + </para> + +<programlisting language="XML" role="XML"> +</programlisting> + + </step> + <step> + <para> + And edit it to match the following: + </para> + +<programlisting language="XML" role="XML"><Valve className="org.jboss.web.tomcat.service.sso.ClusteredSingleSignOn" +cookieDomain="yourdomain.com" /> +</programlisting> + <para> + This will ensure the <literal>JSESSIONIDSSO</literal> cookie is used in the correct domain, allowing the SSO authentication to occur. + </para> + + </step> + <step> + <para> + Copy server configuration <emphasis role="bold">all</emphasis> and create another two configurations <emphasis role="bold">node1</emphasis> and <emphasis role="bold">node2</emphasis> from it. + </para> + + </step> + <step> + <para> + Start both cluster nodes with commands: + </para> + +<programlisting> +./run.sh -c node1 -b machine1.yourdomain.com -Dexo.profiles=cluster -Djboss.messaging.ServerPeerID=0 & +./run.sh -c node2 -b machine2.yourdomain.com -Dexo.profiles=cluster -Djboss.messaging.ServerPeerID=1 & +</programlisting> + + </step> + <step> + <para> + Go to <uri>http://machine1.yourdomain.com:8080/portal</uri> and login as a user. + </para> + + </step> + <step> + <para> + Access a private URL on the second host, such as <uri>http://machine2.yourdomain.com:8080/portal/dologin</uri>, for example. + </para> + <para> + Now you should be logged directly into <literal>machine2</literal> thanks to SSO valve. + </para> + + </step> + <step> + <para> + Logout from SSO initiating machine1.yourdomain.com should also logged you out from other cluster nodes. So you should be logout directly from machine2 as well. + </para> + + </step> + + </procedure> + + <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Enabling_SSO_using_JBoss_SSO_Valve-Enabling_SSO_with_Other_Web_Applications"> + <title>Enabling SSO with Other Web Applications</title> + <para> + As mentioned earlier, in order to use SSO authentication between JBoss Enterprise Portal Platform instances and other web applications, the roles defined in the web application must match those used in the portal instance (unless you have the <parameter>requireReauthentication</parameter> parameter set to <literal>true</literal>). + </para> + + </formalpara> + <para> + As an example, to use the SSO Valve to authenticate a user in both a portal instance and the JMX Console, the following actions would be required: + </para> + <procedure> + <title></title> + <step> + <para> + Open the <filename><replaceable><JBOSS_HOME></replaceable>/server/node1/deploy/jmx-console.war/WEB-INF/web.xml</filename> file and edit it as follows: + </para> + <substeps> + <step> + <para> + Change the <parameter><role-name></parameter> entry in the <parameter><auth-constraint></parameter> element (line <literal>110</literal>) from <literal>JBossAdmin</literal> to <literal>users</literal>: + </para> + +<programlisting language="XML" role="XML"><auth-constraint> +  + <role-name>users</role-name> +</auth-constraint></programlisting> + + </step> + <step> + <para> + Change the <parameter><role-name></parameter> entry in the <parameter><security-role></parameter> element (line <literal>120</literal>) from <literal>JBossAdmin</literal> to <literal>users</literal> + </para> + +<programlisting language="XML" role="XML"><security-role> +  + <role-name>users</role-name> +</security-role></programlisting> + + </step> + + </substeps> + + </step> + + </procedure> + + <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Enabling_SSO_using_JBoss_SSO_Valve-Testing_SSO_With_Other_Web_Applications"> + <title>Testing SSO With Other Web Applications</title> + <para> + To test that SSO authentication is enabled from portal instances to other web applications (in this case, the JMX Console), do the following: + </para> + + </formalpara> + <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Enabling_SSO_using_JBoss_SSO_Valve-Test_SSO_Between_Portal_and_JMX_Console"> + <title>Test SSO Between Portal and JMX Console</title> + <step> + <para> + Start a portal instance on one node: + </para> + +<programlisting>./run.sh -c node1 -b machine1.yourdomain.com -Dexo.profiles=cluster -Djboss.messaging.ServerPeerID=0 & +</programlisting> + + </step> + <step> + <para> + Navigate to <uri>http://machine1.yourdomain.com:8080/portal/private/classic</uri> and authenticate with the pre-configured user account "<systemitem>root</systemitem>" (password "<systemitem>gtn </systemitem>"). + </para> + + </step> + <step> + <para> + Navigate to <uri>http://machine1.yourdomain.com:8080/jmx-console</uri>. You should be automatically authenticated into the JMX Console. + </para> + + </step> + + </procedure> + + <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Enabling_SSO_using_JBoss_SSO_Valve-Using_SSO_to_Authenticate_From_the_Public_Page"> + <title>Using SSO to Authenticate From the Public Page</title> + <para> + The previous configuration changes in this section are useful if a user is using a secured URL (<ulink type="http" url="http://localhost:8080/portal/private/classic" />, for example) to log in to the portal instance. + </para> + + </formalpara> + <para> + Further changes are needed however, if SSO authentication is required to work with the <guilabel>Sign In</guilabel> button on the front page of the portal (<ulink type="http" url="http://localhost:8080/portal/classic" />). + </para> + <para> + To enable this functionality, the <guilabel>Sign In</guilabel> link must redirect to some secured URL, which will ensure that JAAS authentication will be enforced directly without showing login dialog. + </para> + <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Enabling_SSO_using_JBoss_SSO_Valve-Redirect_to_Use_SSO_Valve_Authentication"> + <title>Redirect to Use SSO Valve Authentication</title> + <step> + <para> + Open the <filename><replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/web.war/groovy/groovy/webui/component/UIBannerPortlet.gtml</filename> file and edit the line: + </para> + +<programlisting language="Java" role="java"><a class="Login" onclick="$signInAction"><%=_ctx.appRes("UILoginForm.label.Signin")%></a> +</programlisting> + <para> + To read: + </para> + +<programlisting language="Java" role="java"><a class="Login" href="/portal/private/classic"><%=_ctx.appRes("UILoginForm.label.Signin")%></a> +</programlisting> + + </step> + <step> + <para> + Open the <filename><replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/web.war/groovy/portal/webui/component/UILogoPortlet.gtmpl</filename> file and change the line: + </para> + +<programlisting language="Java" role="java"><a onclick="$signInAction"><%=_ctx.appRes("UILogoPortlet.action.signin")%></a> +</programlisting> + <para> + To read: + </para> + +<programlisting language="Java" role="java"><a href="/portal/private/classic"><%=_ctx.appRes("UILogoPortlet.action.signin")%></a> +</programlisting> + + </step> + + </procedure> + + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-SSO_Single_Sign_On_-Central_Authentication_Service"> + <title>Central Authentication Service</title> + <para> + This Single Sign On plugin enables seamless integration between JBoss Enterprise Portal Platform and the Central Authentication Service (<emphasis role="bold">CAS</emphasis>) Single Sign On Framework. Details about CAS can be found <ulink url="http://www.ja-sig.org/cas/"> here </ulink> . + </para> + <para> + The integration consists of two parts; the first part consists of installing or configuring a CAS server, the second part consists of setting up the portal to use the CAS server. + </para> + <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Central_Authentication_Service-CAS_server"> + <title>CAS server</title> + <step> + <para> + Set up the server to authenticate against the portal login module. + </para> + + </step> + <step> + <para> + Downloaded CAS from <ulink type="http" url="http://www.jasig.org/cas/download"> http://www.jasig.org/cas/download </ulink> . + </para> + <para> + The version, tested with these instructions is <emphasis role="bold">CAS 3.3.5</emphasis>. Other versions may work. + </para> + + </step> + <step> + <para> + Extract the downloaded file into a suitable location. This location will be referred to as <replaceable>CAS_DIR</replaceable> in the following example. + </para> + + </step> + + </procedure> + + <para> + The simplest way to configure the web archive is to make the necessary changes directly into the CAS codebase. + </para> + <note> + <para> + To perform the final build step and complete these instructions you will need the Apache Maven 2. Download it from <ulink type="http" url="http://maven.apache.org/download.html"> here </ulink> . + </para> + + </note> + <para> + Change the default authentication handler with the one provided by JBoss Enterprise Portal Platform. + </para> + <para> + The CAS Server Plugin makes secure callbacks to a RESTful service installed on the remote JBoss Enterprise Portal Platform 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 controlled by the <filename>cas.war/WEB-INF/deployerConfigContext.xml </filename> file. + </para> + <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Central_Authentication_Service-Modifying_CAS_server"> + <title>Modifying CAS server</title> + <step> + <para> + Open <filename><replaceable>CAS_DIR</replaceable>/cas-server-webapp/src/main/webapp/WEB-INF/deployerConfigContext.xml</filename> + </para> + + </step> + <step> + <para> + Replace this code: + </para> + +<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default102.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> + <para> + with the following (ensure you set the host, port and context with the values corresponding to your portal). Also available in <filename>GATEIN_SSO_HOME/cas/plugin/WEB-INF/deployerConfigContext.xml</filename>.): + </para> + +<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default103.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> + + </step> + <step> + <para> + Copy <filename><replaceable>PORTAL_SSO</replaceable>/cas/plugin/WEB-INF/lib/sso-cas-plugin-<VERSION>.jar</filename> and <filename><replaceable>PORTAL_SSO</replaceable>/cas/plugin/WEB-INF/lib/commons-httpclient-<VERSION>.jar</filename> into the <filename><replaceable>CAS_DIR</replaceable>/cas-server-webapp/src/main/webapp/WEB-INF/lib</filename> created directory. + </para> + + </step> + <step> + <para> + If you have not already done so, download an instance of Tomcat and extract it into a suitable location (which will be called <filename>TOMCAT_HOME</filename> for these instructions). + </para> + + </step> + <step> + <para> + Edit <filename>TOMCAT_HOME/conf/server.xml</filename> and change the 8080 port to 8888 to avoid a conflict with the default JBoss Enterprise Portal Platform. + </para> + <note> + <para> + If JBoss Enterprise Portal Platform is running on the same machine as Tomcat other ports will need to be changed in addition to 8080 in order to avoid conflicts. They can be changed to any free port. For example; you can change the admin port from 8005 to 8805 and the AJP port from 8009 to 8809. + </para> + + </note> + + </step> + <step> + <para> + Navigate locally to the <filename><replaceable>CAS_DIR</replaceable>/cas-server-webapp</filename> directory and execute the following command: + </para> + +<programlisting>mvn install +</programlisting> + + </step> + <step> + <para> + Copy the <filename><replaceable>CAS_DIR</replaceable>/cas-server-webapp/target/cas.war</filename> file into the <filename>TOMCAT_HOME/webapps</filename> directory. + </para> + <para> + Tomcat should start without issue and should be accessible at <ulink type="http" url="http://localhost:8888/cas"> http://localhost:8888/cas </ulink> . + </para> + <note> + <para> + At this stage the login functionality will not be available. + </para> + + </note> + <mediaobject> + <imageobject> + <imagedata fileref="images/AuthenticationAndIdentity/SSO/cas.png" format="PNG" scale="100" width="444" /> + </imageobject> + + </mediaobject> + + </step> + + </procedure> + + <note> + <para> + On logout, the CAS server will display the CAS logout page with a link to return to the portal. To make the CAS server redirect to the portal page after a logout, modify the <filename>cas.war/WEB-INF/cas-servlet.xml</filename> to include the follow line : + </para> + +<programlisting> +<bean id="logoutController" class="org.jasig.cas.web.LogoutController" + p:centralAuthenticationService-ref="centralAuthenticationService" + p:logoutView="casLogoutView" + p:warnCookieGenerator-ref="warnCookieGenerator" + p:ticketGrantingTicketCookieGenerator-ref="ticketGrantingTicketCookieGenerator" + p:followServiceRedirects="true"/> +</programlisting> + + </note> + <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Central_Authentication_Service-Setup_the_CAS_client"> + <title>Setup the CAS client</title> + <step> + <para> + Copy all the libraries from the <filename><replaceable>PORTAL_SSO</replaceable>/cas/gatein.ear/lib</filename> directory into the <filename>JBOSS_HOME/server/default/deploy/gatein.ear/lib</filename>) directory. + </para> + + </step> + <step> + <para> + Edit the <filename>jboss-as/server/<replaceable>PROFILE</replaceable>/deploy/gatein.ear/META-INF/gatein-jboss-beans.xml</filename> and uncomment this section: + </para> + +<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default105.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> + <para> + There's a line comment already in this source file to assist you. + </para> +  + </step> + <step> + <para> + The installation can be tested at this point (assuming the CAS server on Tomcat is running): + </para> + <procedure> + <step> + <para> + Start (or restart) JBoss Enterprise Portal Platform and direct your web browser to <ulink type="http" url="http://localhost:8888/cas"> http://localhost:8888/cas </ulink> . + </para> + + </step> + <step> + <para> + Login with the username <literal>root</literal> and the password <literal>gtn</literal> (or any other account created through the portal). + </para> + + </step> + + </procedure> + + + </step> + + </procedure> + + <para> + To utilize the Central Authentication Service, JBoss Enterprise Portal Platform needs to redirect all user authentication to the CAS server. + </para> + <para> + Information about where the CAS is hosted must be properly configured within the JBoss Enterprise Portal Platform instance. The required configuration is done by modifying three files. + </para> + <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Central_Authentication_Service-Redirect_to_CAS"> + <title>Redirect to CAS</title> + <step> + <para> + Modify the '<emphasis role="bold">Sign In</emphasis>' link in the <filename><replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/web.war/groovy/groovy/webui/component/UIBannerPortlet.gtml</filename> file as follows: + </para> + +<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default106.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> + + </step> + <step> + <para> + Modify the '<emphasis role="bold">Sign In</emphasis>' link in the <filename><replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/web.war/groovy/portal/webui/component/UILogoPortlet.gtmpl</filename> file as follows: + </para> + +<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default107.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> + + </step> + <step> + <para> + Replace the entire contents of <filename>gatein.ear/02portal.war/login/jsp/login.jsp</filename> with: + </para> + +<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default108.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> + + </step> + <step> + <para> + Add the following Filters at the top of the filter chain in <filename>gatein.ear/02portal.war/WEB-INF/web.xml</filename>: + </para> + +<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default109.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> + + </step> + + </procedure> + + <para> + Once these changes have been made, all links to the user authentication pages will redirect to the CAS centralized authentication form and CAS can be used as an SSO implementation in your portal. + </para> + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-SSO_Single_Sign_On_-Java_Open_Single_Sign_On_Project"> + <title>Java Open Single Sign-On Project</title> + <para> + This Single Sign On plugin enables seamless integration between JBoss Enterprise Portal Platform and the Java Open Single Sign-On Project (<emphasis role="bold">JOSSO</emphasis>) Single Sign On Framework. Details about JOSSO can be found at <ulink url="http://www.josso.org"> www.josso.org </ulink> . + </para> + <para> + This section details setting up the JOSSO server to authenticate against the JBoss Enterprise Portal Platform login module. + </para> + <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Java_Open_Single_Sign_On_Project-JOSSO_server"> + <title>JOSSO server</title> + <step> + <para> + Download JOSSO from <ulink type="http" url="http://sourceforge.net/projects/josso/files/"> http://sourceforge.net/projects/josso/files/ </ulink> . + </para> + <note> + <para> + Use the package that embeds Apache Tomcat. The integration was tested with JOSSO-1.8.1. + </para> + + </note> + + </step> + <step> + <para> + Extract the package into what will be called <filename>JOSSO_HOME</filename> in this example. + </para> + + </step> + + </procedure> + + <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Java_Open_Single_Sign_On_Project-Modifying_JOSSO_server"> + <title>Modifying JOSSO server</title> + <step> + <para> + Copy the files from <filename><replaceable>PORTAL_SSO</replaceable>/josso/plugin</filename> into the <filename>JOSSO_HOME</filename> directory created in the last step. + </para> + <para> + This action should replace or add the following files to the <filename>JOSSO_HOME/webapps/josso/WEB-INF/lib</filename> directory: + </para> + <itemizedlist> + <listitem> + <para> + <filename>JOSSO_HOME/lib/josso-gateway-config.xml</filename> + </para> + + </listitem> + <listitem> + <para> + <filename>JOSSO_HOME/lib/josso-gateway-gatein-stores.xml</filename> + </para> + + </listitem> + <listitem> + <para> + <filename>JOSSO_HOME/webapps/josso/WEB-INF/classes/gatein.properties</filename> + </para> + + </listitem> + + </itemizedlist> + + </step> + <step> + <para> + Edit <filename>TOMCAT_HOME/conf/server.xml</filename> file and change the 8080 port to 8888 to avoid a conflict with the default JBoss Enterprise Portal Platform port. + <note> + <title>Port Conflicts</title> + <para> + If JBoss Enterprise Portal Platform is running on the same machine as Tomcat, other ports need to be changed in addition to 8080 in order 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> + + </para> + + </step> + <step> + <para> + Tomcat will start and allow access to <ulink type="http" url="http://localhost:8888/josso/signon/login.do"> http://localhost:8888/josso/signon/login.do </ulink> but at this stage login will not be available. + </para> + <mediaobject> + <imageobject> + <imagedata fileref="images/AuthenticationAndIdentity/SSO/opensso.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + + </step> + + </procedure> + + <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Java_Open_Single_Sign_On_Project-Setup_the_JOSSO_client"> + <title>Setup the JOSSO client</title> + <step> + <para> + Copy the library files from <filename><replaceable>PORTAL_SSO</replaceable>/josso/gatein.ear/lib</filename> into <filename>gatein.ear/lib</filename> (or into <filename>GATEIN_HOME/lib</filename> if the product is running in Tomcat). + </para> + + </step> + <step> + <para> + Copy the <filename><replaceable>PORTAL_SSO</replaceable>/josso/gatein.ear/portal.war/WEB-INF/classes/josso-agent-config.xml</filename> file into the <filename>gatein.ear/02portal.war/WEB-INF/classes</filename> directory (or into <filename>JBOSS_HOME/webapps/portal.war/WEB-INF/classes</filename>, or <filename>GATEIN_HOME/conf</filename> if the product is running in Tomcat). + </para> + + </step> + <step> + <para> + Edit <filename>jboss-as/server/<replaceable>PROFILE</replaceable>/deploy/gatein.ear/META-INF/gatein-jboss-beans.xml</filename> and uncomment this section: + </para> + +<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default111.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> + + </step> + <step> + <para> + In Tomcat, edit <filename>JBOSS_HOME/conf/jaas.conf</filename> and uncomment this section: + </para> + +<programlisting>org.gatein.sso.agent.login.SSOLoginModule required; +org.exoplatform.services.security.j2ee.TomcatLoginModule requiredtm +portalContainerName=portal +realmName=gatein-domain; +</programlisting> + + </step> + <step> + <para> + The installation can be tested at this point. + </para> + <substeps> + <step> + <para> + Start (or restart) JBoss Enterprise Portal Platform, and (assuming the JOSSO server on Tomcat is running) direct your browser to <ulink type="http" url="http://localhost:8888/josso/signon/login.do"> http://localhost:8888/josso/signon/login.do </ulink> . + </para> + + </step> + <step> + <para> + Login with the username <literal>root</literal> and the password <literal>gtn</literal> or any account created through the portal. + </para> + + </step> + + </substeps> + + </step> + + </procedure> + + <para> + The next part of the process is to redirect all user authentication to the JOSSO server. + </para> + <para> + Information about where the JOSSO server is hosted must be properly configured within the JBoss Enterprise Portal Platform instance. The required configuration is done by modifying four files: + </para> + <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Java_Open_Single_Sign_On_Project-Setup_the_portal_to_redirect_to_JOSSO"> + <title>Setup the portal to redirect to JOSSO</title> + <step> + <para> + In the <filename><replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/web.war/groovy/groovy/webui/component/UIBannerPortlet.gtml</filename> file modify the 'Sign In' link as follows: + </para> + +<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default112.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> + + </step> + <step> + <para> + Modify the '<emphasis role="bold">Sign In</emphasis>' link in the <filename>gatein.ear/web.war/groovy/portal/webui/component/UILogoPortlet.gtmpl</filename> file as follows: + </para> + +<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default113.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> + + </step> + <step> + <para> + Replace the entire contents of <filename>gatein.ear/02portal.war/login/jsp/login.jsp</filename> with: + </para> + +<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default114.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> + + </step> + <step> + <para> + Add the following Filters to the top of the filter chain in <filename>gatein.ear/02portal.war/WEB-INF/web.xml</filename>: + </para> + +<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default115.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> + + </step> + + </procedure> + + <para> + From now on, all links redirecting to the user authentication pages will redirect to the JOSSO centralized authentication form. + </para> + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-SSO_Single_Sign_On_-OpenSSO"> + <title>OpenSSO</title> + <para> + This section details the setting up of OpenSSO server to authenticate against the JBoss Enterprise Portal Platform login module. + </para> + <procedure id="proc-Reference_Guide_eXo_JCR_1.14-OpenSSO-Obtaining_OpenSSO"> + <title>Obtaining OpenSSO</title> + <step> + <para> + OpenSSO must be purchased from <ulink type="http" url="http://www.oracle.com/technetwork/middleware/id-mgmt/overview/index.html"> Oracle </ulink> . + </para> + <para> + For testing purposes, use OpenSSO_80U2, which can be downloaded from <ulink type="http" url="http://download.oracle.com/otn/nt/middleware/11g/oracle_opensso_80U2.zip">Oracle </ulink> . + </para> + + </step> + <step> + <para> + Extract the package into a suitable location. This location will be referred to as <filename>OPENSSO_HOME</filename> in this example. + </para> + + </step> + + </procedure> + + <note> + <para> + It is also possible to use OpenAM instead of OpenSSO server. OpenAM is free and the integration steps between Enterprise Portal Platform and OpenAM are very similar as with OpenSSO. More info is available <ulink type="http" url="http://community.jboss.org/wiki/GateInAndOpenAMIntegration"> here </ulink> . + </para> + + </note> + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-SSO_Single_Sign_On_-Modifying_the_OpenSSO_server"> + <title>Modifying the OpenSSO server</title> + <para> + To configure the web server as required, it is simpler to directly modify the source files. + </para> + <para> + The first step is to add the JBoss Enterprise Portal Platform Authentication Plugin. + </para> + <para> + The plugin makes secure callbacks to a RESTful service installed on the remote JBoss Enterprise Portal Platform 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. + </para> + <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Modifying_the_OpenSSO_server-Modifying_OpenSSO_server"> + <title>Modifying OpenSSO server</title> + <step> + <para> + Obtain a copy of Tomcat and extract it into a suitable location. This location will be referred to as <filename>TOMCAT_HOME</filename> in this example. + </para> + + </step> + <step> + <para> + Edit <filename>TOMCAT_HOME/conf/server.xml</filename> and change the 8080 port to 8888 to avoid a conflict with the default JBoss Enterprise Portal Platform port. + <note> + <para> + If JBoss Enterprise Portal Platform is running on the same machine as Tomcat, other ports need to be changed in addition to 8080 in order to avoid port conflicts. They can be changed to any free port. For example, you can change the admin port from 8005 to 8805 and the AJP port from 8009 to 8809. + </para> + + </note> + + </para> + + </step> + <step> + <para> + Ensure the <filename>TOMCAT_HOME/webapps/opensso/config/auth/default/AuthenticationPlugin.xml</filename> file matches the following: + </para> + +<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default117.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> + + </step> + <step> + <para> + Copy the following files into the Tomcat directory at <filename>TOMCAT_HOME/webapps/opensso/WEB-INF/lib</filename>: + </para> + <itemizedlist> + <listitem> + <para> + <filename><replaceable>PORTAL_SSO</replaceable>/opensso/plugin/WEB-INF/lib/sso-opensso-plugin-<VERSION>.jar</filename> + </para> + + </listitem> + <listitem> + <para> + <filename><replaceable>PORTAL_SSO</replaceable>/opensso/plugin/WEB-INF/lib/commons-httpclient-<VERSION>.jar</filename> + </para> + + </listitem> + <listitem> + <para> + <filename><replaceable>PORTAL_SSO</replaceable>/opensso/plugin/WEB-INF/lib/commons-logging-<VERSION>.jar</filename> + </para> + + </listitem> + + </itemizedlist> + + </step> + <step> + <para> + Copy the <filename><replaceable>PORTAL_SSO</replaceable>/opensso/plugin/WEB-INF/classes/gatein.properties</filename> file into the <filename>TOMCAT_HOME/webapps/opensso/WEB-INF/classes</filename> directory. + </para> + + </step> + <step> + <para> + Tomcat should start and be able to access <ulink type="http" url="http://localhost:8888/opensso/UI/Login?realm=gatein"> http://localhost:8888/opensso/UI/Login?realm=gatein </ulink> . + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/AuthenticationAndIdentity/SSO/opensso-shot.png" format="PNG" scale="110" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="150mm" fileref="images/AuthenticationAndIdentity/SSO/opensso-shot.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + <note> + <para> + Login will not be available at this point. + </para> + + </note> + + </step> + + </procedure> + + <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Modifying_the_OpenSSO_server-Configure_the_gatein_realm"> + <title>Configure the "gatein" realm</title> + <step> + <para> + Direct your browser to <ulink type="http" url="http://localhost:8888/opensso"> http://localhost:8888/opensso </ulink> + </para> + + </step> + <step> + <para> + Create a default configuration. + </para> + + </step> + <step> + <para> + Login as <literal>amadmin</literal>. + </para> + <important> + <para> + Go to <menuchoice><guimenu>Configuration</guimenu> <guimenuitem> Authentication </guimenuitem> </menuchoice> and follow the link to <guilabel>Core</guilabel> + </para> + <para> + Add a new value with the class name <literal>org.gatein.sso.opensso.plugin.AuthenticationPlugin</literal>. + </para> + <para> + If this is not done <literal>AuthenticationPlugin</literal> is not available among other OpenSSO authentication modules. + </para> + + </important> + + </step> + <step> + <para> + Go to the <guilabel>Access control</guilabel> tab and create new realm called <literal>gatein</literal>. + </para> + + </step> + <step> + <substeps> + <step> + <para> + Go to the new <literal>gatein</literal> realm and click on the <guilabel>Authentication</guilabel> tab. + </para> + + </step> + <step> + <para> + Click on <guilabel>ldapService</guilabel> (at the bottom in the <guilabel>Authentication chaining</guilabel> section). + </para> + + </step> + <step> + <para> + Change the selection from <literal>Datastore</literal>, which is the default module in the authentication chain, to <literal>AuthenticationPlugin</literal>. + </para> + + </step> + + </substeps> + <para> + These changes enable authentication of the <literal>gatein</literal> realm using the <literal>GateIn REST</literal> service instead of the OpenSSO LDAP server. + </para> + + </step> + <step> + <para> + Go to <guilabel>Advanced properties</guilabel> and change <literal>UserProfile</literal> from <parameter>Required</parameter> to <parameter>Dynamic</parameter> to ensure all new users are automatically created in the OpenSSO datastore after successful authentication. + </para> + + </step> + <step> + <para> + Increase the user privileges to allow REST access with the following procedure: + </para> + <substeps> + <step> + <para> + Go to <menuchoice><guimenu>Access control</guimenu> <guimenuitem> Top level realm </guimenuitem> <guimenuitem> Privileges </guimenuitem> <guimenuitem> All authenticated users </guimenuitem> </menuchoice>. + </para> + + </step> + <step> + <para> + Check the last two checkboxes: + </para> + <itemizedlist> + <listitem> + <para> + Read and write access only for policy properties + </para> + + </listitem> + <listitem> + <para> + Read and write access to all realm and policy properties + </para> + + </listitem> + + </itemizedlist> + + </step> + + </substeps> + + </step> + <step> + <para> + Repeat step 7 for the '<literal>gatein</literal>' realm as well. + </para> + + </step> + + </procedure> + + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-SSO_Single_Sign_On_-Setup_the_OpenSSO_Client"> + <title>Setup the OpenSSO Client</title> + <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Setup_the_OpenSSO_Client-Setup_the_OpenSSO_client"> + <title>Setup the OpenSSO client</title> + <step> + <para> + Copy all libraries from the <filename><replaceable>PORTAL_SSO</replaceable>/opensso/gatein.ear/lib</filename> directory into the <filename>JBOSS_HOME/server/default/deploy/gatein.ear/lib</filename> directory. + </para> + <para> + Alternatively, in a Tomcat environment, copy the libraries into the <filename>JBOSS_HOME/lib</filename> directory. + </para> + + </step> + <step> + <para> + Edit the <filename>jboss-as/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/META-INF/gatein-jboss-beans.xml</filename> and uncomment this section: + </para> + +<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default118.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> + + </step> +  <step> + <para> + Test the installation: + </para> + <procedure> + <step> + <para> + Access JBoss Enterprise Portal Platform by going to <ulink type="http" url="http://localhost:8888/opensso/UI/Login?realm=gatein"> http://localhost:8888/opensso/UI/Login?realm=gatein </ulink> (assuming that the OpenSSO server using Tomcat is still running). + </para> + + </step> + <step> + <para> + Login with the username <literal>root</literal> and the password <literal>gtn</literal> or any account created through the portal. + </para> + + </step> + + </procedure> + + + </step> + + </procedure> + + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-SSO_Single_Sign_On_-Setup_the_portal_to_redirect_to_OpenSSO"> + <title>Setup the portal to redirect to OpenSSO</title> + <para> + The next part of the process is to redirect all user authentication to the OpenSSO server. + </para> + <para> + Information about where the OpenSSO server is hosted must be properly configured within the Enterprise Portal Platform instance. The required configuration is done by modifying three files: + </para> + <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Setup_the_portal_to_redirect_to_OpenSSO-Setup_the_portal_to_redirect_to_OpenSSO"> + <title>Setup the portal to redirect to OpenSSO</title> + <step> + <para> + Modify the '<emphasis role="bold">Sign In</emphasis>' link in the <filename><replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/web.war/groovy/groovy/webui/component/UIBannerPortlet.gtml</filename> file as follows: + </para> + +<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default119.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> + + </step> + <step> + <para> + Modify the '<emphasis role="bold">Sign In</emphasis>' link in the <filename>gatein.ear/web.war/groovy/portal/webui/component/UILogoPortlet.gtmpl</filename> file as follows: + </para> + +<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default120.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> + + </step> + <step> + <para> + Replace the entire contents of <filename>gatein.ear/02portal.war/login/jsp/login.jsp</filename> with: + </para> + +<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default121.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> + + </step> + <step> + <para> + Add the following Filters to the top of the filter chain in <filename>gatein.ear/02portal.war/WEB-INF/web.xml</filename>: + </para> + +<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default122.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> + + </step> + + </procedure> + + <para> + From now on, all links redirecting to the user authentication pages will redirect to the OpenSSO centralized authentication form. + </para> + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-SSO_Single_Sign_On_-SPNEGO_Simple_and_Protected_GSSAPI_Negotiation_Mechanism"> + <title>SPNEGO - Simple and Protected GSSAPI Negotiation Mechanism</title> + <para> + The Simple and Protected GSSAPI Negotiation Mechanism (<emphasis role="bold">SPNEGO</emphasis>) uses desktop credentials provided during a desktop login to transparently authenticate a portal user through a web browser. + </para> + <para> + For illustrative purposes; a typical use case would be: + </para> + <procedure> + <step> + <para> + A user logs into their desktop computer with a login that is governed by an Active Directory domain. + </para> + + </step> + <step> + <para> + The user then launches a web browser to access a web application (that uses JBoss Negotiation) hosted on JBoss Enterprise Portal Platform. + </para> + + </step> + <step> + <para> + The browser transfers the desktop credentials to the web application. + </para> + + </step> + <step> + <para> + JBoss EAP/AS uses background GSS messages with the Active Directory (or any Kerberos Server) to validate the Kerberos ticket from user. + </para> + + </step> + <step> + <para> + The user experiences a seamless single sign on (SSO) into the web application. + </para> + + </step> + + </procedure> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-SPNEGO_Simple_and_Protected_GSSAPI_Negotiation_Mechanism-SPNEGO_Server_Configuration"> + <title>SPNEGO Server Configuration</title> + <para> + In this section, we will describe some necessary steps for setup Kerberos server on Linux. This server will then be used for SPNEGO authentication against JBoss Enterprise Portal Platform. + </para> + <note> + <title>SPNEGO Basics</title> + <para> + The procedure below only describes the basic steps to configure the SPNEGO server in a Linux environment. If you are already familiar with SPNEGO, or if you are using Windows and Active Directory domain, you can jump to the <xref linkend="proc-Reference_Guide_eXo_JCR_1.14-JBoss_Enterprise_Portal_Platform_Configuration-Advanced_SPNEGO_Configuration" /> to see how to integrate SPNEGO with JBoss Enterprise Portal Platform. + </para> + <para> + Please note that Kerberos setup is also dependent on your Linux distribution and so steps can be slightly different in your environment. + </para> + + </note> + <procedure id="proc-Reference_Guide_eXo_JCR_1.14-SPNEGO_Server_Configuration-SPNEGO_Basics"> + <title>SPNEGO Basics</title> + <step> + <para> + Correct the setup of network on the machine. For example, if you are using the "server.local.network" domain as your machine where Kerberos and JBoss Enterprise Portal Platform are localed, add the line containing the machine's IP address to the <emphasis role="bold">/etc/host </emphasis> file. + </para> + +<programlisting> +192.168.1.88 server.local.network +</programlisting> + <note> + <para> + It is not recommended you use loopback addresses. + </para> + + </note> + + </step> + <step> + <para> + Install Kerberos with these packages: krb5-admin-server, krb5-kdc, krb5-config, krb5-user, krb5-clients, and krb5-rsh-server. + </para> + + </step> + <step> + <para> + Edit the Kerberos configuration file at <emphasis role="bold">/etc/krb5.config</emphasis>, including: + </para> + <itemizedlist> + <listitem> + <para> + Uncomment on these lines: + </para> + +<programlisting> +default_tgs_enctypes = des3-hmac-sha1 +default_tkt_enctypes = des3-hmac-sha1 +permitted_enctypes = des3-hmac-sha1 +</programlisting> + + </listitem> + <listitem> + <para> + Add <emphasis role="bold">local.network</emphasis> as a default realm and it is also added to the list of realms and remove the remains of realms. The content looks like: + </para> + +<programlisting> +[libdefaults] + default_realm = LOCAL.NETWORK + +# The following krb5.conf variables are only for MIT Kerberos. + krb4_config = /etc/krb.conf + krb4_realms = /etc/krb.realms + kdc_timesync = 1 + ccache_type = 4 + forwardable = true + proxiable = true + +# The following encryption type specification will be used by MIT Kerberos +# if uncommented. In general, the defaults in the MIT Kerberos code are +# correct and overriding these specifications only serves to disable new +# encryption types as they are added, creating interoperability problems. +# +# Thie only time when you might need to uncomment these lines and change +# the enctypes is if you have local software that will break on ticket +# caches containing ticket encryption types it doesn't know about (such as +# old versions of Sun Java). + + default_tgs_enctypes = des3-hmac-sha1 + default_tkt_enctypes = des3-hmac-sha1 + permitted_enctypes = des3-hmac-sha1 + +# The following libdefaults parameters are only for Heimdal Kerberos. + v4_instance_resolve = false + v4_name_convert = { + host = { + rcmd = host + ftp = ftp + } + plain = { + something = something-else + } + } + fcc-mit-ticketflags = true + +[realms] + LOCAL.NETWORK = { + kdc = server.local.network + admin_server = server.local.network + } + +[domain_realm] + .local.network = LOCAL.NETWORK + local.network = LOCAL.NETWORK + +[login] + krb4_convert = true + krb4_get_tickets = false +</programlisting> + + </listitem> + + </itemizedlist> + + </step> + <step> + <para> + Edit the KDC configuraton file at <emphasis role="bold">/etc/krb5kdc/kdc.conf</emphasis> that looks like. + </para> + +<programlisting> +[kdcdefaults] + kdc_ports = 750,88 + +[realms] + LOCAL.NETWORK = { + database_name = /home/gatein/krb5kdc/principal + admin_keytab = FILE:/home/gatein/krb5kdc/kadm5.keytab + acl_file = /home/gatein/krb5kdc/kadm5.acl + key_stash_file = /home/gatein/krb5kdc/stash + kdc_ports = 750,88 + max_life = 10h 0m 0s + max_renewable_life = 7d 0h 0m 0s + master_key_type = des3-hmac-sha1 + supported_enctypes = aes256-cts:normal arcfour-hmac:normal des3-hmac-sha1:normal des-cbc-crc:normal des:normal des:v4 des:norealm des:onlyrealm des:afs3 + default_principal_flags = +preauth + } + +[logging] + kdc = FILE:/home/gatein/krb5logs/kdc.log + admin_server = FILE:/home/gatein/krb5logs/kadmin.log +</programlisting> + <itemizedlist> + <listitem> + <para> + Create krb5kdc and krb5logs directory for Kerberos database as shown in the configuration file above. + </para> + + </listitem> + <listitem> + <para> + Next, create a KDC database using the following command. + </para> + +<programlisting> +sudo krb5_newrealm +</programlisting> + + </listitem> + <listitem> + <para> + Start the KDC and Kerberos admin servers using these commands: + </para> + +<programlisting> +sudo /etc/init.d/krb5-kdc restart +sudo /etc/init.d/krb-admin-server restart +</programlisting> + + </listitem> + + </itemizedlist> + + </step> + <step> + <para> + Add Principals and create Keys. + </para> + <itemizedlist> + <listitem> + <para> + Start an interactive 'kadmin' session and create the necessary Principals. + </para> + +<programlisting> +sudo kadmin.local +</programlisting> + + </listitem> + <listitem> + <para> + Add the JBoss Enterprise Portal Platform machine and keytab file that need to be authenticated. + </para> + +<programlisting> +addprinc -randkey HTTP/server.local.network(a)LOCAL.NETWORK +ktadd HTTP/server.local.network(a)LOCAL.NETWORK +</programlisting> + + </listitem> + <listitem> + <para> + Add the default JBoss Enterprise Portal Platform user accounts and enter the password for each created user that will be authenticated. + </para> + +<programlisting> +addprinc john +addprinc demo +addprinc root +</programlisting> + + </listitem> + + </itemizedlist> + + </step> + <step> + <para> + Test your changed setup by using the command. + </para> + +<programlisting> +kinit -A demo +</programlisting> + <itemizedlist> + <listitem> + <para> + If the setup works well, you are required to enter the password created for this user in Step 5. Without the -A, the kerberos ticket validation involved reverse DNS lookups, which can get very cumbersome to debug if your network's DNS setup is not great. This is a production level security feature, which is not necessary in this development setup. In production environment, it will be better to avoid -A option. + </para> + + </listitem> + <listitem> + <para> + After successful login to Kerberos, you can see your Kerberos ticket when using this command. + </para> + +<programlisting> +klist +</programlisting> + + </listitem> + <listitem> + <para> + If you want to logout and destroy your ticket, use this command. + </para> + +<programlisting> +kdestroy +</programlisting> + + </listitem> + + </itemizedlist> + + </step> + + </procedure> + + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-SPNEGO_Simple_and_Protected_GSSAPI_Negotiation_Mechanism-SPNEGO_Server_Configuration-Clients"> + <title>Clients</title> + <para> + After performing all configurations above, you need to enable the <emphasis role="bold">Negotiate authentication </emphasis> of Firefox in client machines so that clients could be authenticated by JBoss Enterprise Portal Platform as follows: + </para> + <procedure> + <step> + <para> + Start Firefox, then enter the command: <emphasis role="bold">about:config </emphasis> into the address field. + </para> + + </step> + <step> + <para> + Enter <emphasis role="bold">network.negotiate-auth</emphasis> and set the value as below: + </para> + +<programlisting> +network.negotiate-auth.allow-proxies = true +network.negotiate-auth.delegation-uris = .local.network +network.negotiate-auth.gsslib (no-value) +network.negotiate-auth.trusted-uris = .local.network +network.negotiate-auth.using-native-gsslib = true +</programlisting> + + </step> + + </procedure> + + <note> + <para> + Consult documentation of your OS or web browser if using different browser than Firefox. + </para> + + </note> + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-SPNEGO_Simple_and_Protected_GSSAPI_Negotiation_Mechanism-JBoss_Enterprise_Portal_Platform_Configuration"> + <title>JBoss Enterprise Portal Platform Configuration</title> + <para> + JBoss Enterprise Portal Platform uses JBoss Negotiation to enable SPNEGO-based desktop SSO for the portal. Here are the steps to integrate SPNEGO with JBoss Enterprise Portal Platform. + </para> + <procedure id="proc-Reference_Guide_eXo_JCR_1.14-JBoss_Enterprise_Portal_Platform_Configuration-Advanced_SPNEGO_Configuration"> + <title>Advanced SPNEGO Configuration</title> + <step> + <para> + Activate the Host authentication. Add the following host login module to the <filename>jboss-as/server/<replaceable>PROFILE</replaceable>/conf/login-config.xml</filename>: + </para> + +<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default124.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> + <para> + The '<literal>keyTab</literal>' value should point to the keytab file that was generated by the <literal>kadmin</literal> Kerberos tool. When using Kerberos on Linux, it should be value of parameter <emphasis role="bold">admin_keytab</emphasis> from kdc.conf file. See the <xref linkend="proc-Reference_Guide_eXo_JCR_1.14-SPNEGO_Server_Configuration-SPNEGO_Basics" /> for more details. + </para> + + </step> + <step> + <para> + Extend the core authentication mechanisms to support SPNEGO. Under <filename>deployers/jbossweb.deployer/META-INF/war-deployers-jboss-beans.xml</filename>, add a '<literal>SPNEGO</literal>' authenticators property + </para> + +<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default125.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> + + </step> + <step> + <para> + Add the GateIn SSO module binaries by copying <emphasis role="bold">GATEIN_SSO_HOME/spnego/gatein.ear/lib/sso-agent-VERSION.jar</emphasis> to the <emphasis role="bold">JBOSS_HOME/server/default/deploy/gatein.ear/lib</emphasis> directory. File <emphasis role="bold">GATEIN_SSO_HOME/spnego/gatein.ear/lib/spnego-VERSION.jar</emphasis> needs to be copied to the <emphasis role="bold">JBOSS_HOME/server/default/lib</emphasis> directory. + </para> + + </step> +  <step> + <para> + Modify the <filename>deploy/gatein.ear/META-INF/gatein-jboss-beans.xml</filename> file to match the following: + </para> + +<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default126.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> + <para> + This activates SPNEGO LoginModules with fallback to FORM authentication. When SPNEGO is not available and it needs to fallback to FORM, it will use <emphasis role="bold">gatein-form-auth-domain</emphasis> security domain. + </para> + + </step> + <step> + <para> + Modify <filename>gatein.ear/02portal.war/WEB-INF/web.xml</filename> to match: + </para> + +<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default127.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> + <para> + Integrate the request pre-processing needed for SPNEGO via filters by adding the following filters to the <emphasis role="bold">JBOSS_HOME/server/default/deploy/gatein.ear/02portal.war/WEB-INF/web.xml</emphasis> at the top of the Filter chain. + </para> + +<programlisting language="XML" role="XML"><xi:include href="../../extras/Authentication_Identity_SSO/default128.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> + <para> + This integrates request pre-processing needed for SPNEGO. + </para> + + </step> + <step> + <para> + Edit the '<emphasis role="bold">Sign In</emphasis>' link in <filename><replaceable>JBOSS_HOME</replaceable>/server/<replaceable>PROFILE</replaceable>/deploy/gatein.ear/web.war/groovy/groovy/webui/component/UIBannerPortlet.gtmpl</filename> to match the following: + </para> + +<programlisting language="Java" role="Java"><xi:include href="../../extras/Authentication_Identity_SSO/default129.java" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> + + </step> + <step> + <para> + Start the JBoss Enterprise Portal Platform; + </para> + +<programlisting language="Java" role="Java"><xi:include href="../../extras/Authentication_Identity_SSO/default130.java" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> + <para> + The <replaceable>PROFILE</replaceable> parameter in the above command should be replaced with the server profile modified with the above configuration. + </para> + + </step> + <step> + <para> + Login to Kerberos: + </para> + +<programlisting>kinit -A demo +</programlisting> + + </step> + + </procedure> + + <para> + Clicking the 'Sign In' link on the JBoss Enterprise Portal Platform should automatically sign the 'demo' user into the portal. + </para> + <para> + If you destroy your kerberos ticket with command <command>kdestroy</command>, then try to login again, you will directed to the login screen of JBoss Enterprise Portal Product because you don't have active Kerberos ticket. You can login with predefined account and password "demo"/"gtn" . + </para> + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-SPNEGO_Simple_and_Protected_GSSAPI_Negotiation_Mechanism-JBoss_Enterprise_Portal_Platform_Configuration-Clients"> + <title>Clients</title> + <para> + After performing all configurations above, you need to enable the <emphasis role="bold">Negotiate authentication </emphasis> of Firefox in clients so that clients can be authenticated by JBoss Enterprise Portal Platform as follows: + </para> + <procedure> + <step> + <para> + Start Firefox, then enter the command: <emphasis role="bold">about:config </emphasis> into the address field. + </para> + + </step> + <step> + <para> + Enter <emphasis role="bold">network.negotiate-auth</emphasis> and set the value as below: + </para> + +<programlisting> +network.negotiate-auth.allow-proxies = true +network.negotiate-auth.delegation-uris = .local.network +network.negotiate-auth.gsslib (no-value) +network.negotiate-auth.trusted-uris = .local.network +network.negotiate-auth.using-native-gsslib = true +</programlisting> + + </step> + + </procedure> + + + </section> + + + </section> + + +</section> + + Copied: epp/docs/branches/5.2/Reference_Guide/en-US/modules/RH-WSRP.xml (from rev 8139, epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/RH-WSRP.xml) =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/RH-WSRP.xml (rev 0) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/RH-WSRP.xml 2011-11-25 00:48:53 UTC (rev 8141) @@ -0,0 +1,2003 @@ +<?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 "Reference_Guide_eXo_JCR_1.14.ent"> +%BOOK_ENTITIES; +]> +<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP"> + <title><remark>Web Services for Remote Portlets (WSRP)</remark></title> + <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Introduction"> + <title>Introduction</title> + <para> + The Web Services for Remote Portlets (WSRP) specification defines a web service interface for accessing and interacting with interactive presentation-oriented web services. + </para> + <para> + It has been produced through the efforts of the Web Services for Remote Portlets (WSRP) OASIS Technical Committee. It is based on the requirements gathered and the proposals made to the committee. + </para> + <para> + Scenarios that motivate WSRP functionality include: + </para> + <itemizedlist> + <listitem> + <para> + Content hosts, such as portal servers, providing Portlets as presentation-oriented web services that can be used by aggregation engines. + </para> + + </listitem> + <listitem> + <para> + Aggregating frameworks, including portal servers, consuming presentation-oriented web services offered by content providers and integrating them into the framework. + </para> + + </listitem> + + </itemizedlist> + <para> + More information on WSRP can be found on the official <ulink url="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsrp">website</ulink>. We suggest reading the <ulink url="http://www.oasis-open.org/committees/download.php/10539/wsrp-primer-1.0.html">primer</ulink> for a good, albeit technical, overview of WSRP. + </para> + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Level_of_Support"> + <title>Level of Support</title> + <para> + The WSRP Technical Committee defined <ulink url="http://www.oasis-open.org/committees/download.php/3073">WSRP Use Profiles</ulink> to help with WSRP interoperability. Terms defined in that document will be used in this section. + </para> + <para> + JBoss Enterprise Portal Platform provides a <emphasis>Simple</emphasis> level of support for the WSRP Producer, with the exception of out-of-band registration. In-band registration and persistent local state (which are defined at the <emphasis>Complex</emphasis> level) are supported. + </para> + <para> + JBoss Enterprise Portal Platform provides a <emphasis>Medium</emphasis> level of support for the Consumer, excepting HTML markup (as JBoss Enterprise Portal Platform itself does not handle other markup types). Explicit portlet cloning and the <literal>PortletManagement</literal> interface are supported. + </para> + <para> + The WSRP component has Level 1 Producer and Consumer caching. Cookie handling is supported properly on the Consumer. The Producer requires cookie initialization (as this improves interoperability with some consumers). + </para> + <para> + JBoss Enterprise Portal Platform does not support custom window states or modes, therefore neither does the WSRP component. It does, however, support CSS on both the Producer (although this is more a function of the portlets than an inherent Producer capability) and Consumer. + </para> + <para> + JBoss Enterprise Portal Platform &VY; includes implementations of WSRP 1.0 and 2.0. + </para> + <para> + All optional features in WSRP 2 are implemented in JBoss Enterprise Portal Platform &VY; except support for lifetimes and leasing support. + </para> + <note> + <para> + As of version &VZ; of Enterprise Portal Platform, WSRP is only activated and supported when deployed on JBoss Enterprise Application Server. + </para> + + </note> + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Deploying_WSRP"> + <title>Deploying WSRP</title> + <note> + <title>Notational Devices</title> + <para> + The following list of support files uses the following notational devices: + </para> + <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Deploying_WSRP-Notations"> + <title>Notations:</title> + <varlistentry> + <term><replaceable>JBOSS_HOME</replaceable></term> + <listitem> + <para> + <replaceable>JBOSS_HOME</replaceable> refers to the directory that your instance of JBoss Enterprise Portal Platform has been extracted/installed to. For example: <filename>/home/<replaceable>USERNAME</replaceable>/jboss-epp-<replaceable><VERSION></replaceable>/</filename> + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term><replaceable>WSRP_PATH</replaceable></term> + <listitem> + <para> + The WSRP files referred to in this section are found in the <filename><replaceable>JBOSS_HOME</replaceable>/jboss-as/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear</filename> directory. + </para> + <para> + For ease of reference this path will be represented by: <replaceable>WSRP_PATH</replaceable>. + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term><replaceable>WSRP_VERSION</replaceable></term> + <listitem> + <para> + <replaceable>WSRP_VERSION</replaceable> represents the version of the WSRP component in use. + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term><replaceable>PORTAL_VERSION</replaceable></term> + <listitem> + <para> + <replaceable>PORTAL_VERSION</replaceable> represents the version of JBoss Enterprise Portal Platform in use. + </para> + + </listitem> + + </varlistentry> + + </variablelist> + + </note> + <para> + Starting with version 2.1.0-GA of the component, WSRP is packaged as a JBoss Enterprise Portal Platform extension and is now self-contained in an easy to install package named <filename>gatein-wsrp-integration.ear</filename>, deployed directly in the <filename>deploy</filename> directory of your JBoss Application Server configuration directory. + </para> + <para> + The extension itself is composed of the following components: + </para> + <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Deploying_WSRP-WSRP_support_files"> + <title>WSRP support files</title> + <varlistentry> + <term><filename>META-INF/</filename></term> + <listitem> + <para> + This directory contains files necessary for EAR packaging. The only file that is of interest from a user perspective is <filename>gatein-wsse-consumer.xml</filename> which allows you to configure WS-Security support for the consumer. + </para> + <para> + Refer to <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-WSRP_and_WS_Security-WS_Security_Configuration" /> section for more details. + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term><filename>extension-component-$PORTAL_VERSION.jar</filename></term> + <listitem> + <para> + This archive which contains the components needed to integrate the WSRP component into JBoss Enterprise Portal Platform. It also includes the default configuration files for the WSRP producer and the default WSRP consumers. + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term><filename>extension-config-$PORTAL_VERSION.jar</filename></term> + <listitem> + <para> + This file contains the configuration file needed by the GateIn extension mechanism to properly register this EAR as an extension. + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term><filename>extension-war-$PORTAL_VERSION.war</filename></term> + <listitem> + <para> + This file contains the configuration files needed by the GateIn extension mechanism to properly setup the WSRP service. It includes <filename>wsrp-configuration.xml</filename> which, in particular, configures several options for the <code> WSRPServiceIntegration </code> component at the heart of the WSRP integration in JBoss Enterprise Portal Platform. + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term><filename>lib/</filename></term> + <listitem> + <para> + This directory contains the different libraries needed by the WSRP service. + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term><filename>wsrp-admin-gui-$WSRP_VERSION.war</filename></term> + <listitem> + <para> + This file contains the WSRP Configuration portlet with which you can configure consumers to access remote servers and how the WSRP producer is configured. + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term><filename>wsrp-producer-jb5wsss-$WSRP_VERSION.war</filename></term> + <listitem> + <para> + This file contains the producer-side support for WS-Security. The only file of interest from a user perspective is <filename>gatein-wsse-producer.xml</filename> which allows you to configure WS-Security support for the producer. + </para> + <para> + Refer to <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-WSRP_and_WS_Security-WS_Security_Configuration" /> for more details. + </para> + + </listitem> + + </varlistentry> + + </variablelist> + <section id="sect-Reference_Guide_eXo_JCR_1.14-Deploying_WSRP-Non_default_Ports_or_Hostnames"> + <title>Non-default Ports or Hostnames</title> + <para> + JBoss WS (the web service stack that JBoss Enterprise Portal Platform uses) should update the port and host name used in WSDL. Refer to the JBoss WS <ulink url="http://community.jboss.org/wiki/JBossWS-UserGuide#Configuration">user guide</ulink> for more information. + </para> + <para> + If the host name and port on which the server runs have been modified, the configuration for the Consumer used to consume JBoss Enterprise Portal Platform's "self" Producer will need to be updated. Refer to <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Consuming_Remote_WSRP_Portlets" /> for directions on how to do this. + </para> + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Deploying_WSRP-Using_WSRP_with_SSL"> + <title>Using WSRP with SSL</title> + <para> + It is possible to use WSRP over SSL for secure exchange of data. Refer to these <ulink url="http://community.jboss.org/wiki/ConfiguringWSRPforuseoverSSL">instructions</ulink> for how to do this. + </para> + + </section> + + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-WSRP_and_WS_Security"> + <title>WSRP and WS-Security</title> + <para> + Portlets may present different data or options depending on the currently authenticated user. For remote portlets, this means having to propagate the user credentials from the consumer back to the producer in a safe and secure manner. + </para> + <para> + The WSRP specification does not directly specify how this should be accomplished, but delegates this work to the existing WS-Security standards. + </para> + <note> + <title>Web Container Compatibility</title> + <para> + WSRP and WS-Security is currently only supported on JBoss Enterprise Portal Platform when running on top of JBoss AS 5. + </para> + + </note> + <warning> + <title>Encryption</title> + <para> + <emphasis role="bold">The use of encryption is strongly recommended.</emphasis> + </para> + <para> + Credentials being sent between the consumer and producer should be encrypted or they will be sent in plain text and could be easily intercepted. + </para> + <para> + You can either configure WS-Security to encrypt and sign the SOAP messages being sent, or secure the transport layer by using an <literal>https</literal> endpoint. + </para> + <para> + Failure to encrypt the SOAP message or transport layer will result in the username and password being sent in plain text. + </para> + + </warning> + <important> + <title>Credentials</title> + <para> + When the consumer sends the user credentials to the producer, it is sending the credentials for the currently authenticated user in the consumer. This makes signing in to remote portlets transparent to end users, but also requires that the producer and consumer use the same credentials. + </para> + <para> + The username and password must be the same and valid on both servers. + </para> + <para> + The recommended approach for this situation would be to use a common LDAP configuration. Please see the User Guide at <ulink type="http" url="docs.redhat.com" /> for information on how to configure LDAP for use with JBoss Enterprise Portal Platform + </para> + + </important> + <para> + This community Wiki <ulink url="http://community.jboss.org/wiki/GateInWSRPAndWebServiceSecurity">article</ulink>, also provides a step-by-step example on how to configure WSRP with WS-Security. + </para> + <section id="sect-Reference_Guide_eXo_JCR_1.14-WSRP_and_WS_Security-WS_Security_Configuration"> + <title>WS-Security Configuration</title> + <para> + JBoss Enterprise Portal Platform uses <application>JBossWS Native</application> to handle ws-security. + </para> + <para> + Refer to the WS-Security section of the <ulink url="http://www.jboss.org/jbossas/docs/5-x">JBoss AS 5 Administration and Configuration Guide </ulink> for in-depth configuration options. + </para> + <para> + 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. + </para> + <para> + The following are the JBossWS Native configuration files which need to be configure for WSRP: + </para> + <variablelist> + <title></title> + <varlistentry> + <term>gatein-wsrp-integration.ear/META-INF/gatein-wsse-consumer.xml</term> + <listitem> + <para> + BossWS configuration file for the consumer. + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term>gatein-wsrp-integration.ear/wsrp-producer-jb5wss.war/WEB-INF/conf/gatein-wsse-producer.xml</term> + <listitem> + <para> + JBossWS configuration file for the producer. + </para> + + </listitem> + + </varlistentry> + + </variablelist> + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-WSRP_and_WS_Security-WS_Security_Producer_Configuration"> + <title>WS-Security Producer Configuration</title> + <para> + Other than the JBossWS configuration file mention above, no other configuration changes should be necessary for the producer. + </para> + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-WSRP_and_WS_Security-WS_Security_Consumer_Configuration"> + <title>WS-Security Consumer Configuration</title> + <para> + The consumer requires some changes before it will function properly with WS-Security. + </para> + <para> + The consumer needs access to the current servlet request since this is used to retrieve the currently authenticated user. In order to access this information, the consumer needs a special servlet-filter added to the portal. + </para> + <procedure id="proc-Reference_Guide_eXo_JCR_1.14-WS_Security_Consumer_Configuration-Add_the_servlet_filter"> + <title>Add the servlet-filter</title> + <step> + <para> + Open <filename><replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/02portal.war/WEB-INF/web.xml</filename> and add the following: + </para> + +<programlisting role="XML"> + <filter> + <filter-name>ServletAccessFilter</filter-name> + <filter-class>org.gatein.wsrp.servlet.ServletAccessFilter</filter-class> + </filter> + <filter-mapping> + <filter-name>ServletAccessFilter</filter-name> + <url-pattern>/*</url-pattern> + </filter-mapping> +</programlisting> + + </step> + <step> + <para> + Check the <guilabel>Enable WS Security</guilabel> checkbox in the consumer configuration options of the WSRP Configuration portlet + </para> + <mediaobject> + <imageobject> + <imagedata align="center" fileref="images/WSRP/config_wss_selected.png" format="PNG" scalefit="1" valign="middle" width="444" /> + </imageobject> + + </mediaobject> + </step> + </procedure> + + + </section> + + <section> + <title>WS-Security Consumer Checklist</title> + <para> + In order for the consumer to handle ws-security, the following items must be implemented: + </para> + <orderedlist> + <listitem> + <para> + The JBossWS configuration files must be configured + </para> + + </listitem> + <listitem> + <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> + + </listitem> + + </orderedlist> + <para> + The consumer will not properly handle ws-security unless all three items are correctly configured. + </para> + + </section> + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Making_a_Portlet_Remotable"> + <title>Making a Portlet Remotable</title> + <note> + <para> + Only JSR-286 (Portlet 2.0) portlets can be made remotable as the mechanism to expose a portlet to WSRP relies on a JSR-286-only functionality. + </para> + + </note> + <para> + JBoss Enterprise Portal Platform does <emphasis role="bold">not</emphasis>, by default, expose local portlets for consumption by remote WSRP consumers. + </para> + <para> + In order to make a portlet remotely available, it must be made "remotable" by marking it as such in the associated <filename>portlet.xml</filename>. + </para> + <para> + A specific <code>org.gatein.pc.remotable container-runtime-option</code> is used to accomplish this. Setting its value to <code>true</code> makes the portlet available for remote consumption, while setting its value to <code>false</code> will not publish it remotely. + </para> + <para> + As specifying the remotable status for a portlet is optional, nothing need be done if portlets do not need to be remotely available. + </para> + <para> + In the following example, the "BasicPortlet" portlet is specified as being remotable. + </para> + +<programlisting language="XML" role="XML"><xi:include href="../extras/WSRP/default255.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> + <para> + It is also possible to specify that all the portlets declared within a given portlet application be remotable by default. + </para> + <para> + 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. + </para> + <para> + For example: + </para> + +<programlisting language="XML" role="XML"><xi:include href="../extras/WSRP/default256.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> + <para> + This example defines two portlets. As the <code>org.gatein.pc.remotable container-runtime-option</code> is 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. + </para> + <para> + It is possible to override this 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. + </para> + <para> + In the example above, the <literal>RemotelyExposedPortlet</literal> 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>. + </para> + <para> + The <literal>NotRemotelyExposedPortlet</literal>, however, overrides the default behavior and is not remotely exposed. + </para> + <note> + <title>Note</title> + <para> + Portlets are not remotely exposed if no top-level <code>org.gatein.pc.remotable container-runtime-option</code> value is set to <code>true</code>. + </para> + + </note> + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Consuming_WSRP_portlets_from_a_remote_Consumer"> + <title>Consuming WSRP portlets from a remote Consumer</title> + <para> + Configuration is extremely variable between different WSRP Consumers. Most, however, require a specification of the URL for the Producer's WSDL definition. If the JBoss Enterprise Portal Platform Consumer is not being used, refer to the documentation for the Consumer that is in use for specific instructions. + </para> + <para> + For instructions on how to specify this URL in JBoss Enterprise Portal Platform, refer to <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Consuming_Remote_WSRP_Portlets" />. + </para> + <para> + JBoss Enterprise Portal Platform's Producer is automatically set up when a portal instance is deployed with the WSRP service. + </para> + <para> + The WSDL file can be accessed at: + </para> + <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Consuming_WSRP_portlets_from_a_remote_Consumer-File_paths"> + <title>File paths:</title> + <varlistentry> + <term>WSRP 1.0:</term> + <listitem> + <para> + <filename>http://<replaceable>{hostname}</replaceable>:<replaceable>{port}</replaceable>/wsrp-producer/v1/MarkupService?wsdl</filename>. + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term>WSRP 2.0:</term> + <listitem> + <para> + <filename>http://<replaceable>{hostname}</replaceable>:<replaceable>{port}</replaceable>/wsrp-producer/v2/MarkupService?wsdl</filename>. + </para> + + </listitem> + + </varlistentry> + + </variablelist> + <para> + The default hostname is <literal>localhost</literal> and the default port is <literal>8080</literal>. + </para> + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Consuming_Remote_WSRP_Portlets"> + <title>Consuming Remote WSRP Portlets</title> + <section id="sect-Reference_Guide_eXo_JCR_1.14-Consuming_Remote_WSRP_Portlets-Overview"> + <title>Overview</title> + <para> + To be able to consume WSRP portlets exposed by a remote producer, JBoss Enterprise Portal Platform's WSRP consumer must be configured to access that remote producer. + </para> + <para> + Access to a remote producer can be configured using the provided configuration portlet. Alternatively, it is also possible to configure access to remote producers using an XML descriptor. The configuration portlet is the recommended method. + </para> + <para> + Once a remote producer has been configured, the portlets that it exposes are then available in the Application Registry to be added to categories and then to pages. + </para> +  + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Consuming_Remote_WSRP_Portlets-Configuring_a_Remote_Producer"> + <title>Configuring a Remote Producer</title> + <para> + Access to a remote producer needs to be defined so that portlets can be consumed within JBoss Enterprise Portal Platform. This section will show how to configure access to <emphasis role="bold">NetUnity</emphasis>'s public WSRP producer. + </para> + <para> + Firstly using the configuration portlet and then how the same result can be accomplished with a producer descriptor, though it is far easier to do so via the configuration portlet. + </para> + <important> + <title>Chunked Encoding</title> + <para> + Some WSRP producers, such as Oracle, do not support chunked encoding. If your producer does not support chunked encoding, it will not be able to properly connect to the producer. + </para> + <para> + This will manifest itself with the following error: + </para> + +<screen>Caused by: org.jboss.ws.WSException: Invalid HTTP server response [503] - Service Unavailable. +</screen> + <para> + A workaround for this issue involves editing the <parameter>chunksize</parameter> setting in the <filename>standard-jaxws-client-config.xml</filename> file. + </para> + <para> + Refer to <ulink type="http" url="http://community.jboss.org/wiki/Workaroundwhenchunkedencodingisnotsupported">http://community.jboss.org/wiki/Workaroundwhenchunkedencodingisnotsupported</ulink> for more information. + </para> + + </important> + <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuring_a_Remote_Producer-The_Configuration_Portlet"> + <title>The Configuration Portlet</title> + <para> + JBoss Enterprise Portal Platform provides a graphical portlet to assist with configuring access to, and other facets of, remote WSRP Producers. + </para> + <para> + It is available at: <ulink type="http" url="http://localhost:8080/portal/login?initialURI=%2Fportal%2Fprivate%2Fclass..." />. + </para> + <para> + The portlet also is a group page for /platform/administrators + </para> + <para> + Although the Configuration Portlet is installed by default in JBoss Enterprise Portal Platform &VY;., installation instructions are included below should the portlet ever need to be re-installed: + </para> + <procedure id="proc-Reference_Guide_eXo_JCR_1.14-The_Configuration_Portlet-Installing_the_configuration_portlet"> + <title><emphasis role="bold">Installing the configuration portlet:</emphasis></title> + <step> + <para> + Log into the portal as an administrator and go to the Application Registry (Click <ulink url="http://localhost:8080/portal/private/classic/administration/registry">http://localhost:8080/portal/private/classic/administration/registry</ulink> if using the default installation). + </para> + + </step> + <step> + <para> + Add the WSRP Configuration portlet to the Administration category. If the Import Applications functionality is used, the WSRP Configuration portlet will be automatically added to the Administration category. + </para> + + </step> + <step> + <para> + Once the portlet is added to a category, it can be added to a page and used. It is recommended that it be added to the same page as the Application Registry (as other operations relating to WSRP and adding portlets to categories are somewhat related). Add the WSRP Configuration portlet to the page using the standard procedure. + </para> + + </step> + + </procedure> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-The_Configuration_Portlet-Using_the_Configuration_portlet"> + <title><emphasis role="bold">Using the Configuration portlet</emphasis></title> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/config_init.png" format="PNG" scale="120" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/config_init.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + <para> + This screen presents all the configured consumers associated with their status and possible actions on them. + </para> + <para> + A Consumer can be active or inactive. Activating a Consumer means that it is ready to act as a portlet provider. + </para> + <para> + Note also that a Consumer can be marked as requiring <emphasis>refresh</emphasis>, which means that the information held about it might not be up to date. Refreshing it from the remote Producer will update this information. + </para> + <para> + This can happen for several reasons: the service description for that remote Producer has not been fetched yet, the cached version has expired or modifications have been made to the configuration that could potentially invalidate it, thus requiring re-validation of the information. + </para> + <para> + To create a new Consumer: + </para> + <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Using_the_Configuration_portlet-Creating_a_Consumer"> + <title><emphasis role="bold">Creating a Consumer</emphasis></title> + <step> + <para> + Type "<literal>netunity</literal>" into the "<emphasis role="bold">Create a consumer named:</emphasis>" field. + </para> + + </step> + <step> + <para> + Click on "<emphasis role="bold">Create consumer</emphasis>" to create a new Consumer called <literal>netunity</literal>. + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/config_create.png" format="PNG" scale="100" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/config_create.png" format="PNG" /> + </imageobject> + + </mediaobject> + + </step> + <step> + <para> + In the next form, set the cache expiration value to <parameter>300</parameter> seconds. + </para> + + </step> + <step> + <para> + Leave the default timeout value for web services (WS) operations. + </para> + + </step> + <step> + <para> + Enter the WSDL URL for the producer in the text field. + </para> + + </step> + <step> + <para> + Press the "Refresh & Save" button: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/config_wsdl.png" format="PNG" scale="120" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/config_wsdl.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + + </step> + + </procedure> + + <para> + This will retrieve the service description associated with the Producer which WSRP interface is described by the WSDL file found at the URL entered. + </para> + <para> + In this case, querying the service description will show that the Producer requires registration, that it requested three registration properties and that the current configuration is missing values for these properties: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/config_missing.png" format="PNG" scale="120" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/config_missing.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + <para> + This particular producer requests simple <literal>Yes</literal> or <literal>No</literal> values for the three registration properties. + </para> + <para> + Enter <literal>No</literal>, <literal>Yes</literal> and <literal>No</literal> (in that order) for the values and then pressing the "Refresh & Save" button should result in: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/config_end.png" format="PNG" scale="120" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/config_end.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + <note> + <title>Values</title> + <para> + Unfortunately there is no automated way to learn about which possible values (if any) are expected by the remote Producer. Possible values may be indicated in the registration property description but this is not always the case. Refer to the specific Producer's documentation. + </para> + + </note> + <para> + The Consumer for the <literal>netunity</literal> Producer should now be available as a portlet provider and be ready to be used. + </para> + <para> + If the producer had required registration but did not 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), the following screen would have appeared after pressing the "Refresh & Save" button: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/config_refresh.png" format="PNG" scale="120" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/config_refresh.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + + </section> + + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuring_a_Remote_Producer-Using_XML"> + <title>Using XML</title> + <para> + Although using the WSRP Configuration portlet to configure Consumers is recommended, the WSRP component provides an alternative way to configure consumers. + </para> + <para> + This is done by editing the <filename><replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/conf/gatein/wsrp-consumers-config.xml</filename> XML file. + </para> +  <note> + <title>XML Elements</title> + <para> + An XML Schema defining which elements are available to configure Consumers via XML can be found in <filename><replaceable>WSRP_PATH</replaceable>/lib/wsrp-integration-api-<replaceable>WSRP_VERSION</replaceable>.jar/xsd/gatein_wsrp_consumer_1_0.xsd </filename> + </para> + + </note> +  <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Using_XML-The_Consumer_Configuration_file"> + <title>The Consumer Configuration file</title> + <para> + It is important to understand how the XML Consumers configuration file is processed. It is read the first time the WSRP service starts and the associated information is then put under control of the JCR (Java Content Repository). + </para> + + </formalpara> + <para> + Subsequent launches of the WSRP service will use the JCR-stored information for all producers that are already known to JBoss Enterprise Portal Platform. More specifically, the <filename>wsrp-consumers-config.xml</filename> file is scanned for producer identifiers. Any identifier that is already known will be bypassed and the JCR information associated with this remote producer will be used. + </para> + <para> + The information defined at the XML level is only processed for producer definition for which no information is already present in the JCR. + </para> + <para> + Therefore, to delete a Producer configuration, the associated information in the database must be deleted (this can be accomplished using the configuration portlet as shown in <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Configuring_a_Remote_Producer-The_Configuration_Portlet" /> ). + </para> + <para> + The associated information in <filename>wsrp-consumers-config.xml</filename> (if such information exists) must also be removed, otherwise the producer will be re-created the next time the WSRP is launched. + </para> + <section id="sect-Reference_Guide_eXo_JCR_1.14-Using_XML-Required_Configuration_Information"> + <title>Required Configuration Information</title> + <para> + The following information needs to be provided to configure access to a remote Producer: + </para> + <orderedlist> + <listitem> + <para> + An identifier must be provided for the producer being configured so that it can be referred to later. This is done in the mandatory <literal>id</literal> attribute of the <literal><wsrp-producer></literal> element. + </para> + + </listitem> + <listitem> + <para> + JBoss Enterprise Portal Platform also needs to know about the remote Producer's endpoints to be able to connect to the remote web services and perform WSRP invocations. Use the <literal><endpoint-wsdl-url></literal> element to specify the URL for the WSDL description of the remote WSRP service. + </para> + + </listitem> + + </orderedlist> + <para> + Both the <literal>id</literal> attribute and <literal><endpoint-wsdl-url></literal> elements are required for a functional remote producer configuration. + </para> + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Using_XML-Optional_Configuration"> + <title>Optional Configuration</title> + <para> + It is also possible to provide additional configuration, which, in some cases, might be important to establish a proper connection to the remote producer. + </para> + <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Optional_Configuration-Optional_Configurations"> + <title>Optional Configurations</title> + <varlistentry> + <term>Caching</term> + <listitem> + <para> + To prevent unnecessary traffic between the local consumer and the remote producer, it is possible to cache some of the information sent by the producer (such as the list of offered portlets) for a given duration. + </para> + <para> + The rate at which the information is refreshed is defined by the <literal>expiration-cache</literal> attribute of the <literal><wsrp-producer></literal> element (in seconds). + </para> + <para> + For example; providing a value of <literal>120</literal> for expiration-cache means that the producer information will not be refreshed for 2 minutes after it has been accessed. If no value is provided, JBoss Enterprise Portal Platform will always access the remote producer regardless of whether the remote information has changed or not. + </para> + <para> + Since, in most instances, the information provided by the producer does not change often, use of this caching facility to minimize bandwidth usage is recommended. + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term>WS Timeout</term> + <listitem> + <para> + It is also possible to define a timeout after which WS operations are considered as failed. This is helpful to avoid blocking the WSRP service, as it waits on a service that does not answer. + </para> + <para> + Use the <literal>ws-timeout</literal> attribute of the <literal><wsrp-producer></literal> element to specify how many milliseconds the WSRP service will wait for a response from the remote producer before timing out. + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term>Pre-registration information</term> + <listitem> + <para> + Some producers require consumers to register with them before authorizing them to access their offered portlets. If known, some registration information can be provided in the producer configuration beforehand, so that the consumer can register with the remote producer when required. + </para> + <note> + <para> + Only simple String properties are supported. It is not possible to configure complex registration data. However, this should be sufficient for most cases. + </para> + + </note> + <para> + This pre-registration configuration is done via the <literal><registration-data></literal> element. + </para> + <para> + If the remote producer does not require any registration properties, only an empty <literal><registration-data></literal> element need be provided, as JBoss Enterprise Portal Platform can generate the mandatory information. + </para> + <para> + Values for the registration properties required by the remote producer can be provided via <literal><property></literal> elements. Refer to the example below for more details. + </para> + <para> + Additionally, the default consumer name automatically provided by JBoss Enterprise Portal Platform can be overridden via the <literal><consumer-name></literal> element. When providing a consumer name, please remember that it should uniquely identify your consumer. + </para> + + </listitem> + + </varlistentry> + + </variablelist> + + </section> + + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuring_a_Remote_Producer-Examples"> + <title>Examples</title> + <para> + This is the configuration of the <literal>selfv1</literal> and <literal>selfv2</literal> consumers as found in <filename>default-wsrp.xml</filename> with a cache expiring every 500 seconds and with a 50 second timeout for web service operations: + </para> + <note> + <para> + This file contains the default configuration and should not need to be edited. If modifications are required, the recommended practice is to follow the procedure detailed in <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-The_Configuration_Portlet-Using_the_Configuration_portlet" />. + </para> + + </note> + +<programlisting language="XML" role="XML"><xi:include href="../extras/WSRP/default258.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> + <para> + This is an example of a WSRP descriptor with registration data and cache expiring every minute: + </para> + +<programlisting language="XML" role="XML"><xi:include href="../extras/WSRP/default259.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> + + </section> + + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Consuming_Remote_WSRP_Portlets-Adding_remote_portlets_to_categories"> + <title>Adding remote portlets to categories</title> + <para> + Clicking on the Portlet link in the Application Registry will now show the remote portlets in the <emphasis role="bold">REMOTE</emphasis> tab in the left column: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/remote_portlets.png" format="PNG" scale="120" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/remote_portlets.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + <para> + These portlets are available to be used as regular portlets: they can be used in categories and added to pages. Using the Import Applications functionality will also automatically import them into categories based on the keywords they define. + </para> + <para> + More specifically, to add a <emphasis>WSRP</emphasis> portlet to a category, select <literal>wsrp</literal> in the Application Type drop-down menu: + </para> + <mediaobject> + <imageobject> + <imagedata align="center" fileref="images/WSRP/remote_portlets_category.png" format="PNG" scalefit="1" valign="middle" /> + </imageobject> + + </mediaobject> + + </section> + + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Consumers_Maintenance"> + <title>Consumers Maintenance</title> + <section id="sect-Reference_Guide_eXo_JCR_1.14-Consumers_Maintenance-Modifying_a_Currently_Held_Registration"> + <title>Modifying a Currently Held Registration</title> + <section id="sect-Reference_Guide_eXo_JCR_1.14-Modifying_a_Currently_Held_Registration-Registration_Modification_for_Service_Upgrade"> + <title>Registration Modification for Service Upgrade</title> + <para> + Producers often offer several levels of service depending on consumers' subscription levels (for example). This is implemented at the WSRP level with the registration concept: producers can assert which level of service to provide to consumers based on the values of given registration properties. + </para> + <para> + There may also be cases where the registration information has changed and must be updated. For example, the producer required you to provide a valid email and the previous email address is not valid anymore and needs to be updated. + </para> + <para> + Therefore at times it may be necessary to modify the registration that sets the service agreement between a consumer and a producer. + </para> + <para> + For example; the producer requiring an email that was configured in <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Configuring_a_Remote_Producer-The_Configuration_Portlet" /> . In that case the producer was requiring registration and required a value to be provided for the <literal>email</literal> property. + </para> + <para> + To update the email address that was provided, the remote producer must be informed that some registration data has been modified. + </para> + <para> + The following procedure assumes access to the producer has been configured as previously described. + </para> + <procedure> + <step> + <para> + Go to the configuration screen for the <literal>self</literal> producer and change the value of <literal>email</literal> to <literal>foo(a)example.com</literal> instead of <literal>example(a)example.com</literal>: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/modify_reg_start.png" format="PNG" scale="100" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/modify_reg_start.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + + </step> + <step> + <para> + Click on "<emphasis role="bold">Update properties</emphasis>" to save the change. A "<emphasis role="bold">Modify registration</emphasis>" button should now appear to let you send this new data to the remote producer: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/modify_reg_modify.png" format="PNG" scale="100" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/modify_reg_modify.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + + </step> + <step> + <para> + Click on <emphasis role="bold">Modify registration</emphasis> and, if the updated registration details have been accepted by the remote producer the following should appear: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/modify_reg_end.png" format="PNG" scale="120" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/modify_reg_end.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + + </step> + + </procedure> + + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Modifying_a_Currently_Held_Registration-Registration_Modification_on_Producer_Error"> + <title>Registration Modification on Producer Error</title> + <para> + If a Producer administrator changes the requirements for registered consumers, invoking operations on the producer may fail with an <exceptionname>OperationFailedFault</exceptionname>. JBoss Enterprise Portal Platform will attempt to assist in these cases. + </para> + <para> + This section will discuss an example using the <literal>self</literal> producer. + </para> + <para> + Assuming that the registration requires a valid value for an <literal>email</literal> registration property (as has been shown) the configuration screen for this producer should show: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/config_self.png" format="PNG" scale="120" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/config_self.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + <para> + If the administrator of the producer now requires an additional value to be provided for a <literal>name</literal> registration property operations with this producer will fail. + </para> + <para> + If a registration modification is required, go to the configuration screen for this remote producer and refresh the information held by the consumer by pressing "<emphasis role="bold">Refresh & Save</emphasis>": + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/modify_reg_self.png" format="PNG" scale="120" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/modify_reg_self.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + <para> + The configuration screen now shows the currently held registration information and the expected information from the producer. + </para> + <para> + Enter a value for the <literal>name</literal> property and then click on "<emphasis role="bold">Modify registration</emphasis>". If the producer accepts the new registration data, the following screen will appear: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/modify_reg_self_end.png" format="PNG" scale="120" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/modify_reg_self_end.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + <note> + <title><emphasis role="bold">JBoss Enterprise Portal Platform &VY; and WSRP 1 Exceptions</emphasis></title> + <para> + In WSRP 1, it can be difficult to ascertain what caused an <exceptionname> OperationFailedFault </exceptionname> as it is a generic exception returned by producers during a failed method invocation. + </para> + <para> + An <exceptionname>OperationFailedFault</exceptionname> failure can be caused by several different reasons, one of them being a request to modify the registration data. + </para> + <para> + In these instances examining the log files may assist in gathering more information about the problem. + </para> + <para> + WSRP 2 introduces an exception that is specific to a request to modify registrations which reduces the ambiguity that currently exists. + </para> + + </note> + + </section> + + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Consumers_Maintenance-Consumer_Operations"> + <title>Consumer Operations</title> + <para> + Several operations are available from the consumer list view of the WSRP configuration portlet: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/consumer_operations.png" format="PNG" scale="120" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/consumer_operations.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + <para> + The available operations are: + </para> + <variablelist> + <varlistentry> + <term>Configure</term> + <listitem> + <para> + Displays the consumer details and allows user to edit them. + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term>Refresh</term> + <listitem> + <para> + Forces the consumer to retrieve the service description from the remote producer to refresh the local information (such as offered portlets, registration information). + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term>Activate/Deactivate</term> + <listitem> + <para> + Activates or deactivates a consumer, governing whether it will be available to provide portlets and receive portlet invocations. + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term>Register/De-register</term> + <listitem> + <para> + Registers or de-registers a consumer based on whether registration is required and/or acquired. + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term>Delete</term> + <listitem> + <para> + Destroys the consumer, after de-registering it if it was registered. + </para> + + </listitem> + + </varlistentry> + + </variablelist> + <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Consumer_Operations-Additional_Functionalities_in_WSRP_2.0"> + <title><emphasis role="bold">Additional Functionalities in WSRP 2.0</emphasis></title> + <para> + In addition to those listed above, the WSRP 2.0 implementation in JBoss Enterprise Portal Platform &VY; also includes the following functions: + </para> + + </formalpara> + <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Consumer_Operations-Additional_Functions"> + <title>Additional Functions:</title> + <varlistentry> + <term>Export</term> + <listitem> + <para> + Exports some or all of the consumer's portlets to be able to later import them in a different context + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term>Import</term> + <listitem> + <para> + Imports some or all of previously exported portlets. + </para> + + </listitem> + + </varlistentry> + + </variablelist> + <section id="sect-Reference_Guide_eXo_JCR_1.14-Consumer_Operations-Importing_and_Exporting_Portlets"> + <title><emphasis role="bold">Importing and Exporting Portlets</emphasis></title> + <para> + Import and export are new functionalities added in WSRP 2. + </para> + <para> + Exporting a portlet allows a consumer to get an opaque representation of the portlet which can then be use by the corresponding import operation to reconstitute it. + </para> + <para> + This is mostly used in migration scenarios during batch operations. Since JBoss Enterprise Portal Platform does not currently support automated migration of portal data, the functionality provided as part of WSRP 2 is necessarily less complete than it could be with full portal support. + </para> + <para> + The import/export implementation in JBoss Enterprise Portal Platform allows users to export portlets from a given consumer and then import them back to replace existing portlets assigned to windows on pages by the previously exported portlets. + </para> + <procedure> + <title></title> + <step> + <para> + Click on the "<guilabel>Export</guilabel>" action for a given consumer to display the list of portlets currently made available by this specific consumer. An example list is shown below: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/export_portlet_list.png" format="PNG" scale="120" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="150mm" fileref="images/WSRP/export_portlet_list.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + + </step> + <step> + <para> + Once portlets have been selected, they can be exported by clicking on the "<guilabel>Export</guilabel>" button. This makes them available for later import: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/export_done.png" format="PNG" scale="120" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="150mm" fileref="images/WSRP/export_done.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + + </step> + <step> + <para> + The portlets can be re-imported directly by pressing the "<guilabel>Use for import</guilabel>" button or, on the Consumers list page, using the "<guilabel>Import</guilabel>" action for a given consumer. + </para> + <para> + The example below assumes that the second option has been used and that several sets of previously exported portlets are available to import from. After clicking the action link, a screen similar to the one below should appear: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/export_list.png" format="PNG" scale="120" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="150mm" fileref="images/WSRP/export_list.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + <para> + This screen presents the list of available exports with available operations for each. + </para> + <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Importing_and_Exporting_Portlets-Operations"> + <title>Operations:</title> + <varlistentry> + <term>View</term> + <listitem> + <para> + Displays the export details as previously seen when the export was first performed. + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term>Delete</term> + <listitem> + <para> + Deletes the selected export, asking you for confirmation first. + </para> + + </listitem> + + </varlistentry> + <varlistentry> + <term>Use for import</term> + <listitem> + <para> + Selects the export to import portlets from. + </para> + + </listitem> + + </varlistentry> + + </variablelist> + + </step> + <step> + <para> + Once you have selected an export to import from, you will see a screen similar to the one below: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/import_start.png" format="PNG" scale="120" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="150mm" fileref="images/WSRP/import_start.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + <para> + The screen displays the list of available exported portlets for the previously selected export. You can select which portlet you want to import by checking the checkbox next to its name. + </para> + + </step> + <step> + <para> + Select the content of which window the imported portlet will replace. This process is done in three steps: + </para> + <para> + This example assumes that you have the following page called <literal>page1</literal> which contains two windows called <literal>NetUnity WSRP 2 Interop - Cache Markup (remote)</literal> and <literal>/samples-remotecontroller-portlet.RemoteControl (remote)</literal>, as shown below: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/import_original_page.png" format="PNG" scale="120" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="150mm" fileref="images/WSRP/import_original_page.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + <para> + In this example, we want to replace the content of the <literal>/samples-remotecontroller-portlet.RemoteControl (remote)</literal> with the content of the <literal>/ajaxPortlet.JSFAJAXPortlet</literal> portlet that was previously exported. + </para> + <procedure> + <title></title> + <step> + <para> + Check the box next to the <literal>/ajaxPortlet.JSFAJAXPortlet</literal> portlet name to indicate that you want to import its data. + </para> + + </step> + <step> + <para> + Select <literal>page1</literal> in the list of available pages. The screen will then refresh to display the list of available windows on that page, similar to the image below: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/import_selected_page.png" format="PNG" scale="120" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="150mm" fileref="images/WSRP/import_selected_page.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + <note> + <title>Note</title> + <para> + At this point, you still need to select which window content you want to replace before being able to complete the import operation + </para> + + </note> + + </step> + <step> + <para> + Select the <literal>/samples-remotecontroller-portlet.RemoteControl (remote)</literal> window, which enables the "<guilabel>Import</guilabel>" button. This indicates that all the necessary data to perform the import is available. + </para> + + </step> + <step> + <para> + Click the "<guilabel>Import</guilabel>" button. A screen similar to the one below will appear: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/import_success.png" format="PNG" scale="120" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="150mm" fileref="images/WSRP/import_success.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + + </step> + + </procedure> + + + </step> + <step> + <para> + The <literal>page1</literal> page should now show that the content of <literal>/samples-remotecontroller-portlet.RemoteControl (remote)</literal> window has been replaced by the content of the <literal>/ajaxPortlet.JSFAJAXPortlet</literal> imported portlet and that the window has been renamed appropriately. + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/import_modified_page.png" format="PNG" scale="120" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="150mm" fileref="images/WSRP/import_modified_page.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + + </step> + + </procedure> + + + </section> + + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Consumers_Maintenance-Erasing_Local_Registration_Data"> + <title>Erasing Local Registration Data</title> + <para> + In rare cases, it may be necessary to erase the local data without being able to de-register first. + </para> + <para> + This can occur when a consumer is registered with a producer that has been modified by its administrator to not require registration any longer. + </para> + <para> + In this scenario, local registration information can be erased from the consumer to allow it to resume interacting with the remote producer. + </para> + <para> + To do this click on the "<emphasis role="bold">Erase local registration</emphasis>" button next to the registration context information on the consumer configuration screen: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/erase_registration.png" format="PNG" scale="80" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/erase_registration.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + <warning> + <para> + This operation is dangerous as it can result in inability to interact with the remote producer if invoked when not required. The warning message below will be displayed before any data is erased. + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/erase_registration_warning.png" format="PNG" scale="100" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/erase_registration_warning.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + + </warning> + + </section> + + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Configuring_the_WSRP_Producer"> + <title>Configuring the WSRP Producer</title> + <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuring_the_WSRP_Producer-Overview"> + <title>Overview</title> + <para> + The behavior of the Portal's WSRP Producer can be configured using the WSRP administration interface, (this is the recommended method), or by editing the <filename><replaceable>WSRP_PATH</replaceable>/lib/gatein.portal.component.wsrp-<replaceable><VERSION></replaceable>-epp-GA.jar/conf/wsrp-producer-config.xml</filename> file. + </para> + <para> + Several aspects can be modified with respect to whether registration is required for consumers to access the Producer's services. An XML Schema for the configuration format is available at <filename><replaceable>WSRP_PATH</replaceable>/lib/wsrp-integration-api-<replaceable>WSRP_VERSION</replaceable>.jar/xsd/gatein_wsrp_producer_1_0.xsd </filename>. + </para> + <para> + An alternative to editing the default <filename>wsrp-producer-config.xml</filename> file is to make a custom copy containing the required configuration options. + </para> + <para> + If a copy is used in place of the original, however, the <filename><replaceable>WSRP_PATH</replaceable>/02portal.war/WEB-INF/conf/wsrp/wsrp-configuration.xml</filename> <emphasis role="bold">must</emphasis> be updated to reference the custom file (this file defines the component <literal>WSRPServiceIntegration</literal> and contains a producer and consumer configuration location). + </para> + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuring_the_WSRP_Producer-Default_Configuration"> + <title>Default Configuration</title> + <para> + The default producer configuration requires that consumers register with it before providing access to its services. However it does not require any specific registration properties (excepting those mandated by the WSRP standard). + </para> + <para> + It does, however, require consumers to be registered before sending them a full service description. This means that the WSRP producer will not provide the list of offered portlets and other capabilities to unregistered consumers. + </para> + <para> + The producer also uses the default <classname>RegistrationPolicy</classname> paired with the default <classname>RegistrationPropertyValidator</classname>. + </para> + <para> + This allows users to customize how Portal's WSRP Producer decides whether a given registration property is valid or not (however property validators are discussed in greater detail in <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Configuring_the_WSRP_Producer-Registration_Configuration" /> ). + </para> + <para> + JBoss Enterprise Portal Platform provides a web interface to configure the producer's behavior. It can be accessed by clicking on the "<emphasis role="bold">Producer Configuration</emphasis>" tab of the "<emphasis role="bold">WSRP</emphasis>" page of the "<emphasis role="bold">admin</emphasis>" portal. + </para> + <para> + The default configuration should show: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/producer_default.png" format="PNG" scale="110" width="444" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/producer_default.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + <para> + You can specify whether or not the producer will send the full service description to unregistered consumers, and, if it requires registration, which <literal>RegistrationPolicy</literal> to use (and, if needed, which <literal>RegistrationPropertyValidator</literal>), along with required registration property description for which consumers must provide acceptable values to successfully register. + </para> + <para> + WSDL URLs to access JBoss Enterprise Portal Platform's WSRP producer are now displayed in either in WSRP 1 or WSRP 2 mode. + </para> + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuring_the_WSRP_Producer-Registration_Configuration"> + <title>Registration Configuration</title> + <para> + In order to have consumers register with Portal's producer the Portal's behavior with respect to registration must be configured. + </para> + <para> + Registration is optional, as are registration properties. The producer can require registration without requiring consumers to pass any registration properties as is the case in the default configuration. + </para> + <para> + The following section discusses configuring a producer's registration behavior from a blank state: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/producer_blank.png" format="PNG" width="700" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/producer_blank.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + <procedure> + <step> + <para> + To allow unregistered consumers to see the list of offered portlets, leave the first checkbox ("<emphasis role="bold">Access to full service description requires consumers to be registered.</emphasis>") unchecked. + </para> + + </step> + <step> + <para> + To specify, however, that consumers will need to be registered to be able to interact with the producer, check the second box ("<emphasis role="bold">Requires registration. Modifying this information will trigger invalidation of consumer registrations."</emphasis>). + </para> + <para> + The screen will refresh and display: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/producer_registration.png" format="PNG" width="700" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/producer_registration.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + + </step> + <step> + <para> + The fully-qualified name for the <classname>RegistrationPolicy</classname> and <classname>RegistrationPropertyValidator</classname> can be specified here. The default values are acceptable. Refer to <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Registration_Configuration-Customization_of_Registration_Handling_Behavior" /> for more information. + </para> + + </step> + <step> + <para> + To add a registration property called <literal>email</literal> click "<emphasis role="bold">Add property</emphasis>" and enter the appropriate information in the fields, providing a description for the registration property that can be used by consumers to determine its purpose: + </para> + <mediaobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/WSRP/producer_email.png" format="PNG" width="700" /> + </imageobject> + <imageobject role="fo"> + <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/producer_email.png" format="PNG" width="444" /> + </imageobject> + + </mediaobject> + + </step> + <step> + <para> + Press "Save" to record the modifications. + </para> + + </step> + + </procedure> + + <note> + <para> + At this time, only String (<literal>xsd:string</literal>) properties are supported. + </para> + + </note> + <note> + <para> + If consumers are already registered with the producer, modifying the configuration of required registration information will trigger the invalidation of held registrations, requiring consumers to modify their registration before being able to access the producer again. The consumer side of that process is documented in <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Modifying_a_Currently_Held_Registration-Registration_Modification_on_Producer_Error" />. + </para> + + </note> + <section id="sect-Reference_Guide_eXo_JCR_1.14-Registration_Configuration-Customization_of_Registration_Handling_Behavior"> + <title>Customization of Registration Handling Behavior</title> + <para> + Registration handling behavior can be customized by users to suit their Producer needs. This is done with an implementation of the <classname>RegistrationPolicy</classname> interface. + </para> + <para> + This interface defines methods that are called by Portal's Registration service so that decisions can be made appropriately. A default registration policy that provides basic behavior is provided and should be enough for most user needs. + </para> + <para> + While the default registration policy provides default behavior for most registration-related aspects, one aspect requires specific configuration: whether a given value for a registration property is acceptable by the WSRP Producer. + </para> + <para> + This is done by plugging a <classname>RegistrationPropertyValidator</classname> into the default registration policy. This allows users to define their own validation mechanism. + </para> + <para> + Refer to the <trademark class="trade">Javadoc</trademark> for <classname>org.gatein.registration.RegistrationPolicy</classname> and <classname>org.gatein.registration.policies.RegistrationPropertyValidator</classname> for more details on what is expected of each method. + </para> + <para> + A defined registration policy is required for the producer to be correctly configured. Do this by specifying the qualified class name of the registration policy. + </para> + <para> + As it is anticipated that most users will use the default registration policy, it is possible to provide the class name of a custom property validator instead to customize the default registration policy behavior. Note that property validators are only used by the default policy. + </para> + <note> + <para> + Since the policy or the validator are defined via their class name and dynamically loaded, it is important to ensure that the identified class is available to the application server. + </para> + <para> + One way to accomplish that is to deploy the policy implementation as a JAR file in the AS instance deploy directory. + </para> + <para> + Note also that, since both policies and validators are dynamically instantiated, they must provide a default, no-argument constructor. + </para> + + </note> + + </section> + + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuring_the_WSRP_Producer-WSRP_Validation_Mode"> + <title>WSRP Validation Mode</title> + <para> + The lack of conformance kit and the wording of the WSRP specification leaves room for differing interpretations, resulting in interoperability issues. It is therefore possible to encounter issues when using consumers from different vendors. + </para> + <para> + Experience of these issues has produced a way to relax the validation that the WSRP producer performs on the data provided by consumers to help with interoperability by accepting data that would normally be invalid. + </para> + <para> + Note that the our validation algorithm is only relaxed on aspects of the specification that are deemed harmless such as invalid language codes. + </para> + <para> + By default, the WSRP producer is configured in strict mode. If you experience issues with a given consumer, you may attempt to relax the validation mode. Un-checking the "Use strict WSRP compliance" checkbox on the Producer configuration screen to do this. + </para> + + </section> + + + </section> + + <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Removing_WSRP"> + <title>Removing WSRP</title> + <para> + If you are not going to use WSRP in your JBoss Enterprise Portal Platform instance, the WSRP configuration files may be left in place. They will not adversely affect your installation. + </para> + <para> + However, if you wish to completely remove WSRP from your portal installation, remove the <filename>gatein-wsrp-integration.ear</filename> file from your application server deploy directory. + </para> +  + </section> + + +</chapter> + Deleted: epp/docs/branches/5.2/Reference_Guide/en-US/modules/WSRP.xml =================================================================== --- epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/WSRP.xml 2011-11-24 17:26:22 UTC (rev 8138) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/WSRP.xml 2011-11-25 00:48:53 UTC (rev 8141) @@ -1,2003 +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 "Reference_Guide_eXo_JCR_1.14.ent"> -%BOOK_ENTITIES; -]> -<chapter id="chap-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP"> - <title>Web Services for Remote Portlets (WSRP)</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Introduction"> - <title>Introduction</title> - <para> - The Web Services for Remote Portlets (WSRP) specification defines a web service interface for accessing and interacting with interactive presentation-oriented web services. - </para> - <para> - It has been produced through the efforts of the Web Services for Remote Portlets (WSRP) OASIS Technical Committee. It is based on the requirements gathered and the proposals made to the committee. - </para> - <para> - Scenarios that motivate WSRP functionality include: - </para> - <itemizedlist> - <listitem> - <para> - Content hosts, such as portal servers, providing Portlets as presentation-oriented web services that can be used by aggregation engines. - </para> - - </listitem> - <listitem> - <para> - Aggregating frameworks, including portal servers, consuming presentation-oriented web services offered by content providers and integrating them into the framework. - </para> - - </listitem> - - </itemizedlist> - <para> - More information on WSRP can be found on the official <ulink url="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsrp">website</ulink>. We suggest reading the <ulink url="http://www.oasis-open.org/committees/download.php/10539/wsrp-primer-1.0.html">primer</ulink> for a good, albeit technical, overview of WSRP. - </para> - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Level_of_Support"> - <title>Level of Support</title> - <para> - The WSRP Technical Committee defined <ulink url="http://www.oasis-open.org/committees/download.php/3073">WSRP Use Profiles</ulink> to help with WSRP interoperability. Terms defined in that document will be used in this section. - </para> - <para> - JBoss Enterprise Portal Platform provides a <emphasis>Simple</emphasis> level of support for the WSRP Producer, with the exception of out-of-band registration. In-band registration and persistent local state (which are defined at the <emphasis>Complex</emphasis> level) are supported. - </para> - <para> - JBoss Enterprise Portal Platform provides a <emphasis>Medium</emphasis> level of support for the Consumer, excepting HTML markup (as JBoss Enterprise Portal Platform itself does not handle other markup types). Explicit portlet cloning and the <literal>PortletManagement</literal> interface are supported. - </para> - <para> - The WSRP component has Level 1 Producer and Consumer caching. Cookie handling is supported properly on the Consumer. The Producer requires cookie initialization (as this improves interoperability with some consumers). - </para> - <para> - JBoss Enterprise Portal Platform does not support custom window states or modes, therefore neither does the WSRP component. It does, however, support CSS on both the Producer (although this is more a function of the portlets than an inherent Producer capability) and Consumer. - </para> - <para> - JBoss Enterprise Portal Platform &VY; includes implementations of WSRP 1.0 and 2.0. - </para> - <para> - All optional features in WSRP 2 are implemented in JBoss Enterprise Portal Platform &VY; except support for lifetimes and leasing support. - </para> - <note> - <para> - As of version &VZ; of Enterprise Portal Platform, WSRP is only activated and supported when deployed on JBoss Enterprise Application Server. - </para> - - </note> - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Deploying_WSRP"> - <title>Deploying WSRP</title> - <note> - <title>Notational Devices</title> - <para> - The following list of support files uses the following notational devices: - </para> - <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Deploying_WSRP-Notations"> - <title>Notations:</title> - <varlistentry> - <term><replaceable>JBOSS_HOME</replaceable></term> - <listitem> - <para> - <replaceable>JBOSS_HOME</replaceable> refers to the directory that your instance of JBoss Enterprise Portal Platform has been extracted/installed to. For example: <filename>/home/<replaceable>USERNAME</replaceable>/jboss-epp-<replaceable><VERSION></replaceable>/</filename> - </para> - - </listitem> - - </varlistentry> - <varlistentry> - <term><replaceable>WSRP_PATH</replaceable></term> - <listitem> - <para> - The WSRP files referred to in this section are found in the <filename><replaceable>JBOSS_HOME</replaceable>/jboss-as/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear</filename> directory. - </para> - <para> - For ease of reference this path will be represented by: <replaceable>WSRP_PATH</replaceable>. - </para> - - </listitem> - - </varlistentry> - <varlistentry> - <term><replaceable>WSRP_VERSION</replaceable></term> - <listitem> - <para> - <replaceable>WSRP_VERSION</replaceable> represents the version of the WSRP component in use. - </para> - - </listitem> - - </varlistentry> - <varlistentry> - <term><replaceable>PORTAL_VERSION</replaceable></term> - <listitem> - <para> - <replaceable>PORTAL_VERSION</replaceable> represents the version of JBoss Enterprise Portal Platform in use. - </para> - - </listitem> - - </varlistentry> - - </variablelist> - - </note> - <para> - Starting with version 2.1.0-GA of the component, WSRP is packaged as a JBoss Enterprise Portal Platform extension and is now self-contained in an easy to install package named <filename>gatein-wsrp-integration.ear</filename>, deployed directly in the <filename>deploy</filename> directory of your JBoss Application Server configuration directory. - </para> - <para> - The extension itself is composed of the following components: - </para> - <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Deploying_WSRP-WSRP_support_files"> - <title>WSRP support files</title> - <varlistentry> - <term><filename>META-INF/</filename></term> - <listitem> - <para> - This directory contains files necessary for EAR packaging. The only file that is of interest from a user perspective is <filename>gatein-wsse-consumer.xml</filename> which allows you to configure WS-Security support for the consumer. - </para> - <para> - Refer to <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-WSRP_and_WS_Security-WS_Security_Configuration" /> section for more details. - </para> - - </listitem> - - </varlistentry> - <varlistentry> - <term><filename>extension-component-$PORTAL_VERSION.jar</filename></term> - <listitem> - <para> - This archive which contains the components needed to integrate the WSRP component into JBoss Enterprise Portal Platform. It also includes the default configuration files for the WSRP producer and the default WSRP consumers. - </para> - - </listitem> - - </varlistentry> - <varlistentry> - <term><filename>extension-config-$PORTAL_VERSION.jar</filename></term> - <listitem> - <para> - This file contains the configuration file needed by the GateIn extension mechanism to properly register this EAR as an extension. - </para> - - </listitem> - - </varlistentry> - <varlistentry> - <term><filename>extension-war-$PORTAL_VERSION.war</filename></term> - <listitem> - <para> - This file contains the configuration files needed by the GateIn extension mechanism to properly setup the WSRP service. It includes <filename>wsrp-configuration.xml</filename> which, in particular, configures several options for the <code> WSRPServiceIntegration </code> component at the heart of the WSRP integration in JBoss Enterprise Portal Platform. - </para> - - </listitem> - - </varlistentry> - <varlistentry> - <term><filename>lib/</filename></term> - <listitem> - <para> - This directory contains the different libraries needed by the WSRP service. - </para> - - </listitem> - - </varlistentry> - <varlistentry> - <term><filename>wsrp-admin-gui-$WSRP_VERSION.war</filename></term> - <listitem> - <para> - This file contains the WSRP Configuration portlet with which you can configure consumers to access remote servers and how the WSRP producer is configured. - </para> - - </listitem> - - </varlistentry> - <varlistentry> - <term><filename>wsrp-producer-jb5wsss-$WSRP_VERSION.war</filename></term> - <listitem> - <para> - This file contains the producer-side support for WS-Security. The only file of interest from a user perspective is <filename>gatein-wsse-producer.xml</filename> which allows you to configure WS-Security support for the producer. - </para> - <para> - Refer to <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-WSRP_and_WS_Security-WS_Security_Configuration" /> for more details. - </para> - - </listitem> - - </varlistentry> - - </variablelist> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Deploying_WSRP-Non_default_Ports_or_Hostnames"> - <title>Non-default Ports or Hostnames</title> - <para> - JBoss WS (the web service stack that JBoss Enterprise Portal Platform uses) should update the port and host name used in WSDL. Refer to the JBoss WS <ulink url="http://community.jboss.org/wiki/JBossWS-UserGuide#Configuration">user guide</ulink> for more information. - </para> - <para> - If the host name and port on which the server runs have been modified, the configuration for the Consumer used to consume JBoss Enterprise Portal Platform's "self" Producer will need to be updated. Refer to <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Consuming_Remote_WSRP_Portlets" /> for directions on how to do this. - </para> - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Deploying_WSRP-Using_WSRP_with_SSL"> - <title>Using WSRP with SSL</title> - <para> - It is possible to use WSRP over SSL for secure exchange of data. Refer to these <ulink url="http://community.jboss.org/wiki/ConfiguringWSRPforuseoverSSL">instructions</ulink> for how to do this. - </para> - - </section> - - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-WSRP_and_WS_Security"> - <title>WSRP and WS-Security</title> - <para> - Portlets may present different data or options depending on the currently authenticated user. For remote portlets, this means having to propagate the user credentials from the consumer back to the producer in a safe and secure manner. - </para> - <para> - The WSRP specification does not directly specify how this should be accomplished, but delegates this work to the existing WS-Security standards. - </para> - <note> - <title>Web Container Compatibility</title> - <para> - WSRP and WS-Security is currently only supported on JBoss Enterprise Portal Platform when running on top of JBoss AS 5. - </para> - - </note> - <warning> - <title>Encryption</title> - <para> - <emphasis role="bold">The use of encryption is strongly recommended.</emphasis> - </para> - <para> - Credentials being sent between the consumer and producer should be encrypted or they will be sent in plain text and could be easily intercepted. - </para> - <para> - You can either configure WS-Security to encrypt and sign the SOAP messages being sent, or secure the transport layer by using an <literal>https</literal> endpoint. - </para> - <para> - Failure to encrypt the SOAP message or transport layer will result in the username and password being sent in plain text. - </para> - - </warning> - <important> - <title>Credentials</title> - <para> - When the consumer sends the user credentials to the producer, it is sending the credentials for the currently authenticated user in the consumer. This makes signing in to remote portlets transparent to end users, but also requires that the producer and consumer use the same credentials. - </para> - <para> - The username and password must be the same and valid on both servers. - </para> - <para> - The recommended approach for this situation would be to use a common LDAP configuration. Please see the User Guide at <ulink type="http" url="docs.redhat.com" /> for information on how to configure LDAP for use with JBoss Enterprise Portal Platform - </para> - - </important> - <para> - This community Wiki <ulink url="http://community.jboss.org/wiki/GateInWSRPAndWebServiceSecurity">article</ulink>, also provides a step-by-step example on how to configure WSRP with WS-Security. - </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-WSRP_and_WS_Security-WS_Security_Configuration"> - <title>WS-Security Configuration</title> - <para> - JBoss Enterprise Portal Platform uses <application>JBossWS Native</application> to handle ws-security. - </para> - <para> - Refer to the WS-Security section of the <ulink url="http://www.jboss.org/jbossas/docs/5-x">JBoss AS 5 Administration and Configuration Guide </ulink> for in-depth configuration options. - </para> - <para> - 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. - </para> - <para> - The following are the JBossWS Native configuration files which need to be configure for WSRP: - </para> - <variablelist> - <title></title> - <varlistentry> - <term>gatein-wsrp-integration.ear/META-INF/gatein-wsse-consumer.xml</term> - <listitem> - <para> - BossWS configuration file for the consumer. - </para> - - </listitem> - - </varlistentry> - <varlistentry> - <term>gatein-wsrp-integration.ear/wsrp-producer-jb5wss.war/WEB-INF/conf/gatein-wsse-producer.xml</term> - <listitem> - <para> - JBossWS configuration file for the producer. - </para> - - </listitem> - - </varlistentry> - - </variablelist> - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-WSRP_and_WS_Security-WS_Security_Producer_Configuration"> - <title>WS-Security Producer Configuration</title> - <para> - Other than the JBossWS configuration file mention above, no other configuration changes should be necessary for the producer. - </para> - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-WSRP_and_WS_Security-WS_Security_Consumer_Configuration"> - <title>WS-Security Consumer Configuration</title> - <para> - The consumer requires some changes before it will function properly with WS-Security. - </para> - <para> - The consumer needs access to the current servlet request since this is used to retrieve the currently authenticated user. In order to access this information, the consumer needs a special servlet-filter added to the portal. - </para> - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-WS_Security_Consumer_Configuration-Add_the_servlet_filter"> - <title>Add the servlet-filter</title> - <step> - <para> - Open <filename><replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/deploy/gatein.ear/02portal.war/WEB-INF/web.xml</filename> and add the following: - </para> - -<programlisting role="XML"> - <filter> - <filter-name>ServletAccessFilter</filter-name> - <filter-class>org.gatein.wsrp.servlet.ServletAccessFilter</filter-class> - </filter> - <filter-mapping> - <filter-name>ServletAccessFilter</filter-name> - <url-pattern>/*</url-pattern> - </filter-mapping> -</programlisting> - - </step> - <step> - <para> - Check the <guilabel>Enable WS Security</guilabel> checkbox in the consumer configuration options of the WSRP Configuration portlet - </para> - <mediaobject> - <imageobject> - <imagedata align="center" fileref="images/WSRP/config_wss_selected.png" format="PNG" scalefit="1" valign="middle" width="444" /> - </imageobject> - - </mediaobject> - </step> - </procedure> - - - </section> - - <section> - <title>WS-Security Consumer Checklist</title> - <para> - In order for the consumer to handle ws-security, the following items must be implemented: - </para> - <orderedlist> - <listitem> - <para> - The JBossWS configuration files must be configured - </para> - - </listitem> - <listitem> - <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> - - </listitem> - - </orderedlist> - <para> - The consumer will not properly handle ws-security unless all three items are correctly configured. - </para> - - </section> - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Making_a_Portlet_Remotable"> - <title>Making a Portlet Remotable</title> - <note> - <para> - Only JSR-286 (Portlet 2.0) portlets can be made remotable as the mechanism to expose a portlet to WSRP relies on a JSR-286-only functionality. - </para> - - </note> - <para> - JBoss Enterprise Portal Platform does <emphasis role="bold">not</emphasis>, by default, expose local portlets for consumption by remote WSRP consumers. - </para> - <para> - In order to make a portlet remotely available, it must be made "remotable" by marking it as such in the associated <filename>portlet.xml</filename>. - </para> - <para> - A specific <code>org.gatein.pc.remotable container-runtime-option</code> is used to accomplish this. Setting its value to <code>true</code> makes the portlet available for remote consumption, while setting its value to <code>false</code> will not publish it remotely. - </para> - <para> - As specifying the remotable status for a portlet is optional, nothing need be done if portlets do not need to be remotely available. - </para> - <para> - In the following example, the "BasicPortlet" portlet is specified as being remotable. - </para> - -<programlisting language="XML" role="XML"><xi:include href="../extras/WSRP/default255.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - <para> - It is also possible to specify that all the portlets declared within a given portlet application be remotable by default. - </para> - <para> - 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. - </para> - <para> - For example: - </para> - -<programlisting language="XML" role="XML"><xi:include href="../extras/WSRP/default256.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - <para> - This example defines two portlets. As the <code>org.gatein.pc.remotable container-runtime-option</code> is 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. - </para> - <para> - It is possible to override this 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. - </para> - <para> - In the example above, the <literal>RemotelyExposedPortlet</literal> 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>. - </para> - <para> - The <literal>NotRemotelyExposedPortlet</literal>, however, overrides the default behavior and is not remotely exposed. - </para> - <note> - <title>Note</title> - <para> - Portlets are not remotely exposed if no top-level <code>org.gatein.pc.remotable container-runtime-option</code> value is set to <code>true</code>. - </para> - - </note> - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Consuming_WSRP_portlets_from_a_remote_Consumer"> - <title>Consuming WSRP portlets from a remote Consumer</title> - <para> - Configuration is extremely variable between different WSRP Consumers. Most, however, require a specification of the URL for the Producer's WSDL definition. If the JBoss Enterprise Portal Platform Consumer is not being used, refer to the documentation for the Consumer that is in use for specific instructions. - </para> - <para> - For instructions on how to specify this URL in JBoss Enterprise Portal Platform, refer to <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Consuming_Remote_WSRP_Portlets" />. - </para> - <para> - JBoss Enterprise Portal Platform's Producer is automatically set up when a portal instance is deployed with the WSRP service. - </para> - <para> - The WSDL file can be accessed at: - </para> - <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Consuming_WSRP_portlets_from_a_remote_Consumer-File_paths"> - <title>File paths:</title> - <varlistentry> - <term>WSRP 1.0:</term> - <listitem> - <para> - <filename>http://<replaceable>{hostname}</replaceable>:<replaceable>{port}</replaceable>/wsrp-producer/v1/MarkupService?wsdl</filename>. - </para> - - </listitem> - - </varlistentry> - <varlistentry> - <term>WSRP 2.0:</term> - <listitem> - <para> - <filename>http://<replaceable>{hostname}</replaceable>:<replaceable>{port}</replaceable>/wsrp-producer/v2/MarkupService?wsdl</filename>. - </para> - - </listitem> - - </varlistentry> - - </variablelist> - <para> - The default hostname is <literal>localhost</literal> and the default port is <literal>8080</literal>. - </para> - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Consuming_Remote_WSRP_Portlets"> - <title>Consuming Remote WSRP Portlets</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Consuming_Remote_WSRP_Portlets-Overview"> - <title>Overview</title> - <para> - To be able to consume WSRP portlets exposed by a remote producer, JBoss Enterprise Portal Platform's WSRP consumer must be configured to access that remote producer. - </para> - <para> - Access to a remote producer can be configured using the provided configuration portlet. Alternatively, it is also possible to configure access to remote producers using an XML descriptor. The configuration portlet is the recommended method. - </para> - <para> - Once a remote producer has been configured, the portlets that it exposes are then available in the Application Registry to be added to categories and then to pages. - </para> -  - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Consuming_Remote_WSRP_Portlets-Configuring_a_Remote_Producer"> - <title>Configuring a Remote Producer</title> - <para> - Access to a remote producer needs to be defined so that portlets can be consumed within JBoss Enterprise Portal Platform. This section will show how to configure access to <emphasis role="bold">NetUnity</emphasis>'s public WSRP producer. - </para> - <para> - Firstly using the configuration portlet and then how the same result can be accomplished with a producer descriptor, though it is far easier to do so via the configuration portlet. - </para> - <important> - <title>Chunked Encoding</title> - <para> - Some WSRP producers, such as Oracle, do not support chunked encoding. If your producer does not support chunked encoding, it will not be able to properly connect to the producer. - </para> - <para> - This will manifest itself with the following error: - </para> - -<screen>Caused by: org.jboss.ws.WSException: Invalid HTTP server response [503] - Service Unavailable. -</screen> - <para> - A workaround for this issue involves editing the <parameter>chunksize</parameter> setting in the <filename>standard-jaxws-client-config.xml</filename> file. - </para> - <para> - Refer to <ulink type="http" url="http://community.jboss.org/wiki/Workaroundwhenchunkedencodingisnotsupported">http://community.jboss.org/wiki/Workaroundwhenchunkedencodingisnotsupported</ulink> for more information. - </para> - - </important> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuring_a_Remote_Producer-The_Configuration_Portlet"> - <title>The Configuration Portlet</title> - <para> - JBoss Enterprise Portal Platform provides a graphical portlet to assist with configuring access to, and other facets of, remote WSRP Producers. - </para> - <para> - It is available at: <ulink type="http" url="http://localhost:8080/portal/login?initialURI=%2Fportal%2Fprivate%2Fclass..." />. - </para> - <para> - The portlet also is a group page for /platform/administrators - </para> - <para> - Although the Configuration Portlet is installed by default in JBoss Enterprise Portal Platform &VY;., installation instructions are included below should the portlet ever need to be re-installed: - </para> - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-The_Configuration_Portlet-Installing_the_configuration_portlet"> - <title><emphasis role="bold">Installing the configuration portlet:</emphasis></title> - <step> - <para> - Log into the portal as an administrator and go to the Application Registry (Click <ulink url="http://localhost:8080/portal/private/classic/administration/registry">http://localhost:8080/portal/private/classic/administration/registry</ulink> if using the default installation). - </para> - - </step> - <step> - <para> - Add the WSRP Configuration portlet to the Administration category. If the Import Applications functionality is used, the WSRP Configuration portlet will be automatically added to the Administration category. - </para> - - </step> - <step> - <para> - Once the portlet is added to a category, it can be added to a page and used. It is recommended that it be added to the same page as the Application Registry (as other operations relating to WSRP and adding portlets to categories are somewhat related). Add the WSRP Configuration portlet to the page using the standard procedure. - </para> - - </step> - - </procedure> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-The_Configuration_Portlet-Using_the_Configuration_portlet"> - <title><emphasis role="bold">Using the Configuration portlet</emphasis></title> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/config_init.png" format="PNG" scale="120" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/config_init.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - <para> - This screen presents all the configured consumers associated with their status and possible actions on them. - </para> - <para> - A Consumer can be active or inactive. Activating a Consumer means that it is ready to act as a portlet provider. - </para> - <para> - Note also that a Consumer can be marked as requiring <emphasis>refresh</emphasis>, which means that the information held about it might not be up to date. Refreshing it from the remote Producer will update this information. - </para> - <para> - This can happen for several reasons: the service description for that remote Producer has not been fetched yet, the cached version has expired or modifications have been made to the configuration that could potentially invalidate it, thus requiring re-validation of the information. - </para> - <para> - To create a new Consumer: - </para> - <procedure id="proc-Reference_Guide_eXo_JCR_1.14-Using_the_Configuration_portlet-Creating_a_Consumer"> - <title><emphasis role="bold">Creating a Consumer</emphasis></title> - <step> - <para> - Type "<literal>netunity</literal>" into the "<emphasis role="bold">Create a consumer named:</emphasis>" field. - </para> - - </step> - <step> - <para> - Click on "<emphasis role="bold">Create consumer</emphasis>" to create a new Consumer called <literal>netunity</literal>. - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/config_create.png" format="PNG" scale="100" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/config_create.png" format="PNG" /> - </imageobject> - - </mediaobject> - - </step> - <step> - <para> - In the next form, set the cache expiration value to <parameter>300</parameter> seconds. - </para> - - </step> - <step> - <para> - Leave the default timeout value for web services (WS) operations. - </para> - - </step> - <step> - <para> - Enter the WSDL URL for the producer in the text field. - </para> - - </step> - <step> - <para> - Press the "Refresh & Save" button: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/config_wsdl.png" format="PNG" scale="120" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/config_wsdl.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - - </step> - - </procedure> - - <para> - This will retrieve the service description associated with the Producer which WSRP interface is described by the WSDL file found at the URL entered. - </para> - <para> - In this case, querying the service description will show that the Producer requires registration, that it requested three registration properties and that the current configuration is missing values for these properties: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/config_missing.png" format="PNG" scale="120" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/config_missing.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - <para> - This particular producer requests simple <literal>Yes</literal> or <literal>No</literal> values for the three registration properties. - </para> - <para> - Enter <literal>No</literal>, <literal>Yes</literal> and <literal>No</literal> (in that order) for the values and then pressing the "Refresh & Save" button should result in: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/config_end.png" format="PNG" scale="120" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/config_end.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - <note> - <title>Values</title> - <para> - Unfortunately there is no automated way to learn about which possible values (if any) are expected by the remote Producer. Possible values may be indicated in the registration property description but this is not always the case. Refer to the specific Producer's documentation. - </para> - - </note> - <para> - The Consumer for the <literal>netunity</literal> Producer should now be available as a portlet provider and be ready to be used. - </para> - <para> - If the producer had required registration but did not 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), the following screen would have appeared after pressing the "Refresh & Save" button: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/config_refresh.png" format="PNG" scale="120" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/config_refresh.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - - </section> - - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuring_a_Remote_Producer-Using_XML"> - <title>Using XML</title> - <para> - Although using the WSRP Configuration portlet to configure Consumers is recommended, the WSRP component provides an alternative way to configure consumers. - </para> - <para> - This is done by editing the <filename><replaceable><JBOSS_HOME></replaceable>/server/<replaceable><PROFILE></replaceable>/conf/gatein/wsrp-consumers-config.xml</filename> XML file. - </para> -  <note> - <title>XML Elements</title> - <para> - An XML Schema defining which elements are available to configure Consumers via XML can be found in <filename><replaceable>WSRP_PATH</replaceable>/lib/wsrp-integration-api-<replaceable>WSRP_VERSION</replaceable>.jar/xsd/gatein_wsrp_consumer_1_0.xsd </filename> - </para> - - </note> -  <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Using_XML-The_Consumer_Configuration_file"> - <title>The Consumer Configuration file</title> - <para> - It is important to understand how the XML Consumers configuration file is processed. It is read the first time the WSRP service starts and the associated information is then put under control of the JCR (Java Content Repository). - </para> - - </formalpara> - <para> - Subsequent launches of the WSRP service will use the JCR-stored information for all producers that are already known to JBoss Enterprise Portal Platform. More specifically, the <filename>wsrp-consumers-config.xml</filename> file is scanned for producer identifiers. Any identifier that is already known will be bypassed and the JCR information associated with this remote producer will be used. - </para> - <para> - The information defined at the XML level is only processed for producer definition for which no information is already present in the JCR. - </para> - <para> - Therefore, to delete a Producer configuration, the associated information in the database must be deleted (this can be accomplished using the configuration portlet as shown in <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Configuring_a_Remote_Producer-The_Configuration_Portlet" /> ). - </para> - <para> - The associated information in <filename>wsrp-consumers-config.xml</filename> (if such information exists) must also be removed, otherwise the producer will be re-created the next time the WSRP is launched. - </para> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Using_XML-Required_Configuration_Information"> - <title>Required Configuration Information</title> - <para> - The following information needs to be provided to configure access to a remote Producer: - </para> - <orderedlist> - <listitem> - <para> - An identifier must be provided for the producer being configured so that it can be referred to later. This is done in the mandatory <literal>id</literal> attribute of the <literal><wsrp-producer></literal> element. - </para> - - </listitem> - <listitem> - <para> - JBoss Enterprise Portal Platform also needs to know about the remote Producer's endpoints to be able to connect to the remote web services and perform WSRP invocations. Use the <literal><endpoint-wsdl-url></literal> element to specify the URL for the WSDL description of the remote WSRP service. - </para> - - </listitem> - - </orderedlist> - <para> - Both the <literal>id</literal> attribute and <literal><endpoint-wsdl-url></literal> elements are required for a functional remote producer configuration. - </para> - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Using_XML-Optional_Configuration"> - <title>Optional Configuration</title> - <para> - It is also possible to provide additional configuration, which, in some cases, might be important to establish a proper connection to the remote producer. - </para> - <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Optional_Configuration-Optional_Configurations"> - <title>Optional Configurations</title> - <varlistentry> - <term>Caching</term> - <listitem> - <para> - To prevent unnecessary traffic between the local consumer and the remote producer, it is possible to cache some of the information sent by the producer (such as the list of offered portlets) for a given duration. - </para> - <para> - The rate at which the information is refreshed is defined by the <literal>expiration-cache</literal> attribute of the <literal><wsrp-producer></literal> element (in seconds). - </para> - <para> - For example; providing a value of <literal>120</literal> for expiration-cache means that the producer information will not be refreshed for 2 minutes after it has been accessed. If no value is provided, JBoss Enterprise Portal Platform will always access the remote producer regardless of whether the remote information has changed or not. - </para> - <para> - Since, in most instances, the information provided by the producer does not change often, use of this caching facility to minimize bandwidth usage is recommended. - </para> - - </listitem> - - </varlistentry> - <varlistentry> - <term>WS Timeout</term> - <listitem> - <para> - It is also possible to define a timeout after which WS operations are considered as failed. This is helpful to avoid blocking the WSRP service, as it waits on a service that does not answer. - </para> - <para> - Use the <literal>ws-timeout</literal> attribute of the <literal><wsrp-producer></literal> element to specify how many milliseconds the WSRP service will wait for a response from the remote producer before timing out. - </para> - - </listitem> - - </varlistentry> - <varlistentry> - <term>Pre-registration information</term> - <listitem> - <para> - Some producers require consumers to register with them before authorizing them to access their offered portlets. If known, some registration information can be provided in the producer configuration beforehand, so that the consumer can register with the remote producer when required. - </para> - <note> - <para> - Only simple String properties are supported. It is not possible to configure complex registration data. However, this should be sufficient for most cases. - </para> - - </note> - <para> - This pre-registration configuration is done via the <literal><registration-data></literal> element. - </para> - <para> - If the remote producer does not require any registration properties, only an empty <literal><registration-data></literal> element need be provided, as JBoss Enterprise Portal Platform can generate the mandatory information. - </para> - <para> - Values for the registration properties required by the remote producer can be provided via <literal><property></literal> elements. Refer to the example below for more details. - </para> - <para> - Additionally, the default consumer name automatically provided by JBoss Enterprise Portal Platform can be overridden via the <literal><consumer-name></literal> element. When providing a consumer name, please remember that it should uniquely identify your consumer. - </para> - - </listitem> - - </varlistentry> - - </variablelist> - - </section> - - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuring_a_Remote_Producer-Examples"> - <title>Examples</title> - <para> - This is the configuration of the <literal>selfv1</literal> and <literal>selfv2</literal> consumers as found in <filename>default-wsrp.xml</filename> with a cache expiring every 500 seconds and with a 50 second timeout for web service operations: - </para> - <note> - <para> - This file contains the default configuration and should not need to be edited. If modifications are required, the recommended practice is to follow the procedure detailed in <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-The_Configuration_Portlet-Using_the_Configuration_portlet" />. - </para> - - </note> - -<programlisting language="XML" role="XML"><xi:include href="../extras/WSRP/default258.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - <para> - This is an example of a WSRP descriptor with registration data and cache expiring every minute: - </para> - -<programlisting language="XML" role="XML"><xi:include href="../extras/WSRP/default259.xml" parse="text" xmlns:xi="http://www.w3.org/2001/XInclude" /></programlisting> - - </section> - - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Consuming_Remote_WSRP_Portlets-Adding_remote_portlets_to_categories"> - <title>Adding remote portlets to categories</title> - <para> - Clicking on the Portlet link in the Application Registry will now show the remote portlets in the <emphasis role="bold">REMOTE</emphasis> tab in the left column: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/remote_portlets.png" format="PNG" scale="120" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/remote_portlets.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - <para> - These portlets are available to be used as regular portlets: they can be used in categories and added to pages. Using the Import Applications functionality will also automatically import them into categories based on the keywords they define. - </para> - <para> - More specifically, to add a <emphasis>WSRP</emphasis> portlet to a category, select <literal>wsrp</literal> in the Application Type drop-down menu: - </para> - <mediaobject> - <imageobject> - <imagedata align="center" fileref="images/WSRP/remote_portlets_category.png" format="PNG" scalefit="1" valign="middle" /> - </imageobject> - - </mediaobject> - - </section> - - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Consumers_Maintenance"> - <title>Consumers Maintenance</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Consumers_Maintenance-Modifying_a_Currently_Held_Registration"> - <title>Modifying a Currently Held Registration</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Modifying_a_Currently_Held_Registration-Registration_Modification_for_Service_Upgrade"> - <title>Registration Modification for Service Upgrade</title> - <para> - Producers often offer several levels of service depending on consumers' subscription levels (for example). This is implemented at the WSRP level with the registration concept: producers can assert which level of service to provide to consumers based on the values of given registration properties. - </para> - <para> - There may also be cases where the registration information has changed and must be updated. For example, the producer required you to provide a valid email and the previous email address is not valid anymore and needs to be updated. - </para> - <para> - Therefore at times it may be necessary to modify the registration that sets the service agreement between a consumer and a producer. - </para> - <para> - For example; the producer requiring an email that was configured in <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Configuring_a_Remote_Producer-The_Configuration_Portlet" /> . In that case the producer was requiring registration and required a value to be provided for the <literal>email</literal> property. - </para> - <para> - To update the email address that was provided, the remote producer must be informed that some registration data has been modified. - </para> - <para> - The following procedure assumes access to the producer has been configured as previously described. - </para> - <procedure> - <step> - <para> - Go to the configuration screen for the <literal>self</literal> producer and change the value of <literal>email</literal> to <literal>foo(a)example.com</literal> instead of <literal>example(a)example.com</literal>: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/modify_reg_start.png" format="PNG" scale="100" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/modify_reg_start.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - - </step> - <step> - <para> - Click on "<emphasis role="bold">Update properties</emphasis>" to save the change. A "<emphasis role="bold">Modify registration</emphasis>" button should now appear to let you send this new data to the remote producer: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/modify_reg_modify.png" format="PNG" scale="100" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/modify_reg_modify.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - - </step> - <step> - <para> - Click on <emphasis role="bold">Modify registration</emphasis> and, if the updated registration details have been accepted by the remote producer the following should appear: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/modify_reg_end.png" format="PNG" scale="120" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/modify_reg_end.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - - </step> - - </procedure> - - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Modifying_a_Currently_Held_Registration-Registration_Modification_on_Producer_Error"> - <title>Registration Modification on Producer Error</title> - <para> - If a Producer administrator changes the requirements for registered consumers, invoking operations on the producer may fail with an <exceptionname>OperationFailedFault</exceptionname>. JBoss Enterprise Portal Platform will attempt to assist in these cases. - </para> - <para> - This section will discuss an example using the <literal>self</literal> producer. - </para> - <para> - Assuming that the registration requires a valid value for an <literal>email</literal> registration property (as has been shown) the configuration screen for this producer should show: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/config_self.png" format="PNG" scale="120" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/config_self.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - <para> - If the administrator of the producer now requires an additional value to be provided for a <literal>name</literal> registration property operations with this producer will fail. - </para> - <para> - If a registration modification is required, go to the configuration screen for this remote producer and refresh the information held by the consumer by pressing "<emphasis role="bold">Refresh & Save</emphasis>": - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/modify_reg_self.png" format="PNG" scale="120" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/modify_reg_self.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - <para> - The configuration screen now shows the currently held registration information and the expected information from the producer. - </para> - <para> - Enter a value for the <literal>name</literal> property and then click on "<emphasis role="bold">Modify registration</emphasis>". If the producer accepts the new registration data, the following screen will appear: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/modify_reg_self_end.png" format="PNG" scale="120" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/modify_reg_self_end.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - <note> - <title><emphasis role="bold">JBoss Enterprise Portal Platform &VY; and WSRP 1 Exceptions</emphasis></title> - <para> - In WSRP 1, it can be difficult to ascertain what caused an <exceptionname> OperationFailedFault </exceptionname> as it is a generic exception returned by producers during a failed method invocation. - </para> - <para> - An <exceptionname>OperationFailedFault</exceptionname> failure can be caused by several different reasons, one of them being a request to modify the registration data. - </para> - <para> - In these instances examining the log files may assist in gathering more information about the problem. - </para> - <para> - WSRP 2 introduces an exception that is specific to a request to modify registrations which reduces the ambiguity that currently exists. - </para> - - </note> - - </section> - - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Consumers_Maintenance-Consumer_Operations"> - <title>Consumer Operations</title> - <para> - Several operations are available from the consumer list view of the WSRP configuration portlet: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/consumer_operations.png" format="PNG" scale="120" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/consumer_operations.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - <para> - The available operations are: - </para> - <variablelist> - <varlistentry> - <term>Configure</term> - <listitem> - <para> - Displays the consumer details and allows user to edit them. - </para> - - </listitem> - - </varlistentry> - <varlistentry> - <term>Refresh</term> - <listitem> - <para> - Forces the consumer to retrieve the service description from the remote producer to refresh the local information (such as offered portlets, registration information). - </para> - - </listitem> - - </varlistentry> - <varlistentry> - <term>Activate/Deactivate</term> - <listitem> - <para> - Activates or deactivates a consumer, governing whether it will be available to provide portlets and receive portlet invocations. - </para> - - </listitem> - - </varlistentry> - <varlistentry> - <term>Register/De-register</term> - <listitem> - <para> - Registers or de-registers a consumer based on whether registration is required and/or acquired. - </para> - - </listitem> - - </varlistentry> - <varlistentry> - <term>Delete</term> - <listitem> - <para> - Destroys the consumer, after de-registering it if it was registered. - </para> - - </listitem> - - </varlistentry> - - </variablelist> - <formalpara id="form-Reference_Guide_eXo_JCR_1.14-Consumer_Operations-Additional_Functionalities_in_WSRP_2.0"> - <title><emphasis role="bold">Additional Functionalities in WSRP 2.0</emphasis></title> - <para> - In addition to those listed above, the WSRP 2.0 implementation in JBoss Enterprise Portal Platform &VY; also includes the following functions: - </para> - - </formalpara> - <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Consumer_Operations-Additional_Functions"> - <title>Additional Functions:</title> - <varlistentry> - <term>Export</term> - <listitem> - <para> - Exports some or all of the consumer's portlets to be able to later import them in a different context - </para> - - </listitem> - - </varlistentry> - <varlistentry> - <term>Import</term> - <listitem> - <para> - Imports some or all of previously exported portlets. - </para> - - </listitem> - - </varlistentry> - - </variablelist> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Consumer_Operations-Importing_and_Exporting_Portlets"> - <title><emphasis role="bold">Importing and Exporting Portlets</emphasis></title> - <para> - Import and export are new functionalities added in WSRP 2. - </para> - <para> - Exporting a portlet allows a consumer to get an opaque representation of the portlet which can then be use by the corresponding import operation to reconstitute it. - </para> - <para> - This is mostly used in migration scenarios during batch operations. Since JBoss Enterprise Portal Platform does not currently support automated migration of portal data, the functionality provided as part of WSRP 2 is necessarily less complete than it could be with full portal support. - </para> - <para> - The import/export implementation in JBoss Enterprise Portal Platform allows users to export portlets from a given consumer and then import them back to replace existing portlets assigned to windows on pages by the previously exported portlets. - </para> - <procedure> - <title></title> - <step> - <para> - Click on the "<guilabel>Export</guilabel>" action for a given consumer to display the list of portlets currently made available by this specific consumer. An example list is shown below: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/export_portlet_list.png" format="PNG" scale="120" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="150mm" fileref="images/WSRP/export_portlet_list.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - - </step> - <step> - <para> - Once portlets have been selected, they can be exported by clicking on the "<guilabel>Export</guilabel>" button. This makes them available for later import: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/export_done.png" format="PNG" scale="120" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="150mm" fileref="images/WSRP/export_done.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - - </step> - <step> - <para> - The portlets can be re-imported directly by pressing the "<guilabel>Use for import</guilabel>" button or, on the Consumers list page, using the "<guilabel>Import</guilabel>" action for a given consumer. - </para> - <para> - The example below assumes that the second option has been used and that several sets of previously exported portlets are available to import from. After clicking the action link, a screen similar to the one below should appear: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/export_list.png" format="PNG" scale="120" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="150mm" fileref="images/WSRP/export_list.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - <para> - This screen presents the list of available exports with available operations for each. - </para> - <variablelist id="vari-Reference_Guide_eXo_JCR_1.14-Importing_and_Exporting_Portlets-Operations"> - <title>Operations:</title> - <varlistentry> - <term>View</term> - <listitem> - <para> - Displays the export details as previously seen when the export was first performed. - </para> - - </listitem> - - </varlistentry> - <varlistentry> - <term>Delete</term> - <listitem> - <para> - Deletes the selected export, asking you for confirmation first. - </para> - - </listitem> - - </varlistentry> - <varlistentry> - <term>Use for import</term> - <listitem> - <para> - Selects the export to import portlets from. - </para> - - </listitem> - - </varlistentry> - - </variablelist> - - </step> - <step> - <para> - Once you have selected an export to import from, you will see a screen similar to the one below: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/import_start.png" format="PNG" scale="120" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="150mm" fileref="images/WSRP/import_start.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - <para> - The screen displays the list of available exported portlets for the previously selected export. You can select which portlet you want to import by checking the checkbox next to its name. - </para> - - </step> - <step> - <para> - Select the content of which window the imported portlet will replace. This process is done in three steps: - </para> - <para> - This example assumes that you have the following page called <literal>page1</literal> which contains two windows called <literal>NetUnity WSRP 2 Interop - Cache Markup (remote)</literal> and <literal>/samples-remotecontroller-portlet.RemoteControl (remote)</literal>, as shown below: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/import_original_page.png" format="PNG" scale="120" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="150mm" fileref="images/WSRP/import_original_page.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - <para> - In this example, we want to replace the content of the <literal>/samples-remotecontroller-portlet.RemoteControl (remote)</literal> with the content of the <literal>/ajaxPortlet.JSFAJAXPortlet</literal> portlet that was previously exported. - </para> - <procedure> - <title></title> - <step> - <para> - Check the box next to the <literal>/ajaxPortlet.JSFAJAXPortlet</literal> portlet name to indicate that you want to import its data. - </para> - - </step> - <step> - <para> - Select <literal>page1</literal> in the list of available pages. The screen will then refresh to display the list of available windows on that page, similar to the image below: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/import_selected_page.png" format="PNG" scale="120" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="150mm" fileref="images/WSRP/import_selected_page.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - <note> - <title>Note</title> - <para> - At this point, you still need to select which window content you want to replace before being able to complete the import operation - </para> - - </note> - - </step> - <step> - <para> - Select the <literal>/samples-remotecontroller-portlet.RemoteControl (remote)</literal> window, which enables the "<guilabel>Import</guilabel>" button. This indicates that all the necessary data to perform the import is available. - </para> - - </step> - <step> - <para> - Click the "<guilabel>Import</guilabel>" button. A screen similar to the one below will appear: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/import_success.png" format="PNG" scale="120" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="150mm" fileref="images/WSRP/import_success.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - - </step> - - </procedure> - - - </step> - <step> - <para> - The <literal>page1</literal> page should now show that the content of <literal>/samples-remotecontroller-portlet.RemoteControl (remote)</literal> window has been replaced by the content of the <literal>/ajaxPortlet.JSFAJAXPortlet</literal> imported portlet and that the window has been renamed appropriately. - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/import_modified_page.png" format="PNG" scale="120" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="150mm" fileref="images/WSRP/import_modified_page.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - - </step> - - </procedure> - - - </section> - - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Consumers_Maintenance-Erasing_Local_Registration_Data"> - <title>Erasing Local Registration Data</title> - <para> - In rare cases, it may be necessary to erase the local data without being able to de-register first. - </para> - <para> - This can occur when a consumer is registered with a producer that has been modified by its administrator to not require registration any longer. - </para> - <para> - In this scenario, local registration information can be erased from the consumer to allow it to resume interacting with the remote producer. - </para> - <para> - To do this click on the "<emphasis role="bold">Erase local registration</emphasis>" button next to the registration context information on the consumer configuration screen: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/erase_registration.png" format="PNG" scale="80" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/erase_registration.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - <warning> - <para> - This operation is dangerous as it can result in inability to interact with the remote producer if invoked when not required. The warning message below will be displayed before any data is erased. - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/erase_registration_warning.png" format="PNG" scale="100" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/erase_registration_warning.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - - </warning> - - </section> - - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Configuring_the_WSRP_Producer"> - <title>Configuring the WSRP Producer</title> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuring_the_WSRP_Producer-Overview"> - <title>Overview</title> - <para> - The behavior of the Portal's WSRP Producer can be configured using the WSRP administration interface, (this is the recommended method), or by editing the <filename><replaceable>WSRP_PATH</replaceable>/lib/gatein.portal.component.wsrp-<replaceable><VERSION></replaceable>-epp-GA.jar/conf/wsrp-producer-config.xml</filename> file. - </para> - <para> - Several aspects can be modified with respect to whether registration is required for consumers to access the Producer's services. An XML Schema for the configuration format is available at <filename><replaceable>WSRP_PATH</replaceable>/lib/wsrp-integration-api-<replaceable>WSRP_VERSION</replaceable>.jar/xsd/gatein_wsrp_producer_1_0.xsd </filename>. - </para> - <para> - An alternative to editing the default <filename>wsrp-producer-config.xml</filename> file is to make a custom copy containing the required configuration options. - </para> - <para> - If a copy is used in place of the original, however, the <filename><replaceable>WSRP_PATH</replaceable>/02portal.war/WEB-INF/conf/wsrp/wsrp-configuration.xml</filename> <emphasis role="bold">must</emphasis> be updated to reference the custom file (this file defines the component <literal>WSRPServiceIntegration</literal> and contains a producer and consumer configuration location). - </para> - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuring_the_WSRP_Producer-Default_Configuration"> - <title>Default Configuration</title> - <para> - The default producer configuration requires that consumers register with it before providing access to its services. However it does not require any specific registration properties (excepting those mandated by the WSRP standard). - </para> - <para> - It does, however, require consumers to be registered before sending them a full service description. This means that the WSRP producer will not provide the list of offered portlets and other capabilities to unregistered consumers. - </para> - <para> - The producer also uses the default <classname>RegistrationPolicy</classname> paired with the default <classname>RegistrationPropertyValidator</classname>. - </para> - <para> - This allows users to customize how Portal's WSRP Producer decides whether a given registration property is valid or not (however property validators are discussed in greater detail in <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Configuring_the_WSRP_Producer-Registration_Configuration" /> ). - </para> - <para> - JBoss Enterprise Portal Platform provides a web interface to configure the producer's behavior. It can be accessed by clicking on the "<emphasis role="bold">Producer Configuration</emphasis>" tab of the "<emphasis role="bold">WSRP</emphasis>" page of the "<emphasis role="bold">admin</emphasis>" portal. - </para> - <para> - The default configuration should show: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/producer_default.png" format="PNG" scale="110" width="444" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/producer_default.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - <para> - You can specify whether or not the producer will send the full service description to unregistered consumers, and, if it requires registration, which <literal>RegistrationPolicy</literal> to use (and, if needed, which <literal>RegistrationPropertyValidator</literal>), along with required registration property description for which consumers must provide acceptable values to successfully register. - </para> - <para> - WSDL URLs to access JBoss Enterprise Portal Platform's WSRP producer are now displayed in either in WSRP 1 or WSRP 2 mode. - </para> - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuring_the_WSRP_Producer-Registration_Configuration"> - <title>Registration Configuration</title> - <para> - In order to have consumers register with Portal's producer the Portal's behavior with respect to registration must be configured. - </para> - <para> - Registration is optional, as are registration properties. The producer can require registration without requiring consumers to pass any registration properties as is the case in the default configuration. - </para> - <para> - The following section discusses configuring a producer's registration behavior from a blank state: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/producer_blank.png" format="PNG" width="700" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/producer_blank.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - <procedure> - <step> - <para> - To allow unregistered consumers to see the list of offered portlets, leave the first checkbox ("<emphasis role="bold">Access to full service description requires consumers to be registered.</emphasis>") unchecked. - </para> - - </step> - <step> - <para> - To specify, however, that consumers will need to be registered to be able to interact with the producer, check the second box ("<emphasis role="bold">Requires registration. Modifying this information will trigger invalidation of consumer registrations."</emphasis>). - </para> - <para> - The screen will refresh and display: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/producer_registration.png" format="PNG" width="700" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/producer_registration.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - - </step> - <step> - <para> - The fully-qualified name for the <classname>RegistrationPolicy</classname> and <classname>RegistrationPropertyValidator</classname> can be specified here. The default values are acceptable. Refer to <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Registration_Configuration-Customization_of_Registration_Handling_Behavior" /> for more information. - </para> - - </step> - <step> - <para> - To add a registration property called <literal>email</literal> click "<emphasis role="bold">Add property</emphasis>" and enter the appropriate information in the fields, providing a description for the registration property that can be used by consumers to determine its purpose: - </para> - <mediaobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/WSRP/producer_email.png" format="PNG" width="700" /> - </imageobject> - <imageobject role="fo"> - <imagedata align="center" contentwidth="140mm" fileref="images/WSRP/producer_email.png" format="PNG" width="444" /> - </imageobject> - - </mediaobject> - - </step> - <step> - <para> - Press "Save" to record the modifications. - </para> - - </step> - - </procedure> - - <note> - <para> - At this time, only String (<literal>xsd:string</literal>) properties are supported. - </para> - - </note> - <note> - <para> - If consumers are already registered with the producer, modifying the configuration of required registration information will trigger the invalidation of held registrations, requiring consumers to modify their registration before being able to access the producer again. The consumer side of that process is documented in <xref linkend="sect-Reference_Guide_eXo_JCR_1.14-Modifying_a_Currently_Held_Registration-Registration_Modification_on_Producer_Error" />. - </para> - - </note> - <section id="sect-Reference_Guide_eXo_JCR_1.14-Registration_Configuration-Customization_of_Registration_Handling_Behavior"> - <title>Customization of Registration Handling Behavior</title> - <para> - Registration handling behavior can be customized by users to suit their Producer needs. This is done with an implementation of the <classname>RegistrationPolicy</classname> interface. - </para> - <para> - This interface defines methods that are called by Portal's Registration service so that decisions can be made appropriately. A default registration policy that provides basic behavior is provided and should be enough for most user needs. - </para> - <para> - While the default registration policy provides default behavior for most registration-related aspects, one aspect requires specific configuration: whether a given value for a registration property is acceptable by the WSRP Producer. - </para> - <para> - This is done by plugging a <classname>RegistrationPropertyValidator</classname> into the default registration policy. This allows users to define their own validation mechanism. - </para> - <para> - Refer to the <trademark class="trade">Javadoc</trademark> for <classname>org.gatein.registration.RegistrationPolicy</classname> and <classname>org.gatein.registration.policies.RegistrationPropertyValidator</classname> for more details on what is expected of each method. - </para> - <para> - A defined registration policy is required for the producer to be correctly configured. Do this by specifying the qualified class name of the registration policy. - </para> - <para> - As it is anticipated that most users will use the default registration policy, it is possible to provide the class name of a custom property validator instead to customize the default registration policy behavior. Note that property validators are only used by the default policy. - </para> - <note> - <para> - Since the policy or the validator are defined via their class name and dynamically loaded, it is important to ensure that the identified class is available to the application server. - </para> - <para> - One way to accomplish that is to deploy the policy implementation as a JAR file in the AS instance deploy directory. - </para> - <para> - Note also that, since both policies and validators are dynamically instantiated, they must provide a default, no-argument constructor. - </para> - - </note> - - </section> - - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Configuring_the_WSRP_Producer-WSRP_Validation_Mode"> - <title>WSRP Validation Mode</title> - <para> - The lack of conformance kit and the wording of the WSRP specification leaves room for differing interpretations, resulting in interoperability issues. It is therefore possible to encounter issues when using consumers from different vendors. - </para> - <para> - Experience of these issues has produced a way to relax the validation that the WSRP producer performs on the data provided by consumers to help with interoperability by accepting data that would normally be invalid. - </para> - <para> - Note that the our validation algorithm is only relaxed on aspects of the specification that are deemed harmless such as invalid language codes. - </para> - <para> - By default, the WSRP producer is configured in strict mode. If you experience issues with a given consumer, you may attempt to relax the validation mode. Un-checking the "Use strict WSRP compliance" checkbox on the Producer configuration screen to do this. - </para> - - </section> - - - </section> - - <section id="sect-Reference_Guide_eXo_JCR_1.14-Web_Services_for_Remote_Portlets_WSRP-Removing_WSRP"> - <title>Removing WSRP</title> - <para> - If you are not going to use WSRP in your JBoss Enterprise Portal Platform instance, the WSRP configuration files may be left in place. They will not adversely affect your installation. - </para> - <para> - However, if you wish to completely remove WSRP from your portal installation, remove the <filename>gatein-wsrp-integration.ear</filename> file from your application server deploy directory. - </para> -  - </section> - - -</chapter> - Copied: epp/docs/branches/5.2/Reference_Guide/en-US/modules/WSRP.xml (from rev 8139, epp/docs/branches/5.2/Reference_Guide-eXoJCR-1.14/en-US/modules/WSRP.xml) =================================================================== --- epp/docs/branches/5.2/Reference_Guide/en-US/modules/WSRP.xml (rev 0) +++ epp/docs/branches/5.2/Reference_Guide/en-US/modules/WSRP.xml 2011-11-25 00:48:53 UTC (rev 8141) @@ -0,0 +1,1370 @@ +<?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 "../Reference_Guide.ent"> + %BOOK_ENTITIES; + ]> +<chapter id="wsrp"> + <title>Web Services for Remote Portlets (WSRP)</title> + + <section> + <title>Introduction</title> + <para>The Web Services for Remote Portlets specification defines a web service interface for accessing and + interacting with interactive presentation-oriented web services. It has been produced through the efforts of + the Web Services for Remote Portlets (WSRP) OASIS Technical Committee. It is based on the requirements + gathered and on the concrete proposals made to the committee. + </para> + + <para>Scenarios that motivate WSRP functionality include: + <itemizedlist> + <listitem> + <para>Content hosts, such as portal servers, providing Portlets as presentation-oriented web services + that can be used by aggregation engines. + </para> + </listitem> + <listitem> + <para>Aggregating frameworks, including portal servers, consuming presentation-oriented web services + offered by content providers and integrating them into the framework. + </para> + </listitem> + </itemizedlist> + </para> + + <para>More information on WSRP can be found on the + <ulink url="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsrp">official website for WSRP</ulink>. + We suggest reading the + <ulink url="http://www.oasis-open.org/committees/download.php/10539/wsrp-primer-1.0.html">primer</ulink> + for a good, albeit technical, overview of WSRP. + </para> + </section> + + <section id="wsrp_support"> + <title>Level of support in JBoss Enterprise Portal Platform</title> + <para>The WSRP Technical Committee defined + <ulink url="http://www.oasis-open.org/committees/download.php/3073">WSRP Use Profiles</ulink> + to help with WSRP interoperability. We will refer to terms defined in that document in + this section. + </para> + + <para>JBoss Enterprise Portal Platform provides a Simple level of support for our WSRP Producer except that out-of-band registration + is not currently handled. We support in-band registration and persistent local state (which are + defined at the Complex level). + </para> + + <para>On the Consumer side, JBoss Enterprise Portal Platform provides a Medium level of support for WSRP, except that we only handle + HTML markup (as JBoss Enterprise Portal Platform itself doesn't handle other markup types). We do support explicit portlet + cloning and we fully support the PortletManagement interface. + </para> + + <para>As far as caching goes, we have Level 1 Producer and Consumer. We support Cookie handling properly on the + Consumer and our Producer requires initialization of cookies (as we have found that it improved interoperabilty + with some consumers). We don't support custom window states or modes, as JBoss Enterprise Portal Platform doesn't either. We do, + however, support CSS on both the Producer (though it's more a function of the portlets than inherent Producer + capability) and Consumer. + </para> + + <para>While we provide a complete implementation of WSRP 1.0, we do need to go through the + <ulink url="http://www.oasis-open.org/committees/download.php/6018">Conformance statements</ulink> + and perform more interoperability testing (an area that needs to be better supported by the WSRP Technical + Committee and Community at large). + </para> + + <para>JBoss Enterprise Portal Platform supports WSRP 2.0 with a complete implementation of the non-optional features. The only + features that we have not implemented is support for lifetimes and leasing + support. + </para> + + <note> + <para>As of version &VY; of JBoss Enterprise Portal Platform, WSRP is only activated and supported + when JBoss Enterprise Portal Platform is deployed on JBoss Application Server. + </para> + </note> + </section> + + <section> + <title>Deploying JBoss Enterprise Portal Platform's WSRP services</title> + <para> + JBoss Enterprise Portal Platform provides a complete support of WSRP 1.0 and 2.0 standard interfaces and offers both consumer and + producer services. Starting with version 2.1.0-GA of the component, WSRP is packaged as a JBoss Enterprise Portal Platform + extension and is now self-contained in an easy to install package named + <filename>$JBOSS_PROFILE_HOME/deploy/gatein-wsrp-integration.ear</filename> + where + <filename>$JBOSS_PROFILE_HOME</filename> + refers to your JBoss AS profile directory (<filename>default</filename>, for instance). + </para> + <para> + The extension itself is composed of the following components, assuming + <code>$WSRP_VERSION</code> + (at the time of the writing, it was 2.1.0-GA) is the version of the WSRP component and + <code>$PORTAL_VERSION</code> + (at the time of the writing, it was &VY;) is the current JBoss Enterprise Portal Platform version: + <itemizedlist> + <listitem> + <para> + <filename>META-INF</filename> + contains files necessary for EAR packaging. The only file that is of interest from a user perspective + is + <filename>gatein-wsse-consumer.xml</filename> + which allows you to configure WS-Security support for the consumer. Please see the + <link linkend="wss_configuration">WSRP and WS-Security</link> section for more details. + </para> + </listitem> + <listitem> + <para> + <filename>extension-component-$PORTAL_VERSION.jar</filename>, which contains the components needed to + integrate the WSRP component into JBoss Enterprise Portal Platform. It also includes the default configuration files for + the WSRP producer and the default WSRP consumers. + </para> + </listitem> + <listitem> + <para> + <filename>extension-config-$PORTAL_VERSION.jar</filename>, which contains the configuration file + needed by the GateIn extension mechanism to properly register this EAR as an extension. + </para> + </listitem> + <listitem> + <para> + <filename>extension-war-$PORTAL_VERSION.war</filename>, which contains the configuration files + needed by the GateIn extension mechanism to properly setup the WSRP service. It includes + <filename>wsrp-configuration.xml</filename> + which, in particular, configures several options for the + <code>WSRPServiceIntegration</code> + component at the heart of the WSRP integration in JBoss Enterprise Portal Platform. + </para> + </listitem> + <listitem> + <para> + <filename>lib</filename>, which contains the different libraries needed by the WSRP service. + </para> + </listitem> + <listitem> + <para> + <filename>wsrp-admin-gui-$WSRP_VERSION.war</filename>, which contains the WSRP Configuration portlet + with which you can configure consumers to access remote servers and how the WSRP producer is + configured. + </para> + </listitem> + <listitem> + <para><filename>wsrp-producer-jb5wsss-$WSRP_VERSION.war</filename>, which contains the producer-side + support for WS-Security. The only file of interest from a user perspective is + <filename>gatein-wsse-producer.xml</filename> which allows you to configure WS-Security support for + the producer. Please see the <link linkend="wss_configuration">WSRP and WS-Security</link> section + for more details. + </para> + </listitem> + </itemizedlist> + </para> + <para> + If you're not going to use WSRP in JBoss Enterprise Portal Platform, it won't adversely affect your installation to leave it + as-is. Otherwise, you can just remove the + <filename>gatein-wsrp-integration.ear</filename> + file from your AS deploy directory. + </para> + + <section id="wsrp-ports"> + <title>Considerations to use WSRP when running JBoss Enterprise Portal Platform on a non-default port or hostname</title> + <para> + JBoss WS (the web service stack that JBoss Enterprise Portal Platform uses) should take care of the details of updating the + port and host name used in WSDL. See the + <ulink url="http://community.jboss.org/wiki/JBossWS-UserGuide#Configuration">JBoss WS user guide on that + subject + </ulink> + 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 + 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> + + <section> + <title>Securing WSRP</title> + <section> + <title>Considerations to use WSRP with SSL</title> + <para>It is possible to use WSRP over SSL for secure exchange of data. Please refer to the + <ulink url="http://community.jboss.org/wiki/ConfiguringWSRPforuseoverSSL">instructions</ulink> + on how to do so from + <ulink url="http://community.jboss.org/wiki/GateIn">GateIn's wiki</ulink>. + </para> + </section> + <section> + <title>WSRP and WS-Security</title> + <para>Portlets may present different data or options depending on the currently authenticated user. For remote + portlets, this means having to propagate the user credentials from the consumer back to the producer in + a safe and secure manner. The WSRP specification does not directly specify how this should be + accomplished, but delegates this work to the existing WS-Security standards. + </para> + <note> + <title>Web Container Compatibility</title> + <para>WSRP and WS-Security is currently only supported on JBoss Enterprise Portal Platform when running on top of JBoss + AS 5. + </para> + </note> + <warning> + <title>Encryption</title> + <para>You will want to encrypt the credentials being sent between the consumer and producer, otherwise they + will be sent in plain text and could be easily intercepted. You can either configure WS-Security to + encrypt and sign the SOAP messages being sent, or secure the transport layer by using an https endpoint. + Failure to encrypt the soap message or transport layer will result in the username and password being + sent in plain text. <emphasis role="bold">Use of encryption is strongly recommended.</emphasis> + </para> + </warning> + <important> + <title>Credentials</title> + <para>When the consumer sends the user credentials to the producer, it is sending the credentials for the + currently authenticated user in the consumer. This makes signing in to remote portlets transparent + to end users, but also requires that the producer and consumer use the same credentials. This means + that the username and password must be the same and valid on both servers. + </para> + <para>The recommended approach for this situation would be to use a common ldap configuration. Please + see the user guide on how to configure ldap for use with JBoss Enterprise Portal Platform + </para> + </important> + <para>The GateIn Wiki article, <ulink url="http://community.jboss.org/wiki/GateInWSRPAndWebServiceSecurity"> + GateIn WSRP and Web Service Security</ulink>, also provides a step-by-step example on how to configure + WSRP with WS-Security. + </para> + <section id="wss_configuration"> + <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. + </para> + <para> The following are the JBossWS Native configuration files which need to be configure for WSRP: + </para> + <itemizedlist> + <listitem> + <para> + <filename>gatein-wsrp-integration.ear/META-INF/gatein-wsse-consumer.xml</filename>: JBossWS + configuration file for the consumer. + </para> + </listitem> + <listitem> + <para> + <filename>gatein-wsrp-integration.ear/wsrp-producer-jb5wss.war/WEB-INF/conf/gatein-wsse-producer.xml + </filename>: JBossWS configuration file for the producer. + </para> + </listitem> + </itemizedlist> + </section> + <section> + <title>WS-Security Producer Configuration</title> + <para> + Other than the JBossWS configuration file mention above, no other configuration changes should be necessary + for the producer. + </para> + </section> + <section> + <title>WS-Security Consumer Configuration</title> + <para>The consumer requires a few changes before it will function properly with WS-Security. The consumer + needs access to the current servlet request since this is used to retrieve the currently authenticated + user. In order for the consumer to access this information, it needs a special servlet-filter added to + the portal. + </para> + <para>In <filename>gatein.ear/02portal.war/WEB-INF/web.xml</filename> add the following information: + </para> +<programlisting role="XML"><![CDATA[ + <filter> + <filter-name>ServletAccessFilter</filter-name> + <filter-class>org.gatein.wsrp.servlet.ServletAccessFilter</filter-class> + </filter> + <filter-mapping> + <filter-name>ServletAccessFilter</filter-name> + <url-pattern>/*</url-pattern> + </filter-mapping>]]> +</programlisting> + <para> + Finally, in the WSRP Configuration portlet, in the consumer configuration options, you will need to check the 'Enable WS Security' checkbox: + </para> + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/config_wss_selected.png" format="PNG" align="center" valign="middle" scalefit="1"/> + </imageobject> + </mediaobject> + </section> + <section> + <title>WS-Security Consumer Checklist</title> + <para> + In order for the consumer to handle ws-security, the following steps must be completed properly + </para> + <itemizedlist> + <listitem> + <para>The JBossWS configuration files must be configured</para> + </listitem> + <listitem> + <para>The filter must be added to the portal's web.xml</para> + </listitem> + <listitem> + <para>the enable wss feature must be check in the wsrp admin</para> + </listitem> + </itemizedlist> + <para>The consumer will not properly handle ws-security unless all 3 are properly configured</para> + </section> + </section> + </section> + + <section> + <title>Making a portlet remotable</title> + <important> + <para> + Only JSR-286 (Portlet 2.0) portlets can be made remotable as the mechanism to expose a portlet to WSRP + relies on a JSR-286-only functionality. + </para> + </important> + <para>JBoss Enterprise Portal Platform does + <emphasis role="bold">NOT</emphasis>, by default, expose local portlets for consumption + by remote WSRP consumers. In order to make a portlet remotely available, it must be made "remotable" by marking + it as such in the associated + <filename>portlet.xml</filename>. This is accomplished by using a specific + <code>org.gatein.pc.remotable container-runtime-option</code>. Setting its value to + <code>true</code> + makes the portlet available for remote consumption, while setting its value to + <code>false</code> + will not publish it remotely. As specifying the remotable status for a portlet is optional, you do not need to + do anything if you don't need your portlet to be available remotely. + </para> + <para>In the following example, the "BasicPortlet" portlet is specified as being remotable. + </para> + <example> + <title>Example</title> + <para> + <programlisting><![CDATA[ +<?xml version="1.0" standalone="yes"?> +<portlet-app xmlns="http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd" + xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" + xsi:schemaLocation="http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd" + version="2.0"> +<portlet-app> + <portlet> + <portlet-name>BasicPortlet</portlet-name> + + ... + + <container-runtime-option> + <name>org.gatein.pc.remotable</name> + <value>true</value> + </container-runtime-option> + </portlet> +</portlet-app>]]></programlisting> + </para> + + </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: + </para> + <example> + <title>Example</title> + <para> + <programlisting><![CDATA[ +<?xml version="1.0" standalone="yes"?> +<portlet-app xmlns="http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd" + xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" + xsi:schemaLocation="http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd http://java.sun.com/xml/ns/portlet/portlet-app_2_0.xsd" + version="2.0"> +<portlet-app> + + <portlet> + <portlet-name>RemotelyExposedPortlet</portlet-name> + ... + </portlet> + <portlet> + <portlet-name>NotRemotelyExposedPortlet</portlet-name> + ... + <container-runtime-option> + <name>org.gatein.pc.remotable</name> + <value>false</value> + </container-runtime-option> + </portlet> + + <container-runtime-option> + <name>org.gatein.pc.remotable</name> + <value>true</value> + </container-runtime-option> +</portlet-app>]]> + </programlisting> + </para> + + </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. + </para> + </section> + + <section> + <title>Consuming JBoss Enterprise Portal Platform's WSRP portlets from a remote Consumer</title> + <para>WSRP Producers vary a lot as far as how they are configured. Most of them require that you specify + the URL for the Producer's WSDL definition. Please refer to the remote producer's documentation for specific + instructions. For instructions on how to do so in JBoss Enterprise Portal Platform, please refer to + <xref linkend="consumer_configuration"/>. + </para> + <para> + JBoss Enterprise Portal Platform's Producer is automatically set up when you deploy a portal instance with the WSRP service. + You can access the WSDL file at + <filename>http://{hostname}:{port}/wsrp-producer/v2/MarkupService?wsdl</filename>. If you wish to use only the + WSRP 1 compliant version of the producer, please use the WSDL file found at + <filename>http://{hostname}:{port}/wsrp-producer/v1/MarkupService?wsdl</filename>. + The default hostname is + <literal>localhost</literal> + and the default port is 8080. + </para> + </section> + + <section id="consumer_configuration"> + <title>Consuming remote WSRP portlets in JBoss Enterprise Portal Platform</title> + <section> + <title>Overview</title> + <para> + To be able to consume WSRP portlets exposed by a remote producer, JBoss Enterprise Portal Platform's WSRP consumer needs to + know how to access that remote producer. One can configure access to a remote producer using the provided + configuration portlet. Alternatively, it is also possible to configure access to remote producers using an + XML descriptor, though it is recommended (and easier) to do so via the configuration portlet. + </para> + <para> + Once a remote producer has been configured, the portlets that it exposes are then available in the + Application Registry to be added to categories and then to pages. + </para> + </section> + + <section id="consumer_gui"> + <title>Configuring a remote producer using the configuration portlet</title> + <para> + Let's work through the steps of defining access to a remote producer using the configuration portlet so that its portlets can be + consumed within JBoss Enterprise Portal Platform. We will configure access to NetUnity's public WSRP producer. + </para> + + <note> + <para> + Some WSRP producers do not support chunked encoding that is activated by default by JBoss WS. If your + producer does not support chunked encoding, your consumer will not be able to properly connect to the + producer. This will manifest itself with the following error: + <code>Caused by: org.jboss.ws.WSException: Invalid HTTP server response [503] - Service + Unavailable</code>. + Please see this GateIn's + <ulink url="http://community.jboss.org/wiki/Workaroundwhenchunkedencodingisnotsupported">wiki page + </ulink> + for more details. + </para> + </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 + url="http://localhost:8080/portal/login?initialURI=%2Fportal%2Fprivate%2Fclass..."> + http://localhost:8080/portal/login?initialURI=%2Fportal%2Fprivate%2Fclass... + </ulink> + </para> + + <para> + You should see a screen similar to: + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/config_init.png" format="PNG" align="center" valign="middle" + scalefit="1"/> + </imageobject> + </mediaobject> + This screen presents all the configured Consumers associated with their status and possible actions on + them. A Consumer can be active or inactive. Activating a Consumer means that it is ready to act as a + portlet provider. Note also that a Consumer can be marked as requiring refresh meaning that the + information held about it might not be up to date and refreshing it from the remote Producer might be a + good idea. This can happen for several reasons: the service description for that remote Producer has not + been fetched yet, the cached version has expired or modifications have been made to the configuration + that could potentially invalidate it, thus requiring re-validation of the information. + </para> + + <note> + <para> + The WSRP configuration didn't use to be installed by default in previous versions of JBoss Enterprise Portal Platform. + We include here the legacy instructions on how to install this portlet in case you ever need to + re-install it. + </para> + <para> + Use the usual procedure to log in as a Portal administrator and go to the Application + Registry. With the default install, you can just go to + <ulink + url="http://localhost:8080/portal/login?initialURI=%2Fportal%2Fprivate%2Fclass..."> + http://localhost:8080/portal/login?initialURI=%2Fportal%2Fprivate%2Fclass... + </ulink> + Add the WSRP Configuration portlet to the Administration category. If you use the Import Applications + functionality, the WSRP Configuration portlet will be automatically added to the Administration + category. + </para> + <para> + Now that the portlet is added to a category, it can be added to a page and used. We recommend adding + it to the same page as the Application Registry as operations relating to WSRP and adding portlets to + categories are somewhat related as we will see. Go ahead and add the WSRP Configuration portlet to the + page using the standard procedure. + </para> + </note> + + <para> + Next, we create a new Consumer which we will call <literal>netunity</literal>. Type + "<literal>netunity</literal>" in + the "Create a consumer named:" field then click on "Create consumer": + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/config_create.png" format="PNG" align="center" valign="middle" + scalefit="1"/> + </imageobject> + </mediaobject> + You should now see a form allowing you to enter/modify the information about the Consumer. + Set the cache expiration value to 300 seconds, leave the default timeout value for web services (WS) + operations and enter the WSDL URL for the producer in the text field + and press the "Refresh & Save" button: + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/config_wsdl.png" format="PNG" align="center" valign="middle" + scalefit="1"/> + </imageobject> + </mediaobject> + This will retrieve the service description associated with the Producer which WSRP interface is described + by the WSDL file found at the URL you just entered. In our case, querying the service description will + allow us to learn that the Producer requires registration, requested three registration properties and that + we are missing values for these properties: + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/config_missing.png" format="PNG" align="center" valign="middle" + scalefit="1"/> + </imageobject> + </mediaobject> + This particular producer requests simple + <literal>Yes</literal> + or + <literal>No</literal> + values for the three registration properties. Entering <literal>No</literal>, + <literal>Yes</literal> + and + <literal>No</literal> + (in that order) for the values and then pressing the "Refresh & Save" button should result in: + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/config_end.png" format="PNG" align="center" valign="middle" + scalefit="1"/> + </imageobject> + </mediaobject> + + <note> + <para>At this point, there is no automated way to learn about which possible values (if any) are + expected by the remote Producer. Sometimes, the possible values will be indicated in the + registration + property description but this is not always the case... Please refer to the specific Producer's + documentation. + </para> + </note> + </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: + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/config_refresh.png" format="PNG" align="center" valign="middle" + scalefit="1"/> + </imageobject> + </mediaobject> + </para> + </section> + + <section id="consumer_xml"> + <title>Configuring access to remote producers via XML</title> + + <para>While we recommend you use the WSRP Configuration portlet to configure Consumers, we provide an + alternative way to configure consumers by adding an XML file called + <filename>wsrp-consumers-config.xml</filename> in the + <filename>$JBOSS_PROFILE_HOME/conf/gatein/</filename> directory. + <note> + <para>An XML Schema defining which elements are available to configure Consumers via XML can be found + in + <filename> + $JBOSS_PROFILE_HOME/deploy/gatein-wsrp-integration.ear/lib/wsrp-integration-api-$WSRP_VERSION.jar/xsd/gatein_wsrp_consumer_1_0.xsd + </filename> + </para> + </note> + <important> + <para> + It is important to note that once the XML configuration file for consumers has been read upon + the WSRP service first start, the associated information is put under control of JCR (Java Content + Repository). Subsequent launches of the WSRP service will use the JCR-stored information and ignore + the content of the XML configuration file. + </para> + +  + </important> + </para> + + <section> + <title>Required configuration information</title> + + <para>Let's now look at which information needs to be provided to configure access to a remote producer. + </para> + + <para>First, we need to provide an identifier for the producer we are configuring so that we can refer to it + afterwards. This is accomplished via the mandatory + <literal>id</literal> + attribute of the + <literal><wsrp-producer></literal> + element. + </para> + + <para>JBoss Enterprise Portal Platform also needs to learn about the remote producer's endpoints to be able to connect to the + remote web services and perform WSRP invocations. This is accomplished by specifying the URL for the + WSDL description for the remote WSRP service, using the + <literal><endpoint-wsdl-url></literal> + element. + </para> + + <para>Both the + <literal>id</literal> + attribute and + <literal><endpoint-wsdl-url></literal> + elements are required for a functional remote producer configuration. + </para> + </section> + + <section> + <title>Optional configuration</title> + <para>It is also possible to provide addtional configuration, which, in some cases, might be important to + establish a proper connection to the remote producer. + </para> + + <para>One such optional configuration concerns caching. To prevent useless roundtrips between the local + consumer and the remote producer, it is possible to cache some of the information sent by the producer + (such as the list of offered portlets) for a given duration. The rate at which the information is + refreshed is + defined by the + <literal>expiration-cache</literal> + attribute of the + <literal><wsrp-producer></literal> + element which specifies the refreshing period in seconds. For example, providing a value of 120 for + expiration-cache means that the producer information will not be refreshed for 2 minutes after it has + been somehow accessed. If no value is provided, JBoss Enterprise Portal Platform will always access the remote producer + regardless of whether the remote information has changed or not. Since, in most instances, the + information provided by the producer does not change often, we recommend that you use this caching + facility to minimize bandwidth usage. + </para> + + <para>It is also possible to define a timeout after which WS operations are considered as failed. This is + helpful to avoid blocking the WSRP service, waiting forever on the service that doesn't answer. Use the + <literal>ws-timeout</literal> + attribute of the + <literal><wsrp-producer></literal> + element to specify how many milliseconds the WSRP service will wait for a response from the remote + producer before timing out and giving up. + </para> + + <para>Additionally, some producers require consumers to register with them before authorizing them to access + their offered portlets. If you know that information beforehand, you can provide the required + registration information in the producer configuration so that the consumer can register with the remote + producer when required. + <note> + <para>At this time, though, only simple String properties are supported and it is not possible to + configure complex registration data. This should, however, be sufficient for most cases. + </para> + </note> + </para> + + <para>Registration configuration is done via the + <literal><registration-data></literal> + element. Since JBoss Enterprise Portal Platform can generate the mandatory information for you, if the remote producer does + not require any registration properties, you only need to provide an empty + <literal><registration-data></literal> + element. Values for the registration properties + required by the remote producer can be provided via + <literal><property></literal> + elements. See the example below for more details. Additionally, you can override the default consumer + name automatically provided by JBoss Enterprise Portal Platform via the + <literal><consumer-name></literal> + element. If you choose to provide a consumer name, please remember that this should uniquely identify + your consumer. + </para> + </section> + + <section> + <title>Examples</title> + + <para> + Here is the configuration of the + <literal>selfv1</literal> + and + <literal>selfv2</literal> + consumers as found in + <filename>$JBOSS_PROFILE_HOME/deploy/gatein-wsrp-integration.ear/lib/extension-component-$WSRP_VERSION.jar/conf/wsrp-consumers-config.xml</filename> + with a cache expiring every 500 seconds and with a 50 second timeout for web service operations. + <note> + <para> + This file contains the default configuration and you shouldn't need to edit it. If you want to make + modifications to it, we recommend that you follow the procedure detailed in + <xref linkend="consumer_gui"/>. + </para> + </note> + </para> + + <example> + <title>Example</title> + <para> + <programlisting><![CDATA[ +<?xml version='1.0' encoding='UTF-8' ?> +<deployments xmlns="http://www.gatein.org/xml/ns/gatein_wsrp_consumer_1_0" + xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" + xsi:schemaLocation="http://www.gatein.org/xml/ns/gatein_wsrp_consumer_1_0 http://www.jboss.org/portal/xsd/gatein_wsrp_consumer_1_0.xsd"> + <deployment> + <wsrp-producer id="selfv1" expiration-cache="500" ws-timeout="50000"> + <endpoint-wsdl-url>http://localhost:8080/wsrp-producer/v1/MarkupService?wsdl</endpoint-wsdl-url> + <registration-data/> + </wsrp-producer> + </deployment> + <deployment> + <wsrp-producer id="selfv2" expiration-cache="500" ws-timeout="50000"> + <endpoint-wsdl-url>http://localhost:8080/wsrp-producer/v2/MarkupService?wsdl</endpoint-wsdl-url> + <registration-data/> + </wsrp-producer> + </deployment> +</deployments>]]> + </programlisting> + </para> + + </example> + + <para>Here is an example of a WSRP descriptor with registration data and cache expiring every minute: + </para> + + <example> + <title>Example</title> + <para> + <programlisting><![CDATA[ +<?xml version='1.0' encoding='UTF-8' ?> +<deployments xmlns="http://www.gatein.org/xml/ns/gatein_wsrp_consumer_1_0" + xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" + xsi:schemaLocation="http://www.gatein.org/xml/ns/gatein_wsrp_consumer_1_0 http://www.jboss.org/portal/xsd/gatein_wsrp_consumer_1_0.xsd"> +<deployments> + <deployment> + <wsrp-producer id="AnotherProducer" expiration-cache="60"> + <endpoint-wsdl-url>http://example.com/producer/producer?WSDL</endpoint-wsdl-url> + <registration-data> + <property> + <name>property name</name> + <lang>en</lang> + <value>property value</value> + </property> + </registration-data> + </wsrp-producer> + </deployment> +</deployments>]]></programlisting> + </para> + </example> + </section> + </section> + + <section> + <title>Adding remote portlets to categories</title> + <para> + If we go to the Application Registry and examine the available portlets by clicking on the + Portlet link, you will now be able to see remote portlets if you click on the REMOTE tab in the left + column: + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/remote_portlets.png" format="PNG" align="center" valign="middle" + scalefit="1"/> + </imageobject> + </mediaobject> + </para> + + <para> + These portlets are, of course, available to be used such as regular portlets: they can be used in + categories and added to pages. If you use the Import Applications functionality, they will also be + automatically imported in categories based on the keywords they define. + </para> + + <para> + More specifically, if you want to add a WSRP portlet to a category, you can access these portlets by + selecting + <literal>wsrp</literal> + in the Application Type drop-down menu: + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/remote_portlets_category.png" format="PNG" align="center" + valign="middle" + scalefit="1"/> + </imageobject> + </mediaobject> + </para> + </section> + </section> + + <section> + <title>Consumers maintenance</title> + + <section> + <title>Modifying a currently held registration</title> + + <section> + <title>Registration modification for service upgrade</title> + <para> + Producers often offer several levels of service depending on consumers' subscription levels (for + example). This is implemented at the WSRP level with the registration concept: producers can assert which + level of service to provide to consumers based on the values of given registration properties. + </para> + <para> + There might also be cases where you just want to update the registration information because it has + changed. For example, the producer required you to provide a valid email and the previously email + address is not valid anymore and needs to be updated. + </para> + <para> + It is therefore sometimes necessary to modify the registration that concretizes the service agreement + between a consumer and a producer. Let's take the example of a producer requiring a valid email (via an + <literal>email</literal> + registration property) as part of its required information that consumers need to provide to be properly + registered. + </para> + <para> + Suppose now that we would like to update the email address that we provided to the remote producer when + we first registered. We will need to tell the producer that our registration data has been modified. + Let's see how to do this. Select the consumer for the remote producer in the available consumers list to + display its configuration. Assuming you want to change the email you registered with to + <literal>foo(a)example.com</literal>, change its value in the field for the + <literal>email</literal> + registration property: + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/modify_reg_start.png" format="PNG" align="center" valign="middle" + scalefit="1"/> + </imageobject> + </mediaobject> + Now click on "Update properties" to save the change. A "Modify registration" button should now appear to + let you send this new data to the remote producer: + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/modify_reg_modify.png" format="PNG" align="center" + valign="middle" scalefit="1"/> + </imageobject> + </mediaobject> + Click on this new button and, if everything went well and your updated registration has been accepted by + the remote producer, you should see something similar to: + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/modify_reg_end.png" format="PNG" align="center" valign="middle" + scalefit="1"/> + </imageobject> + </mediaobject> + </para> + + </section> + + <section id="reg_mod_error"> + <title>Registration modification on producer error</title> + + <para> + It can also happen that a producer administrator decided to change its requirement for registered + consumers. JBoss Enterprise Portal Platform will attempt to help you in this situation. Let's walk through an example using + the <literal>selfv2</literal> consumer. Let's assume that registration is requiring a valid value for an + <literal>email</literal> + registration property. If you go to the configuration screen for this consumer, you should see: + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/config_self.png" format="PNG" align="center" valign="middle" + scalefit="1"/> + </imageobject> + </mediaobject> + + Now suppose that the administrator of the producer now additionaly requires a value to be provided for a + <literal>name</literal> + registration property. We will actually see how to do perform this operation + in JBoss Enterprise Portal Platform when we examine how to configure JBoss Enterprise Portal Platform's producer in + <xref linkend="producer_config"/>. + Operations with this producer will now fail. If you suspect that a registration modification is required, + you should go to the configuration screen for this remote producer and refresh the information held by + the consumer by pressing "Refresh & Save": + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/modify_reg_self.png" format="PNG" align="center" valign="middle" + scalefit="1"/> + </imageobject> + </mediaobject> + + As you can see, the configuration screen now shows the currently held registration information and + the expected information from the producer. Enter a value for the + <literal>name</literal> + property + and then click on "Modify registration". If all went well and the producer accepted your new registration + data, you should see something similar to: + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/modify_reg_self_end.png" format="PNG" align="center" + valign="middle" scalefit="1"/> + </imageobject> + </mediaobject> + + <note> + <para>WSRP 1 makes it rather difficult to ascertain for sure what caused an + <exceptionname>OperationFailedFault</exceptionname> + as it is the generic exception returned by + producers if something didn't quite happen as expected during a method invocation. This means that + <exceptionname>OperationFailedFault</exceptionname> + can be caused by several different reasons, one + of them being a request to modify the registration data. Please take a look at the log files to see + if you can gather more information as to what happened. WSRP 2 introduces an exception that is + specific to a request to modify registrations thus reducing the ambiguity that exists when using WSRP 1. + </para> + + </note> + </para> + </section> + </section> + + <section> + <title>Consumer operations</title> + <para> + Several operations are available from the consumer list view of the WSRP configuration portlet: + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/consumer_operations.png" format="PNG" align="center" valign="middle" + scalefit="1"/> + </imageobject> + </mediaobject> + </para> + <para> + The available operations are: + <itemizedlist> + <listitem> + <para>Configure: displays the consumer details and allows user to edit them</para> + </listitem> + <listitem> + <para>Refresh: forces the consumer to retrieve the service description from the remote producer to + refresh + the local information (offered portlets, registration information, etc.) + </para> + </listitem> + <listitem> + <para>Activate/Deactivate: activates/deactivates a consumer, governing whether it will be available to + provide portlets and receive portlet invocations + </para> + </listitem> + <listitem> + <para>Register/Deregister: registers/deregisters a consumer based on whether registration is required + and/or acquired + </para> + </listitem> + <listitem> + <para>Delete: destroys the consumer, after deregistering it if it was registered</para> + </listitem> + <listitem> + <para>Export: exports some or all of the consumer's portlets to be able to later import them in a + different context + </para> + </listitem> + <listitem> + <para>Import: imports some or all of previously exported portlets</para> + </listitem> + </itemizedlist> + </para> + <note> + <para> + Import/Export functionality is only available to WSRP 2 consumers of producers that support this optional + functionality. Import functionality is only available if portlets had previously been exported. + </para> + </note> + </section> + + <section> + <title>Importing and exporting portlets</title> + <para>Import and export are new functionalities added in WSRP 2. Exporting a portlet allows a consumer to get + an opaque representation of the portlet which can then be use by the corresponding import operation to + reconstitute it. It is mostly used in migration scenarios during batch operations. Since JBoss Enterprise Portal Platform + does not currently support automated migration of portal data, the functionality that we provide as part of + WSRP 2 is necessarily less complete than it could be with full portal support. + </para> + <para>The import/export implementation in JBoss Enterprise Portal Platform (available since 3.1) allows users to export portlets + from a given consumer. + These portlets can then be used to replace existing content on pages. This is accomplished by assigning + previously exported portlets to replace the content displayed by windows on the portal's pages. Let us walk + through an example to make things clearer. + </para> + <para>Clicking on the "Export" action for a given consumer will display the list of portlets currently made + available by this specific consumer. An example of such a list is shown below: + </para> + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/export_portlet_list.png" format="PNG" align="center" valign="middle"/> + </imageobject> + </mediaobject> + <para>Once portlets have been selected, they can be exported by clicking on the "Export" button thus making + them available for later import: + </para> + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/export_done.png" format="PNG" align="center" valign="middle"/> + </imageobject> + </mediaobject> + <para>You can re-import the portlets directly by pressing the "Use for import" button or, on the Consumers list + page, using the "Import" action for a given consumer. Let's assume that you used that second option and that + you currently have several available sets of previously exported portlets to import from. After clicking the + action link, you should see a screen similar to the one below: + </para> + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/export_list.png" format="PNG" align="center" valign="middle"/> + </imageobject> + </mediaobject> + <para>As you can see this screen presents the list of available exports with available operations for each. + <itemizedlist> + <listitem> + <para>View: displays the export details as previously seen when the export was first performed</para> + </listitem> + <listitem> + <para>Delete: deletes the selected export, asking you for confirmation first</para> + </listitem> + <listitem> + <para>Use for import: selects the export to import portlets from</para> + </listitem> + </itemizedlist> + </para> + <para>Once you've selected an export to import from, you will see a screen similar to the one below:</para> + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/import_start.png" format="PNG" align="center" valign="middle"/> + </imageobject> + </mediaobject> + <para>The screen displays the list of available exported portlets for the previously selected export. You can + select which portlet you want to import by checking the checkbox next to its name. Next, you need to select + the content of which window the imported portlet will replace. This process is done in three steps. Let's + assume in this example that you have the following page called + <literal>page1</literal> + and containing two windows called + <literal>NetUnity WSRP 2 Interop - Cache Markup (remote)</literal> + and + <literal>/samples-remotecontroller-portlet.RemoteControl (remote)</literal> + as shown below: + </para> + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/import_original_page.png" format="PNG" align="center" valign="middle"/> + </imageobject> + </mediaobject> + <para>In this example, we want to replace the content of the + <literal>/samples-remotecontroller-portlet.RemoteControl (remote)</literal> + by the content of the + <literal>/ajaxPortlet.JSFAJAXPortlet</literal> + portlet that we previously exported. To do so, we will check the checkbox next to the + <literal>/ajaxPortlet.JSFAJAXPortlet</literal> + portlet name to indicate that we want to import its data and then select the + <literal>page1</literal> + in the list of available pages. The screen will then refresh to display the list of available windows on + that page, similar to the one seen below: + </para> + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/import_selected_page.png" format="PNG" align="center" valign="middle"/> + </imageobject> + </mediaobject> + <para>Note that, at this point, we still need to select the window which content we want to replace before + being able to complete the import operation. Let's select the + <literal>/samples-remotecontroller-portlet.RemoteControl (remote)</literal> + window, at which point the "Import" button will become enabled, indicating that we now have all the + necessary data to perform the import. If all goes well, pressing that button should result in a screen + similar to the one below: + </para> + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/import_success.png" format="PNG" align="center" valign="middle"/> + </imageobject> + </mediaobject> + <para>If you now take a look at the + <literal>page1</literal> + page, you should now see that the content + <literal>/samples-remotecontroller-portlet.RemoteControl (remote)</literal> + window has been replaced by the content of the + <literal>/ajaxPortlet.JSFAJAXPortlet</literal> + imported portlet and the window renamed appropriately: + </para> + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/import_modified_page.png" format="PNG" align="center" valign="middle"/> + </imageobject> + </mediaobject> + </section> + + <section> + <title>Erasing local registration data</title> + <para> + There are rare cases where it might be required to erase the local information without being able to + deregister first. This is the case when a consumer is registered with a producer that has been modified by + its administrator to not require registration anymore. If that ever was to happen (most likely, it won't), + you can erase the local registration information from the consumer so that it can resume interacting with + the remote producer. To do so, click on "Erase local registration" button next to the registration context + information on the consumer configuration screen: + </para> + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/erase_registration.png" format="PNG" align="center" valign="middle"/> + </imageobject> + </mediaobject> + <para> + <emphasis>Warning:</emphasis> + This operation is dangerous as it can result in inability to interact with the remote producer if invoked + when not required. A warning screen will be displayed to give you a chance to change your mind: + </para> + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/erase_registration_warning.png" format="PNG" align="center" + valign="middle"/> + </imageobject> + </mediaobject> + </section> + </section> + + <section id="producer_config"> + <title>Configuring JBoss Enterprise Portal Platform's WSRP Producer</title> + <section> + <title>Overview</title> + <para> + The preferred way to configure the behavior of Portal's WSRP Producer is via the WSRP configuration portlet. + Alternatively, it is possible to add an XML file called + <filename>wsrp-producer-config.xml</filename> + in the + <filename>$JBOSS_PROFILE_HOME/conf/gatein/</filename> + directory. + Several aspects can be modified with respects to whether registration is required for consumers to access + the Producer's services. + <note> + <para>An XML Schema defining which elements are available to configure Consumers via XML can be found + in + <filename> + $JBOSS_PROFILE_HOME/deploy/gatein-wsrp-integration.ear/lib/wsrp-integration-api-$WSRP_VERSION.jar/xsd/gatein_wsrp_producer_1_0.xsd + </filename> + </para> + </note> + <important> + <para> + It is important to note that once the XML configuration file for the producer has been read upon + the WSRP service first start, the associated information is put under control of JCR (Java Content + Repository). Subsequent launches of the WSRP service will use the JCR-stored information and ignore + the content of the XML configuration file. + </para> + </important> + <note> + <para> + The default configuration file for the producer can be found at + <filename>$JBOSS_PROFILE_HOME/deploy/gatein-wsrp-integration.ear/lib/extension-component-$WSRP_VERSION.jar/conf/wsrp-producer-config.xml</filename> + </para> + </note> + </para> + </section> + <section> + <title>Default configuration</title> + <para> + The default producer configuration is to require that consumers register with it before providing access its + services but does not require any specific registration properties (apart from what is mandated by the + WSRP standard). It does, however, require consumers to be registered before sending them a full service + description. This means that our WSRP producer will not provide the list of offered portlets and other + capabilities to unregistered consumers. The producer also uses the default + <classname>RegistrationPolicy</classname> + paired with the default + <classname>RegistrationPropertyValidator</classname>. We will look into property + validators in greater detail later in<xref linkend="registration-configuration"/>. Suffice to say for now + that this allows users to customize how Portal's WSRP Producer decides whether a given registration property + is valid or not. + </para> + <para> + JBoss Enterprise Portal Platform provides a web interface to configure the producer's behavior. You can access it + by clicking on the "Producer Configuration" tab of the "WSRP" page of the "admin" portal. Here's what you + should see with the default configuration: + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/producer_default.png" format="PNG" align="center" valign="middle" + scalefit="1"/> + </imageobject> + </mediaobject> + As would be expected, you can specify whether or not the producer will send the full service description to + unregistered consumers, and, if it requires registration, which + <classname>RegistrationPolicy</classname> + to use (and, if needed, which + <classname>RegistrationPropertyValidator</classname>), along with required + registration property description for which consumers must provide acceptable values to successfully + register. + </para> + <para>New in JBoss Enterprise Portal Platform, we now display the WSDL URLs to access JBoss Enterprise Portal Platform's WSRP producer either in WSRP 1 + or WSRP 2 mode. + </para> + </section> + + <section id="registration-configuration"> + <title>Registration configuration</title> + <para> + In order to require consumers to register with Portal's producer before interacting with it, you need to + configure Portal's behavior with respect to registration. Registration is optional, as are registration + properties. The producer can require registration without requiring consumers to pass any registration + properties as is the case in the default configuration. Let's configure our producer starting with a blank + state: + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/producer_blank.png" format="PNG" align="center" valign="middle" + scalefit="1"/> + </imageobject> + </mediaobject> + We will allow unregistered consumers to see the list of offered portlets so we leave the first checkbox + ("Access to full service description requires consumers to be registered.") unchecked. We will, however, + specify that consumers will need to be registered to be able to interact with our producer. Check the second + checkbox ("Requires registration. Modifying this information will trigger invalidation of consumer + registrations."). The screen should now refresh and display: + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/producer_registration.png" format="PNG" align="center" + valign="middle" scalefit="1"/> + </imageobject> + </mediaobject> + You can specify the fully-qualified name for your + <classname>RegistrationPolicy</classname> + and + <classname>RegistrationPropertyValidator</classname> + there. We will keep the default value. See + <xref linkend="custom_registration"/> + for more details. Let's add, however, a registration property called + <literal>email</literal>. Click "Add property" and enter the appropriate information in the fields, + providing a description for the registration property that can be used by consumers to figure out its + purpose: + <mediaobject> + <imageobject> + <imagedata fileref="images/WSRP/producer_email.png" format="PNG" align="center" valign="middle" + scalefit="1"/> + </imageobject> + </mediaobject> + Press "Save" to record your modifications. + + <note> + <para>At this time, only String (xsd:string) properties are supported. If your application requires more + complex properties, please let us know. + </para> + </note> + + <note> + <para>If consumers are already registered with the producer, modifying the configuration of required + registration + information will trigger the invalidation of held registrations, requiring consumers to modify their + registration before being able to access the producer again. We saw the consumer side of that process + in + <xref linkend="reg_mod_error"/>. + </para> + + </note> + </para> + + <section id="custom_registration"> + <title>Customization of Registration handling behavior</title> + <para> + Registration handling behavior can be customized by users to suit their Producer needs. This is + accomplished by providing an implementation of the + <classname>RegistrationPolicy</classname> + interface. This interface defines methods that are called by Portal's Registration service so that + decisions can be made appropriately. A default registration policy that provides basic + behavior is provided and should be enough for most user needs. + </para> + <para> + While the default registration policy provides default behavior for most registration-related aspects, + there is still one aspect that requires configuration: whether a given value for a registration property + is acceptable by the WSRP Producer. This is accomplished by plugging a + <classname>RegistrationPropertyValidator</classname> + in the default registration policy. This allows users to define their own validation mechanism. + </para> + <para> + Please refer to the + <trademark class="trade">Javadoc</trademark> + for + <classname>org.gatein.registration.RegistrationPolicy</classname> + and + <classname>org.gatein.registration.policies.RegistrationPropertyValidator</classname> + for more + details on what is expected of each method. + </para> + <para>Defining a registration policy is required for the producer to be correctly configured. This is + accomplished by specifying the qualified class name of the registration policy. Since we anticipate that + most users will use the default registration policy, it is possible to provide the class + name of your custom property validator instead to customize the default registration policy behavior. + Note that property validators are only used by the default policy. + + <note> + <para>Since the policy or the validator are defined via their class name and dynamically loaded, it is + important that you make sure that the identified class is available to the application server. One + way + to accomplish that is to deploy your policy implementation as JAR file in your AS instance deploy + directory. Note also that, since both policies and validators are dynamically instantiated, they + must + provide a default, no-argument constructor. + </para> + </note> + </para> + </section> + </section> + <section id="strict-mode"> + <title>WSRP validation mode</title> + <para>The lack of conformance kit and the wording of the WSRP specification leaves room for differing + interpretations, resulting in interoperability issues. It is therefore possible to encounter issues when + using consumers from different vendors. We have experienced such issues and have introduced a way to relax + the validation that our WSRP producer performs on the data provided by consumers to help with + interoperability by accepting data that would normally be invalid. Note that we only relax our validation + algorithm on aspects of the specification that are deemed harmless such as invalid language codes. + </para> + <para> + By default, the WSRP producer is configured in strict mode. If you experience issues with a given consumer, + you might want to try to relax the validation mode. This is accomplished by unchecking the "Use strict WSRP + compliance." checkbox on the Producer configuration screen. + </para> + </section> + + </section> +</chapter>

13 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-commits November 2011