Niclas Hedhman wrote: > On Fri, Feb 20, 2009 at 9:53 AM, Rickard Öberg <[email protected]> wrote: > >> WDYT? Is it worth it? What's the usecase? > > > I think that the Context Modifiers has the need, since if they declare > a Private Mixin, there must be something that implements it, and a bit > unlikely that it is present already in the underlying Composite. > > Whether there is a need for overriding public mixins or not, I have > currently no clue.
Assembly time mixin declarations have now been implemented. Usage is: module.addComposites(MyComposite.class).withMixins(SomeMixin.class, AnotherMixin.class); This can be used to *only* declare mixins at assembly time, but I would definitely not encourage that, for readability reasons. The main use of it is as Niclas said: if a concern added with .withConcerns() needs a private mixin, then supply the implementation of it by using withMixins(). /Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
