All Known Implementing Classes:
SQLConfigurator

public interface LegacyDBConfigurator
Classes that implement this will be able to create a NamedQuery from their own config. Used so the ConfiguratorMultiplexor can handle a press of the "convert" button that these classes should also have.
  • Method Details

    • createNamedQueries

      LegacyDBConfigurator.NamedQueryBindingWrapper createNamedQueries(String selectQueryName, String updateQueryName)
      Creates a Select NamedQuery and an Update NamedQuery as well as a NamedQueryBindingConfig from the info currently on the screen and wraps all of this up in a LegacyDBConfigurator.NamedQueryBindingWrapper. The function that calls this is responsible for saving the resources.
      Parameters:
      selectQueryName - Path for the new Select NamedQuery
      updateQueryName - Path for the new Update NamedQuery
      Returns:
      LegacyDBConfigurator.NamedQueryBindingWrapper with blank paths. Not null.
    • getContext

      DesignerContext getContext()
      Needed to save the resource. The configurators have a copy already, while the Multiplexor doesn't.
    • addConvertButton

      void addConvertButton(JButton convertButton)
      Adds a convert button to the configurator
      Parameters:
      convertButton - Completely configured button that will get a path and then call createNamedQuery()
    • hasUpdateQuery

      boolean hasUpdateQuery()
      Returns:
      true if this configurator has a non-empty update query, false otherwise
    • hasUpdateSupport

      boolean hasUpdateSupport()
      Returns:
      true if this configurator has support for push updates, false otherwise