Summary in the development process BaseService provides a public access service file for all controllers or services to reduce repeated injection

BaseService Practical significance

BaseService You can also call it ServiceUtil Wait, this is more casual , In general, this class is used to make something different Controller perhaps Service Reuse... In @Autowired perhaps @Resource The injected attributes are injected only once , Thus reducing multiple Controller perhaps Service Repeated injection in , Can reduce the amount of code , Looks Cleaner , At the same time, only oneortwo basic service class , It will also be much easier .

The first one is Abstract classes are injected uniformly , Use controller perhaps Service Inherit this class

The specific example code is as follows ：

@Service("BaseService")
public abstract class BaseService {
    
    private static final MyLog logger = new MyLog(BaseService.class);

    protected static final String IDENTITY = "identity";
    
    @Resource(name = "AService")
    protected IAService aService;
    @Resource(name = "CService")
    protected ICService cService;
    @Resource(name = "BService")
    protected IBService bService;
    @Autowired
    protected IRService rService;
    @Autowired
    protected CMappingService cMappingService;
    ........
    ........
    ........
    
//  At the same time, it can provide some common methods to provide external controller  Use , Only service injection is ok 

other Controller perhaps Service Inherit in the following way , Then repeated injection can be omitted , In order to reduce the Controller Injection in , Even directly in different Service Inherit ,controller You can use it completely .
But this way, through inheritance, classes that are not used may also be inherited , It didn't end up using . This is a good way, but there is still some suspicion of waste .

@Service("CubeService")
public class CubeService extends BaseService {
    

//  normal Service  The business process in 
........................
........................
........................
........................
........................
}

adopt Util The way of tool class Inject static service classes directly by controller perhaps Service Use

This way looks better , Pass different service classes directly static final Static declaration in class （ You need to start with applicationContext In order to get ）, When it becomes a static attribute , Other controller perhaps service Directly by class name . To get the corresponding single attribute , So that one or several services can be accurately referenced , No waste , But it may look a little longer .

The sample code is as follows ：

public class ServiceUtils {
    

    public static final IEService eService = ToolSpring.getBean(IEService.class);
    public static final IEBService ebService = ToolSpring.getBean(IEBService.class);
    public static final IAService aService = ToolSpring.getBean(IAService.class);
    public static final ICService cService = ToolSpring.getBean(ICService.class);
    public static final PFactory pFactory = ToolSpring.getBean(PFactory.class);
    .....................
    .....................
    .....................
    .....................
    .....................
}

among ToolSpring In order to achieve Spring Interface ApplicationContextAware Of a class adopt Class name or class class To get the corresponding ApplicationContext Medium Bean Get the class injected into the container )
See my other articles for details

Spring ApplicationContextAware Function and use learning summary spring bean Initialization process summary
ApplicationContext obtain Spring Medium Bean Understanding and way , Gain understanding of injection
spring frame stay Util General tool classes are loaded spring Medium Bean object

Among others controller perhaps Service Directly call

import static com.xxxxx.xxxx.xxxx.xxxx.util.ServiceUtils.eService;

eService.xxxxx Method ( Enter the reference );

or

ServiceUtils.eService.xxxxx Method ( Enter the reference );