[
https://issues.apache.org/jira/browse/OAK-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated OAK-768:
-----------------------
Attachment: OAK-768_b.patch
extended patch that cleans up TODOs and FIXMEs related to missing access to
workspace and principals from root.
note, that along with this changed i decided to clean up the way the Root
associated with a system principal is created during the long process. this
allowed me to simplify the authentication configuration and get rid of passing
nodestore, indexinfo, etc to the login.
a similar scenario in UserInitializer has not yet been addressed but is marked
with a TODO as we need some more work and decision on how to perform the
workspace-init. the latter is currently located in the Oak class but most
probably needs to be replaced.
> 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
> Attachments: OAK-768_b.patch, OAK-768-patch.txt
>
>
> 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
