From do-not-reply at jboss.org Thu Aug 19 13:18:41 2010
Content-Type: multipart/mixed; boundary="===============8720941262327894231=="
MIME-Version: 1.0
From: do-not-reply at jboss.org
To: exo-jcr-commits at lists.jboss.org
Subject: [exo-jcr-commits] exo-jcr SVN: r2956 -
jcr/trunk/docs/reference/en/src/main/docbook/en-US/modules/kernel.
Date: Thu, 19 Aug 2010 13:18:40 -0400
Message-ID: <201008191718.o7JHIeqU006978@svn01.web.mwc.hst.phx2.redhat.com>
--===============8720941262327894231==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Author: nfilotto
Date: 2010-08-19 13:18:39 -0400 (Thu, 19 Aug 2010)
New Revision: 2956
Modified:
jcr/trunk/docs/reference/en/src/main/docbook/en-US/modules/kernel/config=
uration.xml
Log:
EXOJCR-842: commit patch (doc part)
Modified: jcr/trunk/docs/reference/en/src/main/docbook/en-US/modules/kernel=
/configuration.xml
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- jcr/trunk/docs/reference/en/src/main/docbook/en-US/modules/kernel/confi=
guration.xml 2010-08-19 17:17:55 UTC (rev 2955)
+++ jcr/trunk/docs/reference/en/src/main/docbook/en-US/modules/kernel/confi=
guration.xml 2010-08-19 17:18:39 UTC (rev 2956)
@@ -1148,7 +1148,7 @@
PortalContainerDefinition must be a class of type
PortalContainerDefinitionChange. The product prop=
oses
out of the box some implementations that we describe in the next=
sub
- sections.
+ sections.
=
AddDependencies
@@ -1451,6 +1451,71 @@
+
+
+ Disable dynamically a portal container
+
+ It is possible to use component-plugin elemen=
ts
+ in order to dynamically disable one or several portal containers. =
In
+ the example below, we disable the portal container named
+ foo:
+
+ <external-component-plugins>
+ <!-- The full qualified name of the PortalContainerConfig -->
+ <target-component>org.exoplatform.container.definition.PortalConta=
inerConfig</target-component>
+ <component-plugin>
+ <!-- The name of the plugin -->
+ <name>Disable a PortalContainer</name>
+ <!-- The name of the method to call on the PortalContainerConfig in=
order to register the changes on the PortalContainerDefinitions -->
+ <set-method>registerDisablePlugin</set-method>
+ <!-- The full qualified name of the PortalContainerDefinitionDisabl=
ePlugin -->
+ <type>org.exoplatform.container.definition.PortalContainerDefini=
tionDisablePlugin</type>
+ <init-params>
+ <!-- The list of the name of the portal containers to disable --&=
gt;
+ <values-param>
+ <name>names</name>
+ <value>foo</value>
+ </values-param>
+ </init-params>
+ </component-plugin>
+</external-component-plugins>
+
+
+ Descriptions of the fields of a
+ PortalContainerDefinitionDisablePlugin
+
+
+
+
+ names
+
+ The list of the name of the portal containers to
+ disable.
+
+
+
+
+
+ To prevent any accesses to a web application corresponding to
+ PortalContainer that has been disabled, you need to
+ make sure that the following Http Filter (or a sub class of it) has
+ been added to your web.xml in first position as below:
+
+ <filter>
+ <filter-name>PortalContainerFilter</filter-name>
+ <filter-class>org.exoplatform.container.web.PortalContainerFilter&=
lt;/filter-class>
+</filter> =
+
+<filter-mapping>
+ <filter-name>PortalContainerFilter</filter-name>
+ <url-pattern>/*</url-pattern>
+</filter-mapping>
+
+
+ It is only possible to disable a portal container when at
+ least one PortalContainerDefinition has been registered.
+
+
=
--===============8720941262327894231==--