In fixing SLING-1181 I notice that the BundleResourceProvider gets
registered at a set of roots. In the older ResouceProviderEntry it was
only possible to register a single entry at one path location, which
means if one bundle registered its resource with Sling-Bundle-
Resources at /apps, then no others could do the same.
This is no longer the case, many bundles can also register their
resources at the same path eg /apps
The reason for mentioning this change is behavior is a) to warn
everyone that this can now happen and might change existing bundles
that were once in conflict and b) to suggest that where possible more
specific Sling-Bundle-Resources paths are chosen to avoid unnecessary
processing. ie if you have a bundle that provides resources at /apps/
myapp/contenttype/GET.esp then its probably better to use the most
specific path you can, eg /apps/myapp/contenttype or perhaps /apps/myapp
I hope this makes sense, the fix for SLING-1181 should also fix other
ResourceProviders that register sub trees of resources
(fsresourceprovider)
Ian
