PropertiesInitializer currently attemps to load all paths passed to it (the magnolia.initialization.file context param) as relative to the rootPath of the webapp. In many environments, it would be useful to let users have this file outside the webapp, letting them adjust settings without touching the webapp (which could be a non-exploded war file, and you wouldn't really feel comfortable messing about with temp/work files on the appserver would you)

It might also be useful to be able to load it off the classpath, while we're at it, but that'd be another issue.