Yes, but if the frameworks and tools can make you actually more productive, why not use them? The @SpringBean annotation-based approach just works. I've never had any troubles with it and I really don't have to think about it. There's a very shallow learning curve, especially if you're already using Spring. If I've got a need for something in my spring context, I create a field for it and slap that annotation on it and I'm done. I don't have to make sure I initialize some static field in my application class. I don't have to worry about serialization issues. It just works. As Ron Burgundy said, "sixty percent of the time, it works every time." :)
On Thu, Feb 19, 2009 at 6:38 AM, Christian Helmbold <christian.helmb...@yahoo.de> wrote: >> then I'd recommend using maven (or similar) :-) > > I try to use only tools I really nead. Sometimes it seems to me that in Java > programming most time is spent in frameworks and tools and not in the > programming itself. But, yes, I know the JAR hell and time for maven (or > Ivy?) has been come to me ... > > Regards, > Christian > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
