javax.naming
Class LinkLoopException
java.lang.Object
  
java.lang.Throwable
      
java.lang.Exception
          
javax.naming.NamingException
              
javax.naming.LinkException
                  
javax.naming.LinkLoopException
- All Implemented Interfaces: 
 - Serializable
 
public class LinkLoopException
- extends LinkException
 
This exception is thrown when
 a loop was detected will attempting to resolve a link, or an implementation
 specific limit on link counts has been reached.
 
 Synchronization and serialization issues that apply to LinkException
 apply directly here.
- Since:
 
  - 1.3
 
- See Also:
 LinkRef, 
Serialized Form
 
 
 
| 
Constructor Summary | 
LinkLoopException()
 
          Constructs a new instance of LinkLoopException. | 
LinkLoopException(String explanation)
 
          Constructs a new instance of LinkLoopException with an explanation
 All the other fields are initialized to null. | 
 
 
 
| Methods inherited from class javax.naming.NamingException | 
appendRemainingComponent, appendRemainingName, getCause, getExplanation, getRemainingName, getResolvedName, getResolvedObj, getRootCause, initCause, setRemainingName, setResolvedName, setResolvedObj, setRootCause | 
 
 
 
LinkLoopException
public LinkLoopException(String explanation)
- Constructs a new instance of LinkLoopException with an explanation
 All the other fields are initialized to null.
- Parameters:
 explanation - A possibly null string containing additional
                                detail about this exception.- See Also:
 Throwable.getMessage()
 
LinkLoopException
public LinkLoopException()
- Constructs a new instance of LinkLoopException.
 All the non-link-related and link-related fields are initialized to null.
 
 Submit a bug or feature
For further API reference and developer documentation, see Java SE Developer Documentation. That documentation contains more detailed, developer-targeted descriptions, with conceptual overviews, definitions of terms, workarounds, and working code examples. Copyright © 1993, 2010, Oracle and/or its affiliates.  All rights reserved.