Quoting Marc Grue <[email protected]>:
Thanks Stan, I missed that discussion.
No probs :)
I checket open issues in Jira, but I don't think my issue is related
to Qi-272 or Qi-274, but I might be mistaken...
No, it (IIRC) isn't.
Isn't
Property<String> someString();
regarded as a method needing an implementation (by Qi4j though)
causing the implementing Mixin to be included in the composite? I'm
confused and could well be mixing up terms.
Yes, but the implementation for property (and association, and
manyassociation) methods is provided by Qi4j itself by default, so it
won't even look at your mixin.
Shouldn't it be possible to have an entity with only Properties and
a Lifecycle??
Now I had to make a dummyMethod() in my entity interface and a dummy
implementation in the Mixin in order for the Lifecycle to work.
Seems wrong, when there's several Properties in use already, and
some of them needs to be set upon entity creation...
Cheers,
Marc
Yeah, I ended up in doing dummyMethods at first too. To get rid of
those, you need to explicitly extend your entity composite from
Lifecycle interface in order for your Lifecycle mixin to kick in.
Like this:
@Mixins(SomeEntityMixinWithJustLC.class)
public interface SomeEntityWithJustLC
extends SomeEntity, EntityComposite, Lifecycle
{
}
where SomeEntityMixinWithJustLC implements only Lifecycle.
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
