[ https://issues.apache.org/jira/browse/JCR-3222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13194074#comment-13194074 ]
Felix Meschberger commented on JCR-3222: ---------------------------------------- Unfortunately this is a compiled library and I cannot see, what's changed .... But then, somehow this feels like official Reflection Programming .... How about using OSGi services ? (0) The DavexServletService is already registered as a Servlet service for Whiteboard Http Service registration (1) We could add a contextId configuration which could be configured to refer to a HttpContext service used by the Whiteboard registration (2) Support a SessionProvider service providing pluggability Sling (or other OSGi based use cases) could then just provide the missing pieces. Will provide a proposed patch. > Allow servlet filters to specify custom session providers > --------------------------------------------------------- > > Key: JCR-3222 > URL: https://issues.apache.org/jira/browse/JCR-3222 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: jackrabbit-jcr-server > Reporter: Jukka Zitting > Priority: Minor > Attachments: jackrabbit-jcr-server-2.6-SNAPSHOT.jar > > > In order to integrate the Jackrabbit davex server functionality with their > custom authentication logic, the Sling project currently needs to embed and > subclass the davex servlet classes. It would be cleaner if such tight > coupling wasn't needed. > One way to achieve something like that would be to allow external components > to provide a custom SessionProvider instance as an extra request attribute. > This way for example a servlet filter that implements such custom > authentication logic could easily make its functionality available to the > standard davex servlet in Jackrabbit. -- 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