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 (athena.apache.org: domain of ickydude@gmail.com designates
 209.85.128.186 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:mime-version:content-type;
        b=VLfLKVXANZ9wHyjfyL1aLr7bW2P9gibt46Y+RBQbnKS+KlxXrR0Y+3ABGKr3hIfNM/wJvDQZp6cgdX/U8F84k504Hc3w72rEiM3emW1lnNMRtyOEvYXOG1o1xKGmrg40Y4bgAbE1sj/g+A+8Yw+MNIZx364KOm93DDiq4bjaVAw=
Message-ID: <478e164b0710031540j145d7f79k41ec9c2f0f38dc4@mail.gmail.com>
Date: Wed, 3 Oct 2007 16:40:57 -0600
From: "Matt Peterson" <ickydude@gmail.com>
To: dev@directory.apache.org
Subject: Relationship of Interceptors and Partitions
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_25056_19765023.1191451257732"

------=_Part_25056_19765023.1191451257732
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Greetings,

I'm trying to write a custom partition that will be used as context
partition, but I'd like to continue to use the Btree/Jdbm partition
implementation for the system configuration partition.

With a little trial and error (mostly errors), I've found out that several
methods in the JdbmPartition (used by the system configuration partition
partition) will not work unless preceeded by a corresponding "fix-ups"
provided by the interceptors.  For example, calls to to the methods in
org.apache.directory.server.core.normalization.NormalizationService must be
made, or BindDNs can not be resolved.  Unfortunately,  MyCustomPartition,
doesn't like the way that LdapDNs, attributes and filters are normalized by
org.apache.directory.server.core.normalization.NormalizationService.

 In other words, there appears to be more than at least one situation where
a correlation between interceptors and partitions is necessary, but what we
have (at least in Apache DS 1.0.x) is a design where all interceptors in the
chain are called regardles of the partition that will eventually be
invoked. To configure per-partition interception.

 Perhaps what I'm looking for is a way that I can insert my interceptor
first in the chain and then optionally skip other interceptors if I
encounter a DN or base that I know will invoke my partition?  According to
documentation for ApacheDS 1.0.x (
http://directory.apache.org/apacheds/1.0/interceptors.html) the Nexus is
called by a "special interceptor" at the end of the chain.  Therefore, it
seems very difficult to skip interceptors in the chain without also
elimintating the call to PartitionNexus ...

I suppose my real question is why ApacheDS wasn't designed so that
interceptors could (optionally) be configured for association only with a
certain suffix or partition.  This would allow the configuration flexibility
that I would need -- to use both the JdbmPartition and my own
customPartition without having to undo all of the normalization, schema,
referral (,etc) stuff in my own customPartition that I didn't want done in
the first place...

Does this make any sense?

--
Matt

------=_Part_25056_19765023.1191451257732
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div>Greetings,</div>
<div>&nbsp;</div>
<div>I&#39;m trying to write a custom partition that will be used as context partition, but I&#39;d like to continue to&nbsp;use the Btree/Jdbm partition implementation for the system configuration partition.</div>
<div>&nbsp;</div>
<div>With a little trial and error (mostly errors), I&#39;ve found out that several methods in the JdbmPartition (used by the system configuration partition partition) will not work unless preceeded by a corresponding &quot;fix-ups&quot; provided by the interceptors.&nbsp; For example, calls to to&nbsp;the methods in 
org.apache.directory.server.core.normalization.NormalizationService must be made, or BindDNs can not be resolved.&nbsp;&nbsp;Unfortunately,&nbsp; MyCustomPartition, doesn&#39;t like the way that LdapDNs, attributes and filters are normalized by 
org.apache.directory.server.core.normalization.NormalizationService.&nbsp;</div>
<div>&nbsp;</div>
<div>
<div>In other words, there appears to be more than at least one situation where a correlation between interceptors and partitions is necessary, but what we have (at least in Apache DS 1.0.x) is a design where all interceptors in the chain are called regardles of the partition that will eventually be invoked.&nbsp;To configure&nbsp;per-partition interception.
</div>
<div>&nbsp;</div></div>
<div>
<div>Perhaps what I&#39;m looking for is a way that I can insert my interceptor first in the chain and then optionally skip other interceptors if I encounter a DN or base that I know will invoke my partition?&nbsp; According to documentation for ApacheDS 
1.0.x (<a onclick="return top.js.OpenExtLink(window,event,this)" href="http://directory.apache.org/apacheds/1.0/interceptors.html" target="_blank">http://directory.apache.org/apacheds/1.0/interceptors.html</a>) the Nexus is called by a &quot;special interceptor&quot; at the end of the chain.&nbsp; Therefore, it seems very difficult to skip interceptors in the chain without also elimintating the call to PartitionNexus ...
</div>
<div>&nbsp;</div>
<div>I suppose my real question is why ApacheDS wasn&#39;t designed so that interceptors could&nbsp;(optionally) be configured&nbsp;for association only with a certain suffix or partition.&nbsp; This would allow the&nbsp;configuration flexibility that I would need -- to use both the JdbmPartition and my own customPartition without having to undo all of the normalization, schema, referral (,etc) stuff in my own customPartition that I didn&#39;t want done in the first place...
</div>
<div>&nbsp;</div>
<div>Does this make any sense?</div>
<div>&nbsp;</div>
<div>--</div>
<div>Matt</div></div>
<div>&nbsp;</div>
<div>&nbsp;</div>
<div>&nbsp;</div>

------=_Part_25056_19765023.1191451257732--