Michael Hunger wrote: > Where would you store the per instance metadata? In the entitystore? > In an associated MetaData entity thats referencing the entity or the > association? > MetaData per Entity instance would be cool as this would allow per isntance > configuration or helping resolving data > dependend security concerns.
If this is desired then, again, I think the best way to add it is to have a Mixin for general Metadata. We had that in SiteVision, and it was definitely very useful, but we added it explicitly where we wanted it by adding a "Metadata" interface+mixin to the class. > One question about the metadata is if it is persistent (see above) or just > transient information (like adding > intermediary information to an order during the order process which is > discarded after the process is complete). If it is done through a Mixin, this is an implementation detail of that mixin. > Regarding Qualifiers: > > I'd also go for qualifier as (Association)Role is misleading if you call the > additional data also roles. > Then the container containing the role and the role itself have the same name. > > May there be a mental mixup with QualifiedIdentities for the users? QualifiedIdentity is an SPI-level concept so it should be fine. > Under the hood its not the same as a map association as (imho) you don't have > just a > Map<Role,Entity> but rather a Collection<Qualifier<Role,Entity>> perhaps even > a Set. > So the same role can appear multiple times but then has to be associated with > different entities? > Correct me if I'm not right. That is true, the semantics is indeed different as the same qualifier can appear many times. /Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
