[
https://issues.apache.org/jira/browse/OAK-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13627754#comment-13627754
]
angela commented on OAK-768:
----------------------------
those classes are not internal to oak but are exposed on the SPI.
any other implementation other than the ones in the security package will
face the same problem.
i like the proposes solution from antonio as it allows us to resolve a lot
of TODOs and FIXMEs and hacks that we use to work around this missing piece.
and it does neither introduce new interfaces nor copy over all the methods
from ContentSession to the Root interface.
> Enhance Root API in order to provide information about the ContentSession
> --------------------------------------------------------------------------
>
> Key: OAK-768
> URL: https://issues.apache.org/jira/browse/OAK-768
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core
> Reporter: Antonio Sanso
>
> Different areas inside the oak-core code base show the needing of having
> ContentSession information when dealing with the Root Object.
> For an example see OAK-706 and OAK-707.
> For this reason it would nice if we could enhance the Root API with
> Root#getContentSession
> This will solve some of the workarounds currently in place
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
