Issue #231 has been updated by Jonathan Clarke.
Absolutely! In fact, I think we should rework exceptions all round. We use a lot of RuntimeExceptions (which is bad practice) that could be replaced with LSC-specific exceptions. I suggest we build a tree of Exception objects, something like: * LscException ** LscServiceException *** LscServiceCommunicationException *** LscServiceInitializationException *** LscServiceConfigurationException ** LscConfigurationException *** etc **etc Comments? ---------------------------------------- Feature #231: Replace NamingException by a LscServiceException in IService and subsidiaries http://tools.lsc-project.org/issues/231 Author: Sébastien Bahloul Status: New Priority: Normal Assigned to: Category: Core Target version: Because services are now handling different data sources and not only directories, I suggest to change the exception handled by most methods to a new LscServiceException which could include some more information like a "fatal" item to avoid using javax.naming.CommunicationException. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://tools.lsc-project.org/my/account
_______________________________________________________________ Ldap Synchronization Connector (LSC) - http://lsc-project.org lsc-dev mailing list [email protected] http://lists.lsc-project.org/listinfo/lsc-dev
