incubator-lokahi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Feist (JIRA)" <>
Subject [jira] Commented: (LOKAHI-4) Make configuration files (server.xml, based upon temples
Date Fri, 29 Feb 2008 15:56:51 GMT


Jeff Feist commented on LOKAHI-4:

Added patch (templateEngine.patch) for the following issues / enhancements:
- Updated HostingPoolModel to use the new TemplateDeployer
- Added logging code to VelocityTemplateEngine. By default, velocity will use its own logger
and write to the current working directory. The updated code used the currently running lokahi
log4j logger.
- Added MathTool to the VelocityTemplateEngine
- Added a buildString() method to the Templating engines so we can now process individual
strings with the engine. This comes in handy if you would want to template the location of
a deployed file. Eg: /etc/$worker.getPath()/conf/

> Make configuration files (server.xml, based upon temples
> ----------------------------------------------------------------------------
>                 Key: LOKAHI-4
>                 URL:
>             Project: Lokahi
>          Issue Type: Improvement
>            Reporter: Steve Toback
>         Attachments: conf_DB-patch.txt, java-patch.txt, tomcat-api-worker-serverxmlfile-factory.txt,
> As is right now - the server.xml file and files are generated by Lokahi
- and are hard-coded into the respective org.apache.lokahi.modjk.WorkersPropertiesFile and
org.apache.lokahi.tomcat.worker.ServerXmlFile classes 
> This does not allow server.xml files to differ based upon the template used.  Or newer
versions of mod_jk.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message