Remote Systems
v6.4.1

com.ibm.etools.systems.model.impl
Class SystemRemoteChangeEventManager

java.lang.Object
  extended bycom.ibm.etools.systems.model.impl.SystemRemoteChangeEventManager

public class SystemRemoteChangeEventManager
extends Object

Manages the list of registered remote resource change listeners.


Field Summary
static String copyright
           
 
Constructor Summary
SystemRemoteChangeEventManager()
          Constructor
 
Method Summary
 void addSystemRemoteChangeListener(ISystemRemoteChangeListener l)
          Add a listener to list of listeners.
 void notify(ISystemRemoteChangeEvent event)
          Notify all registered listeners of the given event
 void removeSystemRemoteChangeListener(ISystemRemoteChangeListener l)
          Remove a listener to list of listeners.
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Field Detail

copyright

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

SystemRemoteChangeEventManager

public SystemRemoteChangeEventManager()
Constructor

Method Detail

addSystemRemoteChangeListener

public void addSystemRemoteChangeListener(ISystemRemoteChangeListener l)
Add a listener to list of listeners. If this object is already in the list, this does nothing.


removeSystemRemoteChangeListener

public void removeSystemRemoteChangeListener(ISystemRemoteChangeListener l)
Remove a listener to list of listeners. If this object is not in the list, this does nothing.


notify

public void notify(ISystemRemoteChangeEvent event)
Notify all registered listeners of the given event


Remote Systems
v6.4.1

Copyright © 2005 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.