You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2016/04/18 14:17:25 UTC

[jira] [Created] (OAK-4218) Base SyncMBeanImpl on Oak API

angela created OAK-4218:
---------------------------

             Summary: Base SyncMBeanImpl on Oak API
                 Key: OAK-4218
                 URL: https://issues.apache.org/jira/browse/OAK-4218
             Project: Jackrabbit Oak
          Issue Type: Improvement
          Components: auth-external
            Reporter: angela


While looking at the oak-auth-external code base I found that {{SyncMBeanImpl}} is based on JCR API while sync called during authentication will solely rely on API defined by oak-core.

This not only limits the implementations to operations that can executed on the JCR API but also introduces the risk of inconsistencies.

As a matter of fact {{ExternalLoginModuleTestBase.createMBean}} also lists this as limitation and TODO:

{quote}
        // todo: how to retrieve JCR repository here? maybe we should base the sync mbean on oak directly.
{quote}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)