Hello,
today's question is - should a revision be generated, when the content an entity's collection changes?
For example, we have an entity A, which has a field: List< B> children.
The entity B has a field: A parent.
We persist an entity B with some parent value; an "add" revision for B is of course generated. Should a revision for A be generated (value of one of the java-bean field changes, but no values of fields in the database change)?
Currently, it's not generated, but I think that should be (http://jira.jboss.org/jira/browse/ENVERS-7). However, in case of big collections, it may generate a lot of revisions.
So I'm leaning towards making this configurable. What do you think?
--
Adam
