First note that there are no more releases of 3.x branch planned. This is why my test targets Hibernate 4.1.

Anna, please try to make test case as short as possible. I really want to help you but a) failed to download some dependencies from the public Maven repositories and compile the project; b) did not find anything extraordinary in your mapping or the way you persist entities (plenty of one-to-many mappings with join column exist in the Envers test suite). Notice that we should not need to include Spring to reproduce the issue (assuming it is not an integration problem).

Find attached test project (hhh-7531-test-case.zip), verify copied entity mappings and develop HHH7531Test#testHERE() method to show the issue clearly (assertion failure).

The strange thing is that I get different schema generation script than the one submitted by you (notice the intersection table search_param_auidit):

create table REVINFO (REV integer generated by default as identity, REVTSTMP bigint, primary key (REV))
create table customer.search_param_auidit (REV integer not null, SEARCH_ID bigint not null, id bigint not null, REVTYPE tinyint, primary key (REV, SEARCH_ID, id))
create table customer.search_param_test (id bigint generated by default as identity, NAME varchar(255), SEARCH_ID bigint, primary key (id))
create table customer.search_param_test_AUDIT (id bigint not null, REV integer not null, REVTYPE tinyint, NAME varchar(255), primary key (id, REV))
create table customer.search_test (id bigint generated by default as identity, CREATED_DATE timestamp, DESCRIPTION varchar(255), MODIFY_DATE timestamp, name varchar(255), primary key (id))
create table customer.search_test_AUDIT (id bigint not null, REV integer not null, REVTYPE tinyint, CREATED_DATE timestamp, DESCRIPTION varchar(255), MODIFY_DATE timestamp, name varchar(255), primary key (id, REV))
Change By: Lukasz Antoniak (23/Aug/12 1:24 PM)
Attachment: hhh-7531-test-case.zip
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira