On 2010-06-24 21.25, Marc Grue wrote:

Given ambiguity of a property name in extended interfaces, should the
EntityBuilder methods instance() and instanceFor() behave like demonstrated
in the test below? Or are properties simply required not to be ambiguous?

From a Java point of view the names can be ambiguous, since they are defined in different interfaces and you can use instanceFor(<type>) to specify which one you want. However, the current storages don't store the interface names, and so you would get a clash anyway. I would suggest not using ambiguous names, in general.

/Rickard

_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev

Reply via email to