Re: Pre-insert callback?

• Previous message: Andrey Razumovsky: "Pre-insert callback?"
• In reply to: Andrey Razumovsky: "Pre-insert callback?"
• Next in thread: Andrus Adamchik: "Re: Pre-insert callback?"
• Reply: Andrus Adamchik: "Re: Pre-insert callback?"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

I think these callbacks are defined in the JPA spec. I had started reading
it, hoping to get access to the JPA TCK, but other things happened in my
life. I'd give JSR-220 a ponder.
I don't think anyone would object to adding new callback types, but getting
rid of ones defined in the spec is obviously problematic.

-- 
Kevin
On Fri, Mar 6, 2009 at 11:13 AM, Andrey Razumovsky <
razumovsky.andre..mail.com> wrote:
> Hi,
>
> currently we have prePersist and postPersist callbacks, which are fired for
> new objects. But the problem is that 'prePersist' callback is called only
> when context.newObject() is invoked and the data object has no properties.
> So, since 'preUpdate'is only invoked at modified objects,  there's no
> callback *just before* commit. the only way for me to intercept new objects
> is in "validateForInsert", but this is certainly ugly. Or maybe I'm just
> missing something?
> I suggest that at the minimum we add a new callback ("preInsert").
>  to keep API understandable I find it reasonable to deprecate postPersist
> and rename it to postInsert.
>
> Thanks,
> Andrey
>

• Next message: Henri Yandell: "JIRA upgrade"
• Previous message: Andrey Razumovsky: "Pre-insert callback?"
• In reply to: Andrey Razumovsky: "Pre-insert callback?"
• Next in thread: Andrus Adamchik: "Re: Pre-insert callback?"
• Reply: Andrus Adamchik: "Re: Pre-insert callback?"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2.0.0 : Fri Mar 06 2009 - 15:39:23 EST