title: Spring Method Injection
body: <p>Reading the Spring 3 documentation I came to across Method Injection which I though might solve an issue I was having creating Prototype beans from my Singleton factory however I'm surprised by the documentation stating this:</p>
  
  <p>"In most application scenarios, most beans in the container are singletons."</p>
  
  <p>In my opinion this statement is misleading as I quite often find that I will need to create new instances at run time (which also benefit from dependency injection) but I find the Method Injection pattern a bit clumsy. An example of this would be where my application polled the database for new records created by the user through a front end and then created a new instance to service this record.</p>
  
  <p>Can anybody shed some light on what this statement might mean and if it is true for most developers? I'd appreciate an answer which would include examples to help me understand and hopefully correct what I'm doing wrong (assuming this statement is true)</p>