After some of hours debugging I figured out the problem was in the composite primary Id.
It seems envers cannot handle such a case.
If I have no restrictions on design I avoid composite keys. But when you deal with legacy DBs, you find them in many places.
I will open JIRA on this point, unless I am corrected by Adam Warski.
yes, please open a JIRA :)
Has the issue been solved? Please let me know the version, if already done.
I don't think so, unforutnately.