Philipp Meier wrote: > Uhm, it's not about list of integers, but about something like > ManyAssociation<Qualifier<Integer, OtherEntity>>, so I'm not sure if you > got me right (or I got you wrong).
I think Niclas might have misunderstood you. Nevertheless... > Perhaps my attempt to model is the domain is wrong, so forget about > Integer qualifiers and think String qualifiert: a Person shall be > associated with many (0..*) "Contacts" (think postal address, e-mail > address, phone number) and each association shall be qualified by a > String value (think "home" address, "office" e-mail address. I thought > of modeling this a ManyAssociation<Qualifier<String,Contat>> but the > Qualifier type parameter must be an entity, too. It's possible to model > this as Person-->QualifiedContact-->Contact, with Person having a > ManyAssociation<QualifiedContact> and QualifiedContact having > Property<String> qualifier and Association<Contact> but this looks a > little synthetic, doesn't it? In this case I would proabably actually model this with the type of contact being an entity. You can then, for example, find the contacts in the database which have the "Home" Entity Qualifier. Especially if you add an internationalized touch to it, so that the name is "Home" (English) or "Hemma" (Swedish), it definitely makes more sense to have it be an Entity. /Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
