directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aman Nanner (JIRA)" <j...@apache.org>
Subject [jira] Created: (DIRSERVER-747) Creating new custom Authenticator requires it being in the same package as LdapPrincipal
Date Thu, 21 Sep 2006 16:58:22 GMT
Creating new custom Authenticator requires it being in the same package as LdapPrincipal
----------------------------------------------------------------------------------------

                 Key: DIRSERVER-747
                 URL: http://issues.apache.org/jira/browse/DIRSERVER-747
             Project: Directory ApacheDS
          Issue Type: Improvement
          Components: core
    Affects Versions: 1.0-RC4
            Reporter: Aman Nanner
            Priority: Minor


I have created a new custom authenticator that subclasses AbstractAuthenticator, but I have
discovered that it must belong in the same package as org.apache.directory.server.core.authn.LdapPrincipal,
because it creates a new instance of LdapPrincipal, but the constructor of LdapPrincipal only
has package-level access.  This itself isn't a huge deal, but the custom authenticator must
also be loaded by the same class loader that loads LdapPrincipal, or else it is not considered
to belong to the same package (even though it shares the package name).  This causes some
deployment issues on our J2EE server.  This can also be worked around, but it's kind of a
pain.  If one of the features of ApacheDS is custom authenticators, then I think this issue
should be resolved in some fashion such that custom authenticators can reside in a different
package.

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

        

Mime
View raw message