Tonny Kohar wrote: > Hi, > > On Tue, Mar 3, 2009 at 10:31 PM, Rickard Öberg <[email protected]> wrote: > >> One thing that really sucks is that service dependency injection binding >> *should* be done once in the model, and then just "executed" at runtime. >> This will be faster, and will also help the visualizer, since it could >> then trivially show all service references that have been bound to a >> particular @Service injection. > > Is it for @Service only, how about @Uses ?
The problem here is that the provided services can be determined statically, whereas objects provided for @Uses are entirely done at runtime, so there's no way to know what the @Uses injections will be bound to, if anything at all. The only useful thing we can do is to list for each composite what @Uses are there, so that clients can know what they need to provide for it at instantiation. /Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
