On point i'd like to clarify myself; so @SpringBean is explained with Services in mind, but yes there is no reason for it to represent PROTOTYPE beans. But thats the whole point, thing conversation is not about @SpringBean VS PROTITYPE. @SpringBean can be using to fetch a bean from Spring and put it into ThreadLocal. If within SPRING that is defined with PROTOTYPE scope then you get a PROTOTYPE bean.... so there is no comparison.
The difference is in the concept of injecting components vs services. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/instantiate-panels-in-a-spring-bean-tp2946859p2952224.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
