org.apache.ode.bpel.engine.migration

## Class OutstandingRequestsMigration

- java.lang.Object
- - org.apache.ode.bpel.engine.migration.OutstandingRequestsMigration

- All Implemented Interfaces:
    Migration

      public class OutstandingRequestsMigration
      extends java.lang.Object
      implements Migration

  Migrates OutstandingRequestManager to IMAManager

- - ### Constructor Summary

    Constructors
    Constructor and Description
    `OutstandingRequestsMigration()`

  - ### Method Summary

    Methods
    Modifier and Type | Method and Description
    --- | ---
    `boolean` | `migrate(java.util.Set<BpelProcess> registeredProcesses, BpelDAOConnection connection)` All database migrations are run in the same transaction so if one fails, they will all be rollbacked.

    - ### Methods inherited from class java.lang.Object

      `clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait`

- - ### Constructor Detail

    - #### OutstandingRequestsMigration

          public OutstandingRequestsMigration()

  - ### Method Detail

    - #### migrate

          public boolean migrate(java.util.Set<BpelProcess> registeredProcesses,
                        BpelDAOConnection connection)

      Description copied from interface: `Migration`
      All database migrations are run in the same transaction so if one fails, they will all be rollbacked. There are two ways to fail: either return false or throw an exception. The difference is that throwing an exception will stop the server startup whereas returning false will let the server continue its starting cycle and run on the non-migrated data.
      Specified by:
        `migrate` in interface `Migration`