Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Tim Cooke
  • Liutauras Vilda
  • Jeanne Boyarsky
Sheriffs:
  • Paul Clapham
  • Rob Spoor
  • Junilu Lacar
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Piet Souris
  • Carey Brown
Bartenders:

discussion: why is autowiring bad?

 
author & internet detective
Posts: 41502
881
Eclipse IDE VI Editor Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Report post to moderator
I'd like to start a discussion about this topic, but encourage discussion by all, not just Craig.

Someone was trying to explain to be me why autowiring should never be used. This blog post was used as an example along with some explanation. I can find evidence online to support both sides.

So far, I've been using Spring autowiring for the classes we write and explicit wiring for things like DataSources. The application is large, but organized and we don't have trouble finding things. There are package conventions that the team has agreed to which makes finding things easy. I fail to see how listing all the non-redundant wiring makes things better.

My question: why am I wrong? When I was first getting used to JUnit and learning to trust my gut, posting "why am I wrong" helped a lot. Hopefully it will here.
 
Jeanne Boyarsky
author & internet detective
Posts: 41502
881
Eclipse IDE VI Editor Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Report post to moderator
Just noticed this thread which addresses the topic well. This forum is too popular this week!
 
    Bookmark Topic Watch Topic
  • New Topic