[SLING-7589] HTL doesn't correctly handle synthetic resource inclusions

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Scripting HTL Engine 1.0.54-1.4.0, Scripting HTL Testing Content 1.0.10-1.4.0, Scripting HTL Testing 1.0.10-1.4.0
• Component/s: Scripting
• Assignee: Radu Cotescu
• Reporter: Radu Cotescu
• Created: 17/Apr/18 14:54
• Updated: 22/Jun/18 14:12
• Resolved: 24/Apr/18 09:25

Description

When a synthetic resource is included in a data-sly-resource block element without any resourceType information, the HTL ResourceRuntimeExtension will not correctly dispatch the request. In those cases the request's resource type should be used as a fallback, to identify the correct scripts.

Example:
Assuming caller.html:

<div id="caller" data-sly-resource="${'/content/lorem-ipsum' @ resourceType='syntheticresource'}"></div>

and syntheticresource.html:

<div id="synthetic-resource">
    <span class="wrapper-text">Testing synthetic resource delegation</span>
    <div class="wrapper" data-sly-resource="${@ selectors='selector'}"></div>
</div>

results in the selector.html script not being found, due to not taking into consideration the original resource type of the request.

Issue Links

• links to: GitHub Pull Request #1
• links to: GitHub Pull Request #1
• links to: GitHub Pull Request #3