I was hoping I could piggy-back on an existing velocity/tomcat mechanism instead writing some code to read a property file. Looks like I won't be reinventing the wheel. That's what I wanted to know.
Thanks for info, Doug On Mon, Mar 21, 2011 at 09:00:10PM +0100, Claude Brisson wrote: > Hi Doug, > > this question is far from being specific to Velocity. I'm not aware of > any standard on the subject. You could simply read an unversioned flat > properties file at the time the webapp is launched, or use versioned > branches for development and production. > > Claude > > On 2011-03-15 19:35, Doug Carter wrote: > >Hi All, > > > >I know of a few ways of solving this problem, but I thought I'd check > >with you all, in the likely case I'm reinventing the wheel. > > > >Recently we implemented Single-Sign-On for a velocity app in our > >production environment, which I would like to disable in a development > >environment. I was thinking about setting a property to control > >application authentication. Something like a property file that doesn't > >get checked into SCM, that contains settings based on the running > >application environment. > > > >Is there a "preferred" way of doing this with Velocity? If not, do any of > >you use or are you aware of an easy way to control run-time properties, > >where you can easily disable functionality like authentication during > >development? > > > > > >TIA, > > > >Doug > > > > > > > >--------------------------------------------------------------------- > >To unsubscribe, e-mail: user-unsubscr...@velocity.apache.org > >For additional commands, e-mail: user-h...@velocity.apache.org > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@velocity.apache.org > For additional commands, e-mail: user-h...@velocity.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@velocity.apache.org For additional commands, e-mail: user-h...@velocity.apache.org
