|
From: Anthony F. <ant...@co...> - 2003-05-08 17:21:58
|
First off, I must say this is one of the nicest Java service wrappers I have yet to use. It's flexibility and ease-of-use are unmatched! Kudos and thanks to Leif and the Wrapper team for making it available. I think I may be missing something with configuration that I'm hoping someone has some suggestions for. My standard practice has always been to write config files for my Java applications such that paths are relative to the "home" directory of the application. I also like to put executables (including Wrapper) in a "bin" directory. I know Wrapper is designed to always use the executable directory as the working directory and that relative paths can be used in wrapper.conf which is great because I can count on it. My problem is that all of my non-wrapper.conf config files also need to be "aware" of the location of the executable and specify relative paths with a '../' prefix. The solution I've come up with is to add a "app.home" system property that gets used as the base to all relative paths throughout my application. This is a little cumbersome though since this needs to be done everywhere throughout the application. Is it possible to set the Java process's notion of the current working directory to this "home" directory or am I missing something else entirely? Thanks for the help, -Tony |