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 explanation)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(String explanation)
explanation - Possibly null additional detail about this exception.Throwable.getMessage()public NamingSecurityException()
 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, 2014, Oracle and/or its affiliates.  All rights reserved.