Spring custom autowiring

Question

I have a project where I use heavily autowiring, e.g.

@Component("componentA")
public class ComponentAImpl implements ComponentA

@Component("componentB")
public class ComponentBImpl implements ComponentB {
   @Autowired
   private ComponentA componentA;
}

But I want customer to extend all the classes, so ideally they would just add a single jar into the classpath the the extended class should be used instead of the original one. What I think would be great if they could just set a different name for the bean, e.g.

@component("componentA-custom)

I just need some way to customize the autowire process to look for a bean with "-custom" at the end and load it instead of the original bean. Is there any way to do that?

Any help appreciated. Thank you, Mariusz

How? I don't want to modify my code or any reference. I just want the @Autowire annotation to look for any custom implementation first and then use the original one if custom is not found. — Mariusz Pala, Apr 25 '14 at 10:34

score 1 · Accepted Answer · answered Jul 03 '14 at 13:44

1

I found a solution, there is

@Primary

annotation that can be used to specify that the custom code added should be loaded instead of the original code.

answered Jul 03 '14 at 13:44

Mariusz Pala

961
1
8
17

score 0 · Answer 2 · edited May 23 '17 at 10:32

0

What you are looking for is something similiar to this.
This should help you solve your problem. If you need to get the bean name, you can inject in an instance of applicationContext which will get you the correct bean name (through a reverse lookup). or force all beans (ComponentA and CustomImplementation) to implement BeanNameAware

edited May 23 '17 at 10:32

Community

1
1

answered Apr 24 '14 at 10:26

AdityaKeyal

1,208
8
14

score 0 · Answer 3 · answered Apr 24 '14 at 10:34

0

What You are asking about can be done via @Qualifier annotation, but it cannot generate bean names dynamically.

To allow external beans, You will need to create XML configuration for this, as it overrides annotation - based configuration. Your customers would have to provide:

New beans
XML configuration for your application that uses the new beans.

answered Apr 24 '14 at 10:34

endriu_l

1,649
16
20

I have my class annotated with `@Component("componentA")` and I want to let customers to create a custom implementation annotated with `@Component("componentA-custom")` that should be picked up during the auto-wiring process. So basically I need to customize the way the class is found by name to look first by a different name and if not found - use the default mechanism. – Mariusz Pala Apr 25 '14 at 10:49

Spring custom autowiring

3 Answers3