Bring Core

General DI Flow Diagram

The BringApplication provides a simple entry point to initialize and run a BringApplicationContext. It allows the user to create and configure a BringApplicationContext either by specifying a base package for component scanning or by providing a class that contains configuration information.
The ClassPathScannerFactory is responsible for creating a set of class path scanners, each designed to scan the classpath for specific types of annotated classes relevant to the Bring application. It initializes scanners for components, services, and configuration classes etc.
The BeanPostProcessorDefinitionFactory is responsible for creating and managing a list of BeanFactoryPostProcessor instances. It initializes the list with default post-processors, such as the ConfigurationClassPostProcessor etc. In this step we create Bean definitions for classes annotated with annotations from ClassPathScanner.
The next step will be to go through all bean definitions and register/create beans with dependencies.
The last one BeanPostProcessorFactory is responsible for creating and managing a list BeanPostProcessor instances. It initializes the list with default post-processors such as the ScheduleBeanPostProcessor and add addition logic to them.

Documentations

There are two types of documentation: Markdown (see below) and JavaDoc

Features:

Dependency Injection
Configuration support
- Annotation configuration @Component, @Service.
- Annotation @Autowired
- Java Configuration @Bean, @Configuration.
Annotations
- @Autowired
- @Bean
- @BeanProcessor
- @Component
- @Configuration
- @Order
- @PostConstruct
- @PreDestroy
- @Primary
- @Qualifier
- @ScheduledTask
- @Scope
- @Service
- @Value
Exceptions
additional items: