If you use the ConfigurationFactory from commons-configuration, you can set up a hierarchy of properties files, and have turbine.properties be the last choice. then, save your changes to a myturbine.properties file and it will override any properties that are in turbine.properties. there are unit tests demonstrating this.
Eric > -----Original Message----- > From: Niki Ivanchev [mailto:[EMAIL PROTECTED] > Sent: Friday, April 16, 2004 8:35 AM > To: [EMAIL PROTECTED] > Subject: refreshing turbine.properties or how to change skin on the fly > > > Hello to all. > I have this problem. I am creating some site with web based > administration module. Wtihin this administration mocule, site owner can > chage some site properties. One of this property is the site skin. Since > the default skin can be found on the turbine.properties file: > What I have done is > 1. Administrator selects a skin > 2. From the PullService I get UIManager Tool. > 3. I set the new Skin using setSking(); > But.. when application is restarted, the default skin is selected from > the turbine.properties file. How can I make skin selection 'permanent'? > Shall I write to turbine.properties or there is ready solution to this? > Reghards > Niki > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
