[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4646?page=c...
]
Hernán Chanfreau commented on HHH-4646:
---------------------------------------
I think it's still an issue but I have a problem with new maven repositories and
can't test against last build or 3.5 branch. Appying the patch with the test case will
reproduce this case.
Inconsistent behavior with Audited and MappedSuperclass annotations
-------------------------------------------------------------------
Key: HHH-4646
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4646
Project: Hibernate Core
Issue Type: Bug
Components: envers
Affects Versions: 3.3.2, 3.5.0-Beta-2
Environment: 1) hibernate 3.5 build from trunk (7 nov 09)
2) hibernate-core-3.3.2ga with envers build from branch envers-hibernate3.3 (7 nov 09)
Reporter: Hernán Chanfreau
Assignee: Adam Warski
Priority: Minor
Attachments: mapperSuperclass2TestPatch.txt
Suppose B is a subclass of A.
The subclass B is @Entity and is not audited.
The superclass A is @MappedSuperclass.
The differents/inconsistent behaviors are:
- If A has @Audited at class level, envers does not generate audit info when saving an
instance of B.
- If A has @Audited at field/getter level, envers generates audit info when saving an
instance of B.
You can find the original discussion in envers forum:
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=164340
--
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