Rational Developer for Power Systems Software
V7.6

com.ibm.etools.iseries.ui
Class DisplayContainerNotFoundException

java.lang.Object
  extended by java.lang.Throwable
      extended by java.lang.Exception
          extended by com.ibm.etools.iseries.ui.DisplayContainerNotFoundException
All Implemented Interfaces:
Serializable

public class DisplayContainerNotFoundException
extends Exception

This exception is to report that DisplayContainer is not defined for FormManager or ListManager.

See Also:
Serialized Form

Field Summary
static String Copyright
           
 
Constructor Summary
DisplayContainerNotFoundException()
          DisplayContainerNotFoundException constructor.
DisplayContainerNotFoundException(String s)
          DisplayContainerNotFoundException constructor.
 
Method Summary
static String Copyright()
          Copyright notice.
 
Methods inherited from class java.lang.Throwable
fillInStackTrace, getCause, getLocalizedMessage, getMessage, getStackTrace, initCause, printStackTrace, printStackTrace, printStackTrace, setStackTrace, toString
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait
 

Field Detail

Copyright

public static final String Copyright
See Also:
Constant Field Values
Constructor Detail

DisplayContainerNotFoundException

public DisplayContainerNotFoundException()
DisplayContainerNotFoundException constructor.


DisplayContainerNotFoundException

public DisplayContainerNotFoundException(String s)
DisplayContainerNotFoundException constructor.

Parameters:
s - java.lang.String
Method Detail

Copyright

public static String Copyright()
Copyright notice.

Returns:
java.lang.String

Rational Developer for Power Systems Software
V7.6

Copyright 2011 IBM Corp. All Rights Reserved.

Note: This documentation is for part of an interim API that is still under development and expected to change significantly before reaching stability. It is being made available at this early stage to solicit feedback from pioneering adopters on the understanding that any code that uses this API will almost certainly be broken (repeatedly) as the API evolves.