Hi Michael,
Thanks for your comments ! Please see my thoughts below ...
BTW are you using Cactus on a real project now ? I have not hada lot of
feedback of who's using Cactus and in what environment and I think that
would be something really valuable to learn more what's missing and make
adjustements.
----- Original Message -----
From: "Michael Rimov" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, August 09, 2001 2:26 PM
Subject: Feature Request - Command-line property file location?
> Hello All!
>
> Since Vincent, et al. are working furiously on Cactus 2, I wanted to throw
> this request in:
There is no longer any Cactus 2 now that we have postponed the inclusion of
Mock Objects ... but we are working furiously on Cactus 1.2 ! :-)
>
> 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.
ok, but why do you check in the cactus.properties file ? This is something
that relates to the user environment and as such should not be checked in
CVS.
It also probably means each developer has its own servlet engine deployed on
his local machine, right ? (which I believe if the best option BTW)
>
> Would it be possible to have an optional JVM option that Cactus checks for
> first, something like:
>
> -Dcactus.propertyfile='blah blah blah'
yes, we could do that. But the negative points would be :
1/ that the more you have configuration options, the more difficult it is to
document it properly and the more difficult it is for users to choose how to
configure it ...
2/ It is more difficult to use (you have to specify a full path) and tie you
completely with your environment (because of the path). The good thing with
the classpath is that it is a portable mechanism that will work on any
environment, any OS...
>
> 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?
Why don't you put something like the following in your cactus.properties
cactus.servletRedirectorURL =
http://localhost:8080/mywebapp/ServletRedirector
And then give the rule to developers that they should run their servlet
engine on port 8080 and use the 'mywebapp' context for the test web
application?
Then you can check in cactus.properties, it would work for everyone.
>
> Thanks!
> -Mike
My 2 cents. Tell me what you think.
Thanks
-Vincent
