Sculptor doesn't support List collection type for many-to-many. The reason is
that we didn't find it very useful to use List for that type of association.
It should have been some kind of constraint violation that gives you an
error message.
Note that a many reference without opposite will also result in a
many-to-many association in the hibernate mapping.
If you need improvement of the List support you can add a request in jira.
one-to-many works fine...
Entity Planet {
- List<@Moon> moonList opposite planet2;
}
Entity Moon {
not aggregateRoot // belongs to Planet Aggregate
- @Planet planet2 opposite moonList;
}
/Patrik
Bjoern_G wrote:
>
> Hello,
>
> I have declared a collection in an entity as List. Now the generated Java
> class declares the attribute as List ... = new ArrayList()
>
> but in the Hibernate mapping file it is declared as <set...>
>
> Consequently, when I try to save such an object, Hibernate throws an
> Exception.
>
> Am I overlooking something, or is it a bug in Sculptor?
>
--
View this message in context:
http://www.nabble.com/Scultpor-List%3C%3E-produces-incompatible-Hibernate-%3Cset%3E--tp18694496s17564p18815278.html
Sent from the Fornax-Platform mailing list archive at Nabble.com.
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Fornax-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fornax-developer
