criley 01/05/08 12:47:24
Modified: xdocs advcriteria.xml context-howto.xml
getting-started.xml install.xml peers.xml
python.xml turbine-documentation-project.xml
velocity-site.xml
Log:
removed the build-turbine entries, added some documentatoin for stuff that popped on
the user mailing list
Revision Changes Path
1.5 +18 -0 jakarta-turbine/xdocs/advcriteria.xml
Index: advcriteria.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine/xdocs/advcriteria.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- advcriteria.xml 2001/04/17 23:40:50 1.4
+++ advcriteria.xml 2001/05/08 19:47:09 1.5
@@ -315,6 +315,24 @@
</section>
+ <section name="Debugging Criteria's">
+
+ <p>
+ Criteria contains a toString() method which will output a representation of the
Criteria as a String. As the Criteria to a large extent represents the statements in a
WHERE clause of SQL, the LoggingService can output the SQL. In the
TurbineResources.properties file, under the directive;
+ </p>
+
+ <source>
+ services.LogginService.sql.level = DEBUG
+ </source>
+
+ <p>
+ Set the level to DEBUG.
+ </p>
+
+ </section>
+
+
+
</body>
1.9 +13 -0 jakarta-turbine/xdocs/context-howto.xml
Index: context-howto.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine/xdocs/context-howto.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- context-howto.xml 2001/03/27 22:09:04 1.8
+++ context-howto.xml 2001/05/08 19:47:10 1.9
@@ -147,6 +147,19 @@
</p>
<p>
+This same mechanism can also be used to link to static html;
+</p>
+
+<source>
+ $link.setPage("/path/to/static.html")
+</source>
+
+<p>
+However the HTML page will load itself into a screen and not be embedded withint
the Layouts and Navigations. If you still wish static content to be embedded within
the specified layouts and navigations it is easier to add the static content as a
velocity template and not take advantage of any of the dynamic content addition the
Velocity Context allows.
+</p>
+
+
+<p>
TemplateLink and DynamicURI again expose a rich set of methods and fields to
the link reference, for a full list of fields and methods please refer to
TemplateLink and DynamicURI in the javadocs. Some of the useful methods
1.10 +19 -0 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
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- getting-started.xml 2001/03/01 02:49:26 1.9
+++ getting-started.xml 2001/05/08 19:47:11 1.10
@@ -129,6 +129,25 @@
</section>
+<section name="Generating the Turbine Javadocs">
+<p>
+To generate the Javadocs for Turbine check out Turbine from CVS. The build scripts
for Turbine are in the /jakarta-turbine/build directory. The Ant Target is javadocs,
cd into the build directory and run build.sh or build.bat depending on whether you are
on *nix or Win32;
+</p>
+
+<source>
+ ./build.sh javadocs
+
+ or
+
+ build.bat javadocs
+</source>
+
+<p>
+The javadocs will build to the /jakarta-turbine/docs/apidocs directory.
+</p>
+
+</section>
+
<section name="Further Questions and Comments">
<p>
If you have further questions or comments, please send them to the <a
1.11 +4 -4 jakarta-turbine/xdocs/install.xml
Index: install.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine/xdocs/install.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- install.xml 2001/03/05 17:26:23 1.10
+++ install.xml 2001/05/08 19:47:12 1.11
@@ -332,24 +332,24 @@
-<section name="Ant Tasks available in build-turbine.xml">
+<section name="Ant Tasks available in build.xml">
<p>
The build-turbine.xml contains many Ant tasks. These are run by typing from the
command line;
<ul>
- build-turbine taskname
+ build taskname
</ul>
for example, to run the task which generates the turbine-pool.jar type;
<ul>
- build-turbine pool
+ build pool
</ul>
</p>
<p>
-Other Ant tasks in build-turbine.xml include;
+Other Ant tasks in build.xml include;
</p>
<p>
1.10 +14 -0 jakarta-turbine/xdocs/peers.xml
Index: peers.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine/xdocs/peers.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- peers.xml 2001/04/21 01:56:13 1.9
+++ peers.xml 2001/05/08 19:47:13 1.10
@@ -141,9 +141,23 @@
</p>
<p>
+For example if you wish to set up the MapBuilder to take advantage of an
auto-incrementing Primary Key, you can change the entry in your MapBuilder class from;
+</p>
+
+<source>
+ tMap.setPrimaryKeyMethod(TableMap.IDBROKERTABLE);
+
+ to
+
+ tMap.setPrimaryKeyMethod(TableMap.AUTOINCREMENT);
+
+</source>
+
+<p>
The ID Broker is used in the underlying Peer code. After you have set it
up you need not worry about it anymore.
</p>
+
</section>
1.4 +2 -2 jakarta-turbine/xdocs/python.xml
Index: python.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine/xdocs/python.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- python.xml 2001/04/08 18:35:57 1.3
+++ python.xml 2001/05/08 19:47:14 1.4
@@ -48,8 +48,8 @@
the jpython.jar file into your turibe/lib directory. Now you need to
prepare and compile the jpython files like this:
<source>
- build-turbine prepare-python
- build-turbine jar
+ build prepare-python
+ build jar
</source>
This will create a new turbine library that contains the Python code.
You need to copy this new .jar file to your application's lib
1.6 +2 -2 jakarta-turbine/xdocs/turbine-documentation-project.xml
Index: turbine-documentation-project.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine/xdocs/turbine-documentation-project.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- turbine-documentation-project.xml 2001/04/11 12:56:14 1.5
+++ turbine-documentation-project.xml 2001/05/08 19:47:14 1.6
@@ -206,7 +206,7 @@
</p>
<p>
-<ul> build-turbine docs </ul>
+<ul> build docs </ul>
</p>
<p>
@@ -214,7 +214,7 @@
</p>
<p>
-<ul> ./build-turbine.sh docs </ul>
+<ul> ./build.sh docs </ul>
</p>
<p>
1.11 +18 -0 jakarta-turbine/xdocs/velocity-site.xml
Index: velocity-site.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine/xdocs/velocity-site.xml,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- velocity-site.xml 2001/04/18 13:49:18 1.10
+++ velocity-site.xml 2001/05/08 19:47:15 1.11
@@ -514,6 +514,24 @@
</section>
+<!-- Comment : Multiple Velocity Paths -->
+
+<section name="Multiple Velocity Paths">
+
+<p>
+The VelocityService can support many paths for the Velocity Templates to be loaded
and read from. This is specified in the TurbineResources.properties file;
+</p>
+
+<source>
+ services.VelocityService.file.resource.loader.path =
/templates,/my-templates,/more-tempates
+</source>
+
+<p>
+The multiple paths are comma delimited and are specified from the Servlet Engines
context.
+</p>
+
+</section>
+
</body>
</document>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
