jvanzyl 01/05/12 21:29:30
Modified: xdocs action-event.xml branches.xml building.xml
code-standards.xml contributors.xml db-adapters.xml
faq.xml features.xml fsd.xml
getting-started-tdk.xml index.xml license.xml
model2+1.xml powered.xml security.xml services.xml
turbine-schema.xml
xdocs/howto jboss-howto.xml
Removed: xdocs advcriteria.xml advpeers.xml context-howto.xml
jboss-tdk.xml jsp-configuration.xml
oracle-howto.xml other-docs.xml peers.xml
postgres-howto.xml python.xml summit.xml
sybase-howto.xml torque.xml velocity-site.xml
webmacro-site.xml
Log:
- changing links to reflect movement of howto type xdocs to a directory
specifically for cookbook/howto type documents.
- attributing credit for docs where i could remember who contributed
to a particular document.
- made a first pass at some corrections and amalgamation of duplicate
information.
i am going to start doing some heavy reworking/editing of the docs
to correct errors and try to get a cohesive feel to the documentation
for the 2.1 release.
Revision Changes Path
1.5 +4 -4 jakarta-turbine/xdocs/action-event.xml
Index: action-event.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine/xdocs/action-event.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- action-event.xml 2001/01/22 00:20:07 1.4
+++ action-event.xml 2001/05/13 04:29:08 1.5
@@ -4,7 +4,7 @@
<properties>
<title>Action Events</title>
- <author email="[EMAIL PROTECTED]">Turbine Documentation Team</author>
+ <author email="[EMAIL PROTECTED]">Jon S. Stevens</author>
</properties>
<body>
@@ -17,9 +17,9 @@
need to be familiar with the way that Turbine handles Actions. What happens
is that when a URI has the action= variable defined, a class is executed
before all of your other Screen classes by your Page class. So, consider
-the following URI
-(I'm using the <a href="velocity-site.html">VelocitySite</a>
-example):
+the following URI (I'm using the <a href="velocity-site-howto.html">
+VelocitySite Howto
+</a> example):
</p>
<p>
1.6 +2 -2 jakarta-turbine/xdocs/branches.xml
Index: branches.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine/xdocs/branches.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- branches.xml 2001/05/05 01:30:44 1.5
+++ branches.xml 2001/05/13 04:29:09 1.6
@@ -3,8 +3,8 @@
<document>
<properties>
- <title>Turbine CVS Branches</title>
- <author email="[EMAIL PROTECTED]">Turbine Documentation Team</author>
+ <title>Turbine CVS Branches</title>
+ <author email="[EMAIL PROTECTED]">Rafal Krzewski</author>
</properties>
<body>
1.5 +7 -3 jakarta-turbine/xdocs/building.xml
Index: building.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine/xdocs/building.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- building.xml 2001/03/05 17:37:53 1.4
+++ building.xml 2001/05/13 04:29:09 1.5
@@ -4,7 +4,7 @@
<properties>
<title>Misc. Build Instructions</title>
- <author email="[EMAIL PROTECTED]">Turbine Documentation Team</author>
+ <author email="[EMAIL PROTECTED]">Jon S. Stevens</author>
</properties>
<body>
@@ -17,14 +17,18 @@
<li>Go to the turbine/conf directory.</li>
<li>Edit any of the properties in turbine/conf/master/meta.properties,
or alternatively set those properties in your own .ant.properties.</li>
- <li>Run ./build-conf.sh.</li>
+ <li>Run ./build.sh.</li>
+ <li>
+ Or you can run <strong>ant</strong> if you have
+ an installed version of Ant.
+ </li>
</ol>
</p>
</section>
<section name="Torque">
<p>
For instructions on building Torque, see
- <a href="torque.html">this document</a>.
+ <a href="howto/torque-howto.html">this document</a>.
</p>
</section>
1.10 +4 -6 jakarta-turbine/xdocs/code-standards.xml
Index: code-standards.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine/xdocs/code-standards.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- code-standards.xml 2001/04/30 22:24:38 1.9
+++ code-standards.xml 2001/05/13 04:29:10 1.10
@@ -4,7 +4,8 @@
<properties>
<title>Coding Standards</title>
- <author email="[EMAIL PROTECTED]">Turbine Documentation Team</author>
+ <author email="[EMAIL PROTECTED]">Jon S. Stevens</author>
+ <author email="[EMAIL PROTECTED]">Jason van Zyl</author>
</properties>
<body>
@@ -112,7 +113,8 @@
<p>
7. If you contribute to a file (code or documentation), add yourself to the
-top of the file. For java files the preferred Javadoc format is:
+authors list at the top of the file. For java files the
+preferred Javadoc format is:
</p>
<source><![CDATA[
@@ -175,10 +177,6 @@
<p>
Thanks for your cooperation.
-</p>
-
-<p>
--The Turbine Team
</p>
</section>
1.20 +1 -1 jakarta-turbine/xdocs/contributors.xml
Index: contributors.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine/xdocs/contributors.xml,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- contributors.xml 2001/04/07 07:35:52 1.19
+++ contributors.xml 2001/05/13 04:29:11 1.20
@@ -4,7 +4,7 @@
<properties>
<title>Turbine Contributors</title>
- <author email="[EMAIL PROTECTED]">Turbine Documentation Team</author>
+ <author email="[EMAIL PROTECTED]">Jon S. Stevens</author>
</properties>
<body>
1.6 +1 -1 jakarta-turbine/xdocs/db-adapters.xml
Index: db-adapters.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine/xdocs/db-adapters.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- db-adapters.xml 2001/03/23 00:15:13 1.5
+++ db-adapters.xml 2001/05/13 04:29:11 1.6
@@ -4,7 +4,7 @@
<properties>
<title>DB Adapters</title>
- <author email="[EMAIL PROTECTED]">Turbine Documentation Team</author>
+ <author email="[EMAIL PROTECTED]">Jon S. Stevens</author>
</properties>
<body>
1.5 +1 -1 jakarta-turbine/xdocs/faq.xml
Index: faq.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine/xdocs/faq.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- faq.xml 2001/01/22 00:20:07 1.4
+++ faq.xml 2001/05/13 04:29:12 1.5
@@ -4,7 +4,7 @@
<properties>
<title>Turbine FAQ</title>
- <author email="[EMAIL PROTECTED]">Turbine Documentation Team</author>
+ <author email="[EMAIL PROTECTED]">Jason van Zyl</author>
</properties>
<body>
1.6 +8 -9 jakarta-turbine/xdocs/features.xml
Index: features.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine/xdocs/features.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- features.xml 2001/01/22 00:20:07 1.5
+++ features.xml 2001/05/13 04:29:12 1.6
@@ -4,7 +4,8 @@
<properties>
<title>Turbine Features</title>
- <author email="[EMAIL PROTECTED]">Turbine Documentation Team</author>
+ <author email="[EMAIL PROTECTED]">Jon S. Stevens</author>
+ <author email="[EMAIL PROTECTED]">Jason van Zyl</author>
</properties>
<body>
@@ -27,14 +28,15 @@
<p>
<strong>All of these features have been made possible thanks to the over
-20 developers (and growing all the time!) who have <a href="contributors.html">
+30 developers (and growing all the time!) who have <a href="contributors.html">
contributed</a> to Turbine over the last 2+ years.</strong>
</p>
<ul>
<li>
- Integration with template systems: Velocity, WebMacro, Cocoon,
- FreeMarker, JSP, ECS</li>
+ Integration with template systems: Velocity, WebMacro,
+ FreeMarker, JSP
+ </li>
<li>
Utility code for working with Velocity and WebMacro, such as a
SelectorBox class for building <select> boxes</li>
@@ -51,13 +53,10 @@
Strict MVC guidelines implemented through many interfaces and abstract
classes as well as through the template systems.</li>
<li>
- Integration with 5 Object-Relational tools: DatabaseMap/Peers, Village,
- Town, OPaL, <a href="http://castor.exolab.org";>Castor</a></li>
+ Object-Relational tools: DatabaseMap/Peers, Village,
+ <a href="http://castor.exolab.org";>Castor</a>.</li>
<li>
IDBroker that abstracts the autoinsert/sequence usage from the database</li>
- <li>
- DatabaseMap generation tool that will read a schema and generate the Java
- classes for you</li>
<li>
Failsafe Job based scheduler system (ie: a Java based cron)</li>
<li>
1.5 +1 -1 jakarta-turbine/xdocs/fsd.xml
Index: fsd.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine/xdocs/fsd.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- fsd.xml 2001/03/05 17:26:23 1.4
+++ fsd.xml 2001/05/13 04:29:13 1.5
@@ -4,7 +4,7 @@
<properties>
<title>Turbine Specification</title>
- <author email="[EMAIL PROTECTED]">Turbine Documentation Team</author>
+ <author email="[EMAIL PROTECTED]">Jon S. Stevens</author>
</properties>
<body>
1.4 +6 -6 jakarta-turbine/xdocs/getting-started-tdk.xml
Index: getting-started-tdk.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine/xdocs/getting-started-tdk.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- getting-started-tdk.xml 2001/05/11 13:35:26 1.3
+++ getting-started-tdk.xml 2001/05/13 04:29:13 1.4
@@ -113,7 +113,7 @@
<source><![CDATA[
-./newapp.sh NEWAPP
+./build.sh
]]></source>
@@ -175,7 +175,7 @@
Look at the example app that you now have on your screen. The view that you are
seeing actually consists of 4 different parts (top, bottom, menu and index) that
were assembled for you on the fly by Velocity. In order to see how this works,
-you have to edit the file "webapps/APPNAME/templates/layouts/Default.vm" This
+you have to edit the file "webapps/APPNAME/templates/app/layouts/Default.vm" This
file defines how the default layout is shown on your screen. As you can see,
it is written as a fragment of HTML that will eventually be integrated into your
final page. Editing this file will affect the layout of your entire
@@ -184,7 +184,7 @@
<p>
Knowing now how the page is laid out, go to the directory
-"webapps/APPNAME/templates/navigations" to see the files that will be inserted
+"webapps/APPNAME/templates/app/navigations" to see the files that will be inserted
into the layout template above. Edit the file "DefaultBottom.vm", save your
changes back, and reload your page. By doing this you should see whatever
changes you have made to the file appear at the bottom of your layout. This
@@ -193,7 +193,7 @@
</p>
<p>
-Now go into the directory "webapps/APPNAME/templates/screens" The files in this
+Now go into the directory "webapps/APPNAME/templates/app/screens" The files in this
directory are the ones that replace the "$screen_placeholder" variable in
the original layout. Open up the file "Index.vm" and you will see that a
variable is defined called "$headings" that holds the strings for each of the
@@ -202,7 +202,7 @@
file that is associated with this .vm page, as explained in the next paragraph.
The Index.vm page also includes a number of functions that begin with #, such as
"#entryCell(...)" These functions are replaced with HTML fragments at runtime,
-as defined in the "webapps/APPNAME/templates/GlobalMacros.vm" file. Look at
+as defined in the "webapps/APPNAME/templates/app/GlobalMacros.vm" file. Look at
this file to get an idea of what each of these methods do. This file can be
edited in order to add your own velocity macros to the system as well.
</p>
@@ -220,7 +220,7 @@
handle for it into our session context so that it can be accessed from our
Index.vm page. You would edit this file to change the behavior of a given
page. More information on building sites with Velocity is available
-<a href="velocity-site.html">here.</a>
+<a href="howto/velocity-site-howto.html">here.</a>
</p>
</section>
1.15 +1 -1 jakarta-turbine/xdocs/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine/xdocs/index.xml,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- index.xml 2001/05/12 09:02:34 1.14
+++ index.xml 2001/05/13 04:29:13 1.15
@@ -4,7 +4,7 @@
<properties>
<title>Turbine</title>
- <author email="[EMAIL PROTECTED]">Turbine Documentation Team</author>
+ <author email="[EMAIL PROTECTED]">Jon S. Stevens</author>
</properties>
<body>
1.6 +1 -1 jakarta-turbine/xdocs/license.xml
Index: license.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine/xdocs/license.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- license.xml 2001/03/20 22:42:53 1.5
+++ license.xml 2001/05/13 04:29:14 1.6
@@ -3,7 +3,7 @@
<document>
<properties>
<title>Apache Software License</title>
- <author email="[EMAIL PROTECTED]">Turbine Documentation Team</author>
+ <author email="[EMAIL PROTECTED]">Jason van Zyl</author>
</properties>
<body>
1.3 +1 -1 jakarta-turbine/xdocs/model2+1.xml
Index: model2+1.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine/xdocs/model2+1.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- model2+1.xml 2001/01/22 00:20:08 1.2
+++ model2+1.xml 2001/05/13 04:29:14 1.3
@@ -3,7 +3,7 @@
<document>
<properties>
<title>Turbine Model 2+1</title>
- <author email="[EMAIL PROTECTED]">Turbine Documentation Team</author>
+ <author email="[EMAIL PROTECTED]">Jon S. Stevens</author>
</properties>
<body>
1.13 +1 -1 jakarta-turbine/xdocs/powered.xml
Index: powered.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine/xdocs/powered.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- powered.xml 2001/05/04 00:50:04 1.12
+++ powered.xml 2001/05/13 04:29:17 1.13
@@ -3,7 +3,7 @@
<document>
<properties>
<title>Turbine powered web sites</title>
- <author email="[EMAIL PROTECTED]">Turbine Documentation Team</author>
+ <author email="[EMAIL PROTECTED]">Jon S. Stevens</author>
</properties>
<body>
1.3 +46 -12 jakarta-turbine/xdocs/security.xml
Index: security.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine/xdocs/security.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- security.xml 2001/04/18 13:49:18 1.2
+++ security.xml 2001/05/13 04:29:18 1.3
@@ -8,13 +8,11 @@
<body>
-
-<!-- opening blurb -->
-
<section name="Turbine Security">
<p>
-The Turbine Security includes a <a href="services/security-service.html">Security
Service</a> as well as Actions and Screens that can be extended in the Templating
Services.
+The Turbine Security includes a <a href="services/security-service.html">Security
Service</a>
+as well as Actions and Screens that can be extended in the Templating Services.
</p>
</section>
@@ -26,7 +24,10 @@
<section name="Users, Groups, Roles and Permissions">
<p>
-The default Relational Database schema that Turbine uses for the database security
service, and which the TDK is generated with upon initialisation, includes the data
structure for the managing of permissions. The default or core schema can be viewed at;
+The default Relational Database schema that Turbine uses for the database security
+service, and which the TDK is generated with upon initialisation, includes the
+data structure for the managing of permissions.
+The default or core schema can be viewed at;
</p>
<p>
@@ -34,7 +35,17 @@
</p>
<p>
-The main tables are TURBINE_GROUP, TURBINE_USER, TURBINE_ROLE and
TURBINE_PERMISSION. The Permissions are the individual actions a user is allowed to
take in the system. The Role is a container for the Permissions, in other words a Role
can be made of many Permissions. User is an account that is interaction with the
System and the Group is a something that a User would want to do something in. In the
Turbine mailing lists it has often been described in the same way as a project. In a
project you have fulfill a role, however a User doesnt "belong" to a project they
merely have a role in that project ( or group ). In this manner too a User can have
many Roles within the one Group. For instance a User may have the Role Developer in
the Group, but may also have the Role of Administrator as well. While initially
confusing at first, as there are no group-user or role-user containers, it is a
flexible system and strong system.
+The main tables are TURBINE_GROUP, TURBINE_USER, TURBINE_ROLE and
TURBINE_PERMISSION.
+The Permissions are the individual actions a user is allowed to take in the system.
+The Role is a container for the Permissions, in other words a Role can be made of
+many Permissions. User is an account that is interaction with the System and the
Group
+is a something that a User would want to do something in. In the Turbine mailing
lists
+it has often been described in the same way as a project. In a project you have
fulfill
+a role, however a User doesnt "belong" to a project they merely have a role in that
+project ( or group ). In this manner too a User can have many Roles within the one
+Group. For instance a User may have the Role Developer in the Group, but may also
have
+the Role of Administrator as well. While initially confusing at first, as there
+are no group-user or role-user containers, it is a flexible system and strong
system.
</p>
</section>
@@ -43,7 +54,10 @@
<section name="Access Control Lists">
<p>
-A User's interaction through the system is controlled by the Permissions they are
able to partake in. The AccessControlLists manage this information and present it via
RunData and User Interfaces to the application. The RunData interface through the
getACL() method presents the AccessControlList Object.
+A User's interaction through the system is controlled by the Permissions they are
+able to partake in. The AccessControlLists manage this information and present it
via
+RunData and User Interfaces to the application. The RunData interface through the
+getACL() method presents the AccessControlList Object.
</p>
<source>
@@ -68,7 +82,13 @@
</source>
<p>
-This will check if the User has permission to view this in the Global Group which
is useful for managing Anonymous Users as well as logged in Users across your
application. If however you need stronger security, such as only allowing users that
have logged in, and have a Role in a specific Group, the Permission will need to be
matched to the Group and User. As an example, assume one of your groups is
"Accounting" and the Invoice information is only to be viewed by Usersthat have a Role
in Accounting as well as the Permission "viewinvoice", the above method would be
re-written;
+This will check if the User has permission to view this in the Global Group which
+is useful for managing Anonymous Users as well as logged in Users across your
+application. If however you need stronger security, such as only allowing users
that
+have logged in, and have a Role in a specific Group, the Permission will need to be
+matched to the Group and User. As an example, assume one of your groups is
"Accounting"
+and the Invoice information is only to be viewed by Usersthat have a Role in
Accounting
+as well as the Permission "viewinvoice", the above method would be re-written;
</p>
<source><![CDATA[
@@ -99,7 +119,9 @@
]]></source>
<p>
-If instead the Permission could be across any of the Roles the User has, the method
acl.hasPermission(String permission, GroupSet groups), can be used. As always check
the Javadocs for more detail.
+If instead the Permission could be across any of the Roles the User has, the
+method acl.hasPermission(String permission, GroupSet groups), can be used. As
+always check the Javadocs for more detail.
</p>
@@ -109,7 +131,12 @@
<section name="Templates and Logging In">
<p>
-Managing Anonymous Users and Logged In Users poses problems in applications for
managing the Secure/Strong parts of the application and the Unsecure/Weak parts of the
application. In Turbine, the Action and Screen components make managing this process
quite simple. Assume the only Velocity Template allowed to be viewed without being
logged in is the actual Login.vm template. As this is the only Screen that needs to be
Unsecure/Weak we can manage this via the parent of Login Screen.
+Managing Anonymous Users and Logged In Users poses problems in applications for
managing
+the Secure/Strong parts of the application and the Unsecure/Weak parts of the
+application. In Turbine, the Action and Screen components make managing this
process
+quite simple. Assume the only Velocity Template allowed to be viewed without being
+logged in is the actual Login.vm template. As this is the only Screen that
+needs to be Unsecure/Weak we can manage this via the parent of Login Screen.
</p>
@@ -157,7 +184,9 @@
</source>
<p>
-Note that there is nothing in that method which checks that the User has logged in.
On the other hand, for the Secure or Strong Actions and Screens we would want a check
to ensure that the User has logged in.
+Note that there is nothing in that method which checks that the User has logged in.
+On the other hand, for the Secure or Strong Actions and Screens we would want a
+check to ensure that the User has logged in.
</p>
<source>
@@ -213,7 +242,12 @@
<p>
-In the latter example, before the Screen populates the Context it will check for
the User being logged in by the doBuildTemplate(data) method in the parent. If the
test fails, the context isnt created for the Invoice screen. Another way to manage
this is to seperate the screens into two packages,
com.mycompany.modules.screens.unsecure and com.mycompany.modules.screens.secure and
have a Default.java Screen in each of the packages mimicing the above approaches.
+In the latter example, before the Screen populates the Context it will check for
the
+User being logged in by the doBuildTemplate(data) method in the parent. If the test
+fails, the context isnt created for the Invoice screen. Another way to manage this
+is to seperate the screens into two packages,
com.mycompany.modules.screens.unsecure
+and com.mycompany.modules.screens.secure and have a Default.java Screen in each
+of the packages mimicing the above approaches.
</p>
</section>
1.14 +69 -23 jakarta-turbine/xdocs/services.xml
Index: services.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine/xdocs/services.xml,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- services.xml 2001/04/23 20:13:40 1.13
+++ services.xml 2001/05/13 04:29:18 1.14
@@ -46,11 +46,14 @@
<blockquote>
<p><li>
-<a href="services/assemblerbroker-service.html">Assembler Broker Service</a> - Is
the Service which allows assemblers such as Screens, Actions, Layout and Scheduled
Jobs to be loaded.
+<a href="services/assemblerbroker-service.html">Assembler Broker Service</a>
+- Is the Service which allows assemblers such as Screens, Actions, Layout and
+Scheduled Jobs to be loaded.
</li></p>
<p><li>
-<a href="services/cache-service.html">Cache Service</a> - Provides a persistant
Object Storage mechanism within your application.
+<a href="services/cache-service.html">Cache Service</a>
+- Provides a persistant Object Storage mechanism within your application.
</li></p>
<p><li>
@@ -58,11 +61,15 @@
</li></p>
<p><li>
-<a href="services/db-service.html">DB Service</a> - <b>[TO DO
(PoolBrokerService)]</b> Is a common front end to all database systems. This service
also provides the brokers for Connection Pooling and Database Map Objects.
+<a href="services/db-service.html">DB Service</a>
+- <b>[TO DO (PoolBrokerService)]</b> Is a common front end to all database systems.
+This service also provides the brokers for Connection Pooling and Database Map
Objects.
</li></p>
<p><li>
-<a href="services/factory-service.html">Factory Service</a> - A Service for the
instantiation of objects with either the specified loaders or default class loaders.
+<a href="services/factory-service.html">Factory Service</a>
+- A Service for the instantiation of objects with either the specified loaders or
+default class loaders.
</li></p>
<p><li>
@@ -75,79 +82,118 @@
</li></p>
<p><li>
-<a href="services/jsp-service.html">JSP Service</a> - <b>[TO DO]</b> The JSP
Service is the set of classes that process JSP files inside the Turbine
Layout/Navigations and Screen structure.
+<a href="services/jsp-service.html">JSP Service</a>
+- <b>[TO DO]</b> The JSP Service is the set of classes that process JSP
+files inside the Turbine Layout/Navigations and Screen structure.
</li></p>
<p><li>
-<a href="services/localization-service.html">Localization Service</a> - The single
point of access to all localization resources.
+<a href="services/localization-service.html">Localization Service</a>
+- The single point of access to all localization resources.
</li></p>
<p><li>
-<a href="services/logging-service.html">Logging Service</a> - <b>[TO DO]</b> The
default Loggin implementation for Turbine, logging can be either through an explicite
getLogger() method or by standard printing methods such as info or debug.
+<a href="services/logging-service.html">Logging Service</a>
+- <b>[TO DO]</b> The default Loggin implementation for Turbine, logging can
+be either through an explicite getLogger() method or by standard printing methods
+such as info or debug.
</li></p>
<p><li>
-<a href="services/mimetype-service.html">MimeType Service</a> - The service
maintains the mappings between MIME types and corresponding file name extensions as
well as between locales and character encoding.
+<a href="services/mimetype-service.html">MimeType Service</a>
+- The service maintains the mappings between MIME types and corresponding file
+name extensions as well as between locales and character encoding.
</li></p>
<p><li>
-<a href="services/naming-service.html">Naming Service</a> - <b>[TO DO]</b> Provides
JNDI naming contexts.
+<a href="services/naming-service.html">Naming Service</a>
+- <b>[TO DO]</b> Provides JNDI naming contexts.
</li></p>
<p><li>
-<a href="services/pool-service.html">Pool Service</a> - A service for the pooling
of instantiated Objects, allowing for the recycling and disposal of Objects in the
pool.
+<a href="services/pool-service.html">Pool Service</a>
+- A service for the pooling of instantiated Objects, allowing for the recycling
+and disposal of Objects in the pool.
</li></p>
<p><li>
-<a href="services/pull-service.html">Pull Service</a> - Manages the creation of
application tools that are available to all templates in a Turbine application. The
tools can have global scope, request scope, session scope or persistant scope within
your application.
+<a href="services/pull-service.html">Pull Service</a> -
+Manages the creation of application tools that are available to all templates
+in a Turbine application. The tools can have global scope, request scope, session
+scope or persistant scope within your application.
</li></p>
<p><li>
-<a href="services/resources-service.html">Resources Service</a> - <b>[TO DO
(Configuration)]</b> The Resources Service is the set of classes and the functionality
that allows for the reading and acccessing data from within properties files.
+<a href="services/resources-service.html">Resources Service</a>
+- <b>[TO DO (Configuration)]</b> The Resources Service is the set of classes and
+the functionality that allows for the reading and acccessing data
+from within properties files.
</li></p>
<p><li>
-<a href="services/rundata-service.html">RunData Service</a> - Is the Service which
manages the higher level operations surrounding requests and responses.
+<a href="services/rundata-service.html">RunData Service</a>
+- Is the Service which manages the higher level operations surrounding
+requests and responses.
</li></p>
<p><li>
-<a href="services/scheduler-service.html">Scheduler Service</a> - This service
manages the schedule queue giving Cron like functionality. The ScheduledJob can be
stored in a database or a properties file.
+<a href="services/scheduler-service.html">Scheduler Service</a>
+- This service manages the schedule queue giving Cron like functionality.
+The ScheduledJob can be stored in a database or a properties file.
</li></p>
<p><li>
-<a href="services/security-service.html">Security Service</a> - <b>[TO DO]</b> A
service for the management of Users, Groups, Roles and Permissions in the system,
allowing for those Objects to interact with either Database or LDAP backends. The
service also allows for the security to be managed without a backend.
+<a href="services/security-service.html">Security Service</a>
+- <b>[TO DO]</b> A service for the management of Users, Groups, Roles and
Permissions
+in the system, allowing for those Objects to interact with either
+Database or LDAP backends. The service also allows for the security to be managed
+without a backend.
</li></p>
<p><li>
-<a href="services/servlet-service.html">Servlet Service</a> - Encapsulates the
information provided by the ServletContext API, and makes it available from anywhere
in the code.
+<a href="services/servlet-service.html">Servlet Service</a>
+- Encapsulates the information provided by the ServletContext API,
+and makes it available from anywhere in the code.
</li></p>
<p><li>
-<a href="services/template-service.html">Template Service</a> - <b>[TO DO]</b> The
Service for the mapping of templates to their screens and actions.
+<a href="services/template-service.html">Template Service</a>
+- <b>[TO DO]</b> The Service for the mapping of templates to their
+screens and actions.
</li></p>
<p><li>
-<a href="services/uniqueid-service.html">Unique ID Service</a> - Allows for the
creation of Context unique and pseudo random identifiers.
+<a href="services/uniqueid-service.html">Unique ID Service</a>
+- Allows for the creation of Context unique and pseudo random identifiers.
</li></p>
<p><li>
-<a href="services/upload-service.html">Upload Service</a> - This service manages
multipart/form-data POST requests, storing them temporarily in memory or locally. The
resultant Objects can be manipulated through a FileItem Object.
+<a href="services/upload-service.html">Upload Service</a>
+- This service manages multipart/form-data POST requests, storing them
+temporarily in memory or locally. The resultant Objects can be manipulated through
+a FileItem Object.
</li></p>
<p><li>
-<a href="services/velocity-service.html">Velocity Service</a> - <b>[TO DO]</b> The
service for the processing of Velocity Templates from within the Turbine
Layout/Navigations and Screen structure.
+<a href="services/velocity-service.html">Velocity Service</a>
+- <b>[TO DO]</b> The service for the processing of Velocity Templates from within
+the Turbine Layout/Navigations and Screen structure.
</li></p>
<p><li>
-<a href="services/webmacro-service.html">WebMacro Service</a> - <b>[TO DO]</b> The
service for the processing of WebMacro Templates from within Turbine
Layout/Navigations and Screen structure.
+<a href="services/webmacro-service.html">WebMacro Service</a>
+- <b>[TO DO]</b> The service for the processing of WebMacro Templates from within
+Turbine Layout/Navigations and Screen structure.
</li></p>
<p><li>
-<a href="services/xmlrpc-service.html">XML-RPC Service</a> - <b>[TO DO]</b> This
service manages xml-rpc calls to a remote Server.
+<a href="services/xmlrpc-service.html">XML-RPC Service</a>
+- <b>[TO DO]</b> This service manages xml-rpc calls to a remote Server.
</li></p>
<p><li>
-<a href="services/xslt-service.html">XSLT Service</a> - <b>[TO DO]</b> The service
which is used to transform XML with an XSLT stylesheet.
+<a href="services/xslt-service.html">XSLT Service</a>
+- <b>[TO DO]</b> The service which is used to transform XML with an XSLT
stylesheet.
</li></p>
</blockquote>
1.7 +0 -1 jakarta-turbine/xdocs/turbine-schema.xml
Index: turbine-schema.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine/xdocs/turbine-schema.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- turbine-schema.xml 2001/04/10 18:53:53 1.6
+++ turbine-schema.xml 2001/05/13 04:29:20 1.7
@@ -3,7 +3,6 @@
<document>
<properties>
<title>Turbine Core Schema</title>
- <author email="[EMAIL PROTECTED]">Turbine Documentation Team</author>
<author email="[EMAIL PROTECTED]">Cameron Riley</author>
</properties>
1.2 +0 -1 jakarta-turbine/xdocs/howto/jboss-howto.xml
Index: jboss-howto.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine/xdocs/howto/jboss-howto.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- jboss-howto.xml 2001/05/13 04:21:31 1.1
+++ jboss-howto.xml 2001/05/13 04:29:29 1.2
@@ -12,7 +12,6 @@
<section name="3 Steps to get the Catalina included with TDK to work with
JBoss2.2.1">
<p>
By: <a href="mailto:john NOSPAM murphyfutures.com">John Menke</a><br/>
- $Id: jboss-howto.xml,v 1.1 2001/05/13 04:21:31 jvanzyl Exp $
</p>
<p>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
