You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2013/10/08 13:22:42 UTC
[jira] [Commented] (SLING-2212) Implement Servlet API 3.0
[ https://issues.apache.org/jira/browse/SLING-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13789116#comment-13789116 ]
Bertrand Delacretaz commented on SLING-2212:
--------------------------------------------
IMO the backwards compatibility with Servlet API 2.5 needs to be verified by automated tests - maybe just running the affected code on an older embedded Jetty server is sufficient.
> Implement Servlet API 3.0
> -------------------------
>
> Key: SLING-2212
> URL: https://issues.apache.org/jira/browse/SLING-2212
> Project: Sling
> Issue Type: Improvement
> Components: Engine
> Affects Versions: Engine 2.2.6
> Reporter: Aleksander Bandelj
> Attachments: servlet30.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> New versions of Pax Web, Equinox Web, Grizzly and other OSGI web servers will use version 3.0 of Servlet API. Sling Engine implementing only 2.5 will not run in these. Since Sling Engine implements API interfaces (ServletContext notably), it will have to implement new API methods and tighten some existing type signatures. Change is supposed to be backward-compatible (Sling Engine implementing 3.0 API can be used with 2.5 API as well).
--
This message was sent by Atlassian JIRA
(v6.1#6144)