[
https://issues.apache.org/jira/browse/SLING-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12576955#action_12576955
]
Felix Meschberger commented on SLING-310:
-----------------------------------------
In Rev. 635535 I fixed the missing disposal (hence service unregistration) of
the SlingServletContext. In addition I prevent null pointer exceptions in the
SlingServletContext if called after the SlingMainServlet has been deactivated.
These calls may come from deactivation methods called because the
SlingServletContext is unregistered (e.g. the JspScriptEngineFactory, which
ensure the unregistration of a Jasper specific servlet context attribute)
> SlingMainServlet still used as the HttpContext after being deactivated
> ----------------------------------------------------------------------
>
> Key: SLING-310
> URL: https://issues.apache.org/jira/browse/SLING-310
> Project: Sling
> Issue Type: Bug
> Reporter: Bertrand Delacretaz
> Assignee: Felix Meschberger
> Fix For: 2.0.0
>
> Attachments: log.txt, SLING-310-0954.patch, SLING-310-debug.log,
> SLING-310-fmeschbe.patch, SLING-310.log
>
>
> In revision 633868, with this build/start sequence:
> cd launchpad/webapp
> cd ../app ; mvn clean install ; cd - ; mvn clean integration-test
> -Dintegration.test.wait=true
> Some integration tests fail, like for example
> PropertyRenderingTest.testTextNoExt
> The problem is that mimeTypeService is null here:
> HttpContext httpContext = new HttpContext() {
> public String getMimeType(String name) {
> return mimeTypeService.getMimeType(name);
> }
> event though the mimeTypeService of the enclosing class is set.
> Not sure what's happening, maybe there are several instances of this
> HttpContext around.
> To simplify, I'll change SlingMainServlet to implement HttpContext
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
