>From: Feist, Jeffrey >I know this topic was mentioned before. Lokahi needs better >support for different versions of apache. Right now Lokahi >will only deploy one type of config file for apache: >ApacheConfFile from lokahi.properties. There is also an issue
The name of the configuration file should really be something that is attached to the Server. That being said there's no nice place to put that right now... >Do you have any direction you are learning toward when adding >support for additional versions on apache? I was thinking >something similar to how different versions of tomcat are >handled. Currently there is a toggle switch for the version >which contains a value such as 4,5, or 6. This could be done >for Apache versions (version 1, 2, 2.2, etc) and this value >can be used to deploy files / write configs. That would work, but I don't like the way tomcat is currently handled. It was done that way due to the necessity for a quick fix. And has gone beyond it's usefulness. Not to mention the example you cited would be for mod_jk versions... Better to create a template based approach. Attach a template to each server (as in Apache Server or Tomcat Server) allowing customization of the configuration files... That way we don't have to adopt the tool to each new version that requires a new configuration set. There is an existing Jira issue http://issues.apache.org/jira/browse/LOKAHI-4 where Ludovic was kind enough to supply a factory approach to configuration building, which I haven't had the time to fully browse yet. There's no reason why we couldn't use that factory approach and have one of the implementations be a class that generates a configuration file based upon a velocity template for instance. Or some other templating engine. Steve ------------------------------------------------------------------------------ Notice: This e-mail message, together with any attachments, contains information of Merck & Co., Inc. (One Merck Drive, Whitehouse Station, New Jersey, USA 08889), and/or its affiliates (which may be known outside the United States as Merck Frosst, Merck Sharp & Dohme or MSD and in Japan, as Banyu - direct contact information for affiliates is available at http://www.merck.com/contact/contacts.html) that may be confidential, proprietary copyrighted and/or legally privileged. It is intended solely for the use of the individual or entity named on this message. If you are not the intended recipient, and have received this message in error, please notify us immediately by reply e-mail and then delete it from your system. ------------------------------------------------------------------------------
