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.
| Modifier and Type | Field and Description |
|---|---|
| private static final long | serialVersionUID
Use serialVersionUID from JNDI 1.1.1 for interoperability
|
| Access | Constructor and Description |
|---|---|
| public | NamingSecurityException(String
Possibly null additional detail about this exception. explanation)Constructs a new instance of NamingSecurityException using the explanation supplied. |
| public |
| serialVersionUID | back to summary |
|---|---|
| private static final long serialVersionUID Hides javax. Use serialVersionUID from JNDI 1.1.1 for interoperability | |
| NamingSecurityException | back to summary |
|---|---|
| public NamingSecurityException(String explanation) Constructs a new instance of NamingSecurityException using the explanation supplied. All other fields default to null.
| |
| NamingSecurityException | back to summary |
|---|---|
| public NamingSecurityException() Constructs a new instance of NamingSecurityException. All fields are initialized to null. | |
