I've finally started poking around in the code a litte. So far, everything
is very nice! I'm exciting about starting to experiment with this.
There are a lot of concepts to digest, so this may take me a while, but I
have a one question to start with about the core api.
I'm wondering if the Association stuff isn't slightly more complex than it
needs to be, or conversely if there is a reason for the current structure,
maybe it could be make more explicit in the doc (though ideally the code
should speak for itself).
There is Association, AssociationInfo, and AbstractAssociation.
Association extends AbstractAssociation and contributes get/set.
AbstractAssociation extends AssociationInfo and contributes nothing.
AssotiationInfo is self-explanatory.
I don't see the benefit in having AbstractAssociation, and I actually find
this a bit confusing. Wouldn't it be nicer to trash AbstractAssociation,
just use Association, and have a composite interface like:
public interface Association
{
AssociationInfo getInfo();
}
?
I don't see why Associtation should extend AssociationInfo, this doesn't
seem like a proper hierarchy to me.
Anyway, just a thought.
Cheers,
David
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
