You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-dev@jackrabbit.apache.org by "Jukka Zitting (Created) (JIRA)" <ji...@apache.org> on 2012/03/20 17:55:37 UTC

[jira] [Created] (OAK-31) In-memory MicroKernel for testing

In-memory MicroKernel for testing
---------------------------------

                 Key: OAK-31
                 URL: https://issues.apache.org/jira/browse/OAK-31
             Project: Jackrabbit Oak
          Issue Type: Improvement
          Components: mk
            Reporter: Jukka Zitting
            Assignee: Jukka Zitting


It would be good if the default MK implementation in oak-mk could be easily instantiated in an in-memory mode for testing purposes. Such an MK instance should not write anything to disk or otherwise share state with other clients through things like singleton instances, etc.

--
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

        

[jira] [Resolved] (OAK-31) In-memory MicroKernel for testing

Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OAK-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting resolved OAK-31.
------------------------------

       Resolution: Fixed
    Fix Version/s: 0.2

MicroKernelImpl has a default constructor that creates such an in-memory instance.
                
> In-memory MicroKernel for testing
> ---------------------------------
>
>                 Key: OAK-31
>                 URL: https://issues.apache.org/jira/browse/OAK-31
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: mk
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>             Fix For: 0.2
>
>
> It would be good if the default MK implementation in oak-mk could be easily instantiated in an in-memory mode for testing purposes. Such an MK instance should not write anything to disk or otherwise share state with other clients through things like singleton instances, etc.

--
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