- 浏览: 958522 次
文章分类
- 全部博客 (428)
- Hadoop (2)
- HBase (1)
- ELK (1)
- ActiveMQ (13)
- Kafka (5)
- Redis (14)
- Dubbo (1)
- Memcached (5)
- Netty (56)
- Mina (34)
- NIO (51)
- JUC (53)
- Spring (13)
- Mybatis (17)
- MySQL (21)
- JDBC (12)
- C3P0 (5)
- Tomcat (13)
- SLF4J-log4j (9)
- P6Spy (4)
- Quartz (12)
- Zabbix (7)
- JAVA (9)
- Linux (15)
- HTML (9)
- Lucene (0)
- JS (2)
- WebService (1)
- Maven (4)
- Oracle&MSSQL (14)
- iText (11)
- Development Tools (8)
- UTILS (4)
- LIFE (8)
最新评论
-
Donald_Draper:
Donald_Draper 写道刘落落cici 写道能给我发一 ...
DatagramChannelImpl 解析三(多播) -
Donald_Draper:
刘落落cici 写道能给我发一份这个类的源码吗Datagram ...
DatagramChannelImpl 解析三(多播) -
lyfyouyun:
请问楼主,执行消息发送的时候,报错:Transport sch ...
ActiveMQ连接工厂、连接详解 -
ezlhq:
关于 PollArrayWrapper 状态含义猜测:参考 S ...
WindowsSelectorImpl解析一(FdMap,PollArrayWrapper) -
flyfeifei66:
打算使用xmemcache作为memcache的客户端,由于x ...
Memcached分布式客户端(Xmemcached)
SqlSessionFactory初始化:http://donald-draper.iteye.com/blog/2331917
Mybatis加载解析Mapper(xml)文件第一讲:http://donald-draper.iteye.com/blog/2333125
Mybatis加载解析Mapper(xml)文件第二讲:http://donald-draper.iteye.com/blog/2333191
Mybatis 解析Mapper(class):http://donald-draper.iteye.com/blog/2333293
//全局文件的解析的方法在XMLConfigBuilder中,今天来具体看一下如何解析environments
//XMLConfigBuilder
//解析transactionManager
先看configuration的构造,启动有JDBC,POOLED类型的映射关系,这个在解析environment节点时,需要用到
从上可以看出JDBC,POOLED类型别名的映射关系如下:
JDBC,JdbcTransactionFactory
POOLED,PooledDataSourceFactory
//JdbcTransactionFactory
//TransactionFactory
现在来看一下jdbc事务
//Transaction
从上面可以看出jdbc对应的事务工厂为JdbcTransactionFactory,由JdbcTransactionFactory,根据数据源,事务级别以及自动提交属性来,创建JdbcTransaction,而JdbcTransaction的事务管理,是通过数据连接connection,而connection是从datasource获取,JdbcTransaction的事务管理,就是依靠相应的数据库driver,来管理,实际依赖于数据库。
//解析dataSource
// PooledDataSourceFactory
//UnpooledDataSourceFactory
//PooledDataSource
从上面可以看出解析datasource节点,就是解析器属性,并初始化datasource,
PooledDataSourceFactory继承UnpooledDataSourceFactory,改变的只是数据源类型,
PooledDataSourceFactory对应的数据源为PooledDataSource,而UnpooledDataSourceFactory对应的为,UnpooledDataSource;
我们再来看解析environment节点是,environment的构造
//Environment
再来看,Configuration设置environment
总结:
事务类型为jdbc对应的事务工厂为JdbcTransactionFactory,由JdbcTransactionFactory,根据数据源,事务级别以及自动提交属性来,创建JdbcTransaction,而JdbcTransaction的事务管理,是通过数据连接connection,而connection是从datasource获取,JdbcTransaction的事务管理,就是依靠相应的数据库driver,来管理,实际依赖于数据库;解析datasource节点,就是解析器属性,并初始化datasource,PooledDataSourceFactory继承UnpooledDataSourceFactory,改变的只是数据源类型,PooledDataSourceFactory对应的数据源为PooledDataSource,而UnpooledDataSourceFactory对应的为,UnpooledDataSource。
Mybatis加载解析Mapper(xml)文件第一讲:http://donald-draper.iteye.com/blog/2333125
Mybatis加载解析Mapper(xml)文件第二讲:http://donald-draper.iteye.com/blog/2333191
Mybatis 解析Mapper(class):http://donald-draper.iteye.com/blog/2333293
//全局文件的解析的方法在XMLConfigBuilder中,今天来具体看一下如何解析environments
//XMLConfigBuilder
private void parseConfiguration(XNode root) { try { propertiesElement(root.evalNode("properties")); typeAliasesElement(root.evalNode("typeAliases")); pluginElement(root.evalNode("plugins")); objectFactoryElement(root.evalNode("objectFactory")); objectWrapperFactoryElement(root.evalNode("objectWrapperFactory")); settingsElement(root.evalNode("settings")); //解析environments environmentsElement(root.evalNode("environments")); databaseIdProviderElement(root.evalNode("databaseIdProvider")); typeHandlerElement(root.evalNode("typeHandlers")); mapperElement(root.evalNode("mappers")); } catch(Exception e) { throw new BuilderException((new StringBuilder()).append("Error parsing SQL Mapper Configuration. Cause: ").append(e).toString(), e); } } //解析environments private void environmentsElement(XNode context) throws Exception { if(context != null) { if(C == null) environment = context.getStringAttribute("default"); Iterator i$ = context.getChildren().iterator(); //遍历environments的child节点environment,并解析 do { if(!i$.hasNext()) break; XNode child = (XNode)i$.next(); String id = child.getStringAttribute("id"); //如果environment的id属性,与environments的default相同时,才解析 if(isSpecifiedEnvironment(id)) { //解析transactionManager TransactionFactory txFactory = transactionManagerElement(child.evalNode("transactionManager")); //解析dataSource DataSourceFactory dsFactory = dataSourceElement(child.evalNode("dataSource")); javax.sql.DataSource dataSource = dsFactory.getDataSource(); org.apache.ibatis.mapping.Environment.Builder environmentBuilder = (new org.apache.ibatis.mapping.Environment.Builder(id)).transactionFactory(txFactory).dataSource(dataSource); configuration.setEnvironment(environmentBuilder.build()); } } while(true); } }
//解析transactionManager
先看configuration的构造,启动有JDBC,POOLED类型的映射关系,这个在解析environment节点时,需要用到
typeAliasRegistry.registerAlias("JDBC", org/apache/ibatis/transaction/jdbc/JdbcTransactionFactory); typeAliasRegistry.registerAlias("POOLED", org/apache/ibatis/datasource/pooled/PooledDataSourceFactory);
public Configuration() { safeRowBoundsEnabled = false; safeResultHandlerEnabled = true; mapUnderscoreToCamelCase = false; aggressiveLazyLoading = true; multipleResultSetsEnabled = true; useGeneratedKeys = false;//允许JDBC支持生成的键 useColumnLabel = true; cacheEnabled = true;//全局的映射器启用或禁用缓存 callSettersOnNulls = false; localCacheScope = LocalCacheScope.SESSION;//本地一级缓存作用域 jdbcTypeForNull = JdbcType.OTHER; lazyLoadTriggerMethods = new HashSet(Arrays.asList(new String[] { "equals", "clone", "hashCode", "toString" })); defaultExecutorType = ExecutorType.SIMPLE; autoMappingBehavior = AutoMappingBehavior.PARTIAL; variables = new Properties(); objectFactory = new DefaultObjectFactory();//默认ObjectFactory objectWrapperFactory = new DefaultObjectWrapperFactory();//默认DefaultObjectWrapperFactory mapperRegistry = new MapperRegistry(this); lazyLoadingEnabled = false; interceptorChain = new InterceptorChain();//插件链 typeHandlerRegistry = new TypeHandlerRegistry();//类型处理注册器 typeAliasRegistry = new TypeAliasRegistry();//类型别名注册器 languageRegistry = new LanguageDriverRegistry(); //mappedStatements Map mappedStatements = new StrictMap("Mapped Statements collection"); //mappedStatements,method,二级缓存 caches = new StrictMap("Caches collection"); //MapperInterface 方法返回结果类型Map resultMaps = new StrictMap("Result Maps collection"); //MapperInterface 方法参数类型Map parameterMaps = new StrictMap("Parameter Maps collection"); //主键生成器Map keyGenerators = new StrictMap("Key Generators collection"); loadedResources = new HashSet(); //Mapper.xml 中statement片段 sqlFragments = new StrictMap("XML fragments parsed from previous mappers"); //未解析处理的statements incompleteStatements = new LinkedList(); //未解析处理的CacheRefs incompleteCacheRefs = new LinkedList(); //未解析处理的ResultMaps incompleteResultMaps = new LinkedList(); //未解析处理的Methods incompleteMethods = new LinkedList(); cacheRefMap = new HashMap(); typeAliasRegistry.registerAlias("JDBC", org/apache/ibatis/transaction/jdbc/JdbcTransactionFactory); typeAliasRegistry.registerAlias("MANAGED", org/apache/ibatis/transaction/managed/ManagedTransactionFactory); typeAliasRegistry.registerAlias("JNDI", org/apache/ibatis/datasource/jndi/JndiDataSourceFactory); typeAliasRegistry.registerAlias("POOLED", org/apache/ibatis/datasource/pooled/PooledDataSourceFactory); typeAliasRegistry.registerAlias("UNPOOLED", org/apache/ibatis/datasource/unpooled/UnpooledDataSourceFactory); typeAliasRegistry.registerAlias("PERPETUAL", org/apache/ibatis/cache/impl/PerpetualCache); typeAliasRegistry.registerAlias("FIFO", org/apache/ibatis/cache/decorators/FifoCache); typeAliasRegistry.registerAlias("LRU", org/apache/ibatis/cache/decorators/LruCache); typeAliasRegistry.registerAlias("SOFT", org/apache/ibatis/cache/decorators/SoftCache); typeAliasRegistry.registerAlias("WEAK", org/apache/ibatis/cache/decorators/WeakCache); typeAliasRegistry.registerAlias("VENDOR", org/apache/ibatis/mapping/VendorDatabaseIdProvider); typeAliasRegistry.registerAlias("XML", org/apache/ibatis/scripting/xmltags/XMLLanguageDriver); typeAliasRegistry.registerAlias("RAW", org/apache/ibatis/scripting/defaults/RawLanguageDriver); typeAliasRegistry.registerAlias("SLF4J", org/apache/ibatis/logging/slf4j/Slf4jImpl); typeAliasRegistry.registerAlias("COMMONS_LOGGING", org/apache/ibatis/logging/commons/JakartaCommonsLoggingImpl); typeAliasRegistry.registerAlias("LOG4J", org/apache/ibatis/logging/log4j/Log4jImpl); typeAliasRegistry.registerAlias("JDK_LOGGING", org/apache/ibatis/logging/jdk14/Jdk14LoggingImpl); typeAliasRegistry.registerAlias("STDOUT_LOGGING", org/apache/ibatis/logging/stdout/StdOutImpl); typeAliasRegistry.registerAlias("NO_LOGGING", org/apache/ibatis/logging/nologging/NoLoggingImpl); typeAliasRegistry.registerAlias("CGLIB", org/apache/ibatis/executor/loader/CglibProxyFactory); typeAliasRegistry.registerAlias("JAVASSIST", org/apache/ibatis/executor/loader/JavassistProxyFactory); languageRegistry.setDefaultDriverClass(org/apache/ibatis/scripting/xmltags/XMLLanguageDriver); languageRegistry.register(org/apache/ibatis/scripting/defaults/RawLanguageDriver); }
从上可以看出JDBC,POOLED类型别名的映射关系如下:
JDBC,JdbcTransactionFactory
POOLED,PooledDataSourceFactory
<environments default="development"> <environment id="development"> <transactionManager type="JDBC" /> <dataSource type="POOLED"> <property name="driver" value="${driver}" /> <property name="url" value="${url}" /> <property name="username" value="${username}" /> <property name="password" value="${password}" /> </dataSource> </environment> </environments>
private TransactionFactory transactionManagerElement(XNode context) throws Exception { if(context != null) { String type = context.getStringAttribute("type"); Properties props = context.getChildrenAsProperties(); //从类型解决器中,获取type对应的类型的实例,从上面的配置来看 //实际为JdbcTransactionFactory TransactionFactory factory = (TransactionFactory)resolveClass(type).newInstance(); //设置JdbcTransactionFactory属性 factory.setProperties(props); return factory; } else { throw new BuilderException("Environment declaration requires a TransactionFactory."); } }
//JdbcTransactionFactory
public class JdbcTransactionFactory implements TransactionFactory { public void setProperties(Properties properties) { } //根据数据连接新建事务 public Transaction newTransaction(Connection conn) { return new JdbcTransaction(conn); } //根据数据源和事务级别和是否自动提交,新建事务 public Transaction newTransaction(DataSource ds, TransactionIsolationLevel level, boolean autoCommit) { return new JdbcTransaction(ds, level, autoCommit); } }
//TransactionFactory
public interface TransactionFactory { public abstract void setProperties(Properties properties); public abstract Transaction newTransaction(Connection connection); public abstract Transaction newTransaction(DataSource datasource, TransactionIsolationLevel transactionisolationlevel, boolean flag); }
现在来看一下jdbc事务
public class JdbcTransaction implements Transaction { private static final Log log = LogFactory.getLog(org/apache/ibatis/transaction/jdbc/JdbcTransaction); protected Connection connection;//数据库连接 protected DataSource dataSource;//数据源 protected TransactionIsolationLevel level;//事务级别 protected boolean autoCommmit;//自动提交属性 public JdbcTransaction(DataSource ds, TransactionIsolationLevel desiredLevel, boolean desiredAutoCommit) { dataSource = ds; level = desiredLevel; autoCommmit = desiredAutoCommit; } public JdbcTransaction(Connection connection) { this.connection = connection; } public Connection getConnection() throws SQLException { if(connection == null) openConnection(); return connection; } public void commit() throws SQLException { if(connection != null && !connection.getAutoCommit()) { if(log.isDebugEnabled()) log.debug((new StringBuilder()).append("Committing JDBC Connection [").append(connection).append("]").toString()); connection.commit(); } } public void rollback() throws SQLException { if(connection != null && !connection.getAutoCommit()) { if(log.isDebugEnabled()) log.debug((new StringBuilder()).append("Rolling back JDBC Connection [").append(connection).append("]").toString()); connection.rollback(); } } public void close() throws SQLException { if(connection != null) { resetAutoCommit(); if(log.isDebugEnabled()) log.debug((new StringBuilder()).append("Closing JDBC Connection [").append(connection).append("]").toString()); connection.close(); } } protected void setDesiredAutoCommit(boolean desiredAutoCommit) { try { if(connection.getAutoCommit() != desiredAutoCommit) { if(log.isDebugEnabled()) log.debug((new StringBuilder()).append("Setting autocommit to ").append(desiredAutoCommit).append(" on JDBC Connection [").append(connection).append("]").toString()); connection.setAutoCommit(desiredAutoCommit); } } catch(SQLException e) { throw new TransactionException((new StringBuilder()).append("Error configuring AutoCommit. Your driver may not support getAutoCommit() or setAutoCommit(). Requested setting: ").append(desiredAutoCommit).append(". Cause: ").append(e).toString(), e); } } protected void resetAutoCommit() { try { if(!connection.getAutoCommit()) { if(log.isDebugEnabled()) log.debug((new StringBuilder()).append("Resetting autocommit to true on JDBC Connection [").append(connection).append("]").toString()); connection.setAutoCommit(true); } } catch(SQLException e) { log.debug((new StringBuilder()).append("Error resetting autocommit to true before closing the connection. Cause: ").append(e).toString()); } } //获取connection protected void openConnection() throws SQLException { if(log.isDebugEnabled()) log.debug("Openning JDBC Connection"); connection = dataSource.getConnection(); if(level != null) connection.setTransactionIsolation(level.getLevel()); setDesiredAutoCommit(autoCommmit); } }
//Transaction
public interface Transaction { public abstract Connection getConnection() throws SQLException; public abstract void commit() throws SQLException; public abstract void rollback() throws SQLException; public abstract void close() throws SQLException; }
从上面可以看出jdbc对应的事务工厂为JdbcTransactionFactory,由JdbcTransactionFactory,根据数据源,事务级别以及自动提交属性来,创建JdbcTransaction,而JdbcTransaction的事务管理,是通过数据连接connection,而connection是从datasource获取,JdbcTransaction的事务管理,就是依靠相应的数据库driver,来管理,实际依赖于数据库。
//解析dataSource
private DataSourceFactory dataSourceElement(XNode context) throws Exception { if(context != null) { //获取数据源的类型,和属性 String type = context.getStringAttribute("type"); Properties props = context.getChildrenAsProperties(); //根据type从configuration的类型处理器,获取具体的DataSourceFactory //从上文,我们看一看到type为POOLED,对应的是PooledDataSourceFactory DataSourceFactory factory = (DataSourceFactory)resolveClass(type).newInstance(); factory.setProperties(props); return factory; } else { throw new BuilderException("Environment declaration requires a DataSourceFactory."); } }
// PooledDataSourceFactory
public class PooledDataSourceFactory extends UnpooledDataSourceFactory { public PooledDataSourceFactory() { dataSource = new PooledDataSource(); } }
//UnpooledDataSourceFactory
public class UnpooledDataSourceFactory implements DataSourceFactory { private static final String DRIVER_PROPERTY_PREFIX = "driver."; private static final int DRIVER_PROPERTY_PREFIX_LENGTH = "driver.".length(); protected DataSource dataSource; public UnpooledDataSourceFactory() { dataSource = new UnpooledDataSource(); } public void setProperties(Properties properties) { Properties driverProperties = new Properties(); //获取dataSource的对象描述 MetaObject metaDataSource = SystemMetaObject.forObject(dataSource); //获取dataSource的所有属性,并设置 for(Iterator i$ = properties.keySet().iterator(); i$.hasNext();) { Object key = i$.next(); String propertyName = (String)key; if(propertyName.startsWith("driver.")) { String value = properties.getProperty(propertyName); driverProperties.setProperty(propertyName.substring(DRIVER_PROPERTY_PREFIX_LENGTH), value); } else if(metaDataSource.hasSetter(propertyName)) { String value = (String)properties.get(propertyName); Object convertedValue = convertValue(metaDataSource, propertyName, value); metaDataSource.setValue(propertyName, convertedValue); } else { throw new DataSourceException((new StringBuilder()).append("Unknown DataSource property: ").append(propertyName).toString()); } } //设置metaDataSource的driverProperties属性 if(driverProperties.size() > 0) metaDataSource.setValue("driverProperties", driverProperties); } public DataSource getDataSource() { return dataSource; } //将value转化为metaDataSource的对应setValue的参数类型 private Object convertValue(MetaObject metaDataSource, String propertyName, String value) { Object convertedValue = value; Class targetType = metaDataSource.getSetterType(propertyName); if(targetType == java/lang/Integer || targetType == Integer.TYPE) convertedValue = Integer.valueOf(value); else if(targetType == java/lang/Long || targetType == Long.TYPE) convertedValue = Long.valueOf(value); else if(targetType == java/lang/Boolean || targetType == Boolean.TYPE) convertedValue = Boolean.valueOf(value); return convertedValue; } }
//PooledDataSource
public class PooledDataSource implements DataSource { private final PoolState state; private final UnpooledDataSource dataSource; protected int poolMaximumActiveConnections; protected int poolMaximumIdleConnections; protected int poolMaximumCheckoutTime; protected int poolTimeToWait; protected String poolPingQuery; protected boolean poolPingEnabled; protected int poolPingConnectionsNotUsedFor; private int expectedConnectionTypeCode; }
从上面可以看出解析datasource节点,就是解析器属性,并初始化datasource,
PooledDataSourceFactory继承UnpooledDataSourceFactory,改变的只是数据源类型,
PooledDataSourceFactory对应的数据源为PooledDataSource,而UnpooledDataSourceFactory对应的为,UnpooledDataSource;
我们再来看解析environment节点是,environment的构造
org.apache.ibatis.mapping.Environment.Builder environmentBuilder = (new org.apache.ibatis.mapping.Environment.Builder(id)).transactionFactory(txFactory).dataSource(dataSource);
//Environment
public final class Environment { private final String id; private final TransactionFactory transactionFactory; private final DataSource dataSource; public static class Builder { public Environment build() { return new Environment(id, transactionFactory, dataSource); } private String id; private TransactionFactory transactionFactory; private DataSource dataSource; public Builder(String id) { this.id = id; } } }
再来看,Configuration设置environment
public void setEnvironment(Environment environment) { this.environment = environment; }
总结:
事务类型为jdbc对应的事务工厂为JdbcTransactionFactory,由JdbcTransactionFactory,根据数据源,事务级别以及自动提交属性来,创建JdbcTransaction,而JdbcTransaction的事务管理,是通过数据连接connection,而connection是从datasource获取,JdbcTransaction的事务管理,就是依靠相应的数据库driver,来管理,实际依赖于数据库;解析datasource节点,就是解析器属性,并初始化datasource,PooledDataSourceFactory继承UnpooledDataSourceFactory,改变的只是数据源类型,PooledDataSourceFactory对应的数据源为PooledDataSource,而UnpooledDataSourceFactory对应的为,UnpooledDataSource。
发表评论
-
Mybatis缓存实现
2016-12-07 10:36 946SqlSessionFactory初始化:http://don ... -
DefaultSqlSession第三讲-事务提交,回滚,关闭SqlSession,清除缓存
2016-11-20 11:07 5610上面两篇讲过query和update及flushStateme ... -
DefaultSqlSession第二讲-更新,刷新Statement
2016-11-20 11:06 595上一篇文章中,我们讲到DefaultSqlSession的查询 ... -
DefaultSqlSession第一讲query解析
2016-11-20 11:06 1576上一篇文章:我们说过DefaultSqlSession,Def ... -
Mybatis的SqlSession解析
2016-11-20 11:02 2454在前文中,Mybatis使用教程中,有下面一段代码: Sql ... -
Mybatis的Reflector解析
2016-11-18 12:53 2127Mybatis的MetaObject解析:http://don ... -
Mybatis的MetaObject解析
2016-11-18 11:40 9517SqlSessionFactory初始化:http://don ... -
mybatis 动态标签语句的解析(BoundSql)
2016-10-30 09:48 5676SqlSessionFactory初始化:http://don ... -
Mybatis 解析Mapper(class)
2016-10-26 11:44 3273SqlSessionFactory初始化:http://don ... -
Mybatis加载解析Mapper(xml)文件第二讲
2016-10-25 21:30 4702SqlSessionFactory初始化:http://don ... -
Mybatis加载解析Mapper(xml)文件第一讲
2016-10-25 16:51 6093SqlSessionFactory初始化:http://don ... -
SqlSessionFactory初始化
2016-10-20 15:38 2413mybatis 使用教程:http://donald-drap ... -
mybatis 使用教程
2016-10-14 09:03 872Myeclispe下mybatis generator的使 ... -
Spring+Mybatis多数据源的实现
2016-09-21 18:15 3056浅谈Spring事务隔离级别:http://www.cnblo ... -
mybaitis CDATA 防止字符被解析
2016-08-17 18:45 693在使用mybatis 时我们sql是写在xml 映射文件中,如 ... -
Myeclispe下mybatis generator的使用
2016-07-05 18:05 1338准备:下载附件包解压到myeclispe的dropins文件夹 ...
相关推荐
Mybatis插件机制详解
MyBatis+Geneator详解..
MyBatis 源码解析:通过源码深入理解 SQL 的执行过程 抓下来打包成了HTML文件, 方便离线观看
mybatis SQL日志解析;查看日志时mybatis打印的日志查询条件以及参数不是拼接好的,想复制对应sql在本地执行时比较麻烦,通过前端编写页面进行日志解析,拼接sql中的问号以及参数变课轻松实现
MyBatis源码分析.pdf
# 1. 前言 本文旨在探讨在SpringBoot框架下,...MyBatis在使用时需要开发者手动解析实体关系映射并转换为MyBatis内部对象注入容器,而MyBatis Plus则能够自动解析实体关系映射,并提供了内置的Mapper和通用的Service
mybatis动态sql 详解.pdf
MyBatis日志解析工具支持MyBatis3.0以上版本,能够将Mybatis打印的SQL日志转换成SQL语句。 使用方法请查看 https://blog.csdn.net/warehouse666/article/details/90111704
项目需要springboot 可以绕过mybatis xml加载直接解析带标签的sql 演示代码,给需要的码农
springmvc+mybatis全套视频详解及源码 百度盘链接,有需要的朋友可以下载学学,多学点技术没什么坏处
Mybatis Generator配置详解 ,可以参考一下,希望有所用。
详细说明了MyBatis的resultMap使用方法
Spring整合Mybatis源码解析
如果你不会配置mybatis中的相关xml配置,就进来看看,手把手教学,可以从零开始
这是Mybatis的详解以及使用,里面包括我写的一个小例子以及数据库表结构和数据的sql语句。详细介绍了mybatis的使用方法。
MyBatis源码解析
Mybatis源码解析设计源码:该项目基于Java开发,包含37个文件,主要使用Java语言。该项目旨在对Mybatis框架的源代码进行深入解析,以帮助开发者更好地理解和使用Mybatis,提高开发效率和质量。
mybatis源码解析视频的讲解是由某知名老师讲解。包你学完可以完全理解mybatis框架实现原理等。
Mybatis笔记详解,有兴趣的人可以一看,可以解决自己的一些盲区知识点
MyBatis的一个主要的特点就是需要程序员自己编写sql,那么如果表太多的话,难免会很麻烦,所以mybatis官方提供了一个逆向工程,可以针对单表自动生成mybatis执行所需要的代码(包括mapper.xml、mapper.java、po..)...