|
Deprecated Methods |
org.eclipse.rse.ui.RSESystemTypeAdapter.acceptContextMenuActionContribution(IHost, Class)
Override SystemViewConnectionAdapter.addActions(SystemMenuManager, org.eclipse.jface.viewers.IStructuredSelection, org.eclipse.swt.widgets.Shell, String) instead.
In order to do so, AbstractRSESystemType.createNewHostInstance(org.eclipse.rse.core.model.ISystemProfile) needs to return
a subclass of Host where the IAdaptable.getAdapter(Class) method is overriden to return a extended
SystemViewConnectionAdapter subclass. |
org.eclipse.rse.subsystems.files.core.subsystems.RemoteFileSubSystem.cancelSearch(IHostSearchResultConfiguration)
|
org.eclipse.rse.ui.view.AbstractSystemViewAdapter.checkForNull(Object[], boolean)
Use AbstractSystemViewAdapter.checkForEmptyList(Object[], Object, boolean) instead. |
org.eclipse.rse.core.subsystems.SubSystem.connect()
|
org.eclipse.rse.core.subsystems.ISubSystem.connect()
use ISubSystem.connect(IProgressMonitor, boolean) from background
thread, or {@link #connect(boolean, IRSECallback) from UI thread. |
org.eclipse.rse.ui.SystemWidgetHelpers.createBrowseButton(Composite, Listener, String)
|
org.eclipse.rse.ui.view.AbstractSystemViewAdapter.doDrop(Object, Object, boolean, boolean, IProgressMonitor)
use doDrop(Object from, Object to, boolean sameSystemType, boolean sameSystem, int srcType, IProgressMonitor monitor) instead |
org.eclipse.rse.core.subsystems.IRemoteSystemEnvVar.getAdditionalAttributes()
|
org.eclipse.rse.ui.view.AbstractSystemViewAdapter.getEmptyMessageObject()
Use AbstractSystemViewAdapter.checkForEmptyList(Object[], Object, boolean) instead. |
org.eclipse.rse.core.IRSESystemType.getName()
Use IRSESystemType.getId() for accessing the unique id or IRSESystemType.getLabel() for the UI label. |
org.eclipse.rse.connectorservice.dstore.DStoreConnectorService.getNoLaunchEnabled(SubSystem)
Use instead AbstractConnectorService.isServerLaunchTypeEnabled(ISubSystem, ServerLaunchType)
or SubSystemConfiguration.supportsServerLaunchType(ServerLaunchType) |
org.eclipse.rse.subsystems.files.core.servicesubsystem.AbstractRemoteFile.getParentNoRoot()
- shouldn't need apis like this |
org.eclipse.rse.core.subsystems.SubSystem.getProperties(Object, String[])
this shouldn't be used |
org.eclipse.rse.core.subsystems.ISubSystem.getProperties(Object, String[])
this shouldn't be used |
org.eclipse.rse.core.subsystems.SubSystem.getProperty(Object, String)
this shouldn't be used |
org.eclipse.rse.core.subsystems.ISubSystem.getProperty(Object, String)
this shouldn't be used |
org.eclipse.rse.ui.view.AbstractSystemViewAdapter.getRemoteAdapter(Object)
use SystemAdapterHelpers.getRemoteAdapter(o, getViewer()) instead |
org.eclipse.rse.core.subsystems.SubSystem.getRemoteAttribute(String)
|
org.eclipse.rse.connectorservice.dstore.DStoreConnectorService.getRexecLaunchEnabled(SubSystem)
Use instead AbstractConnectorService.isServerLaunchTypeEnabled(ISubSystem, ServerLaunchType)
or SubSystemConfiguration.supportsServerLaunchType(ServerLaunchType) |
org.eclipse.rse.subsystems.files.core.servicesubsystem.AbstractRemoteFile.getRoot()
- shouldn't need apis like this |
org.eclipse.rse.core.subsystems.SubSystem.getRunnableContext()
this is scheduled to be removed since we want to
avoid UI components in SubSystem. |
org.eclipse.rse.core.model.ISystemViewInputProvider.getShell()
use other methods for getting the active workbench shell,
e.g. SystemBasePlugin.getActiveWorkbenchShell() |
org.eclipse.rse.ui.RSEUIPlugin.getShowPreferencePageActions()
will be moved to using command/hander extension point |
org.eclipse.rse.core.model.ISystemRegistry.getSubSystemConfigurations()
use ISystemRegistry.getSubSystemConfigurationProxies() and filter the
list of needed subsystem configurations in order to activate only those
that are really needed. |
org.eclipse.rse.ui.view.SubSystemConfigurationAdapter.getSubSystemPropertyPages(ISubSystemConfiguration)
this method will likely be removed in the future, because the
underlying mechanism of finding the registered property pages for a
SubSystemConfiguration does not scale since it activates unrelated
plug-ins. Existing Platform functionality for getting the list of
property pages registered against a SubSystem should be used, once
the SubSystem class is loaded -- but not by referencing the
SubSystemConfiguration. See also Eclipse Bugzilla bug 197129. |
org.eclipse.rse.core.model.ISystemRegistry.getSubSystemsBySubSystemConfigurationCategory(String, IHost)
use ISystemRegistry.getSubSystemConfigurationProxiesByCategory(String)
and instantiate only those subsystem configurations from the proxy
that are really needed. Then, use ISubSystemConfiguration.getSubSystems(boolean)
with a parameter true. |
org.eclipse.rse.core.IRSECoreRegistry.getSystemType(String)
Use IRSECoreRegistry.getSystemTypeById(String). |
org.eclipse.rse.ui.view.AbstractSystemViewAdapter.getSystemViewElementAdapter(Object)
use SystemAdapterHelpers.getViewAdapter(o, getViewer()) instead |
org.eclipse.rse.core.subsystems.SubSystem.getVendorAttribute(String, String)
use property sets directly now |
org.eclipse.rse.core.subsystems.ISubSystem.getVendorAttribute(String, String)
Subsystems can now take named property sets. These should be used instead.
See IPropertySet |
org.eclipse.rse.core.model.ISystemViewInputProvider.getViewer()
use other methods for getting the active viewer. |
org.eclipse.rse.ui.validators.ValidatorUniqueString.isValid(String)
You should be using ValidatorUniqueString.validate(String) and SystemMessage objects |
org.eclipse.rse.services.clientserver.PathUtility.normalizeUnix(String)
this should not be used since \ is a valid part of
UNIX file names. Also, a better normalizer would also consider
swquences like a/../b and a/./b -- Try to work without this
method. |
org.eclipse.rse.ui.dialogs.SystemPromptDialog.pack()
|
org.eclipse.rse.subsystems.shells.core.subsystems.RemoteCmdSubSystem.runCommand(String, Object)
|
org.eclipse.rse.subsystems.shells.core.subsystems.RemoteCmdSubSystem.runCommand(String, Object, boolean)
|
org.eclipse.rse.subsystems.shells.core.subsystems.RemoteCmdSubSystem.runShell(Object)
|
org.eclipse.rse.subsystems.shells.core.subsystems.RemoteCmdSubSystem.sendCommandToShell(String, Object)
use RemoteCmdSubSystem.sendCommandToShell(String, Object, IProgressMonitor) |
org.eclipse.rse.subsystems.shells.core.subsystems.IRemoteCmdSubSystem.sendCommandToShell(String, Object)
use sendCommandToShell(IProgressMonitor, String input, Object commmandObject) |
org.eclipse.rse.core.subsystems.IRemoteSystemEnvVar.setAdditionalAttributes(String)
|
org.eclipse.rse.ui.SystemWidgetHelpers.setHelp(Control, IViewPart, Object)
|
org.eclipse.rse.core.subsystems.SubSystem.setProperties(Object, String[], String[])
this shouldn't be used |
org.eclipse.rse.core.subsystems.ISubSystem.setProperties(Object, String[], String[])
this shouldn't be used |
org.eclipse.rse.core.subsystems.SubSystem.setProperty(Object, String, String)
this shouldn't be used |
org.eclipse.rse.core.subsystems.ISubSystem.setProperty(Object, String, String)
this shouldn't be used |
org.eclipse.rse.core.subsystems.SubSystem.setRemoteAttribute(String, String)
|
org.eclipse.rse.core.subsystems.RemoteServerLauncher.setRestrictedType(String, String)
|
org.eclipse.rse.core.subsystems.SubSystem.setVendorAttribute(String, String, String)
use property sets directly now |
org.eclipse.rse.core.subsystems.ISubSystem.setVendorAttribute(String, String, String)
Subsystems can now take named property sets. These should be used instead.
See IPropertySet |