The following will inject every MyFilter instance that has a type that extends SpecificDataInterface as generic argument into the List. @Autowired private List<MyFilter<? extends SpecificDataInterface>> list;
I have that kind of spring setup working an abstract class with an autowired field public abstract class AbstractJobRoute extends RouteBuilder { @Autowired private GlobalSettingsService settingsService; and several children defined with @Component annotation.
If you’re using Java 8 and Spring Framework 4, you can use Optional. @Autowired public MyConfiguration(Optional<MyServiceA> myServiceA, Optional<MyServiceB> myServiceB){ myServiceA.ifPresent(service->{this.myServiceA = service}); myServiceB.ifPresent(service->{this.myServiceB = service}); }
Simple solution is to upgrade to Spring 4.0 as it will automatically consider generics as a form of @Qualifier, as below: @Autowired private Item<String> strItem; // Injects the stringItem bean @Autowired private Item<Integer> intItem; // Injects the integerItem bean Infact, you can even autowire nested generics when injecting into a list, as below: // Inject … Read more
Autowiring (link from Dunes comment) happens after the construction of an object. Therefore they will not be set until after the constructor has completed. If you need to run some initialization code, you should be able to pull the code in the constructor into a method, and annotate that method with @PostConstruct.
I’m not sure you can exclude packages explicitly with an <exclude-filter>, but I bet using a regex filter would effectively get you there: <context:component-scan base-package=”com.example”> <context:exclude-filter type=”regex” expression=”com\.example\.ignore\..*”/> </context:component-scan> To make it annotation-based, you’d annotate each class you wanted excluded for integration tests with something like @com.example.annotation.ExcludedFromITests. Then the component-scan would look like: <context:component-scan base-package=”com.example”> … Read more
I think you could use Spring’s @Lazy annotation on one of the autowired fields to break circular dependency. I’m not sure if this works/exists in mentioned Spring version.
We can’t autowire static fields in spring because the Spring context might not be loaded when the java class loader loads the static values. In that case the class loader won’t properly inject the static fields in the bean and will fail.
You should autowire interface AbstractManager instead of class MailManager. If you have different implemetations of AbstractManager you can write @Component(“mailService”) and then @Autowired @Qualifier(“mailService”) combination to autowire specific class. This is due to the fact that Spring creates and uses proxy objects based on the interfaces.
Starting with Spring 4.3, if a class, which is configured as a Spring bean, has only one constructor, the @Autowired annotation can be omitted and Spring will use that constructor and inject all necessary dependencies. Regarding the default constructor: You either need the default constructor, a constructor with the @Autowired annotation when you have multiple … Read more