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] Closed: (DIRSERVER-577) Loosen LdapProtocolProvider-ServerLdapContext coupling.
Date Wed, 27 Aug 2008 19:57:44 GMT

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

Alex Karasulu closed DIRSERVER-577.
-----------------------------------

    Resolution: Fixed

The protocol provider no longer uses JNDI - we use the DirectoryService in core directly and
the rewrite removes this problem.

> Loosen LdapProtocolProvider-ServerLdapContext coupling.
> -------------------------------------------------------
>
>                 Key: DIRSERVER-577
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-577
>             Project: Directory ApacheDS
>          Issue Type: Improvement
>          Components: ldap
>    Affects Versions: 1.0-RC1
>            Reporter: Marc DeXeT
>            Assignee: Alex Karasulu
>            Priority: Minor
>             Fix For: 1.5.4
>
>
> LdapProtocoleProvider is heavely coupled to ServerLdapContext, even the package name
has changed to 'server'.
> To allow more custom override, I suggest to do 'instanceof' test at least on LdapContext.lookup("")
result.
> You can see such direct casting into SessionRegistry
> /.../
> else if ( ctx != null && allowAnonymous )
>         {
>             ServerLdapContext slc = null;
>             if ( ! ( ctx instanceof ServerLdapContext ) )
>             {
>                 slc = ( ServerLdapContext ) ctx.lookup( "" );
>             }
>             else
>             {
>                 slc = ( ServerLdapContext ) ctx;
>             }
> /.../

-- 
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