Class TstStatefulPoolableConnector

java.lang.Object
org.identityconnectors.testconnector.TstAbstractConnector
org.identityconnectors.testconnector.TstStatefulPoolableConnector
All Implemented Interfaces:
Connector, CreateOp, DeleteOp, LiveSyncOp, SearchOp<Filter>, SPIOperation, SyncOp, PoolableConnector

public class TstStatefulPoolableConnector extends TstAbstractConnector implements PoolableConnector
  • Constructor Details

    • TstStatefulPoolableConnector

      public TstStatefulPoolableConnector()
  • Method Details

    • init

      public void init(Configuration cfg)
      Description copied from interface: Connector
      Initialize the connector with its configuration. For instance in a JDBC Connector this would include the database URL, password, and user.
      Specified by:
      init in interface Connector
      Overrides:
      init in class TstAbstractConnector
      Parameters:
      cfg - instance of the Configuration object implemented by the Connector developer and populated with information in order to initialize the Connector.
    • getConfiguration

      public Configuration getConfiguration()
      Description copied from interface: Connector
      Return the configuration that was passed to Connector.init(Configuration).
      Specified by:
      getConfiguration in interface Connector
      Returns:
      The configuration that was passed to Connector.init(Configuration).
    • dispose

      public void dispose()
      Description copied from interface: Connector
      Dispose of any resources the Connector uses.
      Specified by:
      dispose in interface Connector
    • checkAlive

      public void checkAlive()
      Description copied from interface: PoolableConnector
      Checks if the connector is still alive.

      A connector can spend a large amount of time in the pool before being used. This method is intended to check if the connector is alive and operations can be invoked on it (for instance, an implementation would check that the connector's physical connection to the resource has not timed out).

      The major difference between this method and TestOp.test() is that this method must do only the minimum that is necessary to check that the connector is still alive. TestOp.test() does a more thorough check of the environment specified in the Configuration, and can therefore be much slower.

      This method can be called often. Implementations should do their best to keep this method fast.

      Specified by:
      checkAlive in interface PoolableConnector