db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tfisc...@apache.org
Subject svn commit: r1506313 - /db/torque/torque4/trunk/torque-site/src/site/xdoc/documentation/codegen-reference/configuration.xml
Date Tue, 23 Jul 2013 21:57:18 GMT
Author: tfischer
Date: Tue Jul 23 21:57:18 2013
New Revision: 1506313

URL: http://svn.apache.org/r1506313
Log:
TORQUE-296 improve docs for auto-defining outlets

Modified:
    db/torque/torque4/trunk/torque-site/src/site/xdoc/documentation/codegen-reference/configuration.xml

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=1506313&r1=1506312&r2=1506313&view=diff
==============================================================================
--- db/torque/torque4/trunk/torque-site/src/site/xdoc/documentation/codegen-reference/configuration.xml
(original)
+++ db/torque/torque4/trunk/torque-site/src/site/xdoc/documentation/codegen-reference/configuration.xml
Tue Jul 23 21:57:18 2013
@@ -207,9 +207,10 @@
       Each outlet must have an unique name; it is recommended to use
       namespaces for avoiding name conflicts if more than one template set 
       is used. Also, the type of the outlet must be given (currently
-      supported are "velocity" and "java"). Depending on the type, further
-      informations need to be given: The velocity outlets need the path
-      to the template (relative to the templates subdirectory),
+      supported are "velocity", "groovy", and "java"). 
+      Depending on the type, further informations need to be given: 
+      The velocity and groovy outlets need the path to the template 
+      (relative to the templates subdirectory),
       the java outlets need the class of the outlet class.
       For example, this defines a java and a velocity outlet:
     </p>
@@ -313,6 +314,8 @@
         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.
+      </p>
+      <p>
         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
@@ -320,6 +323,14 @@
         Also, the encoding of the templates will be assumed to be 
         the vm's default encoding.
       </p>
+      <p>
+        If a template exists in two known languages 
+        (e.g. myTemplate.vm and myTemplate.groovy), it is currently undefined
+        which template of the two will be used for automatic outlet definition.
+        So if automatic outlet definition is used for defining outlets,
+        make sure all templates have a different filename even when omitting
+        the suffix.
+      </p>
     </subsection>
   </section>
  </body>



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


Mime
View raw message