The module's virtualURIMapping node used to not be bootstrapped but autogenerated with random uuid by the module mechanism. VirtualURIManager caches the defined mappings and reloads them upon a change to any mapping's configuration. This is based on node uuids. If one does such change and doesn't activate the particular mapping but the whole virtualURIMapping node, the uuid at Public gets changed and the manager is not able to reload it as it expects the former uuid. This causes all the module's mappings to not be working and the only way to fix it is to restart the webapp so that the manager registers all the existing mappings from scratch. We should fallback to path in such case.