[SLING-10934] Bundled scripts in the form of <resourceLabel>.<METHOD>.<extension> override the Sling POST Servlet

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Scripting Core 2.4.0, Servlets Resolver 2.9.0, Scripting Bundle Maven Plugin 0.5.0
• Fix Version/s: Scripting Core 2.4.2, Scripting Bundle Maven Plugin 0.5.2
• Component/s: Maven Plugins and Archetypes, Scripting, Servlets
• Assignee: Karl Pauls
• Reporter: Karl Pauls
• Created: 21/Nov/21 23:43
• Updated: 21/Dec/21 09:16
• Resolved: 22/Nov/21 11:02

Description

Currently, it is not really possible using bundled scripts to provide a script for a resource label with an HTTP method and at the same time a script for only the HTTP method. Furthermore, when providing the former, there is a small difference in precedence compared to scripts provided via the resource tree.

In other words, it should be possible to have (for a given resource type, e.g. foo) a foo/POST.jsp and as well as a foo/foo.POST.jsp and they should have the same matching and priority like scripts provided via the resource tree.

On the metadata level, this can be achieved by just adding the resource label as a selector to the resulting capability but to make it work at runtime, we need to add a match to the bundle render unit lookup.

Issue Links

• links to: GitHub Pull Request #2
• links to: GitHub Pull Request #9
• links to: GitHub Pull Request #11