[exo-jcr-commits] exo-jcr SVN: r2883 - jcr/branches/1.12.x/docs/reference/en/src/main/docbook/en-US/modules/core.
do-not-reply at jboss.org
do-not-reply at jboss.org
Thu Aug 5 07:14:22 EDT 2010
Author: sergiykarpenko
Date: 2010-08-05 07:14:22 -0400 (Thu, 05 Aug 2010)
New Revision: 2883
Modified:
jcr/branches/1.12.x/docs/reference/en/src/main/docbook/en-US/modules/core/core.xml
jcr/branches/1.12.x/docs/reference/en/src/main/docbook/en-US/modules/core/ldap-configuration.xml
jcr/branches/1.12.x/docs/reference/en/src/main/docbook/en-US/modules/core/organization-service-listener.xml
jcr/branches/1.12.x/docs/reference/en/src/main/docbook/en-US/modules/core/organization-service.xml
jcr/branches/1.12.x/docs/reference/en/src/main/docbook/en-US/modules/core/security-service.xml
jcr/branches/1.12.x/docs/reference/en/src/main/docbook/en-US/modules/core/spring-security-integration.xml
Log:
EXOJCR-869: link fixes
Modified: jcr/branches/1.12.x/docs/reference/en/src/main/docbook/en-US/modules/core/core.xml
===================================================================
--- jcr/branches/1.12.x/docs/reference/en/src/main/docbook/en-US/modules/core/core.xml 2010-08-05 10:29:53 UTC (rev 2882)
+++ jcr/branches/1.12.x/docs/reference/en/src/main/docbook/en-US/modules/core/core.xml 2010-08-05 11:14:22 UTC (rev 2883)
@@ -13,8 +13,6 @@
products and modules, it also can be used in the business logic.</para>
<para>It's Authentication and Security, Organization, Database, Logging,
- JNDI, LDAP, Document reader and other services. Find more on <ulink
- url="http://wiki.exoplatform.org/xwiki/bin/view/Core/">eXo
- site</ulink></para>
+ JNDI, LDAP, Document reader and other services.</para>
</section>
</chapter>
Modified: jcr/branches/1.12.x/docs/reference/en/src/main/docbook/en-US/modules/core/ldap-configuration.xml
===================================================================
--- jcr/branches/1.12.x/docs/reference/en/src/main/docbook/en-US/modules/core/ldap-configuration.xml 2010-08-05 10:29:53 UTC (rev 2882)
+++ jcr/branches/1.12.x/docs/reference/en/src/main/docbook/en-US/modules/core/ldap-configuration.xml 2010-08-05 11:14:22 UTC (rev 2883)
@@ -3,6 +3,7 @@
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
<chapter id="Core.LDAPConfiguration">
<?dbhtml filename="ch-ldap-configuration.html"?>
+
<title>LDAP Configuration</title>
<section>
@@ -91,10 +92,9 @@
<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="JNDI API>http://java.sun.com/products/jndi">JNDI
- API>http://java.sun.com/products/jndi</ulink> context parameters.
- This configuration is activated by the init-param ldap.config of service
- LDAPServiceImpl.</para>
+ <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.</para>
<programlisting><component>
<key>org.exoplatform.services.ldap.LDAPService</key>
@@ -120,7 +120,7 @@
<listitem>
<para><emphasis role="bold">providerURL</emphasis>: LDAP server URL
(see <ulink
- url="PROVIDER_URL>http://java.sun.com/products/jndi/1.2/javadoc/javax/naming/Context.html#PROVIDER_URL">PROVIDER_URL>http://java.sun.com/products/jndi/1.2/javadoc/javax/naming/Context.html#PROVIDER_URL</ulink>).
+ url="http://java.sun.com/products/jndi/1.2/javadoc/javax/naming/Context.html#PROVIDER_URL">PROVIDER_URL</ulink>).
For multiple ldap servers, use comma separated list of host:port
(Ex. ldap://127.0.0.1:389,10.0.0.1:389).</para>
</listitem>
@@ -128,33 +128,33 @@
<listitem>
<para><emphasis role="bold">rootdn</emphasis>: dn of user that will
be used by the service to authenticate on the server (see <ulink
- url="SECURITY_PRINCIPAL>http://java.sun.com/products/jndi/1.2/javadoc/javax/naming/Context.html#SECURITY_PRINCIPAL">SECURITY_PRINCIPAL>http://java.sun.com/products/jndi/1.2/javadoc/javax/naming/Context.html#SECURITY_PRINCIPAL</ulink>).</para>
+ url="http://java.sun.com/products/jndi/1.2/javadoc/javax/naming/Context.html#SECURITY_PRINCIPAL">SECURITY_PRINCIPAL</ulink>).</para>
</listitem>
<listitem>
<para><emphasis role="bold">password</emphasis>: password for user
rootdn (see <ulink
- url="SECURITY_CREDENTIALS>http://java.sun.com/products/jndi/1.2/javadoc/javax/naming/Context.html#SECURITY_CREDENTIALS">SECURITY_CREDENTIALS>http://java.sun.com/products/jndi/1.2/javadoc/javax/naming/Context.html#SECURITY_CREDENTIALS</ulink>).</para>
+ url="http://java.sun.com/products/jndi/1.2/javadoc/javax/naming/Context.html#SECURITY_CREDENTIALS">SECURITY_CREDENTIALS</ulink>).</para>
</listitem>
<listitem>
<para><emphasis role="bold">authenticationType</emphasis>: type of
authentication to be used (see <ulink
- url="SECURITY_AUTHENTICATION>http://java.sun.com/products/jndi/1.2/javadoc/javax/naming/Context.html#SECURITY_AUTHENTICATION">SECURITY_AUTHENTICATION>http://java.sun.com/products/jndi/1.2/javadoc/javax/naming/Context.html#SECURITY_AUTHENTICATION</ulink>).
+ url="http://java.sun.com/products/jndi/1.2/javadoc/javax/naming/Context.html#SECURITY_AUTHENTICATION">SECURITY_AUTHENTICATION</ulink>).
Use one of none, simple, strong. Default is simple.</para>
</listitem>
<listitem>
<para><emphasis role="bold">version</emphasis>: LDAP protocol
version (see <ulink
- url="java.naming.ldap.version>http://java.sun.com/products/jndi/tutorial/ldap/misc/version.html">java.naming.ldap.version>http://java.sun.com/products/jndi/tutorial/ldap/misc/version.html</ulink>).
+ url="http://java.sun.com/products/jndi/tutorial/ldap/misc/version.html">java.naming.ldap.version</ulink>).
Set to 3 if your server supports LDAP V3.</para>
</listitem>
<listitem>
<para><emphasis role="bold">referalMode</emphasis>: one of follow,
ignore,throw (see <ulink
- url="REFERRAL>http://java.sun.com/products/jndi/1.2/javadoc/javax/naming/Context.html#REFERRAL">REFERRAL>http://java.sun.com/products/jndi/1.2/javadoc/javax/naming/Context.html#REFERRAL</ulink>).</para>
+ url="http://java.sun.com/products/jndi/1.2/javadoc/javax/naming/Context.html#REFERRAL">REFERRAL</ulink>).</para>
</listitem>
<listitem>
@@ -247,14 +247,14 @@
</listitem>
</itemizedlist>
- <para>Example : </para>
+ <para>Example :</para>
<programlisting>uid=john,cn=People,o=MyCompany,c=com</programlisting>
<para>However, if users exist deeply under userURL, eXo will be able
to retrieve them.</para>
- <para>Example : </para>
+ <para>Example :</para>
<programlisting>uid=tom,ou=France,ou=EMEA,cn=People,o=MyCompany,c=com</programlisting>
@@ -548,7 +548,7 @@
the given objectClass attributes. The classes must at least define the
attribute designated by membershipTypeMemberValue.</para>
- <para>Example : Adding membership validator would produce : </para>
+ <para>Example : Adding membership validator would produce :</para>
<programlisting>cn=validator,ou=human-resources,ou=groups,ou=portal,dc=exoplatform,dc=org
objectclass: top
@@ -780,12 +780,10 @@
<title>OpenLDAP dynlist overlays</title>
<para>If you use OpenLDAP, you may want to use the <ulink
- url="overlays > http://www.openldap.org/faq/data/cache/1169.html">overlays
- > http://www.openldap.org/faq/data/cache/1169.html</ulink>. Here is
- how you can use the <ulink
- url="dynlist overlay > http://www.openldap.org/faq/data/cache/1209.html">dynlist
- overlay > http://www.openldap.org/faq/data/cache/1209.html</ulink> to
- have memberships dynamically populated.</para>
+ 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.</para>
<para>The main idea is to have your memberships populated dynamically by
an ldap query. Thus, you no longer have to maintain manually the roles
Modified: jcr/branches/1.12.x/docs/reference/en/src/main/docbook/en-US/modules/core/organization-service-listener.xml
===================================================================
--- jcr/branches/1.12.x/docs/reference/en/src/main/docbook/en-US/modules/core/organization-service-listener.xml 2010-08-05 10:29:53 UTC (rev 2882)
+++ jcr/branches/1.12.x/docs/reference/en/src/main/docbook/en-US/modules/core/organization-service-listener.xml 2010-08-05 11:14:22 UTC (rev 2883)
@@ -3,14 +3,14 @@
"hp://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
<chapter id="Core.OrganizationListener">
<?dbhtml filename="ch-organization-service-listener.html"?>
+
<title>Organization Listener</title>
<section>
<title>Overview</title>
- <para>The <link linkend="CoreOrganizationService">Organization
- Service</link>The Core Organization Service provides a mechanism to
- receive notifications when :</para>
+ <para>The <link linkend="Core.OrganizationService">Organization
+ Service</link> provides a mechanism to receive notifications when :</para>
<itemizedlist>
<listitem>
@@ -141,8 +141,8 @@
<para>Registering the listeners is then achieved by using the ExoContainer
plugin mechanism. Learn more about it on the <link
- linkend="KernelServiceConfigurationForBeginners">Service Configuration for
- Beginners</link> article.</para>
+ linkend="Kernel.ServiceConfigurationforBeginners">Service Configuration
+ for Beginners</link> article.</para>
<para>To effectively register organization service's listeners you simply
need to use the <>addListenerPlugin</> seer injector.</para>
Modified: jcr/branches/1.12.x/docs/reference/en/src/main/docbook/en-US/modules/core/organization-service.xml
===================================================================
--- jcr/branches/1.12.x/docs/reference/en/src/main/docbook/en-US/modules/core/organization-service.xml 2010-08-05 10:29:53 UTC (rev 2882)
+++ jcr/branches/1.12.x/docs/reference/en/src/main/docbook/en-US/modules/core/organization-service.xml 2010-08-05 11:14:22 UTC (rev 2883)
@@ -1,149 +1,149 @@
-<?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">
-<chapter id="Core.OrganizationService">
- <?dbhtml filename="ch-organization-service-listener.html"?>
- <title>Organization Service</title>
-
- <section id="Overview">
- <title>Overview</title>
-
- <para>OrganizationService is the service that allows to access the
- Organization model. This model is composed of :</para>
-
- <itemizedlist>
- <listitem>
- <para>Users</para>
- </listitem>
-
- <listitem>
- <para>Groups</para>
- </listitem>
-
- <listitem>
- <para>Memberships</para>
- </listitem>
- </itemizedlist>
-
- <para>It is the basis of eXo personalization and authorizations in eXo and
- is used allover the platform. The model is abstract and does not rely on
- any specific storage. Multiple implementations exist in exo :</para>
-
- <itemizedlist>
- <listitem>
- <para>hibernate : for storage into a RDBMS</para>
- </listitem>
-
- <listitem>
- <para>jndi : for storage into a directory such as an LDAP or MS Active
- Directory</para>
- </listitem>
-
- <listitem>
- <para>jcr : for storage inside a Java Content Repository</para>
- </listitem>
- </itemizedlist>
- </section>
-
- <section>
- <title>Organizational Model</title>
-
- <section>
- <title>User</title>
-
- <itemizedlist>
- <listitem>
- <para>username used as the identified</para>
- </listitem>
-
- <listitem>
- <para>Profile (identity and preferences)</para>
- </listitem>
- </itemizedlist>
- </section>
-
- <section>
- <title>Group</title>
-
- <para>Gather a set of users</para>
-
- <itemizedlist>
- <listitem>
- <para>applicative or business</para>
- </listitem>
-
- <listitem>
- <para>tree structure</para>
- </listitem>
-
- <listitem>
- <para>no inheritance</para>
- </listitem>
-
- <listitem>
- <para>expressed as /group/subgroup/subsubgroup</para>
- </listitem>
- </itemizedlist>
- </section>
-
- <section>
- <title>Membership</title>
-
- <itemizedlist>
- <listitem>
- <para>qualifies the group belonging</para>
- </listitem>
-
- <listitem>
- <para>"Member of group as XXX"</para>
- </listitem>
-
- <listitem>
- <para>expressed as : manager:/organization/hr, *:/partners</para>
- </listitem>
- </itemizedlist>
- </section>
- </section>
-
- <section>
- <title>Related articles and how-tos</title>
-
- <itemizedlist>
- <listitem>
- <para><ulink
- url="http://wiki.exoplatform.org/xwiki/bin/view/JCR/Organization+Service">JCR
- Organization Service</ulink></para>
- </listitem>
- </itemizedlist>
-
- <itemizedlist>
- <listitem>
- <para><ulink
- url="http://wiki.exoplatform.org/xwiki/bin/view/Core/Update+ConversationState+when+user's+Membership+changed">Update
- ConversationState when user's Membership changed</ulink></para>
- </listitem>
-
- <listitem>
- <para><ulink url="Organization Service Initializer">Organization
- Service Initializer</ulink></para>
- </listitem>
-
- <listitem>
- <para><ulink
- url="http://wiki.exoplatform.org/xwiki/bin/view/Portal/Accessing+User+Profile">How
- to Access User Profile in your code</ulink></para>
- </listitem>
-
- <listitem>
- <para><ulink url="CoreOrganizationListener">How to create your own
- Organization Listener</ulink></para>
- </listitem>
-
- <listitem>
- <para><ulink
- url="How to manipulate Users and Memberships Programmatically">How to
- manipulate Users and Memberships Programmatically</ulink></para>
- </listitem>
- </itemizedlist>
- </section>
-</chapter>
+<?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">
+<chapter id="Core.OrganizationService">
+ <?dbhtml filename="ch-organization-service.html"?>
+ <title>Organization Service</title>
+
+ <section id="Overview">
+ <title>Overview</title>
+
+ <para>OrganizationService is the service that allows to access the
+ Organization model. This model is composed of :</para>
+
+ <itemizedlist>
+ <listitem>
+ <para>Users</para>
+ </listitem>
+
+ <listitem>
+ <para>Groups</para>
+ </listitem>
+
+ <listitem>
+ <para>Memberships</para>
+ </listitem>
+ </itemizedlist>
+
+ <para>It is the basis of eXo personalization and authorizations in eXo and
+ is used allover the platform. The model is abstract and does not rely on
+ any specific storage. Multiple implementations exist in exo :</para>
+
+ <itemizedlist>
+ <listitem>
+ <para>hibernate : for storage into a RDBMS</para>
+ </listitem>
+
+ <listitem>
+ <para>jndi : for storage into a directory such as an LDAP or MS Active
+ Directory</para>
+ </listitem>
+
+ <listitem>
+ <para>jcr : for storage inside a Java Content Repository</para>
+ </listitem>
+ </itemizedlist>
+ </section>
+
+ <section>
+ <title>Organizational Model</title>
+
+ <section>
+ <title>User</title>
+
+ <itemizedlist>
+ <listitem>
+ <para>username used as the identified</para>
+ </listitem>
+
+ <listitem>
+ <para>Profile (identity and preferences)</para>
+ </listitem>
+ </itemizedlist>
+ </section>
+
+ <section>
+ <title>Group</title>
+
+ <para>Gather a set of users</para>
+
+ <itemizedlist>
+ <listitem>
+ <para>applicative or business</para>
+ </listitem>
+
+ <listitem>
+ <para>tree structure</para>
+ </listitem>
+
+ <listitem>
+ <para>no inheritance</para>
+ </listitem>
+
+ <listitem>
+ <para>expressed as /group/subgroup/subsubgroup</para>
+ </listitem>
+ </itemizedlist>
+ </section>
+
+ <section>
+ <title>Membership</title>
+
+ <itemizedlist>
+ <listitem>
+ <para>qualifies the group belonging</para>
+ </listitem>
+
+ <listitem>
+ <para>"Member of group as XXX"</para>
+ </listitem>
+
+ <listitem>
+ <para>expressed as : manager:/organization/hr, *:/partners</para>
+ </listitem>
+ </itemizedlist>
+ </section>
+ </section>
+
+ <section>
+ <title>Related articles and how-tos</title>
+
+ <itemizedlist>
+ <listitem>
+ <para><ulink
+ url="http://wiki.exoplatform.org/xwiki/bin/view/JCR/Organization+Service">JCR
+ Organization Service</ulink></para>
+ </listitem>
+ </itemizedlist>
+
+ <itemizedlist>
+ <listitem>
+ <para><ulink
+ url="http://wiki.exoplatform.org/xwiki/bin/view/Core/Update+ConversationState+when+user's+Membership+changed">Update
+ ConversationState when user's Membership changed</ulink></para>
+ </listitem>
+
+ <listitem>
+ <para><ulink url="Organization Service Initializer">Organization
+ Service Initializer</ulink></para>
+ </listitem>
+
+ <listitem>
+ <para><ulink
+ url="http://wiki.exoplatform.org/xwiki/bin/view/Portal/Accessing+User+Profile">How
+ to Access User Profile in your code</ulink></para>
+ </listitem>
+
+ <listitem>
+ <para><ulink url="CoreOrganizationListener">How to create your own
+ Organization Listener</ulink></para>
+ </listitem>
+
+ <listitem>
+ <para><ulink
+ url="How to manipulate Users and Memberships Programmatically">How to
+ manipulate Users and Memberships Programmatically</ulink></para>
+ </listitem>
+ </itemizedlist>
+ </section>
+</chapter>
Modified: jcr/branches/1.12.x/docs/reference/en/src/main/docbook/en-US/modules/core/security-service.xml
===================================================================
--- jcr/branches/1.12.x/docs/reference/en/src/main/docbook/en-US/modules/core/security-service.xml 2010-08-05 10:29:53 UTC (rev 2882)
+++ jcr/branches/1.12.x/docs/reference/en/src/main/docbook/en-US/modules/core/security-service.xml 2010-08-05 11:14:22 UTC (rev 2883)
@@ -3,6 +3,7 @@
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
<chapter id="Core.SecurityService">
<?dbhtml filename="ch-security-service.html"?>
+
<title>Security Service</title>
<section>
@@ -14,8 +15,8 @@
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="Java Tutorial>http://java.sun.com/j2se/1.5.0/docs/guide/security/jaas/tutorials/GeneralAcnAndAzn.html">Java
- Tutorial>http://java.sun.com/j2se/1.5.0/docs/guide/security/jaas/tutorials/GeneralAcnAndAzn.html</ulink></para>
+ url="http://java.sun.com/j2se/1.5.0/docs/guide/security/jaas/tutorials/GeneralAcnAndAzn.html">Java
+ Tutorial</ulink></para>
</section>
<section>
@@ -120,7 +121,6 @@
* @throws Exception
*/
Identity createIdentity(String userId) throws Exception;
-
}</programlisting>
<para>It is up to the application developer (and deployer) whether to
@@ -260,9 +260,6 @@
appropriate AS. In particular, we have dedicated Login modules for
Tomcat, JBoss, Jonas and WebSphere.</para>
- <para><emphasis role="bold">TODO: configuration examples for Tomcat,
- JBoss, Jonas and WebSphere</emphasis></para>
-
<para>Besides that, for the case when third party authentication
mechanism required, we have <emphasis
role="bold">org.exoplatform.services.security.jaas.IdentitySetLoginModule</emphasis>,
Modified: jcr/branches/1.12.x/docs/reference/en/src/main/docbook/en-US/modules/core/spring-security-integration.xml
===================================================================
--- jcr/branches/1.12.x/docs/reference/en/src/main/docbook/en-US/modules/core/spring-security-integration.xml 2010-08-05 10:29:53 UTC (rev 2882)
+++ jcr/branches/1.12.x/docs/reference/en/src/main/docbook/en-US/modules/core/spring-security-integration.xml 2010-08-05 11:14:22 UTC (rev 2883)
@@ -3,6 +3,7 @@
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
<chapter id="Core.SpringSecurityIntegration">
<?dbhtml filename="ch-spring-security-integration.html"?>
+
<title>Spring Security Integration</title>
<section>
More information about the exo-jcr-commits
mailing list