You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Pierre-Arnaud Marcelot (JIRA)" <ji...@apache.org> on 2011/08/26 18:26:41 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 ]
Pierre-Arnaud Marcelot updated DIRSERVER-866:
---------------------------------------------
Fix Version/s: (was: 2.0.0-M2)
2.0.0-M3
> 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: 2.0.0-M3
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira