You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2008/07/09 15:17:31 UTC

[jira] Updated: (DIRSERVER-577) Loosen LdapProtocolProvider-ServerLdapContext coupling.

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

Emmanuel Lecharny updated DIRSERVER-577:
----------------------------------------

    Fix Version/s: 1.5.3

Let's kill this issue. I'm not sure it's even a problem right now.

> 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
>            Priority: Minor
>             Fix For: 1.5.3
>
>
> 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.