Overview | Package | Class | Tree | Deprecated | Index | Help
PREV CLASS NEXT CLASS | FRAMES NO FRAMES
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD

## org.apache.ode.bpel.engine.migration
Class CorrelationKeyMigration

    java.lang.Object
      org.apache.ode.bpel.engine.migration.CorrelationKeyMigration

All Implemented Interfaces:
  Migration

    public class CorrelationKeyMigration

extends java.lang.Object
implements Migration

Migrates the correlation key values to a scheme containing the OModel correlation set id to one using its name. So something like 1~abc~de will become foo~abc~de.

Constructor Summary
`CorrelationKeyMigration()`

Method Summary
`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

### CorrelationKeyMigration

    public CorrelationKeyMigration()

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`

Overview | Package | Class | Tree | Deprecated | Index | Help
PREV CLASS NEXT CLASS | FRAMES NO FRAMES
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD