当前页面: 
在线文档首页 > 
JDK 5 Documentation v6.0, Java 2 SDK 英文文档
CommunicationException (Java Platform SE 6) - JDK 5 Documentation v6.0, Java 2 SDK 英文文档
javax.naming
Class CommunicationException
java.lang.Object
  
java.lang.Throwable
      
java.lang.Exception
          
javax.naming.NamingException
              
javax.naming.CommunicationException
- All Implemented Interfaces: 
 - Serializable
 
public class CommunicationException
- extends NamingException
 
This exception is thrown when the client is 
 unable to communicate with the directory or naming service.
 The inability to communicate with the service might be a result
 of many factors, such as network partitioning, hardware or interface problems,
 failures on either the client or server side.
 This exception is meant to be used to capture such communication problems.
 
 Synchronization and serialization issues that apply to NamingException
 apply directly here.
- Since:
 
  - 1.3
 
- See Also:
 - Serialized Form
 
 
 
 
 
| Methods inherited from class javax.naming.NamingException | 
appendRemainingComponent, appendRemainingName, getCause, getExplanation, getRemainingName, getResolvedName, getResolvedObj, getRootCause, initCause, setRemainingName, setResolvedName, setResolvedObj, setRootCause, toString, toString | 
 
 
 
CommunicationException
public CommunicationException(String explanation)
- Constructs a new instance of CommunicationException using the
 arguments supplied.
- Parameters:
 explanation - Additional detail about this exception.- See Also:
 Throwable.getMessage()
 
CommunicationException
public CommunicationException()
- Constructs a new instance of CommunicationException.
 
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 2006 Sun Microsystems, Inc. All rights reserved. Use is subject to license terms. Also see the documentation redistribution policy.