You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Alex Karasulu (JIRA)" <ji...@apache.org> on 2007/08/18 04:40:30 UTC

[jira] Updated: (DIRSERVER-866) Initialization with another backend than JDBM for the system partition

     [ https://issues.apache.org/jira/browse/DIRSERVER-866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Karasulu updated DIRSERVER-866:
------------------------------------

    Fix Version/s:     (was: 1.5.1)
                   1.5.2

> Initialization with another backend than JDBM for the system partition
> ----------------------------------------------------------------------
>
>                 Key: DIRSERVER-866
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-866
>             Project: Directory ApacheDS
>          Issue Type: New Feature
>            Reporter: Emmanuel Lecharny
>             Fix For: 1.5.2
>
>
> The initialization process statically declare a JdbmPartition in the current base code. If we were to use another backend, we should use a factory plus a configuration to initialize the alternate implementation :
> in DefaultPartitionNexus.initializeSystemPartition() method, we have :
> ...
>         system = new JdbmPartition(); // using default implementation.
>         system.init( factoryCfg, systemCfg );
> ...
> where system is the system backend.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.