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 and Description |
|---|
ContextNotEmptyException()
Constructs a new instance of ContextNotEmptyException with all name resolution fields and explanation initialized to null.
|
ContextNotEmptyException(String
Constructs a new instance of ContextNotEmptyException using an explanation.
|
appendRemainingComponent, appendRemainingName, getCause, getExplanation, getRemainingName, getResolvedName, getResolvedObj, getRootCause, initCause, setRemainingName, setResolvedName, setResolvedObj, setRootCause, toString, toStringaddSuppressed, fillInStackTrace, getLocalizedMessage, getMessage, getStackTrace, getSuppressed, printStackTrace, printStackTrace, printStackTrace, setStackTracepublic ContextNotEmptyException(Stringexplanation)
explanation - Possibly null string containing additional detail about this exception.
Throwable.getMessage()
public ContextNotEmptyException()