--
--
cordialement, regards,
Emmanuel Lécharny
www.iktek.com
directory.apache.org
--- Begin Message ---
On Thu, May 29, 2008 at 4:54 PM, Emmanuel Lecharny <[EMAIL PROTECTED]>
wrote:
> Alex Karasulu wrote:
>
>> 1) The ExceptionInterceptor search method has this portion of code which
>>> is
>>> problematic :
>>>
>>> EntryFilteringCursor cursor = nextInterceptor.search( opContext
>>> );
>>> if ( ! cursor.next() )
>>>
>>> The next() call will run the filters, leading to a call to the
>>> CollectiveAttribute accept() method, which does a lookup. This lookup is
>>> obviously overkilling (see point 2), but the problem is that when the
>>> NamingEnumerationAdaptor is created in the ServerLdapContext, filters are
>>> run a second time.
>>>
>>>
>>>
>>
>> How is this code fragment above problematic in itself outside of the
>> lookup
>> due to the CollectiveAttributeInterceptor's filter?
>>
>>
> Just because filters are run twice, when they should only be invoked once.
So what should we change in ExceptionInterceptor?
Alex
--- End Message ---
