Remote Systems
v6.4.1

Deprecated API

Deprecated Classes
com.ibm.etools.systems.files.ui.actions.SystemCreateEditActions
          - use SystemRemoteFileOpenWithMenu now 
com.ibm.etools.systems.files.ui.actions.SystemCreateEditLineActions
          - use SystemRemoteFileLineOpenWithMenu now 
com.ibm.etools.systems.core.ui.messages.SystemDialogPageMessageLine
          

DO NOT USE THIS CLASS!

This class attempts to wrap the message constructs of eclipse provided property and wizard pages with an ISystemMessageLine interface. It fails to do this properly and is extremely fragile since it depends on knowledge of the internal structure of eclipse provided windows.

Use SystemMessageLine instead. 

com.ibm.etools.systems.files.ui.actions.SystemSearchCreateEditLineActions
          - use SystemRemoteSearchOpenWithMenu now 
com.ibm.etools.systems.core.ui.view.team.SystemTeamViewActiveProfileAction
          TODO: delete this action after next MRI rev, as it will be replaced by SystemTeamViewActiveProfileAction and SystemTeamViewMakeInActiveProfileAction. 
 

Deprecated Fields
com.ibm.etools.systems.model.ISystemResourceChangeEvents.EVENT_COMMAND_FINISHED
          use EVENT_COMMAND_SHELL_FINISHED 
 

Deprecated Methods
com.ibm.etools.systems.core.ui.view.ISystemDragDropAdapter.doDrop(Object, Object, boolean, boolean, IProgressMonitor)
          use doDrop(Object from, Object to, boolean sameSystemType, boolean sameSystem, int srcType, IProgressMonitor monitor) instead 
com.ibm.etools.systems.core.ui.view.AbstractSystemViewAdapter.doDrop(Object, Object, boolean, boolean, IProgressMonitor)
          use doDrop(Object from, Object to, boolean sameSystemType, boolean sameSystem, int srcType, IProgressMonitor monitor) instead 
com.ibm.etools.systems.files.importexport.jar.RemoteJarFileExportOperation.filesOnClasspath(IFile, IPath, IJavaProject, IProgressMonitor)
          As of 2.1 use the method with additional IPackageFragmentRoot paramter 
com.ibm.etools.systems.dstore.core.model.DataStore.getByteStreamHandler()
            
com.ibm.etools.systems.universal.UniversalSystem.getDaemonLaunchEnabled(SubSystemImpl)
          Use instead AbstractSystem.isEnabledServerLaunchType(SubSystem, ServerLaunchType) or SubSystemFactoryImpl.supportsServerLaunchType(ServerLaunchType) 
com.ibm.etools.systems.dstore.core.miners.miner.Miner.getLocalizedString(String)
          use DataStoreResources. instead. This will be removed next major release 
com.ibm.etools.systems.dstore.core.model.DataStore.getLocalizedString(String)
            
com.ibm.etools.systems.universal.UniversalSystem.getNoLaunchEnabled(SubSystemImpl)
          Use instead AbstractSystem.isEnabledServerLaunchType(SubSystem, ServerLaunchType) or SubSystemFactoryImpl.supportsServerLaunchType(ServerLaunchType) 
com.ibm.etools.systems.universal.UniversalSystem.getRexecLaunchEnabled(SubSystemImpl)
          Use instead AbstractSystem.isEnabledServerLaunchType(SubSystem, ServerLaunchType) or SubSystemFactoryImpl.supportsServerLaunchType(ServerLaunchType) 
com.ibm.etools.systems.core.ui.validators.ValidatorUniqueString.isValid(String)
          You should be using ValidatorUniqueString.validate(String) and SystemMessage objects 
com.ibm.etools.systems.files.importexport.jar.RemoteJarExportData.logErrors()
          will be removed in final 2.0 
com.ibm.etools.systems.filters.impl.SystemFilterPoolManagerImpl.logMessage(String)
          Use either logInfo, logWarning, logError, or logDebugMessage. This method now calls logInfo. 
com.ibm.etools.systems.files.importexport.jar.RemoteJarExportData.logWarnings()
          will be removed in final 2.0 
com.ibm.etools.systems.core.ui.dialogs.SystemPromptDialog.pack()
            
com.ibm.etools.systems.dstore.core.model.DataStore.setByteStreamHandler()
            
com.ibm.etools.systems.dstore.core.model.DataStore.setByteStreamHandler(IByteStreamHandler)
            
com.ibm.etools.systems.universal.UniversalSystem.setDaemonLaunchEnabled(SubSystemImpl, boolean)
          use AbstractSystem.enableServerLaunchType(SubSystem, ServerLaunchType, boolean) or your subsystem factory should override SubSystemFactoryImpl.supportsServerLaunchType(ServerLaunchType) 
com.ibm.etools.systems.core.ui.SystemWidgetHelpers.setHelp(Control, IViewPart, Object)
            
com.ibm.etools.systems.files.importexport.jar.RemoteJarExportData.setLogErrors(boolean)
          will be removed in final 2.0 
com.ibm.etools.systems.files.importexport.jar.RemoteJarExportData.setLogWarnings(boolean)
          will be removed in final 2.0 
com.ibm.etools.systems.universal.UniversalSystem.setNoLaunchEnabled(SubSystemImpl, boolean)
          use AbstractSystem.enableServerLaunchType(SubSystem, ServerLaunchType, boolean) or your subsystem factory should override SubSystemFactoryImpl.supportsServerLaunchType(ServerLaunchType) 
com.ibm.etools.systems.subsystems.IBMServerLauncher.setPort(Integer)
          call IBMServerLauncher.setRexecPort(Integer) or IBMServerLauncher.setDaemonPort(Integer) instead.  
com.ibm.etools.systems.subsystems.impl.IBMServerLauncherImpl.setPort(Integer)
          call IBMServerLauncherImpl.setRexecPort(Integer) or IBMServerLauncherImpl.setDaemonPort(Integer) instead. 
com.ibm.etools.systems.universal.UniversalSystem.setRexecLaunchEnabled(SubSystemImpl, boolean)
          use AbstractSystem.enableServerLaunchType(SubSystem, ServerLaunchType, boolean) or your subsystem factory should override SubSystemFactoryImpl.supportsServerLaunchType(ServerLaunchType) 
com.ibm.etools.systems.dstore.core.client.ClientConnection.setUsingSSL(boolean)
            
 

Deprecated Constructors
com.ibm.etools.systems.core.ui.SystemBaseForm(ISystemMessageLine)
          You should now use the constructor that takes a shell. 
 


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.