• CollectionConstraint could be used in InstantiatingComponentAdapter.createDefaultParameters when a Collection or array type is detected
• Could envision a NanoGroovyBuilder constraint syntax using and(), or(), not(), key(), type(), etc.

Before we apply this contribution I need to know:

1) Is this a workaround for a use case that cannot be achieved with the current support for arrays?

2) If this attempts to solve something that cannot be solved with arrays, what is your case?

3) Would you accept an implementation that leverages generics (and jdk 1.5?)

2. I can't think of anything at the moment that this would solve that couldn't be done with arrays, other than further specification/narrowing of what you want in your collection/array in a container that might have many components of the same type and you wish to configure a component that doesn't receive all of them. No concrete example right now.

3. A generics implementation will be nice but doesn't add much on top of what's achievable with arrays today. I also probably won't see JDK1.5 for a while in my work-related projects anyway due to appserver vendors typically taking awhile to formally support it (my IT dept. won't move to a new JDK until it's supported by the appserver vendor).