javax.naming

Class NotContextException

Contents
  • All Implemented Interfaces:
    Serializable

    public class NotContextException
extends NamingException
    This exception is thrown when a naming operation proceeds to a point where a context is required to continue the operation, but the resolved object is not a context. For example, Context.destroy() requires that the named object be a context. If it is not, NotContextException is thrown. Another example is a non-context being encountered during the resolution phase of the Context methods.

    It is also thrown when a particular subtype of context is required, such as a DirContext, and the resolved object is a context but not of the required subtype.

    Synchronization and serialization issues that apply to NamingException apply directly here.

    Since:
    1.3
    See Also:
    Context.destroySubcontext(javax.naming.Name), Serialized Form

    • Constructor Detail

      • NotContextException

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

      • NotContextException

        public NotContextException()
        Constructs a new instance of NotContextException. All fields default 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/notcontextexception.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