You are correct: if you need to inject 13 dependencies into a class, it’s a pretty sure sign that you are violating the Single Responsibility Principle. Switching to Property Injection will not help, as it will not decrease the number of dependencies – it will only imply that those dependencies are optional instead of mandatory. … Read more
If you look at the signature you will see that it’s just a Service Locator with another name. Service Locator is an anti-pattern and I consider the relationship transitive, so I consider IDependencyResolver an anti-pattern. Apart from that, the interface is also broken because it has no Release method.
My list of reasons why you should prefer injecting services: Your class is dependent only on the services it needs, not the service container. This means the service can be used in an environment which is not using the Symfony service container. For example, you can turn your service into a library that can be … Read more
@Named gives a CDI managed bean an EL name to be used in view technologies like JSF or JSP. Note that in a CDI application you don’t need the @Named annotation to make a bean managed by CDI (thanks to @Karl for his comment). @ManagedBean makes the bean managed by JSF and you can: inject … Read more
I wanted to leverage on the solution provided by Sotirios Delimanolis but adding transparent autowiring to the mix. The idea is to turn plain servlets into autowire-aware objects. So I created a parent abstract servlet class that retrieves the Spring context, gets and autowiring-capable factory and uses that factory to autowire the servlet instances (the … Read more
When using bean-discovery-mode=”annotated” only classes with a bean defining annotation are discovered. All other classes are ignored. Any scope type is a bean defining annotation. If a scope type is declared on a bean class, then the bean class is said to have a bean defining annotation [spec]. The 1.1 spec is not completely clear … Read more
Constructor and property injection gives you the option to initialize the object even in a non CDI environment easily, e.g a unit test. In a non-CDI environment you can still simply use the object by just passing the constructor arg. OtherBean b = ….; new MyBean(b); If you just use field injection you usually must … Read more
This is not necessarily so. As long as your static logger exposes a method for: Injection of the classes you WANT injected, or Injection of the DI Container in an appropriate method call prior to running it (say in something like the asp.net global.asax Application_Start method), then you should be fine. Here’s an example. Take … Read more
Having recently spiked the use of 6 of these (Windsor, Unity, Spring.Net, Autofac, Ninject, StructureMap) I can offer a quick summary of each, our selection criteria and our final choice. Note: we did not look at PicoContainer.Net as one of our team considered the .Net port to be quite poor from the Java version. We … Read more
See here and here for a pretty thorough technical comparison of several IoC containers, although somewhat outdated by now (they’re from before Windsor 2.0) However, I don’t think there are really any vital features that Windsor offers and other containers don’t. Windsor, StructureMap, Spring.NET have all been around for several years and have been used … Read more