[
https://issues.apache.org/jira/browse/SLING-10934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Radu Cotescu updated SLING-10934:
---------------------------------
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.
was:
Currently, it is not really possible using bundled scripts to provide a script
for a resource label with a method and at the same time a script for only the
method. Furthermore, when providing the former, there is a small difference in
precedence compared to normal scripts.
In other words, it should be possible to have (for a given resource type, say:
foo) a foo/POST.jsp as well as a foo/foo.POST.jsp and they should be used the
same way they would be when provided from the repository.
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, we need to add a
match to the bundle render unit look up.
> Bundled scripts in the form of <resourceLabel>.<METHOD>.<extension> override
> the Sling POST Servlet
> ---------------------------------------------------------------------------------------------------
>
> Key: SLING-10934
> URL: https://issues.apache.org/jira/browse/SLING-10934
> Project: Sling
> Issue Type: Bug
> Components: Maven Plugins and Archetypes, Scripting, Servlets
> Affects Versions: Scripting Core 2.4.0, Servlets Resolver 2.9.0, Scripting
> Bundle Maven Plugin 0.5.0
> Reporter: Karl Pauls
> Assignee: Karl Pauls
> Priority: Major
> Fix For: Scripting Core 2.4.2, Scripting Bundle Maven Plugin
> 0.5.2, Servlets Resolver 2.9.2
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
