Encapsulating the qualification in concrete Entities of the ManyAssoc makes
more sense for me. It also is a better
design to have concrete types representing this qualified association.
The other way would be like cascading maps (which I don't like at all).
http://www.jexp.de/demotivators/cascading_collections.jpg
Michael
Am 03.04.2009 8:07 Uhr, schrieb Rickard Öberg:
Niclas Hedhman wrote:
On Fri, Apr 3, 2009 at 1:10 PM, Rickard Öberg <[email protected]>
wrote:
interface Movie
extends EntityComposite
{
@Aggregated
ManyAssociation<Casting> cast();
}
and then separately
interface Casting
extends EntityComposite
{
Association<Actor> actor();
Association<Role> role();
}
What say ye?
I never got my head twisted around Qualifiers, so can't really balance
in the advantages of it.
If nothing else; It is easier to;
1. Explain
2. Understand
3. Implement in Qi4j Runtime
so, I think it is a win.
Ok, so both Qualifiers and events are out. That's going to drastically
simplify things :-)
/Rickard
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
