[
https://issues.apache.org/jira/browse/SLING-12643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17953890#comment-17953890
]
Carsten Ziegeler commented on SLING-12643:
------------------------------------------
Changed the approach and removed the duplicate Jakarta based scripting classes,
instead extended the existing ones (where needed):
https://github.com/apache/sling-org-apache-sling-api/commit/bd5348914a418dd9acf4aa2d5e9fae04680ef1de
> Support Jakarta ServletAPI in Scripting
> ---------------------------------------
>
> Key: SLING-12643
> URL: https://issues.apache.org/jira/browse/SLING-12643
> Project: Sling
> Issue Type: Sub-task
> Components: Scripting
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Priority: Major
> Fix For: API 3.0.0, Servlets Resolver 3.0.0, Scripting Core 3.0.0
>
>
> The current implementation for scripting core to support Jakarta Servlet API
> is still based on the javax servlet API - while it is possible to use
> Servlets bassed on the Jakarta Servlet API, everything else is currently not
> supported.
> Apart from the API in scripting core, this API from Sling API needs to be
> supported for Jakarta Servlet:
> - Support for SlingJakartaBindings (next to SlingBindings)
> - Support for SlingJakartaScript (next to SlingScript)
> - Support for SlingJakartaScriptHelper (next to SlingScriptHelper)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
