[
https://issues.apache.org/jira/browse/DIRAPI-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lécharny resolved DIRAPI-359.
--------------------------------------
Resolution: Fixed
Fixed with commit 253211caad1c53e47687137fe36e009d61b1b623
> Propagate exceptions that are caught during the response handling
> -----------------------------------------------------------------
>
> Key: DIRAPI-359
> URL: https://issues.apache.org/jira/browse/DIRAPI-359
> Project: Directory Client API
> Issue Type: Improvement
> Affects Versions: 2.0.1
> Reporter: Emmanuel Lécharny
> Priority: Major
> Fix For: 2.0.2
>
>
> When we have a schema issue (like if we have enabled the {{NIS}} schema on
> the server, but haven't reloaded the {{SchemaManager}} on the client), we
> simply don't get any exception, as it's just swallowed, and the session is
> closed, leading to some painful debugging session.
> We need such exception to be available on teh connection.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
