Whatever happened to this? I'm still getting ambiguous type
exceptions, when I'm invoking newObjectBuilder(Class) -method of
ObjectBuilderFactory. And I have registered both super- and subtypes
to module assembly.
Original mail from 18th Feb.
Quoting Rickard Öberg <[email protected]>:
Hi guys,
We have had quite a bit of trouble with the Object resolution rules,
which have been that if two classes (superclass and subclass) are
registered, then a lookup of the superclass yields ambiguous type
exceptions. This doesn't really make sense, if you do a lookup on
the actual type, and that is registered, so I've changed it to the
following:
Setup:
SuperClass
SubClass1 extends SuperClass
SubClass2 extends SuperClass
Lookups:
newObject(SuperClass.class) -> ok
newObject(SubClass1.class) -> ok
newObject(SubClass2.class) -> ok
If SuperClass is *not* registered, then:
newObject(SuperClass.class) -> AmbiguousTypeException (both
SubClass1 and SubClass2 are possible)
This seems to make more sense to me. Pushed to develop branch.
/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
