Hello, I noticed that with my current Andromda version (a RC1-snapshot from March) the foreign key in the many-to-one relationship is always not-null="false", even if I specify the multiplicity of the association end as "1".
This used to work some time ago (I noticed because one of my unit tests fails).
I couldn't find anything related to this in Jira or the changelog. I don't want to simply try out the latest RC2 build because I'm afraid of potantial XMI-problems and the kind. I only want to to this if it solves the problem.
Is this issue known (and maybe already fixed)?
Thanks Chris
in March there have been some changes related to this feature, mainly due to the Entity inheritance support that was finalized around that time
the non-null="false" you're encountering is because we used to have that for *all* foreign key columns, regardless of multiplicity; of course this was a bug in the Hibernate cartridge, and it was fixed shortly after it had been detected
if you would move to the latest RC2-SNAPSHOT you will only have to pay attention to the bpm4struts stuff, I don't think the Spring/Hibernate cartridges have anything that would break an existing project (except perhaps that <<PrimaryKey>> has been renamed to <<Identifier>>
-- Wouter
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Andromda-user mailing list Andromda-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/andromda-user
