Hi Kiran, >From your reply, I saw a pattern in the problem ... Camel case. I renamed all SevenSeas (including the filename) to lowercase and it works!
Last night I did dig into the persistence store and I did realized that "persisted" schemas file names are all lowercase and I wonder if that will contribute to the problem too? I tested a camelcase filename, i does not have any impact. On Mon, Apr 19, 2010 at 1:23 AM, Kiran Ayyagari <[email protected]>wrote: > hi Cheong, > > I confirm that there is an issue while loading the schema with the > name 'cn=sevenSeas' > but if I give a different name e.x 'cn=xyz' the schema gets loaded > perfectly. > > This is really weird, but can you try with a different schema name > > Kiran Ayyagari > > On Sun, Apr 18, 2010 at 7:15 PM, Cheong Chung Onn > <[email protected]> wrote: > > Hi again, > > > > I have just downloaded ApacheDS 1.5.7 and it has the same problem as > > reported earlier when I import the SevenSeas schema. However, it works > for > > both SevenSeas and my schema when they are imported into version 1.5.5. > > > > Are there extra steps I need to take when importing schema into versions > > after 1.5.5? > > > > > > Cheong Chung Onn wrote, On 4/18/10 11:52 PM: > >> > >> Hi, > >> > >> Importing a customized schema to ApacheDS 1.5.6 does not seems to work > >> though it works on version 1.5.5. After spending a couple of hours of > futile > >> experimentation, I managed to track down the SevenSeas schema example. I > use > >> it to test if it was my schema that is giving problem or it ApacheDS > 1.5.6. > >> The errors reported by ApacheDS when I tried to import the SevenSeas > schema > >> using Apache Studio 1.5.6 on OSX 10.5.6. Below are the errors from the > >> Modification logs > >> > >> Is this fixed in ApacheDS 1.5.7 >
