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: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type;
  b=E76mzAW39GwckwE0O7D+FTv8GgL1NP2IbS9Y8EOtxBuOX9HZGEHQHL2VAJCyhfhnabJrbGHtl2hvyGOGglM5sm//edXId2vINUCXz+sbNUBrX80Qt+bpM7QEkF3q7oxfP2rTGbxIFoXl69Dht9yHjEPj70koC3sXAo/RFjGeuGs=;
Message-ID: <1318637331.1577.YahooMailClassic@web130208.mail.mud.yahoo.com>
Date: Fri, 14 Oct 2011 17:08:51 -0700 (PDT)
From: Harakiri <harakiri_23@yahoo.com>
Subject: Re: Upgrading to apacheds-service-2.0.0-M3.jar -
 ClassNotFoundException
To: users@directory.apache.org
In-Reply-To: 
 <CADwPi+HMf8vm+aDeCcMi3TZZag-FzvjOOdp3J4MX2OC5g-t29g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii


--- On Fri, 10/14/11, Alex Karasulu <akarasulu@apache.org> wrote:

> From: Alex Karasulu <akarasulu@apache.org>
> Subject: Re: Upgrading to apacheds-service-2.0.0-M3.jar - ClassNotFoundException
> To: users@directory.apache.org
> Date: Friday, October 14, 2011, 9:09 AM
> On Fri, Oct 14, 2011 at 3:43 PM,
> Harakiri <harakiri_23@yahoo.com>
> wrote:

> There are several references to fully qualified class names
> in the schema
> partition which will cause problems for you when moving
> from the old version
> to the latest release. This is due to class renaming,
> deletions, and package
> movement.
> 
> I recommend you export an LDIF of your DIT and reimport it
> on the latest
> release. This is the least painful most well defined path
> you can follow for
> an upgrade at this present time.
> 

I dont have any physically stored schema - its just a custom partition which returns static values based on specific search requests - this has nothing todo with reimporting anything - its in memory only - i dont see the custom partition example updated for 2.x and i need the above code to initialize the LDAP server upon start