It's all about defaults. Currently Hivemind has a nice, working implementation for autowiring properties. If we add constructor autowiring, we might have some conflicts.
Anyway... yes, it sounds reasonable. It looks like your remarks are right on the point: autowiring only if there are no declared arguments, only for interfaces and trying to match as many arguments as possible. If there are multiple choices, an error should be reported: the user must specify the arguments -- this is inline with the property autowiring. About enabling/disabling autowiring, we should go the same way as property autowiring: if the user specify any constructor arguments, autowiring is disabled. This poses just one problem: what if the user *wants* to call the no-arg constructor? Maybe an <empty/> or <default/> element nested in <construct>? -- Marcus Brito <[EMAIL PROTECTED]> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
