Description
When injecting bean property with overloaded setter method the framework returns an exception:
org.osgi.service.blueprint.container.ComponentDefinitionException: Unable to find property descriptor <bean-property-setter> on class <bean-class>
Apparently, behaviour for this case was relaxed in Enterprise OSGI 4.2 spec (see section 121.5.7):
"There should only be one set method with a single argument for a specific property. If overloaded properties are
encountered, the chosen set method is unspecified."
Taking into account origin of the Blueprint service and possible migration paths for future users I believe the best case would be to follow Spring 3.x behaviour regarding the case above (just to minimize surprises).
ps:
For user-forum discussion see:
http://mail-archives.apache.org/mod_mbox/incubator-aries-user/201007.mbox/%3C4c446974045723.96045080@wp.pl%3E