db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tfisc...@apache.org
Subject svn commit: r1504273 - /db/torque/torque4/trunk/torque-site/src/site/xdoc/documentation/codegen-reference/configuration.xml
Date Wed, 17 Jul 2013 20:47:37 GMT
Author: tfischer
Date: Wed Jul 17 20:47:37 2013
New Revision: 1504273

URL: http://svn.apache.org/r1504273
TORQUE-296 document auto-defining outlets by existence of templates


Modified: db/torque/torque4/trunk/torque-site/src/site/xdoc/documentation/codegen-reference/configuration.xml
URL: http://svn.apache.org/viewvc/db/torque/torque4/trunk/torque-site/src/site/xdoc/documentation/codegen-reference/configuration.xml?rev=1504273&r1=1504272&r2=1504273&view=diff
--- db/torque/torque4/trunk/torque-site/src/site/xdoc/documentation/codegen-reference/configuration.xml
+++ db/torque/torque4/trunk/torque-site/src/site/xdoc/documentation/codegen-reference/configuration.xml
Wed Jul 17 20:47:37 2013
@@ -45,7 +45,10 @@
         i.e. the outlet is a velocity template, then the path to
         the template is needed as well.<br/>
         All outlet properties can be overridden in the controller
-        configuration.
+        configuration.<br/>
+        For each template with a known file extension, an outlet definition
+        is created automatically.<br/>
+        See below for details on defining outlets.
@@ -299,6 +302,25 @@
         mergepoint definition.
+    <subsection name="automatic outlet definition for templates"
+      <p>
+        For each template with a known file extension
+        (currently .vm for velocity templates and .groovy for groovy scripts),
+        the generator automatically creates an outlet. 
+        The name of these outlets is the path of the file in the template
+        directory, with path separators replaced by dots and the file extension
+        removed. For example, for a file templates/peer/impl/peerImpl.vm,
+        an outlet with the name peer.impl.peerImpl will be created.
+        No outlet will be defined automatically if an outlet definition
+        with the given name already exists.
+        Note that the outlet definitions which are created automatically
+        do not have mergepoint mappings,
+        so you will still have to map the mergepoint mappings explicitly
+        (or define an extra outlets with the mergepoint mappings).
+        Also, the encoding of the templates will be assumed to be 
+        the vm's default encoding.
+      </p>
+    </subsection>
\ No newline at end of file

To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org

View raw message