Re: [Wrapper-user] dev/stage/production configuration selectors

[Leif M. <le...@ta...>]

Chandra,
I would still suggest using Ant to create your wrapper.conf.
If that is not an option, how about this:

In your wrapper.conf file, add an include line like this:
#include ../conf/wrapper-%BUILD_MODE%.conf

The you can set a BUILD_MODE environment variable to control
exactly which include file is used.

I was not clear from your original request how you would
expect the wrapper to know which configuration mode to
be using at any time anyway.

Cheers,
Leif

Chandra Patni wrote:
> BTW, I am only asking for tagging <N> type properties. Usually, one
> would use wrapper.java.initmemory, wrapper.java.maxmemory for memory
> settings. Under this model, one would use wrapper.java.additional.<N>
> for memory settings. 
> We also use these for heaps > 4G. Wrapper is hard coded for no more 4G
> memory even for 64 bit versions.
>
>
>
>
> -----Original Message-----
> From: wra...@li...
> [mailto:wra...@li...] On Behalf Of Chandra
> Patni
> Sent: Wednesday, May 23, 2007 11:27 PM
> To: wra...@li...
> Subject: Re: [Wrapper-user] dev/stage/production configuration selectors
>
> Leif,
> We share application/configuration between servers. One example of this
> is -Xms -Xmx for servers with 2GB vs 4GB memory. And we don't want to
> have proliferation of config files for small changes but at the same
> time allow some minors variation based on tags.
>
> I hope that you recognize that fine grained config selectors are very
> useful features.
>
> One way to achieve the same effect by using 
>
> #include nfspath/%TAG_NAME%/j2ee.conf
>
> Due to strict numbering requirement for wrapper
> wrapper.java.additional.<n>, etc makes this difficult to maintain. Do
> you have any plans to remove this restriction? I was looking at the
> wrapper code and it didn't seem too difficult. 
>
> -Chandra
>
> -----Original Message-----
> From: wra...@li...
> [mailto:wra...@li...] On Behalf Of Leif
> Mortenson
> Sent: Wednesday, May 23, 2007 6:08 PM
> To: wra...@li...
> Subject: Re: [Wrapper-user] dev/stage/production configuration selectors
>
> Chandra,
> This is something that I often do myself using Ant.   It is quite easy
> to
> do token replacements using Ant and generate the wrapper.conf
> from a template.   Have you looked into this?  It would make your
> production wrapper.conf much cleaner than what you suggested.
>
> Let me know if there are some reasons why Ant would not work for
> you.
>
> Cheers,
> Leif
>
> Chandra Patni wrote:
>   
>> It will be quite useful if wrapper can support,
>>
>> wrapper.java.additional.N.development=-DDevSpecificProperty
>> wrapper.java.additional.N.staging=-DStagingSpecificProperty
>> wrapper.java.additional.N.production=-DProductionSpecificProperty
>>
>> #APPLICATION_ROLE variable is set to either (development, staging,
>> production) 
>>
>> wrapper.config.filter.selector=%APPLICATION_ROLE%
>>
>> I am wondering if anything like this already exists or in the
>>     
> pipeline.
>   
>> -Chandra
>>