On 6/4/10, Stanislav Muhametsin <[email protected]> wrote: > Quoting Rickard Öberg <[email protected]>: > >> So now there's a decision to be made: >> Either calls within a mixin will cause concerns to be invoked, or >> not. If not, then to force them to be invoked you have to do a @This >> injection and then call that instead, to ensure that the call goes >> through the proxy. >> >> What makes the most sense? I guess we have to also remember that >> code like this will not work if methods are not routed through the >> composite within the mixin: > > In my app, I'm also invoking all my calls to "myself" through > @This-injected fields. IIRC there was some tutorial or something on > the qi4j.org site, which urged to this kind of behaviour, saying > specifically that if i just to "this.foo(...)" it might not execute > mixins. Guess someone was a psychic. :)
That is because originally (2007) we didn't have any Magic. IIRC, first came the abstract fragment which got subclassed and much later the in-mixin method call interception. So it is a matter of out-dated docs. Cheers > > > _______________________________________________ > qi4j-dev mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/qi4j-dev > -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
