Question on extending the ApacheDS backend

["Barber, Dan (Contractor)" <Da...@Polycom.com>]

All,

 

I've been poking around getting a feel for what might be involved with
extending the backend to support a different database. I have been asked
a question by another member of the team. Given that the server.xml file
references the various partitions as beans, is it intended that the
ApacheDS backend be extendable without actual source code modification
to ApacheDS itself? In other words, could I implement subclasses of
Partition, Partition Configuration, and whatever else might be needed,
roll them into my own jar and reference them in server.xml?

 

Thanks,

 

Dan

 

Re: Question on extending the ApacheDS backend

[Ersin Er <er...@gmail.com>]

Hi Dan,

What you are asking for is perfectly possible. ApacheDS is extensible
in all means. What you see in server.xml are all pluggable. You can
plug new partition implementations or interceptors in order to make
ApacheDS really something different...

On 6/27/07, Barber, Dan (Contractor) <Da...@polycom.com> wrote:
> All,
>
>
>
> I've been poking around getting a feel for what might be involved with
> extending the backend to support a different database. I have been asked
> a question by another member of the team. Given that the server.xml file
> references the various partitions as beans, is it intended that the
> ApacheDS backend be extendable without actual source code modification
> to ApacheDS itself? In other words, could I implement subclasses of
> Partition, Partition Configuration, and whatever else might be needed,
> roll them into my own jar and reference them in server.xml?
>
>
>
> Thanks,
>
>
>
> Dan
>
>
>
>


-- 
Ersin Er

R.A. and Ph.D Student at the Dept. of Computer Eng. in Hacettepe University
http://www.cs.hacettepe.edu.tr

Committer and PMC Member of The Apache Directory Project
http://directory.apache.org