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: <27499427.70831275212137810.JavaMail.jira@thor>
Date: Sun, 30 May 2010 05:35:37 -0400 (EDT)
From: "Emmanuel Lecharny (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Subject: [jira] Resolved: (DIRSERVER-683) Entry lookup are done more than
 once in modify operation
In-Reply-To: <4257735.1154250253937.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-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Lecharny resolved DIRSERVER-683.
-----------------------------------------

    Resolution: Fixed

Removed the useless lookups with http://svn.apache.org/viewvc?rev=949402&view=rev


> Entry lookup are done more than once in modify operation
> --------------------------------------------------------
>
>                 Key: DIRSERVER-683
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-683
>             Project: Directory ApacheDS
>          Issue Type: Improvement
>            Reporter: Emmanuel Lecharny
>            Priority: Minor
>             Fix For: 2.0.0-RC1
>
>
> If we send a modify request, the entry lookup is done in many different interceptors. This operation should be done only once, and the result should be stored soemwhere to be available to other interceptors.
> This means we should create a kind of container that will be pass through all interceptors (may be a kind of requestContext like in servlets). A HashMap could contain these sharable pieces of information.
> For ApacheDS 1.1 or 2.0 ?

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