Unexpected audit entries

[aminmc]

Hi

I have the following object model

Class A {

@OneToMany (cascade=CascadeType.ALL)

  Set<B> setOfClassB = new HashSet<B>();

}

@Audited

Class B {

  String name;

   String value;

  @ManyToOne(cascade=CascadeType.ALL)

   @Audited(targetAuditMode = RelationTargetAuditMode.NOT_AUDITED)

   ClassA belongsTo;

}

Everything is ok. I can create an instance of classA with a set of audited classB's.  WHat is interesting is that if i update ClassA with any other data I get an entry update in the audit table for each entity classB saying an update occurred which is not correct as I only updated classA which is not audited.

I presumed that if I get something out of the set and update that entity then there would be a new audit entry for entity B. 

Am I missing some config set up?

Any help would be appreciated.

Cheers

[al0]

See http://community.jboss.org/thread/159093, it may explain your situation

[aminmc]

Hi

Thanks for your reply.  I tried the option you mentioned however i'm still getting the same issue.  The way around it was to remove the cascadeType.ALL and then changed the way i created classA which gave the correct behaviour.  It seems as though even if i don't update the collection entityB audit is updated. 

Cheers

[adamw]

Hmm that's very weird. Can you try creating a test case for this?

Adam

[aminmc]

Hi Adam

Please find attached a simple spring/hibernate envers example which demonstrates the issue.  CascadeAllEnversTest shows i'm expecting a single entry in audit for the creation of ClassB but when i update ClassA i get 2 entries for ClassB.

Cheers

[adamw]

Thanks! Can you maybe create an bug and attach the testcase there?

Adam

[aminmc]

Hi

I've created a JIRA for this issue:

http://opensource.atlassian.com/projects/hibernate/browse/HHH-6275

Thanks

[adamw]

Thanks!

Adam