Hello All!
Since Vincent, et al. are working furiously on Cactus 2, I wanted to throw
this request in:
I'm interested in being able to have a way to not require that the cactus
properties file be located within the class path. [as an option] Here's
the scenario why:
- Programmer A's machine is a different servlet engine configuration that
Programmer B. Both are using CVS.
With the config file within the source tree, both programmers are gonna
have a tendancy to set things up for themselves, and accidentally commit
the changes every so often. Stuff like this is a big pain in the butt. I
think the way things currently work is fine for most stuff so I'd ask that
by in large we keep things as is, but allow the properties file to be
specified somewhere.
Would it be possible to have an optional JVM option that Cactus checks for
first, something like:
-Dcactus.propertyfile='blah blah blah'
Then the cactus code could check for the System property cactus.property
file and load that property file, and if it doesn't exist, just try to
search the classpath?
Of course, that's just my first thought on how to solve my request. Any
thoughts on this?
Thanks!
-Mike
