Good to know.
We are evaluating envers as a possible solution for storing and retrieving historical data. In some cases LAZY loading is fine but in others we are concerned that calling .size() on a collection may give us (n+1) select issues. Have you any advice on this, any workarounds etc. Also can you point me to areas of the code that I could see if a workaround/extension would be possible and any advice on this too would be appreciated.
Well eager fetching (and joins, as it essentialy boils down to them) aren't easy with historic entities. It will be possible to implement them if you are using the ValidityAuditStrategy, but that's not done yet. As for areas in the code, well ... it would be quite a lot of code . You can look at the various query generators.