On Mon, Mar 16, 2009 at 12:27 PM, Rickard Öberg <[email protected]> wrote:
> Does this seem like an ok fix? I have already tried implementing it, and > that worked well, so I know that it is doable. Is there any problem with it? I think @UseDefault should kick in here... And we could say that @UseDefault for @Uses will be a new instance of the class/composite if it can be instantiated either through CompositeBuilderFactory.newComposite() or for objects with a callable constructor (i.e. Dep Injects allowed). But without @UseDefaults, it should fail as previously. WDYT? Cheers Niclas -- http://www.qi4j.org - New Energy for Java _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
