You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by mp...@apache.org on 2001/08/01 21:17:14 UTC
cvs commit: jakarta-turbine/xdocs/howto action-event-howto.xml context-howto.xml peers-howto.xml security-howto.xml tdk-howto.xml torque-howto.xml velocity-site-howto.xml
mpoeschl 01/08/01 12:17:14
Modified: xdocs Tag: T_2_1_BRANCH getting-started.xml index.xml
project-map.xml proposals.xml
xdocs/howto Tag: T_2_1_BRANCH action-event-howto.xml
context-howto.xml peers-howto.xml
security-howto.xml tdk-howto.xml torque-howto.xml
velocity-site-howto.xml
Log:
update docs in 2.x branch.
now we (jason ;-) can start writing docs for 3.0
Revision Changes Path
No revision
No revision
1.9.4.5 +1 -1 jakarta-turbine/xdocs/getting-started.xml
Index: getting-started.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine/xdocs/getting-started.xml,v
retrieving revision 1.9.4.4
retrieving revision 1.9.4.5
diff -u -r1.9.4.4 -r1.9.4.5
--- getting-started.xml 2001/05/23 03:11:01 1.9.4.4
+++ getting-started.xml 2001/08/01 19:17:13 1.9.4.5
@@ -64,7 +64,7 @@
organized and as you learn about each part of the code, the entire
architecture starts to make sense and is really quite easy to master.
All of our code is well javadoc'd so we encourage you to review not only
-the actual source code, but also the documentation. :-) The diffferent
+the actual source code, but also the documentation. :-) The different
parts of Turbine are:
</p>
1.13.4.4 +1 -1 jakarta-turbine/xdocs/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine/xdocs/index.xml,v
retrieving revision 1.13.4.3
retrieving revision 1.13.4.4
diff -u -r1.13.4.3 -r1.13.4.4
--- index.xml 2001/05/23 03:11:02 1.13.4.3
+++ index.xml 2001/08/01 19:17:13 1.13.4.4
@@ -104,7 +104,7 @@
<a href="http://www.javaworld.com/javaworld/jw-12-1999/jw-12-ssj-jspmvc.html">Model
2 methodology</a> yet expand on it to encompass "View" techologies other
than just JSP as well as more mature methodologies such as
- <a href="action-event.html">Action
+ <a href="./howto/action-event-howto.html">Action
Event</a> handling. Turbine is consided as Model 2 <strong>+ 1</strong>. :-) Please
see the <a href="model2+1.html">discussion</a> of Model 2+1 for more information.
</p>
1.2.4.1 +4 -4 jakarta-turbine/xdocs/project-map.xml
Index: project-map.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine/xdocs/project-map.xml,v
retrieving revision 1.2
retrieving revision 1.2.4.1
diff -u -r1.2 -r1.2.4.1
--- project-map.xml 2001/04/07 00:54:59 1.2
+++ project-map.xml 2001/08/01 19:17:13 1.2.4.1
@@ -111,14 +111,14 @@
These tools are runnable from the command line, and are used for the
development purposes, not during the normal operation of an application.
- The tools include <a href="torque.html">Torque</a>, the tool for
+ The tools include <a href="howto/torque-howto.html">Torque</a>, the tool for
generating Peer Framework classes for your application,
- <a href="intake.html">Intake</a> that generates classes for automation
- of processing of complex HTML forms, and the <a href="migrator.html">
+ <a href="services/intake-service.html">Intake</a> that generates classes for automation
+ of processing of complex HTML forms. <!--, and the <a href="migrator.html">
Migrator</a>, the tool that helps you with bringing your application
up to date with newer releases of Turbine, by performing batches
of search-and-replace operations on your sources. When used properly,
- it can save you a plenty of typing. </p>
+ it can save you a plenty of typing.--> </p>
</section>
1.4.4.1 +2 -5 jakarta-turbine/xdocs/proposals.xml
Index: proposals.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine/xdocs/proposals.xml,v
retrieving revision 1.4
retrieving revision 1.4.4.1
diff -u -r1.4 -r1.4.4.1
--- proposals.xml 2001/04/18 18:07:45 1.4
+++ proposals.xml 2001/08/01 19:17:13 1.4.4.1
@@ -17,22 +17,19 @@
<ul>
<li><a href="proposals/application-service.html">Application Service</a></li>
<li><a href="proposals/browser-bound-app-context.html">Browser Bound Application Context</a></li>
-<li><a href="proposals/bsf-service.html">BSF Service</a></li>
-<li><a href="proposals/core-processing.html">Core Processing</a></li>
<li><a href="proposals/i18n.html">i18n</a></li>
<li><a href="proposals/naming-service.html">Naming Service</a></li>
+<li><a href="proposals/sql.html">New Query Model</a></li>
<li><a href="proposals/package-cleanup.html">Package Cleanup</a></li>
<li><a href="proposals/peers.html">Peer</a></li>
<li><a href="proposals/policy-service.html">Policy Service</a></li>
<li><a href="proposals/pp.html">PP and Related Classes</a></li>
-<li><a href="proposals/resources-service.html">Resources Service</a></li>
<li><a href="proposals/reusable-components.html">Reusable Components</a></li>
-<li><a href="proposals/scheduler-service.html">Scheduler Service</a></li>
<li><a href="proposals/security-service.html">Security Service</a></li>
-<li><a href="proposals/services-framework.html">Services Framework</a></li>
<li><a href="proposals/services-repository.html">Services Repository</a></li>
<li><a href="proposals/xslt-service.html">XSLT Service</a></li>
<li><a href="proposals/unified-templating.html">Unified Templating Service</a></li>
+<li><a href="proposals/bo-managers.html">Torque BO Managers</a></li>
</ul>
</section>
No revision
No revision
1.1.2.2 +2 -2 jakarta-turbine/xdocs/howto/action-event-howto.xml
Index: action-event-howto.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine/xdocs/howto/action-event-howto.xml,v
retrieving revision 1.1.2.1
retrieving revision 1.1.2.2
diff -u -r1.1.2.1 -r1.1.2.2
--- action-event-howto.xml 2001/05/20 15:58:25 1.1.2.1
+++ action-event-howto.xml 2001/08/01 19:17:13 1.1.2.2
@@ -29,7 +29,7 @@
of the Action class will be able to take advantage of what happens next...
</p>
-<source test=""><![CDATA[
+<source><![CDATA[
public class NewUser extends VelocityAction
{
public void doAdd (RunData data, Context context) throws Exception
@@ -50,7 +50,7 @@
Then, write your HTML tags specially like this:
</p>
-<source test=""><![CDATA[
+<source><![CDATA[
<input type="submit" name="eventSubmit_doAdd" value="Add User">
]]></source>
1.1.2.2 +6 -5 jakarta-turbine/xdocs/howto/context-howto.xml
Index: context-howto.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine/xdocs/howto/context-howto.xml,v
retrieving revision 1.1.2.1
retrieving revision 1.1.2.2
diff -u -r1.1.2.1 -r1.1.2.2
--- context-howto.xml 2001/05/14 07:48:54 1.1.2.1
+++ context-howto.xml 2001/08/01 19:17:13 1.1.2.2
@@ -243,10 +243,11 @@
<section name="Adding your own Objects to the Context">
<p>
-As the Context is stored as a Hashtable any Object can be placed inside it and
-be accessed from a template. For instance, in a Velocity Screen in the
-doBuildTemplate() method, a String could be added to the Context. Please refer
-to the Getting Started documentation for more examples of using the Velocity
+As the Context is stored as a Hashtable any Object can be placed inside
+it and be accessed from a template. For instance, in a Velocity Screen
+in the doBuildTemplate() method, a String could be added to the Context.
+Please refer to the <a href="../getting-started.html">Getting
+Started</a> documentation for more examples of using the Velocity
Context with screens and events.
</p>
@@ -369,7 +370,7 @@
adding the Image object to the Velocity Context. Then use this class as the
parent class for the Screens that need access to the Image Object. For more
detail on taking advantage and extending the VelocityScreen Object, please view
-the <a href="getting-started.html">Getting Started</a> Document.
+the <a href="../getting-started.html">Getting Started</a> Document.
</p>
<p>
1.2.2.3 +106 -29 jakarta-turbine/xdocs/howto/peers-howto.xml
Index: peers-howto.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine/xdocs/howto/peers-howto.xml,v
retrieving revision 1.2.2.2
retrieving revision 1.2.2.3
diff -u -r1.2.2.2 -r1.2.2.3
--- peers-howto.xml 2001/05/23 03:11:19 1.2.2.2
+++ peers-howto.xml 2001/08/01 19:17:13 1.2.2.3
@@ -22,8 +22,8 @@
<p>
Peers use Turbine's Database adaptor classes that make uniform connection
to a wide range of databases possible. If your database is not supported
-you can read the Database Adapter docs on how to create a new adaptor for
-your database.
+you can read the <a href="../db-adapters.html">Database Adapter</a> docs on
+how to create a new adaptor for your database.
</p>
<p>
@@ -36,6 +36,79 @@
</section>
+<section name="Capabilities">
+
+<source><![CDATA[
+> I'm looking for an O-R layer for the next version of our system;
+> somebody recommended that I evaluate Peers. I've identified 7
+> structural cases and a few other criteria that I'd like in an O-R tool.
+> Can an experienced Peers user or developer tell me how well it handles
+> these situations?
+>
+> O-R structures:
+> 1) simple (1 class, 1 table)
+
+You use a tool called Torque to generate Peer classes for you. There
+are 4 classes for each table. Base<table-name>Peer, Base<table-name>,
+<table-name>Peer and Base<table-name>
+
+The Base* classes contains all the functionality and should not be
+change. The other two classes are empty and this is where your
+application business logic goes. If you regenerate with torque only the
+Base* classes changes. This allows you to change the schema, but still
+keep your existing code.
+
+> 2) 1:n
+
+Torque will generate methods for you to access the relevant objects.
+
+For example Category and Item. Category.getItems() will give all the
+items for a category or Item.getCategory() will give the associated
+Category for an Item.
+
+Torque also generates methods for joining all objects with less db hits
+as to improve performance.
+
+> 3) n:m
+
+You can use the methods generated by Torque for this, but it would
+probably be more efficient to use a Criteria object. Joins are very
+easy to do and you'll find that you'll be able to do complex multi-table
+joins without a problem.
+
+> 4) self join 1:n (object trees)
+
+Same as (3). I have very efficient code that loads a tree from a table
+into a in memory tree representation with a single db hit. If you're
+interested I can give it to you.
+
+> 5) self join n:m (object maps)
+
+Same as (3).
+
+> 6) simple inheritance (S extends B, each maps to a table with a shared
+> primary key)
+
+I don't think there is any support for this at the moment, but it could
+probably be done.
+
+> 7) polymorphic inheritance (S and T extend B, the application works with
+> a collection of B)
+
+Same as (6)
+
+> The only other real requirement I've got is good documentation.
+
+As an added bonus Peer allows you to create objects from a standard SQL
+query. This gives you the opportunity to do things by hand wherever you
+might find Peers lacking (which isn't a lot :-)
+
+The documentation is coming along nicely, but there is room for
+improvement. We'll help you with Peer if you help out with docs :-)
+]]></source>
+
+</section>
+
<section name="Database Maps">
<p>
@@ -47,7 +120,7 @@
<p>
There is exactly one DatabaseMap for each relational database that you
-connect to. You may wish to connect to more that one database in your
+connect to. You may wish to connect to more than one database in your
application. You should then have one DatabaseMap for each of the
databases.
</p>
@@ -65,7 +138,7 @@
<section name="Peer Classes">
<p>
-Everything in Peers resolve around Peer classes. A Peer class have a
+Everything in Peers resolve around Peer classes. A Peer class has a
one-to-one mapping to a Database table. You use each table's associated
Peer class to do operations on that table. Peer classes can be generated
for you automatically.
@@ -74,7 +147,7 @@
<p>
Peer classes have static methods only, so you would never create objects of
Peer classes. It is not necessary to have objects on this level because
-of the one-to-one mapping with a table. Peer methods are thread-save.
+of the one-to-one mapping with a table. Peer methods are thread safe.
</p>
</section>
@@ -88,8 +161,8 @@
<p>
Data Objects are used almost exclusively with their related Peer classes.
-Where peer classes "wraps around" around a database table, a Data Object
-"wraps around" individual rows of the table. The two always go together.
+Where peer classes "wrap around" around a database table, a Data Object
+"wrap around" individual rows of the table. The two always go together.
</p>
<p>
@@ -186,20 +259,24 @@
<section name="Schema Definition">
<p>
-Peer classes are typically generated by invoking one of the
-<i>build-project</i> scripts that are provided by the TDK. On a unix
-host, for example, the relevant script is called
-<code>build-project.sh</code> and this should be invoked with the
-<code>init</code> argument to generate the peers.
+Peer classes are typically generated by invoking the init task in
+the ant build file (build.xml) provided with an application generated by
+the TDK. This file is located in the WEB-INF/build directory of a generated
+application.
</p>
<p>
Peer class source code is generated based on the project database
schema. The definition of this schema is in XML, and the associated DTD
-is included with the TDK. For the schema described above, the XML would
-look something like
+is included with the TDK. In the TDK, the project schema is located in
+the WEB-INF/conf directory of the project in a file called
+<i>project</i>-schema.xml.
</p>
+<p>
+For the schema described above, the XML would look something like
+</p>
+
<source><![CDATA[
<app-data>
<database>
@@ -315,13 +392,13 @@
<p>
Updates works pretty much the same as inserts. You just need to call
the doUpdate method from your Peer class. Just keep in mind that you
-must add and id column if you wish to do Updates.
+must add an id column if you wish to do updates.
</p>
</section>
<section name="Deletes">
<p>
-Deletes work much in the same way than a select. If you for example
+Deletes work much in the same way as a select. If you, for example,
want to delete the item with id = 3 then you simply add it to the
Criteria and call doDelete.
</p>
@@ -336,15 +413,15 @@
<section name="Advanced Peer Techniques">
<p>
- In this doc I'm going to try and explain a bit more about using Peers than
- just run of the mill selects, inserts and updates. However, this is by no
- means the be-all and end-all of Peer usage. It is just some ideas that I
- have found to work well.
+ In this section I'm going to try and explain a bit more about using
+ Peers than just run of the mill selects, inserts and updates.
+ However, this is by no means the be-all and end-all of Peer usage.
+ It is just some ideas that I have found to work well.
</p>
<p>
<strong>Note:</strong> some information here is out of date (Subclassing).
- The <a href="classhierarchy.html">Class Hierarchy</a> document provides
+ The <a href="../classhierarchy.html">Class Hierarchy</a> document provides
more current information regarding mapping a hierarchy in the OM/Peer
system.
</p>
@@ -353,7 +430,7 @@
<section name="Subclassing">
<p>
- Usually when we begin to extra code for Peer classes we end up with the
+ Usually when we begin to add extra code for Peer classes we end up with the
problem of where to add the code. If we add it to the generated Peer
classes we will loose everything if (and trust me this does happen) we
need to regenerate the classes.
@@ -373,9 +450,9 @@
class.
</p>
<p>
- Using the example in the <a href="peers.html">Peers docs</a> we are
- going to create new classes for the Category and Item tables.
+ Here's how we are create new classes for the Category and Item tables.
</p>
+
<source>
public class MyCategoryPeer extends CategoryPeer
{
@@ -386,7 +463,7 @@
}
}
-public class ItemPeer extends ItemPeer
+public class MyItemPeer extends ItemPeer
{
static public Vector doSelect (Criteria criteria) throws Exception
{
@@ -463,7 +540,7 @@
<section name="Joins and linking objects">
<p>
- Sometimes you would like to have relations between tables to be available
+ Sometimes you would like to have relations between tables be available
in the Peer objects. For example you want the category of an item to be
available through a getCategory() method.
</p>
@@ -498,7 +575,7 @@
crit.addJoin (ItemPeer.CATEGORY_ID, CategoryPeer.CATEGORY_ID);
addSelectColumns ( criteria );
- CategoryPeer.addSelectColumns ( criteria )
+ CategoryPeer.addSelectColumns ( criteria );
// BasePeer returns a Vector of Value (Village) arrays. The array
// order follows the order columns were placed in the Select clause.
@@ -515,13 +592,13 @@
MyItem itm = row2Object (row,
1,
Class.forName
- ("com.mycompany.om.MyItem"))
+ ("com.mycompany.om.MyItem"));
MyCategory cat = CategoryPeer.row2Object
(row,
numColumns+1,
Class.forName
- ("com.mycompany.om.MyCategory"))
+ ("com.mycompany.om.MyCategory"));
itm.setCategory (cat);
results.add (itm);
1.3.2.3 +1 -1 jakarta-turbine/xdocs/howto/security-howto.xml
Index: security-howto.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine/xdocs/howto/security-howto.xml,v
retrieving revision 1.3.2.2
retrieving revision 1.3.2.3
diff -u -r1.3.2.2 -r1.3.2.3
--- security-howto.xml 2001/05/23 03:11:23 1.3.2.2
+++ security-howto.xml 2001/08/01 19:17:13 1.3.2.3
@@ -31,7 +31,7 @@
</p>
<p>
-<ul><a href="turbine-schema.html">Turbine Core Schema</a></ul>
+<ul><a href="../turbine-schema.html">Turbine Core Schema</a></ul>
</p>
<p>
1.4.2.6 +6 -6 jakarta-turbine/xdocs/howto/tdk-howto.xml
Index: tdk-howto.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine/xdocs/howto/tdk-howto.xml,v
retrieving revision 1.4.2.5
retrieving revision 1.4.2.6
diff -u -r1.4.2.5 -r1.4.2.6
--- tdk-howto.xml 2001/06/01 01:35:14 1.4.2.5
+++ tdk-howto.xml 2001/08/01 19:17:13 1.4.2.6
@@ -136,8 +136,8 @@
the <a
href="http://jakarta.apache.org/builds/jakarta-turbine/release/">Turbine
release repository</a>. Search for the directory with the latest version, and
-download the file with a name like tdk-2.1b4.tar.gz (preferred choice for
-Unix systems), or tdk-2.1b4.zip (for Windows systems this may be more
+download the file tdk-2.1.tar.gz (preferred choice for
+Unix systems), or tdk-2.1.zip (for Windows systems this may be more
practical).
</p>
@@ -350,7 +350,7 @@
SQL.java. In fact, when you did your Insert of the data, Turbine called a
method called "doInsert" inside of the SQL class in order to insert the data.
A full explaination of how actions work is available
-<a href="action-event.html">here.</a>
+<a href="action-event-howto.html">here.</a>
</p>
</section>
@@ -411,13 +411,13 @@
thing that you have to change are the references to the Servlet 2.3
DTDs in your web.xml file. If you change these references, webapps that
you develop with the TDK should be fully portable. We use the Tomcat 4.0
-because it is the burgeoning standard.
+server because it is the burgeoning standard.
</p>
<p>
We'll add more notes to this as the TDK gains more deployment features.
-There is a very primitive 'deploy' target, but all it does it package
-up your webapp in a WAR file.
+There is a very primitive 'deploy' target, but all it currently does is
+package up your webapp in a WAR file.
</p>
</section>
1.1.2.6 +42 -24 jakarta-turbine/xdocs/howto/torque-howto.xml
Index: torque-howto.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine/xdocs/howto/torque-howto.xml,v
retrieving revision 1.1.2.5
retrieving revision 1.1.2.6
diff -u -r1.1.2.5 -r1.1.2.6
--- torque-howto.xml 2001/06/04 23:53:33 1.1.2.5
+++ torque-howto.xml 2001/08/01 19:17:13 1.1.2.6
@@ -40,6 +40,7 @@
<source><![CDATA[
torque/
lib/ <-- Jar files required by Torque (stand-alone version)
+ dtd/ <--- DTD for Torque XML database descriptors.
schema/ <--- Project specific XML database descriptor.
templates/ <--- Velocity templates used for source generation.
xsl/ <--- XSLT stylesheets use for HTML generation.
@@ -108,31 +109,23 @@
</td>
</tr>
<tr>
- <td>targetPackage</td>
- <td>
- This is package in which your generated OM sources
- will be placed.
- </td>
-</tr>
-<tr>
- <td>addSaveMethod</td>
- <td>
-
- </td>
+ <td>extend</td>
+ <td>Used in conjuction with the OM generation.</td>
</tr>
<tr>
- <td>addGetByNameMethod</td>
- <td>
- </td>
+ <td>mapname</td>
+ <td>Used in conjuction with the OM generation.</td>
</tr>
<tr>
- <td>complexObjectModel</td>
+ <td>suffix</td>
<td>
+ Used in conjuction with the OM generation.
</td>
</tr>
<tr>
- <td>basePrefix</td>
+ <td>targetPackage</td>
<td>
+ Used in conjuction with the OM generation.
</td>
</tr>
<tr>
@@ -172,6 +165,10 @@
<td></td>
</tr>
<tr>
+ <td>configDir</td>
+ <td>The directory Torque looks in for the <em>build.properties</em> file.</td>
+</tr>
+<tr>
<td>templatePath</td>
<td>The path to the Velocity templates used for source generation.</td>
</tr>
@@ -219,20 +216,40 @@
</table>
- <table name="Jobentry">
- <column name="JOBID" null="false" primaryKey="true" type="INTEGER"/>
- <column name="MINUTE" default="-1" null="false" type="INTEGER"/>
- <column name="HOUR" default="-1" null="false" type="INTEGER"/>
- <column name="WEEKDAY" default="-1" null="false" type="INTEGER"/>
- <column name="DAY_OF_MONTH" default="-1" null="false" type="INTEGER"/>
- <column name="TASK" null="false" size="99" type="VARCHAR"/>
- <column name="EMAIL" size="99" type="VARCHAR"/>
+ <table name="TURBINE_PERMISSION" idMethod="idbroker">
+ <column name="PERMISSION_ID" required="true" primaryKey="true" type="INTEGER"/>
+ <column name="PERMISSION_NAME" required="true" size="99" type="VARCHAR" javaName="Name"/>
+
+ <unique>
+ <unique-column name="PERMISSION_NAME"/>
+ </unique>
+
</table>
+ <table name="TURBINE_ROLE_PERMISSION">
+ <column name="ROLE_ID" required="true" primaryKey="true" type="INTEGER"/>
+ <column name="PERMISSION_ID" required="true" primaryKey="true" type="INTEGER"/>
+
+ <foreign-key foreignTable="TURBINE_ROLE">
+ <reference local="ROLE_ID" foreign="ROLE_ID"/>
+ </foreign-key>
+
+ <foreign-key foreignTable="TURBINE_PERMISSION">
+ <reference local="PERMISSION_ID" foreign="PERMISSION_ID"/>
+ </foreign-key>
+ </table>
+
</database>
]]></source>
<p>
+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>
+
+<!--
+
+<p>
This is what the resultant SQL looks like, in the case the target database is
<a href="http://www.mysql.com">MySQL</a>:
</p>
@@ -360,6 +377,7 @@
</tr>
</table>
+-->
</section>
1.2.2.3 +1 -1 jakarta-turbine/xdocs/howto/velocity-site-howto.xml
Index: velocity-site-howto.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine/xdocs/howto/velocity-site-howto.xml,v
retrieving revision 1.2.2.2
retrieving revision 1.2.2.3
diff -u -r1.2.2.2 -r1.2.2.3
--- velocity-site-howto.xml 2001/05/23 03:11:27 1.2.2.2
+++ velocity-site-howto.xml 2001/08/01 19:17:13 1.2.2.3
@@ -421,7 +421,7 @@
<p>
There is also a new feature of Turbine that the VelocitySiteAction takes
-advantage of, it is called <a href="action-event.html">Action Event</a>.
+advantage of, it is called <a href="action-event-howto.html">Action Event</a>.
Please click the link and read more documentation about it. This is an
excellent way to write your actions because now they are entirely event
driven based on which button was clicked in the HTML form.
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org
Re: cvs commit: jakarta-turbine/xdocs/howto action-event-howto.xml context-howto.xml peers-howto.xml security-howto.xml tdk-howto.xml torque-howto.xml velocity-site-howto.xml
Posted by Incze Lajos <in...@mail.matav.hu>.
Sorry for the previous message. (torque/fulcrum to the nightly).
I should have payed attention to the alpha directory (and
related announcements).
incze
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-dev-help@jakarta.apache.org