To use any Eclipse extension point, including those defined by the Remote System Explorer, you must first create a plug-in project using the plug-in development environment (PDE), which you will do shortly. At its simplest, a plug-in project requires a MANIFEST.MF file describing the plugin and its dependencies and, if extending the workbench a plugin.xml file identifying the extension points being implemented, and a set of Java classes implementing those extension points. There is usually also a plug-in class file that is used as the overall manager of the project, and point of integration that other classes can rely on.
-
If you already have a plugin project, you will need to update it slightly to make it extend SystemBasePlugin and add the few methods it requires. You may wish to examine these steps to see what methods to add. The Eclipse environment will keep your classpaths and plugin dependecies in sync for you.
-
Eclipse supplies a number of plug-in project templates, which generate a number of project files that illustrate examples of various Eclipse extension points. While you are free to pick one of these, or indeed start with any existing plug-in project if you have one, in the RSE tutorials everything is created by hand so as to keep focused on the RSE-required classes and files.
-
The following tutorial uses numbered steps to indicate where you are required to do something as you follow along.
-
Step By Step: Creating an RSE Plug-in Project
-
-
Select File->New->Project.
-
In the dialog box select the Plug-in Project wizard. Click Next >.
-
-
-
In the first page of the wizard enter "RSESamples" for the project name (without the quotes). Click Next >.
-
-
-
In the second page of the wizard enter your company for the Plug-in Provider, change the Activator to be "rsesamples.RSESamplesPlugin", and click Next >.
-
-
-
In the third page of the wizard uncheck the "Create a plug-in using one of the templates" checkbox and click Finish.
-
-
-
Your new plugin project is created and visible in the Package Explorer of the Plug-in Development perspective. Your new plugin properties are also open in the plug-in editor.
-
Go to the dependencies tab of the plug-in editor and add the following plugins to the list:
-
-
org.eclipse.core.resources
-
org.eclipse.rse.ui
-
org.eclipse.rse.services
-
org.eclipse.rse.files.ui
-
org.eclipse.rse.shells.ui
-
org.eclipse.rse.subsystems.files.core
-
org.eclipse.rse.subsystems.shells.core
-
-
-
Now go to the MANIFEST.MF tab of the plugin properties.
-This shows the source for the MANIFEST.MF file associated with this plugin.
-Change the Bundle-SymbolicName line adding a singleton:=true directive.
-
-Bundle-SymbolicName:RSESamples;singleton:=true
-
-This allows us to add extensions to the plugin at a later point.
-Save the plugin properties and close the editor.
-
-
-Right-click on the RSESamples project and create a plugin.xml file.
-Normally this would be created if you used a template to create your plugin.
-We will use this file to add extensions to RSE but for now it will just be a skeleton with the following contents:
-
-<plugin>
-</plugin>
-
-Add the lines above to the empty plugin.xml file and save it.
-
-
Expand the src folder, then the rsesamples package folder, and double-click on RSESamplesPlugin.java to edit this class.
-Change it as described below. Reference the source here for the details.
-
-
Extend SystemBasePlugin instead of AbstractUIPlugin
-
Add the declaration for resourceBundle
-
Add the declaration for messageFile
-
Invoke the superclass constructor from this constructor
-
Add the initializeImageRegistry() method
-
Add the getMessageFile() method
-
Add the getResourceBundle() method
-
Add the static getWorkspace() method
-
Add the static getResourceString(String) method
-
Add the static getPluginMessageFile() method
-
Add the static getPluginMessage(String) method
-
-
-
Create the project's resources file for translatable strings: right-click on the RSESamples project and select New->File to open the New File wizard. Enter rseSamplesResources.properties for the file name, as was specified in the call to loadResourceBundle in the plug-in class's constructor. Press Finish to create the file. You will populate as you go through the tutorials, so for now just close the editor opened for the file.
-
Create the project's RSE-style messages file for translatable messages: right-click on the RSESamples project and select New->File to get the New File wizard. Enter rseSamplesMessages.xml for the file name, as was specified in the call to loadMessageFile in the plug-in class's constructor. Press Finish to create the file. You will see the XML editor open for the new file. Press the Source tab at the bottom of the editor, and enter the following lines (so that you can add messages to the file later on):
-
-<?xml version="1.0" encoding='UTF-8'?>
-<!DOCTYPE MessageFile SYSTEM "../org.eclipse.rse.ui/messageFile.dtd">
-<!-- This is a message file used by SystemMessage and SystemMessageDialog -->
-<MessageFile Version="1.0">
- <Component Name="RSE Samples" Abbr="RSS">
- <Subcomponent Name="General" Abbr="G">
- <MessageList>
- <Message ID="1001" Indicator="E">
- <LevelOne>Sample message</LevelOne>
- <LevelTwo>This is a sample with one substitution variable: %1</LevelTwo>
- </Message>
- </MessageList>
- </Subcomponent>
- </Component>
-</MessageFile>
-
-Save and close the file.
-
-
Your plugin is created and you are ready to go. Now you only need to add the code to implement the extension points.
-
To use any Eclipse extension point, including those defined by the Remote System Explorer, you must first create a plug-in project using the plug-in development environment (PDE), which you will do shortly. At its simplest, a plug-in project requires a MANIFEST.MF file describing the plugin and its dependencies and, if extending the workbench a plugin.xml file identifying the extension points being implemented, and a set of Java classes implementing those extension points. There is usually also a plug-in class file that is used as the overall manager of the project, and point of integration that other classes can rely on.
+
If you already have a plugin project, you will need to update it slightly to make it extend SystemBasePlugin and add the few methods it requires. You may wish to examine these steps to see what methods to add. The Eclipse environment will keep your classpaths and plugin dependecies in sync for you.
+
Eclipse supplies a number of plug-in project templates, which generate a number of project files that illustrate examples of various Eclipse extension points. While you are free to pick one of these, or indeed start with any existing plug-in project if you have one, in the RSE tutorials everything is created by hand so as to keep focused on the RSE-required classes and files.
+
The following tutorial uses numbered steps to indicate where you are required to do something as you follow along.
+
Step By Step: Creating an RSE Plug-in Project
+
+
Select File->New->Project.
+
In the dialog box select the Plug-in Project wizard. Click Next >.
+
+
+
In the first page of the wizard enter "RSESamples" for the project name (without the quotes). Click Next >.
+
+
+
In the second page of the wizard enter your company for the Plug-in Provider, change the Activator to be "rsesamples.RSESamplesPlugin", and click Next >.
+
+
+
In the third page of the wizard uncheck the "Create a plug-in using one of the templates" checkbox and click Finish.
+
+
+
Your new plugin project is created and visible in the Package Explorer of the Plug-in Development perspective. Your new plugin properties are also open in the plug-in editor.
+
Go to the dependencies tab of the plug-in editor and add the following plugins to the list:
+
+
org.eclipse.core.resources
+
org.eclipse.rse.ui
+
org.eclipse.rse.services
+
org.eclipse.rse.files.ui
+
org.eclipse.rse.shells.ui
+
org.eclipse.rse.subsystems.files.core
+
org.eclipse.rse.subsystems.shells.core
+
+
+
Now go to the MANIFEST.MF tab of the plugin properties.
+This shows the source for the MANIFEST.MF file associated with this plugin.
+Change the Bundle-SymbolicName line adding a singleton:=true directive.
+
+Bundle-SymbolicName:RSESamples;singleton:=true
+
+This allows us to add extensions to the plugin at a later point.
+Save the plugin properties and close the editor.
+
+
+Right-click on the RSESamples project and create a plugin.xml file.
+Normally this would be created if you used a template to create your plugin.
+We will use this file to add extensions to RSE but for now it will just be a skeleton with the following contents:
+
+<plugin>
+</plugin>
+
+Add the lines above to the empty plugin.xml file and save it.
+
+
Expand the src folder, then the rsesamples package folder, and double-click on RSESamplesPlugin.java to edit this class.
+Change it as described below. Reference the source here for the details.
+
+
Extend SystemBasePlugin instead of AbstractUIPlugin
+
Add the declaration for resourceBundle
+
Add the declaration for messageFile
+
Invoke the superclass constructor from this constructor
+
Add the initializeImageRegistry() method
+
Add the getMessageFile() method
+
Add the getResourceBundle() method
+
Add the static getWorkspace() method
+
Add the static getResourceString(String) method
+
Add the static getPluginMessageFile() method
+
Add the static getPluginMessage(String) method
+
+
+
Create the project's resources file for translatable strings: right-click on the RSESamples project and select New->File to open the New File wizard. Enter rseSamplesResources.properties for the file name, as was specified in the call to loadResourceBundle in the plug-in class's constructor. Press Finish to create the file. You will populate as you go through the tutorials, so for now just close the editor opened for the file.
+
Create the project's RSE-style messages file for translatable messages: right-click on the RSESamples project and select New->File to get the New File wizard. Enter rseSamplesMessages.xml for the file name, as was specified in the call to loadMessageFile in the plug-in class's constructor. Press Finish to create the file. You will see the XML editor open for the new file. Press the Source tab at the bottom of the editor, and enter the following lines (so that you can add messages to the file later on):
+
+<?xml version="1.0" encoding='UTF-8'?>
+<!DOCTYPE MessageFile SYSTEM "../org.eclipse.rse.ui/messageFile.dtd">
+<!-- This is a message file used by SystemMessage and SystemMessageDialog -->
+<MessageFile Version="1.0">
+ <Component Name="RSE Samples" Abbr="RSS">
+ <Subcomponent Name="General" Abbr="G">
+ <MessageList>
+ <Message ID="1001" Indicator="E">
+ <LevelOne>Sample message</LevelOne>
+ <LevelTwo>This is a sample with one substitution variable: %1</LevelTwo>
+ </Message>
+ </MessageList>
+ </Subcomponent>
+ </Component>
+</MessageFile>
+
+Save and close the file.
+
+
Your plugin is created and you are ready to go. Now you only need to add the code to implement the extension points.
+
+
+
+
Index: guide/tutorial/DeveloperSubSystem2.html
===================================================================
RCS file: /cvsroot/dsdp/org.eclipse.tm.rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/DeveloperSubSystem2.html,v
retrieving revision 1.4
diff -u -r1.4 DeveloperSubSystem2.html
--- guide/tutorial/DeveloperSubSystem2.html 14 May 2007 09:43:48 -0000 1.4
+++ guide/tutorial/DeveloperSubSystem2.html 12 Sep 2007 18:51:48 -0000
@@ -108,7 +108,7 @@
// Now, subset master list, based on filter string...
NamePatternMatcher subsetter = new NamePatternMatcher(filterString);
Vector v = new Vector();
- for (int idx=0; idx <1; allTeams.length; idx++)
+ for (int idx=0; idx < allTeams.length; idx++)
{
if (subsetter.matches(allTeams[idx].getName()))
v.addElement(allTeams[idx]);
@@ -124,7 +124,7 @@
String devrName = filterString.substring(slashIdx+1);
TeamResource[] allTeams = getAllTeams();
TeamResource match = null;
- for (int idx=0; (match==null) && (idx < allTeams.length); idx++)
+ for (int idx=0; (match==null) && (idx < allTeams.length); idx++)
if (allTeams[idx].getName().equals(teamName))
match = allTeams[idx];
if (match != null)
Index: guide/tutorial/TeamResourceAdapter.html
===================================================================
RCS file: /cvsroot/dsdp/org.eclipse.tm.rse/doc/org.eclipse.rse.doc.isv/guide/tutorial/TeamResourceAdapter.html,v
retrieving revision 1.2
diff -u -r1.2 TeamResourceAdapter.html
--- guide/tutorial/TeamResourceAdapter.html 4 Aug 2006 20:37:04 -0000 1.2
+++ guide/tutorial/TeamResourceAdapter.html 12 Sep 2007 18:51:48 -0000
@@ -1,228 +1,228 @@
-
-
-
-
-
-
-
-
-TeamResourceAdapter Class After Editing
-
-
-
-
TeamResourceAdapter Class After Editing
-
-package samples.model;
-
-import org.eclipse.jface.resource.ImageDescriptor;
-import org.eclipse.jface.viewers.IStructuredSelection;
-import org.eclipse.rse.ui.SystemMenuManager;
-import org.eclipse.rse.ui.view.AbstractSystemViewAdapter;
-import org.eclipse.rse.ui.view.ISystemRemoteElementAdapter;
-import org.eclipse.swt.widgets.Shell;
-import org.eclipse.ui.views.properties.IPropertyDescriptor;
-
-import samples.RSESamplesPlugin;
-import samples.subsystems.DeveloperSubSystem;
-
-/**
- * This is the adapter which enables us to work with our remote team resources.
- */
-public class TeamResourceAdapter extends AbstractSystemViewAdapter implements
- ISystemRemoteElementAdapter {
-
- /**
- * Constructor.
- */
- public TeamResourceAdapter() {
- super();
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.AbstractSystemViewAdapter#addActions(org.eclipse.rse.ui.SystemMenuManager,
- * org.eclipse.jface.viewers.IStructuredSelection, org.eclipse.swt.widgets.Shell, java.lang.String)
- */
- public void addActions(SystemMenuManager menu,
- IStructuredSelection selection, Shell parent, String menuGroup)
- {
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.AbstractSystemViewAdapter#getImageDescriptor(java.lang.Object)
- */
- public ImageDescriptor getImageDescriptor(Object element)
- {
- return RSESamplesPlugin.getDefault().getImageDescriptor("ICON_ID_TEAM");
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.AbstractSystemViewAdapter#getText(java.lang.Object)
- */
- public String getText(Object element)
- {
- return ((TeamResource)element).getName();
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.AbstractSystemViewAdapter#getAbsoluteName(java.lang.Object)
- */
- public String getAbsoluteName(Object object)
- {
- TeamResource team = (TeamResource)object;
- return "Team_"+team.getName();
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.AbstractSystemViewAdapter#getType(java.lang.Object)
- */
- public String getType(Object element)
- {
- return RSESamplesPlugin.getResourceString("property.team_resource.type");
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.AbstractSystemViewAdapter#getParent(java.lang.Object)
- */
- public Object getParent(Object element)
- {
- return null; // not really used, which is good because it is ambiguous
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.AbstractSystemViewAdapter#hasChildren(java.lang.Object)
- */
- public boolean hasChildren(Object element)
- {
- return true;
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.AbstractSystemViewAdapter#getChildren(java.lang.Object)
- */
- public Object[] getChildren(Object element)
- {
- return ((TeamResource)element).getDevelopers();
- }
-
- /**
- * @see org.eclipse.rse.ui.view.AbstractSystemViewAdapter#internalGetPropertyDescriptors()
- */
- protected IPropertyDescriptor[] internalGetPropertyDescriptors()
- {
- return null;
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.AbstractSystemViewAdapter#internalGetPropertyValue(java.lang.Object)
- */
- protected Object internalGetPropertyValue(Object key)
- {
- return null;
- }
-
- /**
- * Intercept of parent method to indicate these objects can be renamed using the RSE-supplied
- * rename action.
- */
- public boolean canRename(Object element)
- {
- return true;
- }
-
- /**
- * Intercept of parent method to actually do the rename. RSE supplies the rename GUI, but
- * defers the action work of renaming to this adapter method.
- */
- public boolean doRename(Shell shell, Object element, String newName)
- {
- ((TeamResource)element).setName(newName);
- return true;
- }
- // --------------------------------------
- // ISystemRemoteElementAdapter methods...
- // --------------------------------------
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.ISystemRemoteElementAdapter#getAbsoluteParentName(java.lang.Object)
- */
- public String getAbsoluteParentName(Object element)
- {
- return "root"; // not really applicable as we have no unique hierarchy
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.ISystemRemoteElementAdapter#getSubSystemConfigurationId(java.lang.Object)
- */
- public String getSubSystemConfigurationId(Object element)
- {
- return "samples.subsystems.factory"; // as declared in extension in plugin.xml
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.ISystemRemoteElementAdapter#getRemoteTypeCategory(java.lang.Object)
- */
- public String getRemoteTypeCategory(Object element)
- {
- return "developers"; // Course grained. Same for all our remote resources.
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.ISystemRemoteElementAdapter#getRemoteType(java.lang.Object)
- */
- public String getRemoteType(Object element)
- {
- return "team"; // Fine grained. Unique to this resource type.
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.ISystemRemoteElementAdapter#getRemoteSubType(java.lang.Object)
- */
- public String getRemoteSubType(Object element)
- {
- return null; // Very fine grained. We don't use it.
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.ISystemRemoteElementAdapter#refreshRemoteObject(java.lang.Object, java.lang.Object)
- */
- public boolean refreshRemoteObject(Object oldElement, Object newElement)
- {
- TeamResource oldTeam = (TeamResource)oldElement;
- TeamResource newTeam = (TeamResource)newElement;
- newTeam.setName(oldTeam.getName());
- return false; // If developer objects held references to their team names, we'd have to return true
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.ISystemRemoteElementAdapter#getRemoteParent(org.eclipse.swt.widgets.Shell, java.lang.Object)
- */
- public Object getRemoteParent(Shell shell, Object element) throws Exception
- {
- return null; // maybe this would be a Project or Roster object, or leave as null if this is the root
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.ISystemRemoteElementAdapter#getRemoteParentNamesInUse(org.eclipse.swt.widgets.Shell, java.lang.Object)
- */
- public String[] getRemoteParentNamesInUse(Shell shell, Object element)
- throws Exception
- {
- DeveloperSubSystem ourSS = (DeveloperSubSystem)getSubSystem(element);
- TeamResource[] allTeams = ourSS.getAllTeams();
- String[] allNames = new String[allTeams.length];
- for (int idx = 0; idx < allTeams.length; idx++)
- allNames[idx] = allTeams[idx].getName();
- return allNames; // Return list of all team names
- }
-
- /* (non-Javadoc)
- * @see org.eclipse.rse.ui.view.ISystemRemoteElementAdapter#supportsUserDefinedActions(java.lang.Object)
- */
- public boolean supportsUserDefinedActions(Object object) {
- return false;
- }
-
-}
-
-
-
+
+
+
+
+
+
+
+
+TeamResourceAdapter Class After Editing
+
+
+
+
TeamResourceAdapter Class After Editing
+
+package samples.model;
+
+import org.eclipse.jface.resource.ImageDescriptor;
+import org.eclipse.jface.viewers.IStructuredSelection;
+import org.eclipse.rse.ui.SystemMenuManager;
+import org.eclipse.rse.ui.view.AbstractSystemViewAdapter;
+import org.eclipse.rse.ui.view.ISystemRemoteElementAdapter;
+import org.eclipse.swt.widgets.Shell;
+import org.eclipse.ui.views.properties.IPropertyDescriptor;
+
+import samples.RSESamplesPlugin;
+import samples.subsystems.DeveloperSubSystem;
+
+/**
+ * This is the adapter which enables us to work with our remote team resources.
+ */
+public class TeamResourceAdapter extends AbstractSystemViewAdapter implements
+ ISystemRemoteElementAdapter {
+
+ /**
+ * Constructor.
+ */
+ public TeamResourceAdapter() {
+ super();
+ }
+
+ /* (non-Javadoc)
+ * @see org.eclipse.rse.ui.view.AbstractSystemViewAdapter#addActions(org.eclipse.rse.ui.SystemMenuManager,
+ * org.eclipse.jface.viewers.IStructuredSelection, org.eclipse.swt.widgets.Shell, java.lang.String)
+ */
+ public void addActions(SystemMenuManager menu,
+ IStructuredSelection selection, Shell parent, String menuGroup)
+ {
+ }
+
+ /* (non-Javadoc)
+ * @see org.eclipse.rse.ui.view.AbstractSystemViewAdapter#getImageDescriptor(java.lang.Object)
+ */
+ public ImageDescriptor getImageDescriptor(Object element)
+ {
+ return RSESamplesPlugin.getDefault().getImageDescriptor("ICON_ID_TEAM");
+ }
+
+ /* (non-Javadoc)
+ * @see org.eclipse.rse.ui.view.AbstractSystemViewAdapter#getText(java.lang.Object)
+ */
+ public String getText(Object element)
+ {
+ return ((TeamResource)element).getName();
+ }
+
+ /* (non-Javadoc)
+ * @see org.eclipse.rse.ui.view.AbstractSystemViewAdapter#getAbsoluteName(java.lang.Object)
+ */
+ public String getAbsoluteName(Object object)
+ {
+ TeamResource team = (TeamResource)object;
+ return "Team_"+team.getName();
+ }
+
+ /* (non-Javadoc)
+ * @see org.eclipse.rse.ui.view.AbstractSystemViewAdapter#getType(java.lang.Object)
+ */
+ public String getType(Object element)
+ {
+ return RSESamplesPlugin.getResourceString("property.team_resource.type");
+ }
+
+ /* (non-Javadoc)
+ * @see org.eclipse.rse.ui.view.AbstractSystemViewAdapter#getParent(java.lang.Object)
+ */
+ public Object getParent(Object element)
+ {
+ return null; // not really used, which is good because it is ambiguous
+ }
+
+ /* (non-Javadoc)
+ * @see org.eclipse.rse.ui.view.AbstractSystemViewAdapter#hasChildren(java.lang.Object)
+ */
+ public boolean hasChildren(Object element)
+ {
+ return true;
+ }
+
+ /* (non-Javadoc)
+ * @see org.eclipse.rse.ui.view.AbstractSystemViewAdapter#getChildren(java.lang.Object)
+ */
+ public Object[] getChildren(Object element)
+ {
+ return ((TeamResource)element).getDevelopers();
+ }
+
+ /**
+ * @see org.eclipse.rse.ui.view.AbstractSystemViewAdapter#internalGetPropertyDescriptors()
+ */
+ protected IPropertyDescriptor[] internalGetPropertyDescriptors()
+ {
+ return null;
+ }
+
+ /* (non-Javadoc)
+ * @see org.eclipse.rse.ui.view.AbstractSystemViewAdapter#internalGetPropertyValue(java.lang.Object)
+ */
+ protected Object internalGetPropertyValue(Object key)
+ {
+ return null;
+ }
+
+ /**
+ * Intercept of parent method to indicate these objects can be renamed using the RSE-supplied
+ * rename action.
+ */
+ public boolean canRename(Object element)
+ {
+ return true;
+ }
+
+ /**
+ * Intercept of parent method to actually do the rename. RSE supplies the rename GUI, but
+ * defers the action work of renaming to this adapter method.
+ */
+ public boolean doRename(Shell shell, Object element, String newName)
+ {
+ ((TeamResource)element).setName(newName);
+ return true;
+ }
+ // --------------------------------------
+ // ISystemRemoteElementAdapter methods...
+ // --------------------------------------
+
+ /* (non-Javadoc)
+ * @see org.eclipse.rse.ui.view.ISystemRemoteElementAdapter#getAbsoluteParentName(java.lang.Object)
+ */
+ public String getAbsoluteParentName(Object element)
+ {
+ return "root"; // not really applicable as we have no unique hierarchy
+ }
+
+ /* (non-Javadoc)
+ * @see org.eclipse.rse.ui.view.ISystemRemoteElementAdapter#getSubSystemConfigurationId(java.lang.Object)
+ */
+ public String getSubSystemConfigurationId(Object element)
+ {
+ return "samples.subsystems.factory"; // as declared in extension in plugin.xml
+ }
+
+ /* (non-Javadoc)
+ * @see org.eclipse.rse.ui.view.ISystemRemoteElementAdapter#getRemoteTypeCategory(java.lang.Object)
+ */
+ public String getRemoteTypeCategory(Object element)
+ {
+ return "developers"; // Course grained. Same for all our remote resources.
+ }
+
+ /* (non-Javadoc)
+ * @see org.eclipse.rse.ui.view.ISystemRemoteElementAdapter#getRemoteType(java.lang.Object)
+ */
+ public String getRemoteType(Object element)
+ {
+ return "team"; // Fine grained. Unique to this resource type.
+ }
+
+ /* (non-Javadoc)
+ * @see org.eclipse.rse.ui.view.ISystemRemoteElementAdapter#getRemoteSubType(java.lang.Object)
+ */
+ public String getRemoteSubType(Object element)
+ {
+ return null; // Very fine grained. We don't use it.
+ }
+
+ /* (non-Javadoc)
+ * @see org.eclipse.rse.ui.view.ISystemRemoteElementAdapter#refreshRemoteObject(java.lang.Object, java.lang.Object)
+ */
+ public boolean refreshRemoteObject(Object oldElement, Object newElement)
+ {
+ TeamResource oldTeam = (TeamResource)oldElement;
+ TeamResource newTeam = (TeamResource)newElement;
+ newTeam.setName(oldTeam.getName());
+ return false; // If developer objects held references to their team names, we'd have to return true
+ }
+
+ /* (non-Javadoc)
+ * @see org.eclipse.rse.ui.view.ISystemRemoteElementAdapter#getRemoteParent(org.eclipse.swt.widgets.Shell, java.lang.Object)
+ */
+ public Object getRemoteParent(Shell shell, Object element) throws Exception
+ {
+ return null; // maybe this would be a Project or Roster object, or leave as null if this is the root
+ }
+
+ /* (non-Javadoc)
+ * @see org.eclipse.rse.ui.view.ISystemRemoteElementAdapter#getRemoteParentNamesInUse(org.eclipse.swt.widgets.Shell, java.lang.Object)
+ */
+ public String[] getRemoteParentNamesInUse(Shell shell, Object element)
+ throws Exception
+ {
+ DeveloperSubSystem ourSS = (DeveloperSubSystem)getSubSystem(element);
+ TeamResource[] allTeams = ourSS.getAllTeams();
+ String[] allNames = new String[allTeams.length];
+ for (int idx = 0; idx < allTeams.length; idx++)
+ allNames[idx] = allTeams[idx].getName();
+ return allNames; // Return list of all team names
+ }
+
+ /* (non-Javadoc)
+ * @see org.eclipse.rse.ui.view.ISystemRemoteElementAdapter#supportsUserDefinedActions(java.lang.Object)
+ */
+ public boolean supportsUserDefinedActions(Object object) {
+ return false;
+ }
+
+}
+
-
-
-
-