Link Details

Link 19615 thumbnail
User 226267 avatar

By arsenalist
via arsenalist.com
Published: Apr 21 2007 / 19:01

I like Guice, it’s a nice little tool that gets you all excited by doing Dependency Injection using annotations. That’s where it ends though, it really does. Once you’re past the high of using @Inject in a couple of your classes and on to doing something a little more complex, you realize that you’re a little stuck. And by stuck I don’t mean “totally f***ed” I just mean, you’re going to have to jump through some hoops to get it working..
  • 16
  • 4
  • 875
  • 277

Comments

Add your comment
User 191976 avatar

Ganeshji Marwaha replied ago:

0 votes Vote down Vote up Reply

Wow… This is something that i was thinking of writing for quite sometime now, but have been waiting until the initial guice buzz ends…

I am not against guice, or for spring. In fact, i was one of the people to pounce on this new and shiny DI framework once it came out. Initially, when i had to workaround certain concepts to get things done, i was fine with that, because of the clean DSL guice offers. But going forward, those became pain points, and i had to see guice for what it is… It still is the fastest and the cleanest of all, yet not something that i will ditch spring for.

User 186344 avatar

kunnar replied ago:

0 votes Vote down Vote up Reply

I do not understand why he wants to configure beans in XML. Bean configuration is programming and i like to do it in real programming language not in XML. Is any admin going to change bean configuration? I do not think so. If nobody else than programmers are going to change configuration, then there is not much point to keep it in XML.

Add your comment


Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.