kaz 02/03/27 10:53:13
Modified: xdocs j2ee-integration.xml turbine-schema.xml
xdocs/howto torque-howto.xml
xdocs/proposals application-service.xml i18n.xml
naming-service.xml package-cleanup.xml peers.xml
pp.xml reusable-components.xml security-service.xml
services-repository.xml xslt-service.xml
Log:
Formatting changes to make these documents look better with the new look
and feel that has been deployed across the Turbine sites. I'll
continue this process through each of the Turbine subprojects.
Revision Changes Path
1.2 +69 -76 jakarta-turbine-2/xdocs/j2ee-integration.xml
Index: j2ee-integration.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-2/xdocs/j2ee-integration.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- j2ee-integration.xml 16 Aug 2001 05:10:08 -0000 1.1
+++ j2ee-integration.xml 27 Mar 2002 18:53:13 -0000 1.2
@@ -14,27 +14,22 @@
<p>
This document serves to answer a few common questions about integration
-of Turbine with J2EE technologies. The short answer is that it is all
-Java code and you can choose to use Turbine's solutions to some things
-or you can choose to use J2EE solutions to some things. Turbine is
-increasingly flexible about what parts you choose to use and what parts
-you don't. The reason is because there has been quite a lot of de coupling
-of the various Turbine components as a result of years of development
-and use by people all over the world in various different ways. Wow,
-isn't that cool?
-</p>
-
-<subsection name="What is J2EE?">
-
-<p>
-Many Java technology extensions, including - Servlets, EJB, Swing, JMS,
-Transactions, JNDI, XML, JDBC, JSP, Security
-</p>
-
-</subsection>
-
-<subsection name="How does Turbine work with ... Servlets?">
-
+of Turbine with J2EE technologies including Servlets, EJB, Swing, JMS,
+Transactions, JNDI, XML, JDBC, JSP, and Security. The short answer is
+that it is all Java code and you can choose to use Turbine's solutions
+to some things or you can choose to use J2EE solutions to some things.
+Turbine is increasingly flexible about what parts you choose to use and
+what parts you don't. The reason is because there has been quite a lot
+of de coupling of the various Turbine components as a result of years of
+development and use by people all over the world in various different
+ways. Wow, isn't that cool?
+</p>
+
+<subsection name="How does Turbine work with ... ?">
+<table>
+ <tr>
+ <td>Servlets</td>
+ <td>
<p>
It is a servlet. It is also a set of re-usable components assembled into
a framework. You can choose to work with just the Servlet, you can
@@ -45,30 +40,30 @@
done as well, however we have done it in such a way that it is very
pluggable. Mix and match and use what you want to use. Ignore the rest.
</p>
-
-</subsection>
-
-<subsection name="How does Turbine work with ... EJB?">
-
+ </td>
+ </tr>
+ <tr>
+ <td>EJB</td>
+ <td>
<p>
Turbine provides a framework for developing web applications -
specifically the front end. EJB provides a framework for developing
n-tier applications - specifically the back ends - thus Turbine and EJB
complement each other well at that level.
</p>
-
-</subsection>
-
-<subsection name="How does Turbine work with ... Swing?">
-
+ </td>
+ </tr>
+ <tr>
+ <td>Swing</td>
+ <td>
<p>
Turbine is the for the web - Swing is not - not applicable.
</p>
-
-</subsection>
-
-<subsection name="How does Turbine work with ... JMS?">
-
+ </td>
+ </tr>
+ <tr>
+ <td>JMS</td>
+ <td>
<p>
Turbine provides facilities for plugging in other Services - and thus
JMS could be plugged in as a service to that. Even if it isn't plugged
@@ -76,41 +71,41 @@
related methods into your code. Turbine doesn't prevent you from calling
other Java code.
</p>
-
-</subsection>
-
-<subsection name="How does Turbine work with ... Transactions?">
-
+ </td>
+ </tr>
+ <tr>
+ <td>Transactions</td>
+ <td>
<p>
There is nothing in Turbine explicitly using the JTS/JTA - but can use
EJB and hence these technologies. That belongs in EJB's anyways. :-)
</p>
-
-</subsection>
-
-<subsection name="How does Turbine work with ... JNDI?">
-
+ </td>
+ </tr>
+ <tr>
+ <td>JNDI</td>
+ <td>
<p>
Turbine provides access to JNDI via a Service facility. You can always
choose to implement your own facility as well (ie: if you have an
existing code base that you would like to use, Turbine does not stop you
from using it).
</p>
-
-</subsection>
-
-<subsection name="How does Turbine work with ... XML?">
-
+ </td>
+ </tr>
+ <tr>
+ <td>XML</td>
+ <td>
<p>
Turbine provides support for using and working with XML. Again, nothing
preventing you from using XML within Turbine or even sending XML out
of Turbine.
</p>
-
-</subsection>
-
-<subsection name="How does Turbine work with ... JDBC?">
-
+ </td>
+ </tr>
+ <tr>
+ <td>JDBC</td>
+ <td>
<p>
Turbine provides good support for working with JDBC through the <a
href="http://share.whichever.com/village/";>Village API</a>, the <a
@@ -121,11 +116,11 @@
prevent you from using your own Connection pooling mechanism, we simply
created one because at the time, we needed one and ours works just fine.
</p>
-
-</subsection>
-
-<subsection name="How does Turbine work with ... JSP?">
-
+ </td>
+ </tr>
+ <tr>
+ <td>JSP</td>
+ <td>
<p>
Turbine provides excellent support for using JSP in its model of working
- which is based on the Model 2 style with enhancements, such as solving
@@ -133,11 +128,11 @@
href="http://jakarta.apache.org/velocity/ymtd/ymtd.html";>strongly
suggest</a> that you do not use JSP and seek out other alternatives.
</p>
-
-</subsection>
-
-<subsection name="How does Turbine work with ... Security?">
-
+ </td>
+ </tr>
+ <tr>
+ <td>Security</td>
+ <td>
<p>
Turbine was created long before J2EE was created. Therefore, we needed
to implement our own Security Model. This model is based on Users,
@@ -147,35 +142,31 @@
pattern and you can use Turbine's code as the basis for any additional
security your application requires.
</p>
-
-</subsection>
-
-<subsection name="How does Turbine work with ... container managed security?">
-
+ </td>
+ </tr>
+ <tr>
+ <td>Container Managed Security</td>
+ <td>
<p>
You can use container managed security if you wish, and Turbine provides you with
mechanism for application manged security, in case you need them.
</p>
-
<p>
The main problem with container managed security is that it cannot be managed
from the inside of the application. Whenever you want to add/remove users to
your application (or suite of them) or want to modify user's roles, you need
to use whatever tool your application server provides for that.
</p>
-
<p>
Now, this could work just fine for closed-public applications and intranets,
but would be really unacceptable on open-public sites, where the users need
the ability to register and receive 'accounts' without human interaction.
</p>
-
<p>
Currently Turbine supports the latter model - application managed security.
This is because if it didn't have it, many people would have to write code
to provide it. That's why we created SecurityService in a cooperative effort.
</p>
-
<p>
On the other hand, you don't need to write any code to use declarative
container managed security. You can restrict access to the Turbine
@@ -186,7 +177,9 @@
getUserPrincipal</code> and <code>isUserInRole</code> methods.
above.
</p>
-
+ </td>
+ </tr>
+</table>
</subsection>
</section>
1.2 +94 -119 jakarta-turbine-2/xdocs/turbine-schema.xml
Index: turbine-schema.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-2/xdocs/turbine-schema.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- turbine-schema.xml 16 Aug 2001 05:10:10 -0000 1.1
+++ turbine-schema.xml 27 Mar 2002 18:53:13 -0000 1.2
@@ -32,13 +32,11 @@
<section name="Relationships">
<source test=""><![CDATA[
-
TURBINE_USER -|------o-< TURBINE_USER_GROUP_ROLE
TURBINE_ROLE -|------o-< TURBINE_USER_GROUP_ROLE
TURBINE_GROUP -|------o-< TURBINE_USER_GROUP_ROLE
TURBINE_ROLE -|------o-< TURBINE_ROLE_PERMISSION
TURBINE_PERMISSION -|------o-< TURBINE_ROLE_PERMISSION
-
]]></source>
</section>
@@ -49,26 +47,16 @@
the src/sql directory of the Turbine distribution.
</p>
-<p>
-<strong>ID_TABLE</strong>
-</p>
-
-<p>
-The ID_TABLE carries the information for the next ID
-number in the specified tables. This table is useful when
-the database being used has no data-type which carries out
-auto-increment operations.
-</p>
-
+<subsection name="ID_TABLE">
<table>
<tr>
- <td>Column Name</td>
- <td>Key</td>
- <td>Data Type</td>
- <td>Default Value</td>
- <td>Null</td>
- <td>Indexed</td>
- <td>Comment</td>
+ <th>Column Name</th>
+ <th>Key</th>
+ <th>Data Type</th>
+ <th>Default Value</th>
+ <th>Null</th>
+ <th>Indexed</th>
+ <th>Comment</th>
</tr>
<tr>
<td>ID_TABLE_ID</td>
@@ -107,25 +95,24 @@
<td></td>
</tr>
</table>
-
-<p>
-<strong>TURBINE_PERMISSION</strong>
-</p>
-
<p>
-The TURBINE_PERMISSION table stores the lowest level of permissions allowed
-for a Turbine User.
+The ID_TABLE carries the information for the next ID
+number in the specified tables. This table is useful when
+the database being used has no data-type which carries out
+auto-increment operations.
</p>
+</subsection>
+<subsection name="TURBINE_PERMISSION">
<table>
<tr>
- <td>Column Name</td>
- <td>Key</td>
- <td>Data Type</td>
- <td>Default Value</td>
- <td>Null</td>
- <td>Indexed</td>
- <td>Comment</td>
+ <th>column name</th>
+ <th>key</th>
+ <th>data type</th>
+ <th>default value</th>
+ <th>null</th>
+ <th>indexed</th>
+ <th>comment</th>
</tr>
<tr>
<td>PERMISSION_ID</td>
@@ -155,27 +142,22 @@
<td></td>
</tr>
</table>
-
-<p>
-<strong>TURBINE_ROLE</strong>
-</p>
-
<p>
-The TURBINE_ROLE table links a Turbine User to a span of permissions.
-Potentially a Turbine User can have many roles within the system. In this case
-a role represents a descriptive word for a series of permissions or actions the
-Turbine User is able to undertake.
+The TURBINE_PERMISSION table stores the lowest level of permissions allowed
+for a Turbine User.
</p>
+</subsection>
+<subsection name="TURBINE_ROLE">
<table>
<tr>
- <td>Column Name</td>
- <td>Key</td>
- <td>Data Type</td>
- <td>Default Value</td>
- <td>Null</td>
- <td>Indexed</td>
- <td>Comment</td>
+ <th>column name</th>
+ <th>key</th>
+ <th>data type</th>
+ <th>default value</th>
+ <th>null</th>
+ <th>indexed</th>
+ <th>comment</th>
</tr>
<tr>
<td>ROLE_ID</td>
@@ -205,28 +187,24 @@
<td></td>
</tr>
</table>
-
<p>
-<strong>TURBINE_GROUP</strong>
-</p>
-
-<p>
-The TURBINE_GROUP table allows for a series of roles and Turbine Users to be
-connected under a Group ID and hence Group Name. For instance there may be a
-group named Administrators with the necessary roles and permissions. There may
-also be many Administrators on the system. The Group table and it's relationship
-with the TURBINE_USER_GROUP_ROLE table maps this functionality.
+The TURBINE_ROLE table links a Turbine User to a span of permissions.
+Potentially a Turbine User can have many roles within the system. In this case
+a role represents a descriptive word for a series of permissions or actions the
+Turbine User is able to undertake.
</p>
+</subsection>
+<subsection name="TURBINE_GROUP">
<table>
<tr>
- <td>Column Name</td>
- <td>Key</td>
- <td>Data Type</td>
- <td>Default Value</td>
- <td>Null</td>
- <td>Indexed</td>
- <td>Comment</td>
+ <th>column name</th>
+ <th>key</th>
+ <th>data type</th>
+ <th>default value</th>
+ <th>null</th>
+ <th>indexed</th>
+ <th>comment</th>
</tr>
<tr>
<td>GROUP_ID</td>
@@ -256,26 +234,25 @@
<td></td>
</tr>
</table>
-
-<p>
-<strong>TURBINE_ROLE_PERMISSION</strong>
-</p>
-
<p>
-The TURBINE_ROLE_PERMISSION table is a bridging table between TURBINE_ROLE and
-TURBINE_PERMISSION that allows a several differant roles to make use of the
-same permission.
+The TURBINE_GROUP table allows for a series of roles and Turbine Users to be
+connected under a Group ID and hence Group Name. For instance there may be a
+group named Administrators with the necessary roles and permissions. There may
+also be many Administrators on the system. The Group table and it's relationship
+with the TURBINE_USER_GROUP_ROLE table maps this functionality.
</p>
+</subsection>
+<subsection name="TURBINE_ROLE_PERMISSION">
<table>
<tr>
- <td>Column Name</td>
- <td>Key</td>
- <td>Data Type</td>
- <td>Default Value</td>
- <td>Null</td>
- <td>Indexed</td>
- <td>Comment</td>
+ <th>column name</th>
+ <th>key</th>
+ <th>data type</th>
+ <th>default value</th>
+ <th>null</th>
+ <th>indexed</th>
+ <th>comment</th>
</tr>
<tr>
<td>ROLE_ID</td>
@@ -296,25 +273,23 @@
<td></td>
</tr>
</table>
-
<p>
-<strong>TURBINE_USER</strong>
-</p>
-
-<p>
-The TURBINE_USER table describes the basic information on the user in the
-system.
+The TURBINE_ROLE_PERMISSION table is a bridging table between TURBINE_ROLE and
+TURBINE_PERMISSION that allows a several differant roles to make use of the
+same permission.
</p>
+</subsection>
+<subsection name="TURBINE_USER">
<table>
<tr>
- <td>Column Name</td>
- <td>Key</td>
- <td>Data Type</td>
- <td>Default Value</td>
- <td>Null</td>
- <td>Indexed</td>
- <td>Comment</td>
+ <th>column name</th>
+ <th>key</th>
+ <th>data type</th>
+ <th>default value</th>
+ <th>null</th>
+ <th>indexed</th>
+ <th>comment</th>
</tr>
<tr>
<td>USER_ID</td>
@@ -416,25 +391,22 @@
<td></td>
</tr>
</table>
-
<p>
-<strong>TURBINE_USER_GROUP_ROLE</strong>
-</p>
-
-<p>
-The TURBINE_USER_GROUP_ROLE describes what roles a given user has as a member of
-a given group.
+The TURBINE_USER table describes the basic information on the user in the
+system.
</p>
+</subsection>
+<subsection name="TURBINE_USER_GROUP_ROLE">
<table>
<tr>
- <td>Column Name</td>
- <td>Key</td>
- <td>Data Type</td>
- <td>Default Value</td>
- <td>Null</td>
- <td>Indexed</td>
- <td>Comment</td>
+ <th>column name</th>
+ <th>key</th>
+ <th>data type</th>
+ <th>default value</th>
+ <th>null</th>
+ <th>indexed</th>
+ <th>comment</th>
</tr>
<tr>
<td>USER_ID</td>
@@ -464,20 +436,22 @@
<td></td>
</tr>
</table>
-
<p>
-<strong>TURBINE_SCHEDULED_JOB</strong>
+The TURBINE_USER_GROUP_ROLE describes what roles a given user has as a member of
+a given group.
</p>
+</subsection>
+<subsection name="TURBINE_SCHEDULED_JOB">
<table>
<tr>
- <td>Column Name</td>
- <td>Key</td>
- <td>Data Type</td>
- <td>Default Value</td>
- <td>Null</td>
- <td>Indexed</td>
- <td>Comment</td>
+ <th>column name</th>
+ <th>key</th>
+ <th>data type</th>
+ <th>default value</th>
+ <th>null</th>
+ <th>indexed</th>
+ <th>comment</th>
</tr>
<tr>
<td>JOB_ID</td>
@@ -561,6 +535,7 @@
<td></td>
</tr>
</table>
+</subsection>
</section>
1.4 +10 -8 jakarta-turbine-2/xdocs/howto/torque-howto.xml
Index: torque-howto.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-2/xdocs/howto/torque-howto.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- torque-howto.xml 15 Mar 2002 11:50:04 -0000 1.3
+++ torque-howto.xml 27 Mar 2002 18:53:13 -0000 1.4
@@ -92,14 +92,15 @@
</section>
<section name="Configuring Torque">
-
-<strong>build.properties</strong>
-
<p>
- Here is a list of all the properties currently supported by Torque:
+ You'll have to modify the following two files to configure Torque.
+ The first is a list of all the properties currently supported by
+ Torque:
</p>
+<subsection name="build.properties">
<table>
+<tr><th>Property</th><th>Description</th></tr>
<tr>
<td>project</td>
<td>The name of your Turbine project. The project name is reflected in the
@@ -170,11 +171,10 @@
</td>
</tr>
<tr>
- <td><strong>You should not have to edit any properties below here!</strong></td>
- <td></td>
+ <td colspan="2"><strong>You should not have to edit any properties below
here!</strong></td>
</tr>
<tr>
- <td>configDir</td>
+ <td colspan="1">configDir</td>
<td>The directory Torque looks in for the <em>build.properties</em> file.</td>
</tr>
<tr>
@@ -202,8 +202,9 @@
<td>Directory where Torque looks for XML database schemas.</td>
</tr>
</table>
+</subsection>
-<strong>project-schema.xml</strong>
+<subsection name="project-schema.xml">
<p>
This is an example of what the XML database schema might look like. This
particular example is a snippet of the database used for Turbines role-based
@@ -255,6 +256,7 @@
Please refer to <a href="torque-schema-ref.html">Torque Schema Reference</a>
to find out more about the the different elements and attributes.
</p>
+</subsection>
<!--
1.2 +2 -2 jakarta-turbine-2/xdocs/proposals/application-service.xml
Index: application-service.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-2/xdocs/proposals/application-service.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- application-service.xml 16 Aug 2001 05:10:42 -0000 1.1
+++ application-service.xml 27 Mar 2002 18:53:13 -0000 1.2
@@ -23,7 +23,7 @@
</section>
<section name="Requirements">
-<p>
+<ul>
<li>
Turbine would probably process a directory of JAR files
that contain sub-applications. The manifest would contain
@@ -82,7 +82,7 @@
Extension do DynamicURI and derivates to support new parameter
(sub-application selector)
</li>
-</p>
+</ul>
</section>
1.2 +2 -3 jakarta-turbine-2/xdocs/proposals/i18n.xml
Index: i18n.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-2/xdocs/proposals/i18n.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- i18n.xml 16 Aug 2001 05:10:42 -0000 1.1
+++ i18n.xml 27 Mar 2002 18:53:13 -0000 1.2
@@ -10,16 +10,15 @@
<body>
<section name="i18n">
-<p>
+<ul>
<li>
Messages that turbine outputs should live in a resource bundles, not
in in TR.props
</li>
-
<li>
Template lookups depending on locale (Is Ilkka working on that?)
</li>
-</p>
+</ul>
</section>
1.2 +2 -3 jakarta-turbine-2/xdocs/proposals/naming-service.xml
Index: naming-service.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-2/xdocs/proposals/naming-service.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- naming-service.xml 16 Aug 2001 05:10:42 -0000 1.1
+++ naming-service.xml 27 Mar 2002 18:53:13 -0000 1.2
@@ -10,14 +10,13 @@
<body>
<section name="Naming service">
-
-<p>
+<ul>
<li>
this service is rater outdated, it needs some cleanup, and adding
suppport for DirContexts (low priority, might be useful in
creating LDAP User Manager / Security Service implementations)
</li>
-</p>
+</ul>
</section>
1.2 +2 -3 jakarta-turbine-2/xdocs/proposals/package-cleanup.xml
Index: package-cleanup.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-2/xdocs/proposals/package-cleanup.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- package-cleanup.xml 16 Aug 2001 05:10:42 -0000 1.1
+++ package-cleanup.xml 27 Mar 2002 18:53:13 -0000 1.2
@@ -11,7 +11,7 @@
<section name="Renaming and reordering">
-<p>
+<ul>
<li>
2.2 will be a good moment to rename, and move classes around.
</li>
@@ -32,8 +32,7 @@
through the generated Peers, so there should not be much bad effect
on users and it will lead to much better public api in Criteria.
</li>
-
-</p>
+</ul>
</section>
</body>
1.2 +2 -4 jakarta-turbine-2/xdocs/proposals/peers.xml
Index: peers.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-2/xdocs/proposals/peers.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- peers.xml 16 Aug 2001 05:10:42 -0000 1.1
+++ peers.xml 27 Mar 2002 18:53:13 -0000 1.2
@@ -11,8 +11,7 @@
<section name="Peers">
-<p>
- <ul>
+<ul>
<li>
Criteria should not extend Hashtable. This is widely considered to be
a bad practice. Even if criteria is to maintain hashtable-like
@@ -28,8 +27,7 @@
class has been created that will solve much of this inefficiency.
It should be integrated with Criteria and BasePeer.
</li>
- </ul>
-</p>
+</ul>
</section>
1.2 +2 -2 jakarta-turbine-2/xdocs/proposals/pp.xml
Index: pp.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-2/xdocs/proposals/pp.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- pp.xml 16 Aug 2001 05:10:42 -0000 1.1
+++ pp.xml 27 Mar 2002 18:53:13 -0000 1.2
@@ -11,7 +11,7 @@
<section name="Parameter parser and its ilk">
-<p>
+<ul>
<li>
clean up and orthogonalize APIs (add vs append vs set)
</li>
@@ -30,7 +30,7 @@
kind of apprach is used to emulate multiple inheritance in Java.
I'd appreciate a comment on this issue from Ilkka.
</li>
-</p>
+</ul>
</section>
1.2 +2 -2 jakarta-turbine-2/xdocs/proposals/reusable-components.xml
Index: reusable-components.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-2/xdocs/proposals/reusable-components.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- reusable-components.xml 16 Aug 2001 05:10:42 -0000 1.1
+++ reusable-components.xml 27 Mar 2002 18:53:13 -0000 1.2
@@ -11,7 +11,7 @@
<section name="Reusable Components">
-<p>
+<ul>
<li>
facilities for presenation of tabular data, with the ability
to do paging, filtering and sorting
@@ -21,7 +21,7 @@
date selection component (skinnable calendar with year/month/week
views in a popup window, includes some JS)
</li>
-</p>
+</ul>
</section>
1.2 +2 -2 jakarta-turbine-2/xdocs/proposals/security-service.xml
Index: security-service.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-2/xdocs/proposals/security-service.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- security-service.xml 16 Aug 2001 05:10:42 -0000 1.1
+++ security-service.xml 27 Mar 2002 18:53:13 -0000 1.2
@@ -11,7 +11,7 @@
<section name="Security Service">
-<p>
+<ul>
<li>
UserManager should become a service in it's own right.
</li>
@@ -91,7 +91,7 @@
of the location of a lot of the classes but I think it would
help a lot with the ease of understanding.
</li>
-</p>
+</ul>
<source test=""><![CDATA[
.
1.2 +26 -27 jakarta-turbine-2/xdocs/proposals/services-repository.xml
Index: services-repository.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-2/xdocs/proposals/services-repository.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- services-repository.xml 16 Aug 2001 05:10:42 -0000 1.1
+++ services-repository.xml 27 Mar 2002 18:53:13 -0000 1.2
@@ -58,35 +58,34 @@
</section>
<section name="Requirements">
- <li>
+ <p>
Services would have to be functional from JAR files. For this to work
the following changes would have to be made:
- <p/>
- <ul>
- <li>
- The Services framework would have to be altered to load services
- packaged in the form of JAR files.
- </li>
-
- <li>
- Dependent services would have to be listed in the manifest so that the
- the initialization of a service could be deferred until all
- prerequisites of the service have been initialized.
- </li>
-
- <li>
- The service package in a JAR should state all of its configuration
- options as it may be necessary to have this configuration information
- extracted from the JAR and added to TR.props or whatever future
- configuration mechanisms we devise. It might be nice to have an
- option in Turbine where there is no TR.props to begin with but
- starting Turbine with a certain option would produce a configuration
- that reflected the use of a set of services. Or Turbine would start,
- but would require some configuration from via a little web application
- before Turbine would accept connections from the outside world.
- </li>
- </ul>
- </li>
+ </p>
+ <ul>
+ <li>
+ The Services framework would have to be altered to load services
+ packaged in the form of JAR files.
+ </li>
+
+ <li>
+ Dependent services would have to be listed in the manifest so that the
+ the initialization of a service could be deferred until all
+ prerequisites of the service have been initialized.
+ </li>
+
+ <li>
+ The service package in a JAR should state all of its configuration
+ options as it may be necessary to have this configuration information
+ extracted from the JAR and added to TR.props or whatever future
+ configuration mechanisms we devise. It might be nice to have an
+ option in Turbine where there is no TR.props to begin with but
+ starting Turbine with a certain option would produce a configuration
+ that reflected the use of a set of services. Or Turbine would start,
+ but would require some configuration from via a little web application
+ before Turbine would accept connections from the outside world.
+ </li>
+ </ul>
</section>
<section name="Scope">
1.2 +2 -2 jakarta-turbine-2/xdocs/proposals/xslt-service.xml
Index: xslt-service.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-2/xdocs/proposals/xslt-service.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- xslt-service.xml 16 Aug 2001 05:10:42 -0000 1.1
+++ xslt-service.xml 27 Mar 2002 18:53:13 -0000 1.2
@@ -11,13 +11,13 @@
<section name="XSLT Service">
-<p>
+<ul>
<li>
support for processing of DOM trees present in memory could be
useful (right now both data and stylesheet are read from disk
files)
</li>
-</p>
+</ul>
</section>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
