[
https://issues.apache.org/jira/browse/SLING-11656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-11656:
-------------------------------------
Description:
The recent refactoring of Sling's engine can lead to AbstractMethodErrors in
SlingHttpServletRequestImpl due to old/buggy code. The problem is that the
updated engine code is counting on a proper servlet 3.0 request implementation,
returning a proper ServletContext (via getServletContext()) and that one
properly implementing getMimeType().
It turns out that this is not the case in the wild which then leads to the
error.
In addition, even if the request implementations are complete, it is a change
in implementation - as the mime type service is most likely not used anymore
> Prevent AbstractMethodError in SlingHttpServletRequestImpl
> ----------------------------------------------------------
>
> Key: SLING-11656
> URL: https://issues.apache.org/jira/browse/SLING-11656
> Project: Sling
> Issue Type: Improvement
> Components: Engine
> Affects Versions: Engine 2.12.0
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Priority: Major
> Fix For: Engine 2.12.2
>
>
> The recent refactoring of Sling's engine can lead to AbstractMethodErrors in
> SlingHttpServletRequestImpl due to old/buggy code. The problem is that the
> updated engine code is counting on a proper servlet 3.0 request
> implementation, returning a proper ServletContext (via getServletContext())
> and that one properly implementing getMimeType().
> It turns out that this is not the case in the wild which then leads to the
> error.
> In addition, even if the request implementations are complete, it is a change
> in implementation - as the mime type service is most likely not used anymore
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
