上接《真的,MyBatis 核心源码入门看这个就够了(二)》
3 Mapper代理对象
我们再次回到demo中的代码:
@org.junit.jupiter.api.Test
void queryBySn() throws IOException {
//1 读取配置文件
InputStream in = Resources.getResourceAsStream("mybatis-config.xml");
//2 加载解析配置文件并获取SqlSessionFactory对象
SqlSessionFactory sqlSessionFactory = new SqlSessionFactoryBuilder().build(in);
//3 获取SqlSession对象
SqlSession sqlSession = sqlSessionFactory.openSession();
//4 通过SqlSession中提供的API方法来操作数据库
DeviceMapper deviceMapper = sqlSession.getMapper(DeviceMapper.class);
Device device = deviceMapper.queryBySn(Device.builder().sn("2234567").build());
System.out.println(device);
//5 关闭会话
sqlSession.close();
}
DeviceMapper deviceMapper = sqlSession.getMapper(DeviceMapper.class);
进入DefaultSqlSession
中查看
public class DefaultSqlSession implements SqlSession {
......
public <T> T getMapper(Class<T> type) {
return configuration.getMapper(type, this);
}
......
}
进入getMapper方法:
public class MapperRegistry {
......
/**
* 获取Mapper接口对应的代理对象
*/
public <T> T getMapper(Class<T> type, SqlSession sqlSession) {
// 获取Mapper接口对应的 MapperProxyFactory 对象
final MapperProxyFactory<T> mapperProxyFactory = (MapperProxyFactory<T>) knownMappers.get(type);
if (mapperProxyFactory == null) {
throw new BindingException("Type " + type + " is not known to the MapperRegistry.");
}
try {
return mapperProxyFactory.newInstance(sqlSession);
} catch (Exception e) {
throw new BindingException("Error getting mapper instance. Cause: " + e, e);
}
}
......
}
进入newInstance 方法
public class MapperProxyFactory<T> {
......
/**
* 创建实现了 mapperInterface 接口的代理对象
*/
protected T newInstance(MapperProxy<T> mapperProxy) {
// 1:类加载器:2:被代理类实现的接口、3:实现了 InvocationHandler 的触发管理类
return (T) Proxy.newProxyInstance(mapperInterface.getClassLoader(), new Class[] { mapperInterface }, mapperProxy);
}
public T newInstance(SqlSession sqlSession) {
final MapperProxy<T> mapperProxy = new MapperProxy<>(sqlSession, mapperInterface, methodCache);
return newInstance(mapperProxy);
}
......
}
如上所示,代理对象是通过JDK动态代理创建,返回的代理对象。
里面也传递了一个实现了 InvocationHandler接口的触发管理类。
public class MapperProxy<T> implements InvocationHandler, Serializable {
......
@Override
public Object invoke(Object proxy, Method method, Object[] args) throws Throwable {
try {
// toString hashCode equals getClass等方法,无需走到执行SQL的流程
if (Object.class.equals(method.getDeclaringClass())) {
return method.invoke(this, args);
} else {
// 提升获取 mapperMethod 的效率,到 MapperMethodInvoker(内部接口) 的 invoke
// 普通方法会走到 PlainMethodInvoker(内部类) 的 invoke
return cachedInvoker(method).invoke(proxy, method, args, sqlSession);
}
} catch (Throwable t) {
throw ExceptionUtil.unwrapThrowable(t);
}
}
......
}
获得Mapper对象的过程,实质上是获取了一个JDK动态代理对象(类型是 $ProxyN)。这个代理类会继承Proxy类,实现被代理的接口。里面持有一个MapperProxy类型的触发管理类。
获取代理对象时序图