henning 2003/07/22 03:44:45
Modified: xdocs/services template-service.xml
Log:
Corrected wrong links
Revision Changes Path
1.4 +4 -4 jakarta-turbine-2/xdocs/services/template-service.xml
Index: template-service.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-2/xdocs/services/template-service.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- template-service.xml 15 Jul 2003 16:13:20 -0000 1.3
+++ template-service.xml 22 Jul 2003 10:44:44 -0000 1.4
@@ -70,12 +70,12 @@
</p>
<p>Note: In all of the following examples, it is assumed that you use
-the <a href="/services/velocity-service.html">VelocityService</a> as
+the <a href="services/velocity-service.html">VelocityService</a> as
your preferred view service. So if you read "Velocity" in the
following paragraphs, this means "default configured view
class". Currently, Turbine includes two supported view services,
-<a href="/services/velocity-service.html">Velocity</a> and
-<a href="/services/jsp-service.html">Java Server Pages (JSP)</a>.
+<a href="services/velocity-service.html">Velocity</a> and
+<a href="services/jsp-service.html">Java Server Pages (JSP)</a>.
</p>
<p>
@@ -172,7 +172,7 @@
<p>
If you now wonder how a template name is mapped to an actual file name: This is
- scope of the templating engine. <a
href="/services/velocity-service.html">Velocity</a>
+ scope of the templating engine. <a
href="services/velocity-service.html">Velocity</a>
e.g. has this wonderful option to load templates from jar archives.
There is no file but if you tell velocity "get about,directions,Driving.vm" and it
returns the rendered template. So getting the actual template is not the job of
the
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]