Emmanuel Lécharny created DIRAPI-495:
----------------------------------------
Summary: Ldap connection stored in the pool are now encapsukated
into MonitoringLdapConnection
Key: DIRAPI-495
URL: https://issues.apache.org/jira/browse/DIRAPI-495
Project: Directory Client API
Issue Type: Improvement
Affects Versions: 2.1.9
Reporter: Emmanuel Lécharny
Fix For: 2.1.10
When we borrow a _LdapConnection_ instance from a LDAP pool, we now get back a
_LdapConnection_ instance of a _MonitoringLdapConnection_ that contains the
real connection.
This is annoying because the _MonitoringLdapConnection_ class exposes the
_LdapConnection_ interface, which forbid teh user to call methods like
_searchAsync_ which belongs to the _LdapAsyncConnection_ interface.
That forces the user to write code like:
{code:java}
SearchFuture searchFuture = ( ( LdapNetworkConnection ) ( (
MonitoringLdapConnection ) connection.wrapped() ).wrapped() ).searchAsync( sr );
{code}
which is extremely heavy...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
