jon 01/05/27 13:25:50
Modified: docs install.html services.html
docs/howto tdk-howto.html
xdocs services.xml
Added: docs/howto ldap-howto.html
xdocs/howto ldap-howto.xml
Log:
added ldap-howto based on email from "Frank W. Nolden"
<[EMAIL PROTECTED]>
Revision Changes Path
1.44 +23 -5 jakarta-turbine/docs/install.html
Index: install.html
===================================================================
RCS file: /home/cvs/jakarta-turbine/docs/install.html,v
retrieving revision 1.43
retrieving revision 1.44
diff -u -r1.43 -r1.44
--- install.html 2001/05/20 01:27:59 1.43
+++ install.html 2001/05/27 20:25:49 1.44
@@ -141,6 +141,24 @@
<table
border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
+ <a name="Installing Ant"><strong>Installing Ant</strong></a>
+ </font>
+ </td></tr>
+ <tr><td><br/></td></tr>
+ <tr><td>
+ <blockquote>
+ <p>
+See the <a href="http://jakarta.apache.org/ant/manual/install.html";>Ant
+documentation</a> for instructions.
+</p>
+ </blockquote>
+ </p>
+ </td></tr>
+ <tr><td><br/></td></tr>
+ </table>
+ <table border="0" cellspacing="0"
cellpadding="2" width="100%">
+ <tr><td bgcolor="#525D76">
+ <font color="#ffffff" face="arial,helvetica,sanserif">
<a name="Ant Tasks available in build.xml"><strong>Ant Tasks available in
build.xml</strong></a>
</font>
</td></tr>
@@ -148,17 +166,17 @@
<tr><td>
<blockquote>
<p>
-The build-turbine.xml contains many Ant tasks. These are run by typing from the
command line;
+The <code>build.xml</code> contains many Ant tasks. These are run by
+typing from the command line:
<ul>
- build taskname
+ ant <taskname>
</ul>
-for example, to run the task which generates the turbine-pool.jar type;
+For example, to run the task which generates the turbine-pool.jar type;
<ul>
- build pool
-</ul>
+ ant <pool></ul>
</p>
<p>
Other Ant tasks in build.xml include;
1.39 +6 -1 jakarta-turbine/docs/services.html
Index: services.html
===================================================================
RCS file: /home/cvs/jakarta-turbine/docs/services.html,v
retrieving revision 1.38
retrieving revision 1.39
diff -u -r1.38 -r1.39
--- services.html 2001/05/20 23:50:57 1.38
+++ services.html 2001/05/27 20:25:49 1.39
@@ -15,6 +15,8 @@
<meta name="email" value="[EMAIL PROTECTED]">
<meta name="author" value="Jason van Zyl">
<meta name="email" value="[EMAIL PROTECTED]">
+ <meta name="author" value="Jon S. Stevens">
+ <meta name="email" value="[EMAIL PROTECTED]">
<title>Turbine - Turbine Services</title>
</head>
@@ -175,7 +177,10 @@
</p>
<p>
The services available with Turbine can be found in the
-org.apache.turbine.services package. These include;
+org.apache.turbine.services package. <strong>Please note that the
+[TODO]'s below simply mean that these services need more complete
+documentation, it does not mean that they are still waiting to be
+implemented.</strong>
</p>
<ul>
<li>
1.12 +1 -1 jakarta-turbine/docs/howto/tdk-howto.html
Index: tdk-howto.html
===================================================================
RCS file: /home/cvs/jakarta-turbine/docs/howto/tdk-howto.html,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- tdk-howto.html 2001/05/21 00:09:34 1.11
+++ tdk-howto.html 2001/05/27 20:25:49 1.12
@@ -302,7 +302,7 @@
</td>
<td bgcolor="#a0ddf0" colspan="" rowspan=""
valign="top" align="left">
<font color="#000000" size="-1" face="arial,helvetica,sanserif">
- ??
+ MySQL
</font>
</td>
<td bgcolor="#a0ddf0" colspan="" rowspan=""
valign="top" align="left">
1.1 jakarta-turbine/docs/howto/ldap-howto.html
Index: ldap-howto.html
===================================================================
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<!-- Content Stylesheet for Site -->
<!-- start the processing -->
<!-- ====================================================================== -->
<!-- Main Page Section -->
<!-- ====================================================================== -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
<meta name="author" value="Frank
W. Nolden">
<meta name="email" value="[EMAIL PROTECTED]">
<meta name="author" value="Jon S. Stevens">
<meta name="email" value="[EMAIL PROTECTED]">
<title>Turbine - LDAP Howto</title>
</head>
<body bgcolor="#ffffff" text="#000000" link="#525D76">
<table border="0" width="100%" cellspacing="0">
<!-- TOP IMAGE -->
<tr>
<td align="left">
<a href="http://jakarta.apache.org";><img
src="http://jakarta.apache.org/images/jakarta-logo.gif"; border="0"/></a>
</td>
<td align="right">
<a href="http://jakarta.apache.org/turbine/";><img src="../images/logo.gif"
alt="Turbine" border="0"/></a>
</td>
</tr>
</table>
<table border="0" width="100%" cellspacing="4">
<tr><td colspan="2">
<hr noshade="" size="1"/>
</td></tr>
<tr>
<!-- LEFT SIDE NAVIGATION -->
<td valign="top" nowrap="true">
<p><strong>Essentials</strong></p>
<ul>
<li> <a href="../index.html">Overview</a>
</li>
<li> <a href="../features.html">Features</a>
</li>
<li> <a href="../fsd.html">Specification</a>
</li>
<li> <a href="../getting-started.html">Getting Started</a>
</li>
<li> <a href="../further-reading.html">Further Reading</a>
</li>
</ul>
<p><strong>Get Involved</strong></p>
<ul>
<li> <a href="../contributors.html">Contributors</a>
</li>
<li> <a
href="http://jakarta.apache.org/site/cvsindex.html";>CVS Repos</a>
</li>
<li> <a href="../faq.html">FAQ</a>
</li>
<li> <a
href="http://jakarta.apache.org/site/mail.html";>Mailing Lists</a>
</li>
<li> <a href="../powered.html">Powered by Turbine</a>
</li>
<li> <a href="../license.html">License</a>
</li>
<li> <a href="../issue-tracking.html">Issue Tracking</a>
</li>
</ul>
<p><strong>Documentation</strong></p>
<ul>
<li> <a href="../turbine-documentation-project.html">Turbine
Documentation</a>
</li>
<li> <a href="../turbine-schema.html">Core Schema</a>
</li>
<li> <a href="../j2ee-integration.html">J2EE Integration</a>
</li>
<li> <a href="../model2+1.html">Model 2+1</a>
</li>
<li> <a href="../pullmodel.html">Pull MVC Model</a>
</li>
<li> <a href="../services.html">Services</a>
</li>
</ul>
<p><strong>Howto Guides</strong></p>
<ul>
<li> <a href="../howto/action-event-howto.html">Action Events
Howto</a>
</li>
<li> <a href="../howto/criteria-howto.html">Criteria Howto</a>
</li>
<li> <a href="../howto/jboss-howto.html">JBoss Howto</a>
</li>
<li> <a href="../howto/jsp-howto.html">JSP Howto</a>
</li>
<li> <a href="../howto/oracle-howto.html">Oracle 8i Howto</a>
</li>
<li> <a href="../howto/peers-howto.html">Peers Howto</a>
</li>
<li> <a href="../howto/postgres-howto.html">Postgres Howto</a>
</li>
<li> <a href="../howto/python-howto.html">Python Howto</a>
</li>
<li> <a href="../howto/security-howto.html">Security Howto</a>
</li>
<li> <a href="../howto/sybase-howto.html">Sybase Howto</a>
</li>
<li> <a href="../howto/tdk-howto.html">TDK Howto</a>
</li>
<li> <a href="../howto/torque-howto.html">Torque Howto</a>
</li>
<li> <a href="../howto/velocity-site-howto.html">Velocity
Site Howto</a>
</li>
<li> <a href="../howto/context-howto.html">Velocity Context
Howto</a>
</li>
<li> <a href="../howto/webmacro-site-howto.html">Webmacro
Site Howto</a>
</li>
</ul>
<p><strong>Development</strong></p>
<ul>
<li> <a href="../active-developers.html">Active Developers</a>
</li>
<li> <a href="../changes.html">Changes</a>
</li>
<li> <a href="../code-standards.html">Coding Specification</a>
</li>
<li> <a href="../branches.html">CVS Branches</a>
</li>
<li> <a href="../db-adapters.html">DB Adapters</a>
</li>
<li> <a href="../deprecation.html">Deprecation Rules</a>
</li>
<li> <a href="../project-map.html">Project Map</a>
</li>
<li> <a href="../proposals.html">Proposals</a>
</li>
<li> <a href="../todo.html">Todo</a>
</li>
</ul>
</td>
<td align="left" valign="top">
<table
border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="LDAP Details"><strong>LDAP Details</strong></a>
</font>
</td></tr>
<tr><td><br/></td></tr>
<tr><td>
<blockquote>
<p>
These are the details on how we came up with this schema for
putting the user-group-permission tables in an LDAP directory. We want to
start with the fact that for the schema proposed we have taken all new
objectClasses and Attributes preceded by turbine to indicate that they are
Turbine specific. We have thought about using the standard and available
LDAP objectClasses and atributes, but finally decided to start the
discussion with the turbine stuff.
</p>
<p>
We also had to make some assumptions regarding the present use of the
user-group-permission tables. This gave us the following schema:
</p>
</blockquote>
</p>
</td></tr>
<tr><td><br/></td></tr>
</table>
<table border="0" cellspacing="0"
cellpadding="2" width="100%">
<tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="Schema"><strong>Schema</strong></a>
</font>
</td></tr>
<tr><td><br/></td></tr>
<tr><td>
<blockquote>
<div align="left">
<table cellspacing="4" cellpadding="0" border="0">
<tr>
<td bgcolor="#023264" width="1" height="1"><img src="/images/void.gif"
width="1" height="1" vspace="0" hspace="0" border="0"/></td>
<td bgcolor="#023264" height="1"><img src="/images/void.gif" width="1"
height="1" vspace="0" hspace="0" border="0"/></td>
<td bgcolor="#023264" width="1" height="1"><img src="/images/void.gif"
width="1" height="1" vspace="0" hspace="0" border="0"/></td>
</tr>
<tr>
<td bgcolor="#023264" width="1"><img src="/images/void.gif" width="1"
height="1" vspace="0" hspace="0" border="0"/></td>
<td bgcolor="#ffffff"><pre>
-- Attribute types --
( 1000.1.1
NAME 'turbineGroupMember'
DESC ''
EQUALITY caseIgnoreMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.12
)
( 1000.1.2
NAME 'turbineObjectData'
DESC ''
SYNTAX 1.3.6.1.4.1.1466.115.121.1.40
)
( 1000.1.3
NAME 'turbinePermission'
DESC ''
EQUALITY caseIgnoreMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
)
( 1000.1.4
NAME 'turbineRoleMember'
DESC ''
EQUALITY caseIgnoreMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.12
)
( 1000.1.5
NAME 'turbineUserCreationDate'
DESC ''
EQUALITY caseIgnoreMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.53
SINGLE-VALUE
)
( 1000.1.6
NAME 'turbineUserFirstName'
DESC ''
EQUALITY caseIgnoreMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
)
( 1000.1.7
NAME 'turbineUserLastLogon'
DESC ''
EQUALITY caseIgnoreMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.53
SINGLE-VALUE
)
( 1000.1.8
NAME 'turbineUserLastModifiedTime'
DESC ''
EQUALITY caseIgnoreMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.53
SINGLE-VALUE
)
( 1000.1.9
NAME 'turbineUserLastName'
DESC ''
EQUALITY caseIgnoreMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
)
( 1000.1.10
NAME 'turbineUserMailAddress'
DESC ''
EQUALITY caseIgnoreIA5Match
SYNTAX 1.3.6.1.4.1.1466.115.121.1.26
)
( 1000.1.11
NAME 'turbineUserPassword'
DESC ''
EQUALITY caseExactMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
SINGLE-VALUE
)
( 1000.1.12
NAME 'turbineUserUniqueId'
DESC ''
EQUALITY caseIgnoreMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
SINGLE-VALUE
)
-- Object classes --
( 1000.2.1
NAME 'turbineGroup'
DESC 'Turbine group'
SUP top
AUXILIARY
MAY ( turbineGroupMember $ turbineObjectData )
)
( 1000.2.2
NAME 'turbineRole'
DESC 'Turbine role'
SUP top
AUXILIARY
MAY ( turbineObjectData $ turbinePermission $ turbineRoleMember )
)
( 1000.2.3
NAME 'turbineUser'
DESC 'Turbine user'
SUP top
AUXILIARY
MUST ( turbineUserUniqueId )
MAY ( turbineObjectData $ turbineUserCreationDate $ turbineUserFirstName $
turbineUserLastLogon $ turbineUserLastModifiedTime $ turbineUserLastName $
turbineUserMailAddress $ turbineUserPassword )
)
</pre></td>
<td bgcolor="#023264" width="1"><img src="/images/void.gif" width="1"
height="1" vspace="0" hspace="0" border="0"/></td>
</tr>
<tr>
<td bgcolor="#023264" width="1" height="1"><img src="/images/void.gif"
width="1" height="1" vspace="0" hspace="0" border="0"/></td>
<td bgcolor="#023264" height="1"><img src="/images/void.gif" width="1"
height="1" vspace="0" hspace="0" border="0"/></td>
<td bgcolor="#023264" width="1" height="1"><img src="/images/void.gif"
width="1" height="1" vspace="0" hspace="0" border="0"/></td>
</tr>
</table>
</div>
</blockquote>
</p>
</td></tr>
<tr><td><br/></td></tr>
</table>
<table border="0" cellspacing="0"
cellpadding="2" width="100%">
<tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="More Details"><strong>More Details</strong></a>
</font>
</td></tr>
<tr><td><br/></td></tr>
<tr><td>
<blockquote>
<p>
We have turbineRole that can have many turbinePermission entries. These
are DN pointing to the turbinePermission objects. turbineUser will hold
all user related information. turbineGroup can hold in the
turbineGroupMember DNs of turbineUser objects. Thus having multiple
users being member of a group. There is however no relation with role at
this stage. The releation role - user is stored in the turbineRole
having multiple DNs in turbineRoleMember. Then we have a user - role
relation thus giving user permission via roles they can perform. There
is no relation between role - user - group in one record. This could be
possible with the DB model, but we could you put this dependancy in the
hierarchical structure of a directory. With the separate user - role and
user - group relations we thought we'd have the most desired relations.
</p>
<p>
Please note that the Object Identifiers (OID) in this example are not
real ones. When we go for the turbine objectClasses and attributes
Turbine (or Apache) have to register (if they not already have) their
own OID starting point in the IANA tree. We are fully open for dicussion
and appreciate your feedback on the mailing list.
</p>
</blockquote>
</p>
</td></tr>
<tr><td><br/></td></tr>
</table>
</td>
</tr>
<!-- FOOTER -->
<tr><td colspan="2">
<hr noshade="" size="1"/>
</td></tr>
<tr><td colspan="2">
<div align="center"><font color="#525D76" size="-1"><em>
Copyright © 1999-2001, Apache Software Foundation
</em></font></div>
</td></tr>
</table>
</body>
</html>
<!-- end the processing -->
1.17 +5 -1 jakarta-turbine/xdocs/services.xml
Index: services.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine/xdocs/services.xml,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- services.xml 2001/05/20 23:51:00 1.16
+++ services.xml 2001/05/27 20:25:50 1.17
@@ -5,6 +5,7 @@
<title>Turbine Services</title>
<author email="[EMAIL PROTECTED]">Cameron Riley</author>
<author email="[EMAIL PROTECTED]">Jason van Zyl</author>
+ <author email="[EMAIL PROTECTED]">Jon S. Stevens</author>
</properties>
<body>
@@ -40,7 +41,10 @@
<p>
The services available with Turbine can be found in the
-org.apache.turbine.services package. These include;
+org.apache.turbine.services package. <strong>Please note that the
+[TODO]'s below simply mean that these services need more complete
+documentation, it does not mean that they are still waiting to be
+implemented.</strong>
</p>
<ul>
1.1 jakarta-turbine/xdocs/howto/ldap-howto.xml
Index: ldap-howto.xml
===================================================================
<?xml version="1.0"?>
<document>
<properties>
<title>LDAP Howto</title>
<author email="[EMAIL PROTECTED]">Frank W. Nolden</author>
<author email="[EMAIL PROTECTED]">Jon S. Stevens</author>
</properties>
<body>
<section name="LDAP Details">
<p>
These are the details on how we came up with this schema for
putting the user-group-permission tables in an LDAP directory. We want to
start with the fact that for the schema proposed we have taken all new
objectClasses and Attributes preceded by turbine to indicate that they are
Turbine specific. We have thought about using the standard and available
LDAP objectClasses and atributes, but finally decided to start the
discussion with the turbine stuff.
</p>
<p>
We also had to make some assumptions regarding the present use of the
user-group-permission tables. This gave us the following schema:
</p>
</section>
<section name="Schema">
<source>
-- Attribute types --
( 1000.1.1
NAME 'turbineGroupMember'
DESC ''
EQUALITY caseIgnoreMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.12
)
( 1000.1.2
NAME 'turbineObjectData'
DESC ''
SYNTAX 1.3.6.1.4.1.1466.115.121.1.40
)
( 1000.1.3
NAME 'turbinePermission'
DESC ''
EQUALITY caseIgnoreMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
)
( 1000.1.4
NAME 'turbineRoleMember'
DESC ''
EQUALITY caseIgnoreMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.12
)
( 1000.1.5
NAME 'turbineUserCreationDate'
DESC ''
EQUALITY caseIgnoreMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.53
SINGLE-VALUE
)
( 1000.1.6
NAME 'turbineUserFirstName'
DESC ''
EQUALITY caseIgnoreMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
)
( 1000.1.7
NAME 'turbineUserLastLogon'
DESC ''
EQUALITY caseIgnoreMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.53
SINGLE-VALUE
)
( 1000.1.8
NAME 'turbineUserLastModifiedTime'
DESC ''
EQUALITY caseIgnoreMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.53
SINGLE-VALUE
)
( 1000.1.9
NAME 'turbineUserLastName'
DESC ''
EQUALITY caseIgnoreMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
)
( 1000.1.10
NAME 'turbineUserMailAddress'
DESC ''
EQUALITY caseIgnoreIA5Match
SYNTAX 1.3.6.1.4.1.1466.115.121.1.26
)
( 1000.1.11
NAME 'turbineUserPassword'
DESC ''
EQUALITY caseExactMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
SINGLE-VALUE
)
( 1000.1.12
NAME 'turbineUserUniqueId'
DESC ''
EQUALITY caseIgnoreMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.15
SINGLE-VALUE
)
-- Object classes --
( 1000.2.1
NAME 'turbineGroup'
DESC 'Turbine group'
SUP top
AUXILIARY
MAY ( turbineGroupMember $ turbineObjectData )
)
( 1000.2.2
NAME 'turbineRole'
DESC 'Turbine role'
SUP top
AUXILIARY
MAY ( turbineObjectData $ turbinePermission $ turbineRoleMember )
)
( 1000.2.3
NAME 'turbineUser'
DESC 'Turbine user'
SUP top
AUXILIARY
MUST ( turbineUserUniqueId )
MAY ( turbineObjectData $ turbineUserCreationDate $ turbineUserFirstName $
turbineUserLastLogon $ turbineUserLastModifiedTime $ turbineUserLastName $
turbineUserMailAddress $ turbineUserPassword )
)
</source>
</section>
<section name="More Details">
<p>
We have turbineRole that can have many turbinePermission entries. These
are DN pointing to the turbinePermission objects. turbineUser will hold
all user related information. turbineGroup can hold in the
turbineGroupMember DNs of turbineUser objects. Thus having multiple
users being member of a group. There is however no relation with role at
this stage. The releation role - user is stored in the turbineRole
having multiple DNs in turbineRoleMember. Then we have a user - role
relation thus giving user permission via roles they can perform. There
is no relation between role - user - group in one record. This could be
possible with the DB model, but we could you put this dependancy in the
hierarchical structure of a directory. With the separate user - role and
user - group relations we thought we'd have the most desired relations.
</p>
<p>
Please note that the Object Identifiers (OID) in this example are not
real ones. When we go for the turbine objectClasses and attributes
Turbine (or Apache) have to register (if they not already have) their
own OID starting point in the IANA tree. We are fully open for dicussion
and appreciate your feedback on the mailing list.
</p>
</section>
</body>
</document>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
![http://jakarta.apache.org/images/jakarta-logo.gif"](http://jakarta.apache.org/images/jakarta-logo.gif"){kind=link}
