You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Pinaki Poddar (JIRA)" <ji...@apache.org> on 2009/01/12 22:54:02 UTC
[jira] Created: (OPENJPA-858) Allow postPersist be invoked
immediately after persist()
Allow postPersist be invoked immediately after persist()
--------------------------------------------------------
Key: OPENJPA-858
URL: https://issues.apache.org/jira/browse/OPENJPA-858
Project: OpenJPA
Issue Type: Improvement
Reporter: Pinaki Poddar
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 comments/views.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (OPENJPA-858) Allow postPersist be invoked
immediately after persist()
Posted by "Pinaki Poddar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pinaki Poddar resolved OPENJPA-858.
-----------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0
2.0.0-M1
> Allow postPersist be invoked immediately after persist()
> --------------------------------------------------------
>
> Key: OPENJPA-858
> URL: https://issues.apache.org/jira/browse/OPENJPA-858
> 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 comments/views.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (OPENJPA-858) Allow postPersist be invoked
immediately after persist()
Posted by "Pinaki Poddar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pinaki Poddar reassigned OPENJPA-858:
-------------------------------------
Assignee: Pinaki Poddar
> Allow postPersist be invoked immediately after persist()
> --------------------------------------------------------
>
> Key: OPENJPA-858
> URL: https://issues.apache.org/jira/browse/OPENJPA-858
> 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 comments/views.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.