[
http://opensource.atlassian.com/projects/hibernate/browse/EJB-288?page=co...
]
Hardy Ferentschik commented on EJB-288:
---------------------------------------
For now we disable the post collection events due to the duplicate callback when replacing
the collection. The JPA spec does not specify anything regarding collection updates so it
is better to keep the status quo.
A possible solution would be to implement some sort of event queue in the entity manager
were we collect all occurring events at flush time and try to de-duplicate events. For
example if a PostCollectionRemoveEvent and a PostCollectionRecreateEvent are triggered and
they originate from the same property you would remove eg the removal event.
Execute the EJB 3.0 callback on collection change
-------------------------------------------------
Key: EJB-288
URL:
http://opensource.atlassian.com/projects/hibernate/browse/EJB-288
Project: Hibernate Entity Manager
Issue Type: Improvement
Components: EntityManager
Affects Versions: 3.3.2.GA
Reporter: Emmanuel Bernard
Assignee: Hardy Ferentschik
Fix For: 3.4.0.CR2
Today collection change does not trigger an event, but we it will, it makes sense to
trigger the ejb 3 lifecycle (minus calling it twice??).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira