[mdr-users] Re: ordering both ends of a many-to-many association
"John V. Sichi" <[email protected]> Mon, 14 Nov 2005 14:23:02 -0800
| Newsgroups | gmane.comp.java.netbeans.modules.mdr.user |
|---|---|
| Message-ID | <[email protected]> |
Martin, thanks for the quick response. I logged an enhancement request for the MOF rule to be enforced somewhere by MDR; this might save someone unwise in MOF lore from shooting themselves in the foot in the future. JVS > -------- Forwarded Message -------- > > From: [email protected] > > To: [email protected] > > Subject: [Issue 68696] New - MOF validation should prevent orderings > > on both ends of association > > Date: 14 Nov 2005 22:06:27 -0000 > > > > http://www.netbeans.org/issues/show_bug.cgi?id=68696 > > Issue #:|68696 > > Summary:|MOF validation should prevent orderings on both ends > > |of association > > product:| > > Component:|mdr > > Version:|current > > Platform:|All > > URL:| > > OS/Version:|All > > Status:|NEW > > Status whiteboard:| > > Keywords:| > > Resolution:| > > Issue type:|ENHANCEMENT > > Priority:|P3 > > Subcomponent:|code > > Assigned to:|issues@mdr > > Reported by:|jsichi > > > > > > > > > > > > > > ------- Additional comments from [email protected] Mon Nov 14 22:06:26 +0000 2005 ------- > > The discussion below from the mdr-users mailing list describes the issue. Since > > MOF does not allow this construct, it would be nice if some part of MDR would > > run validation and reject models violating this MOF rule. > > > > Note: solution to the MOF limitation is to use an intersection class instead of > > a many-to-many association. > > > > ---- > > > > Date: Mon, 14 Nov 2005 19:02:17 +0100 > > From: Martin Matula <[email protected]> > > Content-type: text/plain; charset=ISO-8859-1; format=flowed > > Subject: [mdr-users] ordering both ends of a many-to-many association > > > > > > Hi John, > > > > John V. Sichi wrote: > > > Is this supposed to work? I have a many-to-many association named > > > ExecStreamDataFlow. The two ends are called Input and Consumer, and > > > both reference the same class ExecStream. This association is used to > > > represent the edges of a directed graph of dataflow stream vertices. > > > > No, setting both ends as ordered is illegal in MOF according to MOF > > constraints. > > Regards, > > Martin >