You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2007/04/21 13:20:16 UTC

[jira] Closed: (DIRSERVER-250) An Attempt to Use a New Type of Partition Configuration Fails

     [ https://issues.apache.org/jira/browse/DIRSERVER-250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Lecharny closed DIRSERVER-250.
---------------------------------------


Closing all issues created in 2005 and before which are marked resolved

> An Attempt to Use a New Type of Partition Configuration Fails
> -------------------------------------------------------------
>
>                 Key: DIRSERVER-250
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-250
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: pre-1.0
>         Environment: Linux, Eclipse 3.1.1, Java 1.5_05.
>            Reporter: Lyndon Washington
>         Assigned To: Trustin Lee
>             Fix For: 1.0-RC1
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.