Strange dependency injection goings on

[james frain]

Looking at this example in more detail and trying tofigure out how this works.
see http://static.springsource.org/docs/Spring-MVC-step-by-step/part5.html

My question is ... in the class JdbcProductDaoTests, how is the method

    public void setProductDao(ProductDao productDao) {
        this.productDao = productDao;
    }

actually called?
I can see in the test-context that the bean definition is declared as <bean id="productDao" class="springapp.repository.JdbcProductDao"> <property name="dataSource" ref="dataSource" /> </bean>

However, here's the puzzler, if I rename the method to setProductDaoXXX it still works, but if I call it xxsetProductDao it can't resolve which method to call when building the context.

[Jeanne Boyarsky]

James,
By convention, setters begin with setXXX. When you renamed the method to xxsetProductDao(), it becomes just a random method and not a setter. This makes sense. Spring shouldn't have to look at every single method for dependency injection. Only the constructors and setters.