mybatis-spring-2.0.x (Java 8, Spring 5.x and Spring Batch 4.x)

[pboonphong]

TODO:

• Migrate to Java 8 as same as Spring 5.x.
• Upgrade dependencies, align with Spring Platform.
• Upgrade to JUnit 5
• Wrap Log with Logger to support lambda expressions.
• Verify test cases with AssertJ
• Replace Mockrunner with Mockito 2.x or H2/HSQLDB (TBD) Keep Mockrunner -> see Consider to use Mockito instead of Mockrunner #167
• Create branch 1.3.x, then merge pull request with master.

Release Date: After Spring 5.x and Spring Batch 4.x released

FIXME: Enable SqlSessionTemplateAsyncAfterCompletionTest after migrate BMUnitRunner to BMUnitExtenson

[pboonphong]

Hi @emacarron,

It's been a long time. I'm working on next release of MyBatis-Spring based on Spring 5.x. New version of HibernateDaoSupport required access to SessionFactory, while MyBatis SqlSession do not supported. In addition, direct use of getSqlSession() make me wonder whether it's MyBatis SqlSession or Spring's managed SqlSessionTemplate.

Would you recall why we changing SqlSessionTemplate to SqlSession in following urls? There is no track on code.google.com. I afraid it might be important changes.

pboonphong@2a0ab16
pboonphong@e8d4adb

--
Best regards,
PB

[eddumelendez]

some files have not changed so the year should keep in 2016

[pboonphong]

Thanks. 530e0bf was reverted.

[emacarron]

Sorry for the late reply!!

Opposite to JdbcTemplate or HIbernateTemplate, SqlSessionTemplate is an SqlSession so there is no need to return the implementation (the template). The idea behind that is to make code as generic and simple as possible: no need to do specific code for mybatis-spring or to know the specific class that it uses.

I have seen you added a new method getSqlSessionTemplate() that returns de same instace that the existing getSqlSession method. I would not change that. Looks quite confusing having two methods for the same thing.