public class ContextNotEmptyException extends NamingException
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.destroySubcontext(javax.naming.Name),
Serialized Form remainingName, resolvedName, resolvedObj, rootException | Constructor | Description |
|---|---|
ContextNotEmptyException () |
Constructs a new instance of ContextNotEmptyException with
all name resolution fields and explanation initialized to null.
|
ContextNotEmptyException (String explanation) |
Constructs a new instance of ContextNotEmptyException using an
explanation.
|
appendRemainingComponent, appendRemainingName, getCause, getExplanation, getRemainingName, getResolvedName, getResolvedObj, getRootCause, initCause, setRemainingName, setResolvedName, setResolvedObj, setRootCause, toString, toString addSuppressed, fillInStackTrace, getLocalizedMessage, getMessage, getStackTrace, getSuppressed, printStackTrace, printStackTrace, printStackTrace, setStackTrace public ContextNotEmptyException(String explanation)
explanation - Possibly null string containing
additional detail about this exception.Throwable.getMessage() public ContextNotEmptyException()
Submit a bug or feature
For further API reference and developer documentation, see Java SE Documentation. That documentation contains more detailed, developer-targeted descriptions, with conceptual overviews, definitions of terms, workarounds, and working code examples.
Copyright © 1993, 2025, Oracle and/or its affiliates. All rights reserved. Use is subject to license terms. Also see the documentation redistribution policy.
Scripting on this page tracks web page traffic, but does not change the content in any way.