public class NoInitialContextException extends NamingException
This exception can be thrown during any interaction with the InitialContext, not only when the InitialContext is constructed. For example, the implementation of the initial context might lazily retrieve the context only when actual methods are invoked on it. The application should not have any dependency on when the existence of an initial context is determined.
Synchronization and serialization issues that apply to NamingException apply directly here.
remainingName, resolvedName, resolvedObj, rootException | Constructor | Description |
|---|---|
NoInitialContextException () |
Constructs an instance of NoInitialContextException.
|
NoInitialContextException (String explanation) |
Constructs an instance of NoInitialContextException with an
explanation.
|
appendRemainingComponent, appendRemainingName, getCause, getExplanation, getRemainingName, getResolvedName, getResolvedObj, getRootCause, initCause, setRemainingName, setResolvedName, setResolvedObj, setRootCause, toString, toString addSuppressed, fillInStackTrace, getLocalizedMessage, getMessage, getStackTrace, getSuppressed, printStackTrace, printStackTrace, printStackTrace, setStackTrace public NoInitialContextException()
public NoInitialContextException(String explanation)
explanation - Possibly null additional detail about this exception.Throwable.getMessage() 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, 2025, Oracle and/or its affiliates. All rights reserved. Use is subject to license terms. Also see the documentation redistribution policy.
Scripting on this page tracks web page traffic, but does not change the content in any way.