]
Emmanuel Bernard commented on HHH-5052:
---------------------------------------
I am not super comfortable with exposing EventListenerConfigurator as a public API.
It does several things:
- add the JPA style callbacks
- change the semantics of flush and persist to accommodate JPA
- add JACC support
I imagine the users only want JPA style callbacks and hence are using annotations
already.
If that's the case, we need to prototype a way to push it back the callback listener
configuration to annotations (instead of entitymanager).
EventListenerConfigurator uses Ejb3Configuration but could use
AnnotationConfiguration instead
----------------------------------------------------------------------------------------------
Key: HHH-5052
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5052
Project: Hibernate Core
Issue Type: Improvement
Components: annotations, entity-manager
Affects Versions: 3.2.6, 3.2.7, 3.3.0.CR1, 3.3.0.CR2, 3.3.0.GA, 3.3.0.SP1, 3.3.1,
3.3.2, 3.5.0.Beta-1, 3.5.0-Beta-2, 3.5.0-Beta-3, 3.5.0-Beta-4, 3.5.0-CR-1, 3.5.0-CR-2
Environment: Tested with Hibernate 3.2.6ga, Annotations 3.2.1ga, EntityManager
3.3.2ga but seems to affect the code in the trunk.
Reporter: Alexandre Walter Pretyman
Assignee: Emmanuel Bernard
Priority: Trivial
Fix For: 3.5.1
The class EventListenerConfigurator uses Ejb3Configuration on it's constructor, but
it could use AnnotationConfiguration directly, as the methods called on the
Ejb3Configuration instance by the EventListenerConfigurator, are actually delegations to
the AnnotationConfiguration .
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: