Quoting Dag Blakstad <[email protected]>:
Our team is now trying a different design, with a separate entity the data
that was modeled into a Mixin. The problem has so far only occured when this
Mixin was added to an existing Entity, which has several mixins already.
Could there be a problem with size of metadata inferred by the number of
mixins and properties/relations? I will let you know if this
solution/workaround eliminates the error.
/Dag
I'm not sure about the size of metadata, but if you have
public interface A
{
public Property<String> prop();
}
and
public interface B
{
public Property<String> prop();
}
and you use both A and B in same entity type, one of them will
overwrite the another. Just a little warning about the current
limitations, since you seem to have a lot of properties and relations.
:)
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
