with the new resource provider SPI an intelligent ResourceListener mechanism was introduced which allows to generate and route resource change events only when a listener is actual interested in this change. this works well when the resource provider is a root provider mounted at /.
however this currently fails when an additional resource provider is mounted at a specific path - e.g. at /apps/app1. in this case listeners mounted to specific glob patterns like glob:/apps/*/.html get the changes reported by the resource provider, but listeners registered to / do not.
this is a severe problem as some listeners like the script resolution cache are registered to /.