You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "lucas theisen (JIRA)" <ji...@apache.org> on 2014/04/26 23:11:14 UTC

[jira] [Resolved] (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:all-tabpanel ]

lucas theisen resolved DIRAPI-168.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.0.0-M23

New interface and class were added for connection factory, pooled connection factory was modified in a backwards compatible way to use connection factory instead of config, and connection pool was modified to add a method for getting an unbound connection.  The only functional change to previous code was in the implementation of the pooled connection factory in which I modified the passivate (called when a connection is returned) to ensure that it gets re-initialized (in case the borrower bound the connection to a different account, changed the timeout, or the binary attribute detector was changed).

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