Re: Making sense of callbacks

From: Andrus Adamchik (andru..bjectstyle.org)
Date: Sat Oct 03 2009 - 10:37:06 EDT

  • Next message: Evgeny Ryabitskiy: "Re: Passing null values in parameters, part 2 )"

    I finished this per CAY-1281. Project upgrade is performed on opening
    it in the Modeler, so migration for the existing callback users is
    straightforward.

    Haven't checked whether that works for ROP. I would appreciate if
    somebody could help me with that.

    Andrus

    On Sep 28, 2009, at 9:53 AM, Andrus Adamchik wrote:

    >
    > On Sep 28, 2009, at 4:08 AM, Lachlan Deck wrote:
    >
    >>
    >> So from what I can see the only two changes required were
    >> 'postInsert' and adjusting the meaning of prePersist
    >
    > I also tend to think that less is better. This discussion thread was
    > a nice brainstorming on the callbacks use patterns. So we've played
    > with a few things and now I am fine if we go a full circle to the
    > minimal change suggested earlier, and don't worry about JPA users,
    > extra delete callbacks, or symmetry between callback types (in many
    > respects there's little symmetry if you look at the object lifecycle
    > - http://cayenne.apache.org/doc/persistent-object-lifecycle.html).
    >
    > So here is the change I am going to make:
    >
    > 1. Call "prePersist" before commit
    > 2. Introduce "postAdd" instead of current "prePersist".
    >
    > This change is minimal and is not incompatible with other ideas.
    > Objections?
    >
    > Andrus
    >
    >
    >

    This archive was generated by hypermail 2.0.0 : Sat Oct 03 2009 - 10:38:27 EDT