MyBatis--SqlSessionFactoryBuilder,SqlSessionFactory,SqlSession作用域和生命周期

Scope and Lifecycle

It’s very important to understand the various scopes and lifecycles classes we’ve discussed so far. Using them incorrectly can cause severe concurrency problems.

NOTE Object lifecycle and Dependency Injection Frameworks

Dependency Injection frameworks can create thread safe, transactional SqlSessions and mappers and inject them directly into your beans so you can just forget about their lifecycle. You may want to have a look at MyBatis-Spring or MyBatis-Guice sub-projects to know more about using MyBatis with DI frameworks.

SqlSessionFactoryBuilder

This class can be instantiated, used and thrown away. There is no need to keep it around once you’ve created your SqlSessionFactory. Therefore the best scope for instances of SqlSessionFactoryBuilder is method scope (i.e. a local method variable) . You can reuse the SqlSessionFactoryBuilder to build multiple SqlSessionFactory instances, but it’s still best not to keep it around to ensure that all of the XML parsing resources are freed up for more important things.
：简明翻译：SqlSessionFactoryBuilder类是可以被实例化使用的。我们在使用其创建SqlSessionFactory时，没有必要为了获得相同的SqlSessionFactory每次都去实例化一个SqlSessionFactoryBuilder的对象。在使用一个SqlSessionFactoryBuilder的实例对象可以创建多个SqlSessionFactory时，确保其使用的资源能够得到合理的释放。 SqlSessionFactoryBuilder推荐的作用域是在方法内，例如：将其作为方法的一个方法内部变量。

SqlSessionFactory

Once created, the SqlSessionFactory should exist for the duration of your application execution. There should be little or no reason to ever dispose of it or recreate it. It’s a best practice to not rebuild the SqlSessionFactory multiple times in an application run. Doing so should be considered a “bad smell”. Therefore the best scope of SqlSessionFactory is application scope. This can be achieved a number of ways. The simplest is to use a Singleton pattern or Static Singleton pattern.
：简明概述：SqlSessionFactory的最佳作用域范围是：应用的全局作用域，其生命周期也应该与应用的生命周期相同。推荐的最佳实践是：采用单例（静态单例）设计模式来设计该类！！

SqlSession

Each thread should have its own instance of SqlSession. Instances of SqlSession are not to be shared and are not thread safe. Therefore the best scope is request or method scope. Never keep references to a SqlSession instance in a static field or even an instance field of a class. Never keep references to a SqlSession in any sort of managed scope, such as HttpSession of the Servlet framework. If you’re using a web framework of any sort, consider the SqlSession to follow a similar scope to that of an HTTP request. In other words, upon receiving an HTTP request, you can open a SqlSession, then upon returning the response, you can close it. Closing the session is very important. You should always ensure that it’s closed within a finally block. The following is the standard pattern for ensuring that SqlSessions are closed:

SqlSession session = sqlSessionFactory.openSession();
try {
  // do work
} finally {
  session.close();
}

Using this pattern consistently throughout your code will ensure that all database resources are properly closed.
:简要说明：其生命周期最好控制在方法体内，或是一个request请求期间。也就是说其生命周期最长不应该大于一个HttpRequest请求的生命周期。最后使用结束后不要忘记关闭它，已释放资源。

Mapper Instances

Mappers are interfaces that you create to bind to your mapped statements. Instances of the mapper interfaces are acquired from the SqlSession. As such, technically the broadest scope of any mapper instance is the same as the SqlSession from which they were requested. However,* the best scope for mapper instances is method scope*. That is, they should be requested within the method that they are used, and then be discarded. They do not need to be closed explicitly. While it’s not a problem to keep them around throughout a request, similar to the SqlSession, you might find that managing too many resources at this level will quickly get out of hand. Keep it simple, keep Mappers in the method scope. The following example demonstrates this practice.

SqlSession session = sqlSessionFactory.openSession();
try {
  BlogMapper mapper = session.getMapper(BlogMapper.class);
  // do work
} finally {
  session.close();
}

:简明概述：其生命周期和作用域和SqlSession类似，不过其管理并不需要我们更多的参与。