Yeah that error msg would suggest that 1-1 relationship is fine.
I can't try it myself right now as hitting some other issues but I looked
thru the DDDSample dsl and interestingly found this:
Entity Cargo {
- @TrackingId trackingId key
- @Location origin required fetch="join"
- @Location destination required fetch="join"
- @Itinerary itinerary nullable fetch="join" cascade="all"
inverse opposite cargo
- Set<@HandlingEvent> events cascade="none" opposite cargo
which looks like it maybe it works if the 1-1 is bi-directional?
--
View this message in context:
http://old.nabble.com/DDL-generation-error-on-1.6--tp26347787s17564p26367229.html
Sent from the Fornax-Platform mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Fornax-developer mailing list
Fornax-developer@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fornax-developer
