Mailing-List: contact users-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@directory.apache.org
Received-SPF: pass (athena.apache.org: domain of wjohnson@mqsoftware.com
 designates 66.192.70.108 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C85E0C.BFDFAED9"
Subject: Accessing ApacheDS database directly
Date: Wed, 23 Jan 2008 16:10:23 -0600
Message-ID: <63BEA5E623E09F4D92233FB12A9F7943019B50B5@emailmn.mqsoftware.com>
Thread-Topic: Accessing ApacheDS database directly
Thread-Index: AcheDL/nOtj1AQ2WQPm6yLXcFAIBzQ==
From: "Wayne Johnson" <wjohnson@mqsoftware.com>
To: <users@directory.apache.org>

------_=_NextPart_001_01C85E0C.BFDFAED9
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

We've got ApacheDS embedded into our product and now it's time to start =
looking to the next release. =20
=20
In the next release we would like to be able to edit some of the data in =
the LDAP database while doing an upgrade, however, since we're doing an =
upgrade, the database server shouldn't be up because we're in the =
process of replacing files, etc. =20
=20
How hard would it be to access the Database Backend directly.  How =
advisable is this?  Is it a published API that would be somewhat stable, =
or are we hacking where we shouldn't. =20
=20
Anyone have any hints on where in the source tree to look for these =
backend classes?
=20
Thanks.

Wayne Johnson=20
Senior Software Engineer=20
MQSoftware, Inc.=20
1660 S Highway 100=20
Minneapolis, MN 55416=20
(952) 345-8628=20

=20

------_=_NextPart_001_01C85E0C.BFDFAED9--