[
https://issues.apache.org/jira/browse/JCR-4892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17986975#comment-17986975
]
Carsten Ziegeler commented on JCR-4892:
---------------------------------------
>From my pov compatibility combined with an upgrade path are the key aspects.
>In Sling (as well as in OSGi) we decided to provide new API for support
>Jakarta servlet API next to the API supporting javax servlet API. In Sling we
>primarily added new interfaces and methods, in OSGi we picked different
>packages. The point here is to make it easy to run code that is using the old
>API side by side with code that has already been migrated to use the new API
>(or directly written to use the new API). This way your clients are not forced
>into an all or nothing approach where either all code is using the old API or
>all code has to use the new API.
Apart from the API, there is sometimes also a challenge for the implementation
of the API, can two implementations (for old API and for new API) run at the
same time, can one implementation handle both APIs etc. This of course depends
on the kind of the API and implementation.
> support the jakarta.servlet package name
> ----------------------------------------
>
> Key: JCR-4892
> URL: https://issues.apache.org/jira/browse/JCR-4892
> Project: Jackrabbit Content Repository
> Issue Type: New Feature
> Reporter: Julian Reschke
> Priority: Major
> Fix For: 2.24
>
> Attachments: JCR-4892_v2_project_root.patch,
> JCR-4892_v2_workspace_root.patch, JCR-4892_v3.patch, JCR-4892_v4.patch, clean
> install-Output.txt, jackrabbit-webdav-jakarta.patch, patch.txt, webapp.patch,
> webapp2.patch
>
>
> ...without breaking existing uses for now.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
