Rickard,
I probably don't get the concept of AssociationRole (yet?)... Looking
at your JIRA post;
interface Employer
{
ManyAssociation<AssociationRole<Employee,Position>> employees();
}
1. Why is the Position a good example? Why doesn't it belong inside
the Employee, and the Employee references the Person? For instance, a
Position often comes with Rights and Responsibilities, and wouldn't
that be exploded into a complex problem of references to Entities in
AssocitationRoles, query on fields in AssociationRole "type"??
2. If the interface is instead;
interface Employer
{
SetAssociation<AssociationRole<Employee,Position>> employees();
}
Does that mean that there could be an arbitrarily number of of
AssociationRoles to the same Employee? Otherwise, it doesn't make
sense at all.
Basically, I don't grok the metaphor/pattern here...
We had the discussion in KL a few months ago, about the pro/con of
subtyped Associations. IIRC, we basically said that "in principle a
good idea" but that "EntityStores will have problems". Could you
elaborate on the differences between the AR vs subtypes, from these
two overall pro vs con of subtypes?
Cheers
Niclas
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
