[hibernate-issues] [Hibernate-JIRA] Created: (HHH-4646) Inconsistent behavior with Audited and MappedSuperclass annotations

Hernán Chanfreau (JIRA) noreply at atlassian.com
Mon Dec 7 08:36:08 EST 2009


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.5.0-Beta-2, 3.3.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
            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.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       



More information about the hibernate-issues mailing list