Interesting, I just noticed that with having the <configuration> blocks inside the feature file, they reset/overwrite any changes made via the GUI when restarting. So I think I'll go away from sticking default settings in there.
I understand where you're coming from with the features being rather static - I was then wondering what method people are generally using for deploying applications into their runtimes. OBR? Deployment-Packages? I like the idea of the deployment-package, having a single versioned .dp file that contains all of our apps bundles for version X which could be dropped into the ./deploy directory, but I had read somewhere in the compendium that if you deploy via a deployment-package, then the individual bundles can only be updated ALSO via a deployment package ( I've not yet tested this method tho ). It seems there's several options all with pros/cons - would be nice to see a "current best practice" doc... Mark -- Pull me down under... On Mon, Jul 19, 2010 at 6:33 PM, Guillaume Nodet <[email protected]> wrote: > For the configuration, I'm not sure how to handle the changes, as the > configuration in the feature is mostly an initial configuration but it > could be changed by users afterward, so I'm kinda tempted to say that > we would only register new properties and let existing ones as they > are.
