change a config.properties file in a jar / war fil

问题:

change a config.properties file in a jar / war file in runtime and hotdeploy the changes ? my requirement is something as follows, we have a "config.properties" in a jar/war file , i have to open the file through a webpage and after the user has made necessary changes to it, i have to update the "config.properties" in jar/war file and hot deploy it. can we achieve this feat ? if so can you please point me to relevant sites/documents so that i can jumpstart on this.

回答1:

I will strongly recommend your architecht rethink this solution. What you describe should be done through JNDI or a similar technique, not through reloading properties.

Deployments should be considered static - that any given web container allows for magic trickery should not be depended on, and WILL break some day (most likely at the most inconvenient time).

回答2:

You've got a couple of problems off the top of my head:

1. ensuring that nothing is holding static references to a java.util.Properties that has previously loaded your config.properties file.

2. most servlet engines will unpack your war to a working directory so the properties file you load won't be the one in the war, it will be the unpacked one. This means your changes will be overwritten when you restart the servlet engine because this is typically one of the points the war is unpacked.

While these problems aren't insurmountable I've always found it much easier to implement this sort of behavior by storing the properties in JNDI (as Thorbjørn suggests) or a database (while being careful about the static references I mentioned in point 1).

The JNDI/database solution has the nice side effect of easing deployment into multiple environments because each typically has it's own registry/database.

回答3:

Even that I agree with the comments explained before, I could suggest one solution:

Apache Commons Configuration extension gives you the posibility to do something like:

config.setReloadingStrategy(new FileChangedReloadingStrategy());

That could make the trick to change the configuration file on a runtime basis with no code at all.

However, like JNDI and other methods of web application configuration, the security is a concern. Be careful on which parameters you can/must be able to configure.