I think the best you can do is to provide a test which expose the problem.
On 7/26/07, Ole Ersoy <[EMAIL PROTECTED]> wrote:
Should I reopen the bug then? If I connect to the schema first I get the exception. Emmanuel Lecharny wrote: > The schema partition is used for everything, as all the data stored > into the server are described by it. So it should be declared first. > > On 7/26/07, Ole Ersoy <[EMAIL PROTECTED]> wrote: >> Hey Emmanuel, >> >> I went ahead and closed it. It's pretty minor. I have a feeling the >> order should not matter though. The DAS partition and the schema >> partition are independent. The layout looks like this: >> >> ou=das >> ou=schema >> >> If it were like this or flipped: >> ou=das, ou=schema >> >> then I would understand why the order matters. >> >> Thanks, >> - Ole >> >> >> >> >> Emmanuel Lecharny (JIRA) wrote: >> > [ >> https://issues.apache.org/jira/browse/DIRSERVER-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515625 >> ] >> > >> > Emmanuel Lecharny commented on DIRSERVER-1010: >> > ---------------------------------------------- >> > >> > Actually, as you can see in the stack trace, if you invert the >> order, there is a search done in the partition table, and if the >> partition does not exist, you get an error. So, basically, yes, order >> matters. >> > >> >> Should the order in which hot partitions are connected to matter? >> >> ----------------------------------------------------------------- >> >> >> >> Key: DIRSERVER-1010 >> >> URL: >> https://issues.apache.org/jira/browse/DIRSERVER-1010 >> >> Project: Directory ApacheDS >> >> Issue Type: Bug >> >> Reporter: Ole Ersoy >> >> >> >> If I connect in this order: >> >> dasContext = >> >> adsEmbeddedConnection. >> >> connect( >> >> configuration.getDasPartitionName() ); >> >> schemaContext = >> >> adsEmbeddedConnection. >> >> connect( >> >> configuration.getSchemaPartitionName() ); >> >> I don't get any exceptions. >> >> If I flip the two, I get this exception: >> >> >> org.apache.directory.shared.ldap.exception.LdapNameNotFoundException: >> ou=das >> >> at >> org.apache.directory.server.core.partition.DefaultPartitionNexus.getBackend(DefaultPartitionNexus.java:1064) >> >> >> at >> org.apache.directory.server.core.partition.DefaultPartitionNexus.hasEntry(DefaultPartitionNexus.java:988) >> >> >> at >> org.apache.directory.server.core.interceptor.InterceptorChain$1.hasEntry(InterceptorChain.java:147) >> >> >> at >> org.apache.directory.server.core.interceptor.InterceptorChain$Entry$1.hasEntry(InterceptorChain.java:1246) >> >> >> at >> org.apache.directory.server.core.interceptor.BaseInterceptor.hasEntry(BaseInterceptor.java:130) >> >> >> at >> org.apache.directory.server.core.interceptor.InterceptorChain$Entry$1.hasEntry(InterceptorChain.java:1246) >> >> >> at >> org.apache.directory.server.core.interceptor.BaseInterceptor.hasEntry(BaseInterceptor.java:130) >> >> >> ..... >> >> I'll check in the working DAS in a few days and in the package: >> >> package org.apache.tuscany.das.ldap.emf.test; >> >> There is a test called LdapDASHelperTest that can be run to see this. >> > >> > >
-- Regards, Cordialement, Emmanuel Lécharny www.iktek.com
