on 7/6/01 11:11 AM, "Jon Stevens" <[EMAIL PROTECTED]> wrote:
> on 7/6/01 5:37 AM, "Diethelm Guallar, Gonzalo" <[EMAIL PROTECTED]>
> wrote:
>
>> It might be a good feature to be able to have a base properties
>> file somewhere, which you would (almost) never touch and would
>> be distributed with Turbine, and one or more overriding files
>> that would hold your local config. For example:
>>
>> WEB-INF/conf/TR.props
>> WEB-INF/conf/<servlet>.props
>>
>> and Turbine could know to read TR.props first, then read the local
>> props file, overriding any previous settings.
>
> You can already do that with an "include=" at the bottom of the TR.props
> file.
>
> -jon
Wait, I take that back...test that first...
In reality though, I would rather have the TR.props file generated from a
base set of values instead of overriding existing values.
-jon
--
If you come from a Perl or PHP background, JSP is a way to take
your pain to new levels. --Anonymous
<http://jakarta.apache.org/velocity/ymtd/ymtd.html>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
