[
https://issues.apache.org/jira/browse/SLING-2337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13189238#comment-13189238
]
Jukka Zitting commented on SLING-2337:
--------------------------------------
To me it looks like the problem is in the way the SlingDavExServlet class
implements the org.apache.jackrabbit.server.SessionProvider API.
The SessionProvider interface is pretty clear in that the releaseSession() will
be called when the "session acquired by a previous getSession() call is no
longer needed". Nowhere in this API is it specified that the session lifetime
needs to be limited by the lifetime of the request. A SessionProvider
implementation that closes the session before releaseSession() is called
explicitly breaks the API contract.
We can always debate whether the SessionProvider API should be modified (best
to file a JCR issue for that), but until then there needs to be a way for Sling
to abide by the current API.
> allow the session created by the SlingMainServlet to be left open after the
> request ends
> ----------------------------------------------------------------------------------------
>
> Key: SLING-2337
> URL: https://issues.apache.org/jira/browse/SLING-2337
> Project: Sling
> Issue Type: Improvement
> Components: Authentication, Engine
> Reporter: Justin Edelson
> Assignee: Justin Edelson
> Fix For: Engine 2.2.6, Auth Core 1.1.0, API 2.2.4
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
