RSE Properties API

You can supply your own property pages to any node in the Remote Systems tree or table views. As you author your property page classes, you may find the RSE-supplied base class for property pages of value.

RSE-Supplied Base Class for Property Pages

The RSE supplies a base class for property pages, org.eclipse.rse.ui.propertypages.SystemBasePropertyPage, that extends the base eclipse property page org.eclipse.ui.dialogs.PropertyPage. The advantages of using this RSE-supplied class are:

Property Pages for RSE Non-Remote Resources

You can simply use the eclipse-supplied extension point org.eclipse.ui.propertyPages to contribute property pages to any of the non-remote artifacts from the RSE model. To use this extension point, you need to know the class or, preferably, interface that the objects implement, which we describe here:

RSE Resource Implements Interface
Profile org.eclipse.rse.model.ISystemProfile
Host org.eclipse.rse.model.IHost
Subsystem org.eclipse.rse.core.subsystems.ISubSystem
Filter pool reference org.eclipse.rse.filters.ISystemFilterPoolReference
Filter reference org.eclipse.rse.filters.ISystemFilterReference

Property Pages for RSE Remote Resources

Remote resources have no underlying eclipse resource, and typically all are instances of the same class, meaning insufficient fidelity in scoping property pages to a remote resource of a particular type. Because of this, the RSE supplies its propertyPages extension point, for remote resources, which allows for very explicit scoping of the property page to very specific types of remote resources.