Re: Event handling vs. concurrent/rolled back transactions

From: Andrus (andru..bjectstyle.org)
Date: Mon Jan 20 2003 - 12:24:03 EST

  • Next message: Holger Hoffstätte: "Re: Event handling vs. concurrent/rolled back transactions"

    Here is an idea - move all functionality of
    DataContextTransactionEventHandler to ContextCommitObserver (and get rid of
    DataContextTransactionEventHandler alltogether).

    A new ContextCommitObserver is always instantiated for each commit, and
    therefore can safely store the state.

    It (and its superclass) has callback methods invoked on commit, rollback,
    exceptions and such. If we need extra API in, we can add it...

    >3) a new dataContextRolledBack event so that the handler can clean up
    >properly

    +1, as a part of ContextCommitObserver.

    Andrus

    This archive was generated by hypermail 2.0.0 : Mon Jan 20 2003 - 12:23:25 EST