Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
2.0.0-alpha
-
None
Description
two problems that need to be resolved.
FIrst is that ResourceResolver when handling resource['library:resourceName'], was passing the parsed arguments in backwards to ResourceHandler.createResource. It should have been name, library, but we were passing library,name.
Second problem is that we were prepending the context root twice due to multiple calls to getResource when the value attribute was a resource EL expression. First during the createResource call from ResourceResolver, and then again in the image renderer. Added a check for ResourceHandler.RESOURCE_IDENTIFIER constant prior to calling getResourceURL so we don't add it twice in the EL case.