Enable a chrooted implementation of content manager with relative path resolution
Default implementation of the content manager shipped with the API, is able to secure the access of file within a predifined folder only (SecuredContentManager). However, it only deals with absolute file URLs. It means that if you need to distribute your application within two machines, you MUST have the same content manager storage folder location on both installations. This is not good. It would be better to have an implementation that is able to resolve the content URL using relative paths inside the configured content folder.