Hi,
Reading about the HelloWorld example (Step 1 - Interface Refactoring) I
noticed that there are 4 artifacts related to 1 concept. So I was wondering,
in a system with 100 concepts you'll end up with 400 artifacts?! Why is
there a need for an interface that specifies behavior, than another one that
specifies state and finally a third one that only joins the 2 others?
Shouldn't one interface with behavior and state be sufficient? And also, the
framework gives support for specifying standalone properties (i.e. Name
extends Property<String>). What are the advantages of this fine-grained
break down?
BTW, does qi4j supports some sort of abstract mixins (or even purely
dynamic ones) so there is no need to implement dummy getter/setter method
implementions?
Regards,
Thiago Souza
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
