This exception is thrown when attempting to destroy a context that is not empty.
If the program wants to handle this exception in particular, it should catch ContextNotEmptyException explicitly before attempting to catch NamingException. For example, after catching ContextNotEmptyException, the program might try to remove the contents of the context before reattempting the destroy.
Synchronization and serialization issues that apply to NamingException apply directly here.
This exception is thrown when attempting to destroy a context that is not empty. If the program wants to handle this exception in particular, it should catch ContextNotEmptyException explicitly before attempting to catch NamingException. For example, after catching ContextNotEmptyException, the program might try to remove the contents of the context before reattempting the destroy. Synchronization and serialization issues that apply to NamingException apply directly here.
(->context-not-empty-exception)(->context-not-empty-exception explanation)Constructor.
Constructs a new instance of ContextNotEmptyException using an explanation. All other fields default to null.
explanation - Possibly null string containing additional detail about this exception. - java.lang.String
Constructor. Constructs a new instance of ContextNotEmptyException using an explanation. All other fields default to null. explanation - Possibly null string containing additional detail about this exception. - `java.lang.String`
cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |