This invocation should go through ApplicationConfiguration.
The idea of 'ApplicationConfiguration' is to be a Facade on top of all the different configuration types we have, so that the rest of the system doesn't care where a specific bit of configuration is being loaded from.

I think with the database/jndi configuration changes we lost the code that was resetting the configuration when changes where detected (See `ApplicationConfigration` and `ServerConfigurationBean`). Maybe we should bring back this event, and even add a parameter so that it only "resets" the specific bit of configuration that changed. 

II know it's a bit much to explain over a comment, but I can do the change and you can review it.