Since blueprint doesn't call the getter I don't think it should care about the return type.
So I would tend to think this should be fine. Alasdair On 24 Aug 2010, at 03:58, Lin Sun <[email protected]> wrote: > Hi > > A while back ago, Aries-366 was committed to allow property injection > for properties with overloaded setter method. > > I have one question regarding the changes for a simple scenario with > no overloading. > > For example, in my bean I have - > > // mismatched setters/getters > public void setValue(int v) { > this.value = v; > } > > public Object getValue() { > return null; > } > > In this case, should the blueprint container throw component > definition exception when attempting to create such a bean metadata? > > I tends to think yes, and in our code, we should check the return of > the get method equals to the first parameter of the set method when > there is only one setter method exists. > > Thoughts? > > Lin
