[hibernate-issues] [Hibernate-JIRA] Resolved: (HHH-3633) Envers ignores empty discriminator classes

[Adam Warski (JIRA)]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adam Warski resolved HHH-3633.
------------------------------

         Assignee: Adam Warski
       Resolution: Fixed
    Fix Version/s: 3.4

The problem was the checking if a class is audited: it simply checked if there are any audited properties.
This in fact was changed recently, so it may have worked before. But now everything should be ok.

> Envers ignores empty discriminator classes
> ------------------------------------------
>
>                 Key: HHH-3633
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3633
>             Project: Hibernate Core
>          Issue Type: Bug
>          Components: envers
>    Affects Versions: 3.4
>            Reporter: Mark Derricutt
>            Assignee: Adam Warski
>             Fix For: 3.4
>
>
> 'lo
> I'm just working through updating our system to Hibernate 3.3 and the new maven based envers from trunk and am noticing that empty discriminator classes such as:
> @Entity
> @DiscriminatorValue("11004")
> @Versioned
> public class CountryGeo extends Geo {
> }
> are getting ignored by envers.  This is manifested as the error "An audited relation to a non-audited entity" thrown from ToOneRelationMetadataGenerator.

-- 
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