Project migrated to: http://git.oschina.net/chunanyong/springrain
demo: http://springrain.9iu.org
Documentation http://git.oschina.net/chunanyong/springrain/raw/master/springrain/doc/springrain.pdf
Springrain itself is a complete eclipse project, an example of one-stop spring development, including spring core, spring jdbc, spring mvc. It can be considered as a spring demo.
In ssh I think spring is the only framework worth using
The advantages of spring mvc can be searched on the Internet by yourself, especially after 3.0...
Spring's good scalability, integration, IOC, AOP transactions are already the basic conditions of the project
Hibernate is too complicated, and if it is not used properly, it will have a great impact. The advantage of ibatis is to write SQL into xml files, which is beneficial for database tuning and SQL statement management. Database tuning can use druid to directly output slower SQL, which is better than analysis. The statements in xml are more intuitive. Regarding sql management, all sql statements in springrain are encapsulated by Finder. As long as you check the references of Finder in the project, you can view all the sql statements in the project. In this regard, the advantage of ibatis is very small.
Compared with struts and spring mvc, my personal feeling is still a bit different.
Both controller service dao Entity use annotations. In terms of simplicity, a database only needs one Dao and one Service.
All queries are encapsulated by the Finder tool class. You can write SQL statements anywhere. I only need to check how many places refer to Finder, and I can find the SQL statements of the entire project. It is convenient for future management.
It is recommended to use only one Dao for a database, and the business logic can encapsulate the service, such as userService
The whole project only uses spring, no struts, no hibernate