Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Message-ID: <1488997419.1131054019225.JavaMail.jira@ajax.apache.org>
Date: Thu, 3 Nov 2005 22:40:19 +0100 (CET)
From: "Lyndon Washington (JIRA)" <directory-dev@incubator.apache.org>
To: dev@directory.apache.org
Subject: [jira] Created: (DIREVE-301) An Attempt to Use a New Type of
 Partition Configuration Fails
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

An Attempt to Use a New Type of Partition Configuration Fails
-------------------------------------------------------------

         Key: DIREVE-301
         URL: http://issues.apache.org/jira/browse/DIREVE-301
     Project: Directory Server
        Type: Bug
  Components: server main  
    Versions: 0.9.3    
 Environment: Linux, Eclipse 3.1.1, Java 1.5_05.
    Reporter: Lyndon Washington
 Assigned to: Alex Karasulu 


I have added my own CustomPartiton which extends AbstractContextPartition.  I have some configuration settings specific to my partition, so I have also created a new ContextPartitionConfiguration which extends MutableContextPartitionConfiguration.

Unfortunately, in my CustomPartition.doInit() method I attempt to test if the configuration that is returned from AbstractContextPartition.getConfiguration() is an instance of my new configuration, and discover that it is not. 

The implementation within DefaultContextPartitionNexus.addContextPartition() creates a new MutableContextPartitionConfiguration and copies the known values from the config that was passed into that method, thus by the time my code is called it is never an instance of my new configuration class.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira