javax.naming

Class NamingSecurityException

Contents
  • All Implemented Interfaces:
    Serializable
    Direct Known Subclasses:
    AuthenticationException, AuthenticationNotSupportedException, NoPermissionException

    public abstract class NamingSecurityException
extends NamingException
    This is the superclass of security-related exceptions thrown by operations in the Context and DirContext interfaces. The nature of the failure is described by the name of the subclass.

    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.

    Since:
    1.3
    See Also:
    Serialized Form

    • Constructor Detail

      • NamingSecurityException

        public NamingSecurityException(String explanation)
        Constructs a new instance of NamingSecurityException using the explanation supplied. All other fields default to null.
        Parameters:
        explanation - Possibly null additional detail about this exception.
        See Also:
        Throwable.getMessage()

      • NamingSecurityException

        public NamingSecurityException()
        Constructs a new instance of NamingSecurityException. All fields are initialized to null.

Document created the 11/06/2005, last modified the 04/03/2020
Source of the printed document:https://www.gaudry.be/en/java-api-rf-javax/naming/namingsecurityexception.html

The infobrol is a personal site whose content is my sole responsibility. The text is available under CreativeCommons license (BY-NC-SA). More info on the terms of use and the author.

References

  1. View the html document Language of the document:fr Manuel PHP : https://docs.oracle.com

These references and links indicate documents consulted during the writing of this page, or which may provide additional information, but the authors of these sources can not be held responsible for the content of this page.
The author This site is solely responsible for the way in which the various concepts, and the freedoms that are taken with the reference works, are presented here. Remember that you must cross multiple source information to reduce the risk of errors.

Contents Haut