[
https://issues.apache.org/jira/browse/OODT-606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13643815#comment-13643815
]
Paul Ramirez commented on OODT-606:
-----------------------------------
Here is an example of a velocity template:
$env.USER Welcomes to $metadata.conference#foreach($name in
$metadata.getValues('name')) $name#end!
The $env gets you access to environment variables and the $metadata gets you
access to metadata that is flowed through the PGE. When using $env what follows
the . is the actual environment variable. When using the $metadata what follows
the . is the key name. If you have a metadata key with more than one value and
use the $metadata.key format you will only get the first value. To get all
values use $metadata.getValues(key). For more information on what can be done
in velocity see
http://velocity.apache.org/engine/releases/velocity-1.7/user-guide.html.
This is great for integrating calls to other languages as you can dynamically
make a script to call your other program that may be written in another
language.
> SciPgeWriter that uses ApacheVelocity
> --------------------------------------
>
> Key: OODT-606
> URL: https://issues.apache.org/jira/browse/OODT-606
> Project: OODT
> Issue Type: New Feature
> Components: pge wrapper framework
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Fix For: 0.6
>
>
> We've cooked up a SciPgeInputFileWriter that generates PGE input files based
> on Apache Velocity. Unfortunately this is for 0.3 PGE, so we'll have to
> update to 0.6 once we fix the issues with 0.6 PGE.
> Patch coming shortly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
