public abstract class NamingSecurityException extends NamingException
If the program wants to handle this exception in particular, it should catch NamingSecurityException explicitly before attempting to catch NamingException. A program might want to do this, for example, if it wants to treat security-related exceptions specially from other sorts of naming exception.
Synchronization and serialization issues that apply to NamingException apply directly here.
remainingName, resolvedName, resolvedObj, rootException| Constructor and Description |
|---|
NamingSecurityException()
Constructs a new instance of NamingSecurityException.
|
NamingSecurityException(String
Constructs a new instance of NamingSecurityException using the explanation supplied.
|
appendRemainingComponent, appendRemainingName, getCause, getExplanation, getRemainingName, getResolvedName, getResolvedObj, getRootCause, initCause, setRemainingName, setResolvedName, setResolvedObj, setRootCause, toString, toStringaddSuppressed, fillInStackTrace, getLocalizedMessage, getMessage, getStackTrace, getSuppressed, printStackTrace, printStackTrace, printStackTrace, setStackTracepublic NamingSecurityException(Stringexplanation)
explanation - Possibly null additional detail about this exception.
Throwable.getMessage()
public NamingSecurityException()