In general, there wouldn't be a need to reload the configuration after ApplicationContext startup. However, there is a refresh() method you can call on an ApplicationContext, I don't recall the exact interface that method is defined, but there is one.
You see the line
ApplicationContext context = new ClassPathXmlApplicationContext("config-file.xml");
reads in the configuration and immediately creates
Java objects to represent the xml, once that is done the xml is no longer read or used. So you would have to tell Spring to re-read it.
You can always use Spring JMX and expose that property as an MBean attribute that you can go through a JMX console like jconsole, which comes with the JDK, go to that mbean at runtime and change the value. This will not change the xml, but will change the bean in the Spring container to now have that new value at runtime.
Mark