Framework introduction
◆Powerful JavaBeans-based configuration management using the Inversion of Control (IoC) principle makes the establishment of applications faster and easier.
◆A core Bean factory that can be used in different runtime environments from applets to Java EE.
◆A general abstraction layer for database transactions, allowing plug-in transaction managers to simplify the division of transactions and make them independent of the underlying layer.
◆The built-in generalization strategy for JTA and a single JDBC data source makes Spring's transaction support not require a Java EE environment, which is contrary to the general JTA or EJB CMT.
◆The JDBC abstraction layer provides targeted exception levels (no more extracting original code from SQL exceptions), simplifies error handling, and greatly reduces the amount of coding for programmers. When using JDBC again, you do not need to write another "Termination" module. And JDBC-oriented exceptions are consistent with the Spring Universal Data Access Object (Data Access Object) exception level.
◆Integrate with Hibernate, JDO and iBATIS SQL Maps in the form of resource containers, DAO implementations and transaction strategies. Comprehensive support with numerous rollover control convenience features solves many typical Hibernate integration issues. All of this complies with the Spring Universal Transaction Processing and Universal Data Access Object Exception Level specifications.
◆Flexible MVC web application framework based on core Spring functionality. Developers will have a high degree of control over the framework through the strategy interface, so the framework will adapt to multiple rendering technologies such as JSP, FreeMarker, Velocity, Tiles, iText and POI. It is worth noting that the Spring middle layer can be easily combined with any web layer based on MVC framework, such as Struts, WebWork, or Tapestry.
◆An aspect-oriented programming framework that provides services such as transaction management.
Details
it works
it works
it works