Dmitri Cherkas wrote:what advantages can be of using own suncertify.db.SecurityException instead of standard java.lang.SecurityException ?
No real advantages. But the exception from java.lang has (according to its documentation) nothing to do with the exception in the given interface and therefore I would suggest creating your own exception.
"I implement my own suncertify.db.SecurityException because following to my assignment instructions : I "must not require the installation of a security manager." and from API of java.lang.SecurityException : "Thrown by the security manager to indicate a security violation." therefore it seems that java.lang.SecurityException is bind to using of security manager."
Does seem it logic ?
I think to do my suncertify.db.SecurityException as unchecked exception, is it a good choice ?