[
https://issues.apache.org/jira/browse/OAK-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13731023#comment-13731023
]
Michael Dürig commented on OAK-938:
-----------------------------------
bq. I think we should treat the existing UserManagerImpl in the oak-core plugin
as the delegate class,...
I was thinking the same while tinkering around. In addition we could pass the
root associated with the correct revision (i.e. the "refreshed") root to
{{SessionOperation.perform()}}. That way the session related entities (e.g.
{{UserManager}}) implemented on top of {{Root}} need not rely on side effects.
> UserManager does not honour session refresh settings
> ----------------------------------------------------
>
> Key: OAK-938
> URL: https://issues.apache.org/jira/browse/OAK-938
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core
> Reporter: Antonio Sanso
> Attachments: OAK-938-patch, OAK-938-test-patch.txt
>
>
> When UserManager#getAuthorizable is used in a multiple sessions environment
> where a session creates an user and the other (already acquired) session
> tries to get the authorizable null is returned (even if the other session
> uses refresh-interval to 0)
> unit test to follow
--
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
