Remote Systems
v6.4.1

com.ibm.etools.systems.core.resources
Interface ISystemRemoteEditResourceManager

All Superinterfaces:
ISystemRemoteManager

public interface ISystemRemoteEditResourceManager
extends ISystemRemoteManager

This manager class manages remote resources.


Field Summary
static String Copyright
           
 
Method Summary
 Object getEditObject(ISystemRemotePath key)
          Get a remote edit object given the remote path as a key.
 Object putEditObject(ISystemRemotePath key, Object editObj)
          Store a remote edit object with the given remote path as the key.
 void restore()
          Restore the edit object information from disk.
 void save()
          Save the edit object information to disk.
 
Methods inherited from interface com.ibm.etools.systems.core.resources.ISystemRemoteManager
shutdown, startup
 

Field Detail

Copyright

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

putEditObject

public Object putEditObject(ISystemRemotePath key,
                            Object editObj)
Store a remote edit object with the given remote path as the key. The idea is that each unique remote object can have an associated edit object associated with it, and this object will take care of remote editing of that object. Using the remote path as a key ensures that a resource with a unique path will have a unique remote object.

Returns:
the previously stored edit object, or null if none

getEditObject

public Object getEditObject(ISystemRemotePath key)
Get a remote edit object given the remote path as a key.

Returns:
the stored edit object

save

public void save()
Save the edit object information to disk. Clients must not call this method.


restore

public void restore()
Restore the edit object information from disk. Clients must not call this method.


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.