On 2009-11-19 18.01, Pawel Niemiec wrote:
I did so and... it doesn't work, I got the following exception
Exception in thread "main"
org.qi4j.api.composite.AmbiguousTypeException: More than one visible
CompositeType implements mixintype actorsintheatre.Actor:[interface
actorsintheatre.ActorComposite, interface
actorsintheatre.ActorVanessaComposite]
I've done it with transient composites, does it matter ? I could
maybe send you the whole example code so that you had whole look at
it.
I'm guessing you are doing the instantiation using the "Actor"
interface, which would (correctly) give this exception. When you
instantiate you need to know what you are looking for (i.e.
ActorComposite vs ActorVanessaComposite). Another way to do it is to use
modularization, so that the composites are in different modules, which
would make the lookup of composite type given "Actor" non-ambiguous.
When I look in the online documentation there is only "Content goes
here..." text under Entity Composite link. Could you maybe look at
that by the way ?
Yes, that needs to be fixed, definitely.
/Rickard
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
