On Tue, Sep 17, 2013 at 7:35 PM, <[email protected]> wrote: > > > Having this example comes in very handy, thanks for that. > But I have two questions: is it already foreseeable when the "interface" > will be fixed ? Reason for my question is that I want to build our new > solution on a final release and not on a milestone. > yes, partition interface is already locked, and the only change that will likely happen is in the constructors that we are reviewing at the moment to pass an additional parameter (the DN factory)
> Second question: is there an example how to implement a partition with a > custom backend ? I know there were examples for JDBC in 1.x but did not > find one for 2.0 > take a look at the implementations MavibotPartition or JdbmPartition (which use a disk based backend ) AvlPartition (which is an in-memory partition) these should serve as the perfect examples and if you get stuck somewhere feel free to post here we might be able to help > > > | Gesendet: Samstag, 14. September 2013 um 15:16 Uhr > | Von: "Kiran Ayyagari" <[email protected]> > | An: [email protected] > | Betreff: Re: Re: Re: [ApacheDS] Porting 1.x based custom partition to 2.0 > | Here[1] is the updated sample using M15 (M16 has changed the way a > | partition is initialized, so > | used M15 instead to keep it clear for the sake of understanding, except > | that there is no major change > | in initializing with M16) > | > | ... > | [1] > | > http://svn.apache.org/repos/asf/directory/sandbox/kayyagari/embedded-sample-trunk > > -- Kiran Ayyagari http://keydap.com
