With the new ResourceResolver abstraction and resource resolver chain
in 4.1, the assumption that resources are found by checking for the URL
path under the configured locations is no longer accurate.
A custom ResourceResolver could find resources in ways that don't
depend on a list of locations.
Issuse: SPR-12133
@ -86,11 +86,11 @@ public class ResourceHttpRequestHandler extends WebContentGenerator implements H
@@ -86,11 +86,11 @@ public class ResourceHttpRequestHandler extends WebContentGenerator implements H
@ -105,7 +105,8 @@ public class ResourceHttpRequestHandler extends WebContentGenerator implements H
@@ -105,7 +105,8 @@ public class ResourceHttpRequestHandler extends WebContentGenerator implements H
*/
publicvoidsetLocations(List<Resource>locations){
Assert.notEmpty(locations,"Locations list must not be empty");
this.locations=locations;
this.locations.clear();
this.locations.addAll(locations);
}
publicList<Resource>getLocations(){
@ -154,7 +155,8 @@ public class ResourceHttpRequestHandler extends WebContentGenerator implements H
@@ -154,7 +155,8 @@ public class ResourceHttpRequestHandler extends WebContentGenerator implements H