如何将 Spring 服务注入非组件父级 Class

Question

I have a parent class that is not managed by Spring which has multiple @Component 's inherited from it:

public class Parent {

  public void commonMethod(SomeObj obj) {
    //...
  }
}

@Component
public class ChildA extends Parent {

  public MyObj doSomething(/*...*/) {
    // Some external call
    commonMethod(obj);
  }
}

@Component
public class ChildB extends Parent {

  public MyObj doSomething(/*...*/) {
    // Some external call
    commonMethod(obj);
  }
}

Now I need to call a Spring managed @Service from the Parent class. Of course, since Parent is not a Spring-managed bean, I was thinking to do something like:

@Service
public class SomeServiceImpl implements SomeService {

  public void serviceWork(MyObj obj) {
    // Some static method call
  }
}

public class Parent {

  private SomeService someService;

  public Parent(SomeService someService) { this.someService = someService; }

  public void commonMethod(MyObj obj) {
    someService.serviceWork(obj);
    //...
  }
}

@Component
public class ChildA extends Parent {

  public ChildA(@Autowired SomeService someService) { super(someService); }
  
  public MyObj doSomething(/*...*/) {
    // Some external call
    commonMethod(obj);
  }
}

@Component
public class ChildB extends Parent {

  public ChildA(@Autowired SomeService someService) { super(someService); }

  public MyObj doSomething(/*...*/) {
    // Some external call
    commonMethod(obj);
  }
}

My question is, is this thread safe? Second, is there a better design for this since now I have to @Autowired SomeService and pass it to Parent 's constructor for every child class.

Can I make the Parent class a Spring-managed class? Would that cause any issues since now it becomes a singleton class that's being shared among all the children?

Answer 1

You're confusing classes and instances of objects.

Using your schema above you would have 3 objects instantiated

1 instance of class SomeServiceImpl

1 instance of class ChildA (which happens to implement Parent)

1 instance of class ChildB (which happens to implement Parent)

This is because Spring will create these objects as they are defined as Components/Services. The 1 instance of SomeServiceImpl will be handed to both the instance of ChildA and the instance of ChildB.

Each instance of class ChildA and ChildB would have their own copy of all the data fields in their own class and all super classes. However because you've auto wired the SomeServiceImpl they are pointing at the same instance of SomeServiceImpl.

So if you goal is to call SomeServiceImpl from ChildA and ChildB and have them thread safe this won't work since they are both talking to the same instance.

The general strategy looks correct, you'd have to mark the functions on SomeServiceImpl as synchronised. Assuming it is that you want ChildA and ChildB to share the SomeServiceImpl.

Answer 2

My question is, is this thread safe

no: Spring does not guarantee thread safety. look at Are Spring objects thread safe?

is there a better design for this since now I have to @Autowired SomeService and pass it to Parent's constructor for every child class.

public class Parent implements ApplicationContextAware {
 
private static ApplicationContext context;
public Parent() { this.someService = context.getBean(someService.class); }

But if parent need some bean maybe parent must be a bean to and let the appContext use DI

Answer 3

First of all, please have your future questions more focused and do not ask 5 questions in one post.

---

How to Inject a Spring Service into a Non-Component Parent Class?

You cannot.

You cannot inject an object managed by Spring, into another object NOT managed by Spring.

Why? because, Spring has no idea what other objects in your program are, and hence, it will never have any reference(s) to them, unless they're also managed by Spring, ie they are bean s.

---

My question is, is this thread safe?

There is nothing about Thread-safety here.

---

Second, is there a better design for this since now I have to @Autowired SomeService and pass it to Parent's constructor for every child class?

There are several ways of injection: Setter, Field, and Constructor. Look it up in Google;

---

Can I make the Parent class a Spring-managed class? Would that cause any issues since now it becomes a singleton class that's being shared among all the children?

Yes, you can. You can read Bean Definition Inheritance to see how.