Create relations between portal-types model-driven. Support for Relations Product (complex references). Define sets of rules for validation, creation and lifetime of Archetypes references. ArchGenXML can generate the necessary code and XML-configuration data to use this product.
As an option on command line, up to a tagged-value on
model-level or on a single UML-Association you just define
and set it to
relations. A directed Association results in one Relation.
Give the association and its assoziation ends
They'll be used as the names for the RelationField. If you
don't want a field turn it off by setting a tagged value
on class (or package, model) level to
If the association is not directed (navigable on both association ends) an inverse relation will be created.
will be used for the back-relation on undirected
associations. It defaults to a relation named
toend_fromend, where these are the lowercased versions of the
association ends. If the two ends are named the same, then
the relation will be named
is the name of the association. (Finally, if the option
is set, then it defaults to the association name postfixed
You can use the Multiplicity on in UML to define the
cardinality of an Relation. You can use the minimum and
maximum value here using the syntax
which means at least one relation related objects but not
more than five.
- as described above an association between two portal-types will be created.
- an association between an archetypes class and an interface will create an interface-constraint. the relation is allowed to all classes implementing this interface.