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: <7727004.58341276792163604.JavaMail.jira@thor>
Date: Thu, 17 Jun 2010 12:29:23 -0400 (EDT)
From: "Emmanuel Lecharny (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Subject: [jira] Closed: (DIRSERVER-1059) Interceptor bypass logic is flawed
In-Reply-To: <26568983.1189477169626.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Emmanuel Lecharny closed DIRSERVER-1059.
----------------------------------------


> Interceptor bypass logic is flawed
> ----------------------------------
>
>                 Key: DIRSERVER-1059
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1059
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: 1.5.1
>            Reporter: Emmanuel Lecharny
>             Fix For: 2.0.0-RC1
>
>
> We currently have many places in the code where we are hard-coding the bypassed interceptor (ie, the interceptors which won't be called).
> I think this logic is flawed : as we can add new interceptors, those newly interceptors will be called, or the code where those bypasses are declared should be modified.
> Reverting the logic won't help : if we create a list of called interceptors instead of a list of bypassed interceptors, then we will still have to modify the code to add those new interceptors in the chain.
> Some other way to handle interceptors should be find to allow users to add new interceptors without any problem.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.