Yes, sounds reasonable. At first I was baffled by the "throw an error if no constructor match" part, but then I realized it does makes sense: this will occur only if the class doesn't have a constructor we can satisfy, not even a default constructor.
What about the service ID autowiring? Drop it completly? I still think that the approach I mentioned in my previous message is valid (try to match it only if we couldn't find a matching constructor without it). -- Marcus Brito <[EMAIL PROTECTED]> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
