javax.naming

Class ContextNotEmptyException

  • All Implemented Interfaces:
    Serializable

    public class ContextNotEmptyException
    extends NamingException
    This exception is thrown when attempting to destroy a context that is not empty.

    If the program wants to handle this exception in particular, it should catch ContextNotEmptyException explicitly before attempting to catch NamingException. For example, after catching ContextNotEmptyException, the program might try to remove the contents of the context before reattempting the destroy.

    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

      • ContextNotEmptyException

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

        public ContextNotEmptyException()
        Constructs a new instance of ContextNotEmptyException with all name resolution fields and explanation 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/contextnotemptyexception.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