directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DIRSERVER-1212) Size time limits on SearchControls broken in core-jndi
Date Sun, 24 Aug 2008 17:03:45 GMT

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

Alex Karasulu updated DIRSERVER-1212:
-------------------------------------

    Priority: Minor  (was: Blocker)

This issue was critical because the ldap frontend (protocol-ldap module) used to depend on
the core JNDI LDAP provider and this is not the case any longer.  When it did depend on this
it lacked support for search time and size limits.  With the revamped frontend using the new
DirectoryService API instead of JNDI now we've added the code to handle these size and time
limits.

The core-jndi module is not so much that critical since it is specifically used in embedded
mode and in this mode size and time constraints are less of an issue.  These parameters are
much more critical for the frontend.  

I will be closing this issue or marking it to be fixed later when and if users request it
specifically.  I have the hunch that the core JNDI module will be used less frequently than
the over the wire SUN JNDI LDAP provider for testers interested in an embeddable server. 

> Size time limits on SearchControls broken in core-jndi
> ------------------------------------------------------
>
>                 Key: DIRSERVER-1212
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1212
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: core
>            Reporter: Alex Karasulu
>            Assignee: Alex Karasulu
>            Priority: Minor
>
> I commented out some tests in SearchIT.java in core-integ that rely on the correct operation
of search size and time limits through paramters in a SearchControls object.  This is not
working any longer.  Fix it and remove @Ignore tags.

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


Mime
View raw message