On 2010-10-26 19.35, Stanislav Muhametsin wrote:
I'm not having duplicate names myself, currently. Someone else might do, in future project, or when someone extends his/hers project. Or maybe I will have them in future. Since the big thing in this whole composite-oriented programming, regarding this issue, is that instead of saying this.something() you say someRole.something(), it would be awkward that suddenly, you can NOT say someRole.something() if you have someRole2.something(). Especially since roles are not aware of ALL other roles of the composite they belong to (which is another strength of COP and Qi4j).
That's a lot of "what-if's". I would say then that for now we could do a warning if names clash, and IF a legitimate usecase for clashing names comes up, we can look at a more complex solution. Remember that this does not only affect EntityStore, but also the migration API (in fact it was because the migration API had changed that I noticed your changes in the first place).
/Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
