(The term iBATIS comes from the combination of "internet" and "abatis". It is an open source project recommended by Clinton Begin in 2001. Initially focused on the development of cryptographic software, it is now a durability layer structure based on Java. The durability layer structure provided by iBATIS includes SQLMaps and DataAccessObjects (DAO), and also provides a JPetStore instance developed using this structure. Compared with Hibernate, Apache OJB and other "one-stop" ORM solutions, ibatis is a "semi-automatic" ORM termination. The so-called "semi-automatic" may be a bit awkward in understanding. Looking at the current mainstream ORM, both Hibernate and Apache OJB provide a relatively complete encapsulation of the database structure and a full set of mapping mechanisms from POJO to database tables. Programmers often only need to define the mapping relationship between POJO and database table, and then they can terminate the durability layer operation through the methods provided by Hibernate or OJB. Programmers do not even need to be proficient in SQL. Hibernate/OJB will automatically generate the corresponding SQL and call the JDBC interface to perform according to the proposed storage logic. Using the ORM mechanism provided by ibatis, business logic terminators face simple Java goals. This layer is basically the same as terminating ORM through Hibernate. For detailed data operations, Hibernate will automatically generate SQL sentences, while ibatis requires developers to write detailed SQL sentences. Compared with Hibernate and other "fully automatic" ORM mechanisms, ibatis provides greater freedom for system design with the concession of SQL development workload and database portability. As a beneficial supplement to the "fully automatic" ORM termination, the presentation of ibatis is meaningful.
Ibatis Development Guide.pdf)
收藏
