Hi,
it's about time to talk about exceptions, as many methods will throw an
exception, and it would be good to know what to throw !
We should first have a base exception, and I suggest using
LdapException. Evey other exception will inherit this one.
The second point is that the
Emmanuel Lecharny wrote:
> Hi,
>
> it's about time to talk about exceptions, as many methods will throw an
> exception, and it would be good to know what to throw !
>
> We should first have a base exception, and I suggest using
> LdapException. Evey other excep
All in all, JNDI's exception system is pretty decent, and I think we
should mimic it, but without implementing or extending the JNDI classes
(something ADS is doing, and it collides with the renaming of DN, as
it's not anymore a NAME extension).
thoughts ?
I agree that a exception hierarchy wi
On Sun, Mar 14, 2010 at 10:23 AM, Stefan Seelmann wrote:
> Emmanuel Lecharny wrote:
>> Hi,
>>
>> it's about time to talk about exceptions, as many methods will throw an
>> exception, and it would be good to know what to throw !
>>
>> We should firs
On 3/14/10 10:56 AM, Kiran Ayyagari wrote:
from the recent experience of migrating test cases to client-api
have observed that unlike jndi we return result codes and I liked this
(the jndi exceptions rather give me a feeling like 'use exceptions for
control flow', which is considered as a bad p
On 3/14/10 11:42 AM, Alex Karasulu wrote:
On Sun, Mar 14, 2010 at 10:23 AM, Stefan Seelmann wrote:
Emmanuel Lecharny wrote:
Hi,
it's about time to talk about exceptions, as many methods will throw an
exception, and it would be good to know what to throw !
We should first h
