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 2014/04/07 19:10:15 UTC
[jira] [Commented] (DIRAPI-168) Create an LdapConnectionFactory
that is not pooled to create LdapConnection objects for an
LdapConnectionConfig
[ https://issues.apache.org/jira/browse/DIRAPI-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13962023#comment-13962023 ]
Emmanuel Lecharny commented on DIRAPI-168:
------------------------------------------
There is such a pool of bound connection in a weird place : LdapApiIntegrationUtils.getPooledAdminConnection()
We should move this method into some more convenient place.
> 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
> 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)