Overview of the Spring Framework
The start time was 10:23, the end time was 10:42, and the time was 19 min.
2. History of Spring and the Spring Framework
Spring came into being in 2003 as a response to the complexity of the early J2EE specifications. While some consider Java EE and Spring to be in competition, Spring is, in fact, complementary to Java EE. The Spring programming model does not embrace the Java EE platform specification; rather, it integrates with carefully selected individual specifications from the EE umbrella:
- Servlet API (JSR 340)
- WebSocket API (JSR 356)
- Concurrency Utilities (JSR 236)
- JSON Binding API (JSR 367)
- Bean Validation (JSR 303)
- JPA (JSR 338)
- JMS (JSR 914)
- as well as JTA/JCA setups for transaction coordination, if necessary.
translation
Spring and the history of the Spring framework
Spring was born in 2003 as a response to the complexity of earlier J2EE specifications. While some see Java EE and Spring as competing, Spring is actually complementary to Java EE. The Spring programming model does not contain the Java EE platform specification, but selectively integrates some separate rules:
- Servlet API (JSR 340)
- WebSocket API (JSR 356)
- Concurrency Tools (JSR 236)
- JSON Binding API (JSR 367)
- Bean validation (JSR 303)
- JPA (JSR 338)
- JMS (JSR 914)
- JTA/JCA transaction collaboration is also included if required
vocabulary
- There is a new complexity in the relationship
- C. compete D. compete
- Complementary [ˈ kɒ MPL ɪ t]
- The validation [, v æ l ɪ ‘DE ɪ ʃ goes n]