openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pinaki Poddar (JIRA)" <>
Subject [jira] Resolved: (OPENJPA-858) Allow postPersist be invoked immediately after persist()
Date Mon, 23 Feb 2009 15:03:02 GMT


Pinaki Poddar resolved OPENJPA-858.

       Resolution: Fixed
    Fix Version/s: 2.0.0

> Allow postPersist be invoked immediately after persist()
> --------------------------------------------------------
>                 Key: OPENJPA-858
>                 URL:
>             Project: OpenJPA
>          Issue Type: Improvement
>            Reporter: Pinaki Poddar
>            Assignee: Pinaki Poddar
>             Fix For: 2.0.0-M1, 2.0.0
> OpenJPA invokes postPersist call back after commit or flush. This is compliant to JPA
spec. But the spec itself is slightly ambiguous about what a 'persistent identity' is and
when it is assigned to a persistent instance. 
> But if an application wants to receive a postPersist callback immediately after persist()
-- currently there is no choice. 
> This is a proposal to allow a configuration option for such behavior. A boolean option
(added to MetaDataDefaults) that controls whether postPersist() is called back after commit/flush
(default behavior as it exists now) or immediately after persist().
> Given that the proposed configurable behavior is beyond the spec, I will welcome your

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message