You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@directory.apache.org by "Trustin Lee (JIRA)" <di...@incubator.apache.org> on 2005/06/13 09:12:48 UTC

[jira] Resolved: (DIREVE-112) Extract out JNDI configuration setting management code into JNDI Utils

     [ http://issues.apache.org/jira/browse/DIREVE-112?page=all ]
     
Trustin Lee resolved DIREVE-112:
--------------------------------

    Fix Version: 0.9.1
     Resolution: Fixed

This issue has been resolved.  Please check the branch 'direve-158'.

> Extract out JNDI configuration setting management code into JNDI Utils
> ----------------------------------------------------------------------
>
>          Key: DIREVE-112
>          URL: http://issues.apache.org/jira/browse/DIREVE-112
>      Project: Directory Server
>         Type: Sub-task
>   Components: jndi-provider
>     Reporter: Alex Karasulu
>     Assignee: Trustin Lee
>      Fix For: 0.9.1

>
> The property handling logic in the JNDI code can get out of control very rapidly.  Some of the logic is a direct reflection of JNDI LDAP provider guidelines and can be reused.  However more importantly we need to get this stuff out of the way so it does not clutter things up.  So we need some JNDI LDAP provider utilities for centralizing code dealing with environment settings.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira