Aye wrote:
Thanks Niclas. I woke up this morning and took a look at my Mixin
again. This line was my culprit:
humanResource.positions().add(positions().count(), position);
Instead of using the injected (@This HumanResource humanResource)
interface in both places, I was calling the positions() directly in
the mixin. Agh, my late night mind wasn't working. Thanks again!
Yeah, I've been thinking about this one. Essentially we *could* generate
the abstract methods so that they are implemented to do the same thing
as calling "@This HumanResource humanResource", as a convenience. The
risk is that if we do so people will start having their abstract mixins
extend the interfaces they want to access as a way to avoid using @This,
which will be bad practice. Hm...
/Rickard
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
