Hi John,

when looking at DefaultConfiguration, wouldn't it be possible to wrap the
BootstrapPropertyResolver passed to setBootstrapPropertyResolver in your
RuntimeConfiguration subclass? So you'd have something like

    @Override
    public void setBootstrapPropertyResolver(BootstrapPropertyResolver
resolver) {

super.setBootstrapPropertyResolver(DecoratedBootstrapPropertyResolver(resolver));
    }

That way, you could override certain properties, whereas you can fall back
to the default bootstrap property resolver when needed.

Regards,
  Levi

On Tue, Apr 7, 2009 at 4:47 PM, Newman, John W <[email protected]> wrote:

>  Hello,
>
>
>
> We are currently revisiting all this property file/filtering mess in our
> app.    One thing we had setup was to put all config settings in a master
> property file, and use maven resource filtering in web.xml.
>
>
>
> <init-param>
>
>                   <param-name>ActionResolver.Packages</param-name>
>
>                   <param-value>
>
>                         ${stripes.actionPackages}
>
>                   </param-value>
>
>             </init-param>
>
>             <init-param>
>
>                   <param-name>ActionBeanContext.Class</param-name>
>
>                   <param-value>${stripes.actionBeanContextClass}</
> param-value>
>
>             </init-param>
>
>             <init-param>
>
>                   <param-name>Interceptor.Classes</param-name>
>
>                   <param-value>
>
>                         ${stripes.interceptorClasses}
>
>                   </param-value>
>
>             </init-param>
>
>
>
> We used to have these hard coded, but they started changing from env to env
> so we moved them into our filter files.  Now we are experimenting with some
> cleaner spring classes for this, but we’re not able to get web.xml filtered
> like that.  So I’m looking to remove these settings from here, and set them
> in the code of our Configuration subclass with
> appProperties.getString(“stripes.actionPackages”)
>
>
>
> However digging through the stripes code a bit it appears this is not
> possible?  Configuration just grabs the BootstrapPropertyResolver and goes
> through web-xml etc.  It doesn’t appear there is a way to customize this
> behavior?  It looks like they must be specified in web.xml.  Can I just put
> dummy values in there and change them at a later point?
>
>
>
> Also if anyone knows of a simple easy best practice solution for
> international, multi env app property management please share.  We haven’t
> really run across a tried and true best practice approach for this, it seems
> like everyone does something different and it ends up getting tricky in the
> end.
>
>
>
> Thanks
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> High Quality Requirements in a Collaborative Environment.
> Download a free trial of Rational Requirements Composer Now!
> http://p.sf.net/sfu/www-ibm-com
> _______________________________________________
> Stripes-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/stripes-users
>
>
------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
Stripes-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-users

Reply via email to