|
From: Merri J. <Mer...@sa...> - 2007-06-19 20:14:46
|
I'm not sure of the appropriate forum for this question so I thought I = would start here first. The java applications I support use a common launcher.exe and = launcher.sh file to execute. We have an ini formatted file that drives = the generic launcher where we list the java location, the command line = arguments, and the working directory. We also use the Service Wrapper = to start some of these applications as a service. =20 We may have multiple apps deployed on the same machine, so we have = implemented the launchers in such a way as to allow us to use a master = config file. Basically, it's a file that contains a list of variables = and their values (they are mostly paths) that we can then reference by = variable name in the ini files for each of the app launchers. This = creates a kind of lookthrough so that our customers are able to update = the value of a common variable in the master config file without having = to go and update each individual application ini file. I need to be able to do this same kind of "lookthrough" with the = wrapper.conf files we have created for the service launchers. I have = read the information about the cascading configuration files, but I'm = not sure if the options have to match exactly in the included file. Our = options do not match, so I'm trying to see if there is a way to make = this work without having to make code changes. I've included a sample = of what I am looking to do is below. Master.config file: [properties] JRE_PATH=3DC:/jre/bin/java.exe PROP_1=3DC:/some_path/to_some_file PROP_2=3DC:/another_path/1.0 Wrapper.conf: wrapper.java.command=3D<JRE_PATH> wrapper.java.classpath.1=3D<PROP_2>/wrapper.jar wrapper.java.classpath.2=3D<PROP_2>/xyz.jar wrapper.java.additional.1=3D-Dcom.testing.value=3D<PROP_1>/abc/xyz Is this even possible? Thanks for any and all assistance with this. -Merri |