深入理解MyBatis-Guice：从入门到实践

需积分: 10 37 浏览量更新于2024-07-27 收藏 85KB PDF 举报

"MyBatis-Guice3.2参考文档是MyBatis社区提供的一份教程，旨在帮助用户理解并使用MyBatis与Guice的集成，以便更有效地进行数据库操作和依赖注入。这份文档涵盖了从入门到核心组件的详细内容，包括安装、快速设置、数据源配置等。" 在MyBatis核心教程中，我们首先了解到MyBatis-Guice的动机和历史背景。MyBatis-Guice的出现是为了简化MyBatis框架与Google Guice依赖注入库的整合，提高开发效率。这个项目始于2010年，并随着MyBatis的发展不断更新，以满足开发者对灵活和高效数据库操作的需求。入门部分介绍了如何安装MyBatis-Guice以及快速设置项目。安装过程可能包括添加相关库的依赖，而快速设置则指导用户如何快速启动一个包含MyBatis-Guice的项目。这通常涉及到配置文件的编写和初始化代码的编写。 MyBatis的核心组件部分是教程的重点，详细讲解了MyBatis的启动机制和各个关键组件。MyBatis的启动包括MyBatis的属性配置、数据源提供者、事务工厂等。其中： 1. MyBatis属性配置：这是MyBatis的基础配置，用于设置MyBatis的行为，如日志级别、缓存策略等。 2. 数据源提供者：MyBatis支持多种数据源，包括非池化数据源和池化数据源，它们负责为MyBatis提供数据库连接。 3. 事务工厂：定义了MyBatis如何管理事务，包括何时开始、提交或回滚事务。 4. 别名配置：别名是为Java类创建的简短名称，方便在映射文件中引用。 5. 类型处理器：处理Java类型到JDBC类型的转换，确保数据正确存储和读取。 6. 插件拦截器：允许自定义行为，如日志记录、性能监控等。 7. 映射器配置：定义SQL映射文件的位置和加载方式。 8. 对象工厂：自定义对象创建逻辑，有时用于实现特殊需求。 9. 多数据源：当项目需要连接多个数据库时，MyBatis提供了支持。数据源配置部分详细讲述了MyBatis内置的数据源提供者，包括非池化和池化的数据源，以及JNDI数据源的配置，这些配置对于保证数据库连接的管理和复用至关重要。通过以上内容，开发者可以全面了解并掌握MyBatis-Guice的核心功能，从而在实际项目中有效地使用MyBatis框架，提高代码的可维护性和灵活性。同时，这份教程还强调了遵守版权规定，允许自由复制和分发，但不能收取费用，且每个副本都需要包含版权通知。

Chapter 3. The Core components

3.1. Introduction

Core components are contained in the org.mybatis.guice.* package, providing a set of reusable Google

Guice javax.inject.Providers and com.google.inject.Modules that alleviate users the task to create

MyBatis objects.

3.2. MyBatis Bootstrap

MyBatis offers an excellent APIs layer for the Bootstrap configuration that makes it easy to write custom

bootstrap - by default MyBatis comes with the XML loader - and integrating 3rd part components.

The core component of the Guice approach is represented by the org.mybatis.guice.MyBatisModule that's

able to create the core MyBatis org.apache.ibatis.session.SqlSessionFactory,

org.apache.ibatis.session.SqlSessionManager and the user defined Mappers.

The best way to start is just adding the org.mybatis.guice.MyBatisModule into the

com.google.inject.Injector as shown in the example below and explain details step by step:

Class<? extends Provider<DataSource>> dataSourceProviderType = [...]; ❶

Class<? extends TransactionFactory> txFactoryClass = [...];

❷

Injector injector = Guice.createInjector(

new MyBatisModule() {

@Override

protected void initialize() {

environmentId("development"); ❸

bindDataSourceProviderType(dataSourceProviderType);

bindTransactionFactoryType(txFactoryClass);

}

}, ❹

...

);

SqlSessionFactory sessionFactory = injector.getInstance(SqlSessionFactory.class);

SqlSessionManager sessionManager = injector.getInstance(SqlSessionManager.class);

MyMapper mapper = injector.getInstance(MyMapper.class);

❶ This is the provider that has the task to create and provide the javax.sql.DataSource managed by

MyBatis.

There will be a proper section dedicated to the supported DataSource providers

❷ This is the one has to serve the MyBatis org.apache.ibatis.transaction.TransactionFactory

❸ The org.apache.ibatis.mapping.Environment needs to know the environment id.

❹ Install the MyBatis Module in the Injector.

❺ Retrieve built MyBatis components from the Injector.

Let's have a look now at the MyBatis module components and features:

3.2.1. MyBatis properties

By design, we choose to reuse the default configuration properties provided by Guice to let users feel free to

read and set them in any way you prefer; we suggest to put it in a properties file, maybe filtered and set

depending on which environment users are building the application.

By default, if a configuration property is not specified, it will be ignored and MyBatis will take care about

proper default initialization. Users can initialize properties using the proper setters OR by following method

(please don't bind properties twice!):

binder.bindConstant()

.annotatedWith(Names.named("mybatis.configuration.XXX"))

.to(XXXvalue);

The MyBatis module supports the following parameters:

Table 3.1. org.mybatis.guice.MyBatisModule properties

Property Setter Default

mybatis.environment.id environmentId(String) Not set, it is required

mybatis.configuration.lazyLoadingEnabledlazyLoadingEnabled(boolean) false

mybatis.configuration.aggressiveLazyLoadingaggressiveLazyLoading(boolean) true

mybatis.configuration.multipleResultSetsEnabledmultipleResultSetsEnabled(boolean) true

mybatis.configuration.useGeneratedKeysuseGeneratedKeys(boolean) false

mybatis.configuration.useColumnLabeluseColumnLabel(boolean) true

mybatis.configuration.cacheEnabled useCacheEnabled(boolean) true

mybatis.configuration.defaultExecutorTypeexecutorType(ExecutorType) ExecutorType.SIMPLE

mybatis.configuration.autoMappingBehaviorautoMappingBehavior(AutoMappingBehavior)AutoMappingBehavior.PARTIAL

mybatis.configuration.failFast failFast(boolean) false

3.2.2. The DataSource Provider

The javax.sql.DataSource Provider is one of the two required providers that takes care about building and

injecting the used javax.sql.DataSource.

The mybatis-guice framework comes with some providers that support the MyBatis-native Data Sources and

other well known Data Sources, C3P0, Apache Commons DBCP and BoneCP but users are free to implement

their own javax.sql.DataSource Provider and reference it in the org.mybatis.guice.MyBatisModule.

Please read the following chapter Data Source Providers to obtain more informations about natively supported

providers.

3.2.3. The Transaction Factory

Users are free to plug their preferred org.apache.ibatis.transaction.TransactionFactory:

Class<? extends org.apache.ibatis.transaction.TransactionFactory> txFactoryType = ...

Module module = new MyBatisModule() {

The Core components

剩余30页未读，继续阅读

李事樯

粉丝: 0
资源: 12

深入理解MyBatis-Guice：从入门到实践

Spring+MyBatis开发实战(达内课程)

达内 MyBatis 核心_扫描版_2.42M

MyBatis核心(达内课程)

如何学习mybatis框架

如何快速学习mybatis框架

MyBatis 官方文档

mybatis总配置详解

mybatis源码怎么阅读

如何学好MyBatis

Mybatis框架的使用

最新资源