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.
@author Rosanna Lee
@author Scott Seligman
@see Context#destroySubcontext
@since 1.3