directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "lucas theisen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DIRAPI-168) Create an LdapConnectionFactory that is not pooled to create LdapConnection objects for an LdapConnectionConfig
Date Sat, 26 Apr 2014 23:00:19 GMT

    [ https://issues.apache.org/jira/browse/DIRAPI-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13982129#comment-13982129
] 

lucas theisen commented on DIRAPI-168:
--------------------------------------

Whoops, my bad.  Fixed in revision 1590323.

> Create an LdapConnectionFactory that is not pooled to create LdapConnection objects for
an LdapConnectionConfig
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: DIRAPI-168
>                 URL: https://issues.apache.org/jira/browse/DIRAPI-168
>             Project: Directory Client API
>          Issue Type: Improvement
>    Affects Versions: 1.0.0-M20
>            Reporter: lucas theisen
>            Priority: Minor
>             Fix For: 1.0.0-M23
>
>         Attachments: DefaultLdapConnectionFactory.java, LdapConnectionFactory.java, LdapConnections.java,
PoolableLdapConnectionFactoryWrapper.java
>
>
> If using the ldap server for authentication, you do not want a pooled connection because
you will be doing a bind operation.  However, the ldap connection you want will be otherwise
configured the same as your pool of connections.  It makes sense to have a factory that can
create unbound connections.
> Taking this one step further, the poolable connection factory could use such a connection
factory so that the implementation exists in only one place.
> I will attach code that implements this.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message