Class ObsoleteGui

All Implemented Interfaces:
ImageObserver, MenuContainer, Serializable, Accessible, ClearGui, JMeterGUIComponent, Printable

public class ObsoleteGui extends AbstractJMeterGuiComponent
Default config gui for Configuration Element.
See Also:
  • Constructor Details

    • ObsoleteGui

      public ObsoleteGui()
  • Method Details

    • getLabelResource

      public String getLabelResource()
      Description copied from interface: JMeterGUIComponent
      Get the component's resource name, which getStaticLabel uses to derive the component's label in the local language. The resource name is fixed, and does not vary with the selected language. Normally this method should be overridden in preference to overriding getStaticLabel(). However where the resource name is not available or required, getStaticLabel() may be overridden instead.
      the resource name
    • createTestElement

      public TestElement createTestElement()
      Description copied from interface: JMeterGUIComponent
      JMeter test components are separated into a model and a GUI representation. The model holds the data and the GUI displays it. The GUI class is responsible for knowing how to create and initialize with data the model class that it knows how to display, and this method is called when new test elements are created.

      The canonical implementation looks like this:

       public TestElement createTestElement() {
           TestElementXYZ el = new TestElementXYZ();
           return el;
      the Test Element object that the GUI component represents.
    • modifyTestElement

      public void modifyTestElement(TestElement element)
      Description copied from interface: JMeterGUIComponent
      GUI components are responsible for populating TestElements they create with the data currently held in the GUI components. This method should overwrite whatever data is currently in the TestElement as it is called after a user has filled out the form elements in the gui with new information.

      The canonical implementation looks like this:

       public void modifyTestElement(TestElement element) {
           element.clear(); // many implementations use this
           // Using the element setters (preferred):
           TestElementXYZ xyz = (TestElementXYZ) element;
           ... other GUI fields ...
           // or directly (do not use unless there is no setter for the field):
           element.setProperty(TestElementXYZ.STATE, guiState.getText())
           element.setProperty(TestElementXYZ.CODE, guiCode.getText())
           ... other GUI fields ...
      element - the TestElement to modify
    • createPopupMenu

      public JPopupMenu createPopupMenu()
      Description copied from interface: JMeterGUIComponent
      When a user right-clicks on the component in the test tree, or selects the edit menu when the component is selected, the component will be asked to return a JPopupMenu that provides all the options available to the user from this component.
      a JPopupMenu appropriate for the component.
    • getMenuCategories

      public Collection<String> getMenuCategories()
      Description copied from interface: JMeterGUIComponent
      This is the list of add menu categories this gui component will be available under. For instance, if this represents a Controller, then the MenuFactory.CONTROLLERS category should be in the returned collection. When a user right-clicks on a tree element and looks through the "add" menu, which category your GUI component shows up in is determined by which categories are returned by this method. Most GUI's belong to only one category, but it is possible for a component to exist in multiple categories.
      a Collection of Strings, where each element is one of the constants defined in MenuFactory
      See Also: