Hi,
I am responsible for the Eclipse EMF Teneo project, I run Hibernate with a testsuite of 500+ testcases. I am upgrading to Hibernate 4.2.7SP1. I noticed that for some of my testcases I get the exception below.

This seems to happen when I have a many-to-many mapping with unique="true", with unique="false" it does not happen. (see mapping below in the post)
The many-to-many with unique=true approach is outlined here in the docs:
http://docs.jboss.org/hibernate/orm/4.2/manual/en-US/html_single/#assoc-unidirectional-join-12m

When looking at the stacktrace I get to this call in the Cascade class line 429:
cascadeProperty(
parent,
iter.next(),
elemType,
style,
null,
anything,
isCascadeDeleteEnabled
);
As you can see a null is passed for the propertyName parameter. This seems to result in the exception below.

Not sure if this is a known issue or if I should change my mapping (mapping shown below).

Hi mtaal,

I am getting the same error starting in Hibernate 4.2.7.

Did you ever find a work-around or create a JIRA issue?

Thanks,

Darren Evenson

Hi Darren,
No reply and did not create a JIRA issue. I do not know the standard behavior/approach for hibernate, normally what I am used to is that a JIRA is created after acknowledgement of an issue on a forum.

I moved back to an older version of Hibernate (4.1 something).

gr. Martin

Hi,

I created a test case based on my mapping (which uses a Map, not an indexed list, but the same error results) and created a JIRA issue:

https://hibernate.atlassian.net/browse/HHH-8749

I also linked to this forum thread and added your mapping in comment.

Ok great!

gr. Martin

Hi gr. Martin,

Good News. Bret at Hibernate has already made a fix for this issue. You can test the latest snapshot of 4.2.8 to make sure the fix works in your case. It worked for my case.

- Darren