Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (nike.apache.org: domain of ayyagarikiran@gmail.com
 designates 209.85.220.178 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        b=TLT9dC334vatbydqzMVFKHJwz9GUyD8ycf7TTmS9wtGK2juS1r8OKCFONAJBA9H682
         HArAtbmhc2F4FLW66+m+Iz1YCWrfMcX7OZZoUYL4t6G0dN5Sj8oFf7T94Klm7QIZ5KEu
         68zOhYLVjLp48x/UXJAn9+6kpRbR4PTK/naN0=
MIME-Version: 1.0
Sender: ayyagarikiran@gmail.com
In-Reply-To: 
 <F63F6C4D6F2A0240A71227AA7134D3AB0B6F94DE@THHS2E12BE1X.hostedservice2.net>
References: <4DD96690.8070200@datanomic.com>
	<BANLkTinznk5BMAu9cws9a79AMdLKpvwbiA@mail.gmail.com>
	<F63F6C4D6F2A0240A71227AA7134D3AB0B6F94DE@THHS2E12BE1X.hostedservice2.net>
Date: Mon, 23 May 2011 15:12:25 +0530
Message-ID: <BANLkTinOxqe4D16Fvr4t96s1_UcY+8Q7SA@mail.gmail.com>
Subject: Re: Embedding ApacheDS using DirectoryServiceBean etc
From: Kiran Ayyagari <kayyagari@apache.org>
To: Apache Directory Developers List <dev@directory.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Mon, May 23, 2011 at 2:27 PM, Richard Evans
<richard.evans@datanomic.com> wrote:
> I'm not sure I get this. =A0It seems as though using DirectoryServiceBean=
 and ServiceBuilder just can never work because of this NPE. =A0Surely that=
's a bug? =A0I do create a schema manager in the XML:
>
> =A0<bean class=3D"org.apache.directory.server.config.beans.DirectoryServi=
ceBean" id=3D"dsb">
> =A0 =A0...
> =A0</bean>
>
> =A0<bean id=3D"ds" class=3D"org.apache.directory.server.config.ServiceBui=
lder" factory-method=3D"createDirectoryService">
> =A0 =A0<constructor-arg ref=3D"dsb"/>
> =A0 =A0<constructor-arg ref=3D"il"/>
> =A0 =A0<constructor-arg ref=3D"sm"/>
> =A0</bean>
>
> =A0<bean id=3D"il" class=3D"org.apache.directory.server.core.InstanceLayo=
ut">
> =A0 =A0...
> =A0</bean>
>
> =A0<bean id=3D"sm" class=3D"org.apache.directory.shared.ldap.schemamanage=
r.impl.DefaultSchemaManager"/>
>
what I mean is that the schema manager created in this way is not
useful unless a schema loader is set.

   the procedure goes like this:

        SchemaLoader loader =3D new LdifSchemaLoader(
schemaPartitionDirectory ); // <-- you can also use
JarLdifSchemaLoader
        schemaManager =3D new DefaultSchemaManager( loader );

        // We have to load the schema now, otherwise we won't be able
        // to initialize the Partitions, as we won't be able to parse
        // and normalize their suffix Dn
        schemaManager.loadAllEnabled();

HTH
> Richard
>
> -----Original Message-----
> From: ayyagarikiran@gmail.com [mailto:ayyagarikiran@gmail.com] On Behalf =
Of Kiran Ayyagari
> Sent: 22 May 2011 21:02
> To: Apache Directory Developers List
> Subject: Re: Embedding ApacheDS using DirectoryServiceBean etc
>
> On Mon, May 23, 2011 at 1:10 AM, Richard Evans
> <richard.evans@datanomic.com> wrote:
>> I'm experimenting with embedding ApacheDS (1.5.8-SNAPSHOT built from tru=
nk)
>> using configuration beans created in Spring XML along with the
>> ServiceBuilder. =A0I've attached where I've got to so far - it is not
>> complete, but I've run into a couple of problems.
>>
>> Firstly I get an NPE:
>>
>> java.lang.NullPointerException
>> =A0 =A0at
>> org.apache.directory.server.core.schema.registries.synchronizers.Registr=
ySynchronizerAdaptor.<init>(RegistrySynchronizerAdaptor.java:123)
>> =A0 =A0at
>> org.apache.directory.server.core.schema.SchemaPartition.doInit(SchemaPar=
tition.java:224)
>> =A0 =A0at
>> org.apache.directory.server.core.partition.AbstractPartition.initialize(=
AbstractPartition.java:73)
>> =A0 =A0at
>> org.apache.directory.server.core.DefaultDirectoryService.initialize(Defa=
ultDirectoryService.java:1484)
>> =A0 =A0at
>> org.apache.directory.server.core.DefaultDirectoryService.startup(Default=
DirectoryService.java:962)
>> =A0 =A0at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> =A0 =A0at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav=
a:39)
>> =A0 =A0at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor=
Impl.java:25)
>> =A0 =A0at java.lang.reflect.Method.invoke(Method.java:597)
>> =A0 =A0at rde.tests.apacheds.LaunchADS.main(LaunchADS.java:49)
>>
>> It looks as though the SchemaManager instance is never set on the
>> SchemaPartition created by DefaultSchemaService.
>>
> the SchemaManager won't be created by SchemaPartition automatically
> rather we need to set it after loading
> the schema with any of the available schema loaders.
>
> Take a look at the methods initSchemaLdifPartition and
> initDirectoryService present in ApacheDsService class they might give
> you an idea.
>
>> Secondly, in 1.5.7 the suffix for a partition was a string, now it's a D=
n.
>> =A0There are lots of constructors for the Dn object - which should be us=
ed
>> here?
>>
> you can use the one which takes a single string argument while
> configuring, but in general it is good to use the Dn(SchemaManager,
> String...)
> if you have access to the schema manager.
>> Thanks
>>
>> Richard
>>
>
>
>
> --
> Kiran Ayyagari
>


--=20
Kiran Ayyagari