|
DocIbatis2MyBatis
Migration Steps when Switching from iBATIS to MyBatis
IntroductionMyBatis is a direct fork of the iBATIS code. At the time of this writing, the code is identical, but there are no known plans to continue the iBATIS project within the Apache software foundation. Therefore it is somewhat less of a fork, and more like a bend in the road. As with a corner when driving, there is a slight adjustment to be made. Questions
No. The MyBatis releases will be fully backward compatible. We have no intention to ever change the package name (maybe in version 4 someday). The only think that may need to be changed in the not to distant future is the DTD location. Instructions are below. Don't worry though, your code won't explode if you don't. It will just mean you can't use some of the newer features in the future until you do.
No. The copyright for future code will change. But the license is still the Apache License 2.0.
iBATIS 2 and 3 will be supported, with both 2.3.5 and 3.0.1 GA releases becoming available immediately. iBATIS.NET 1.x and 3.x will be supported, with a new release coming available soon.
Nothing really. Apache won't delete any existing resources. They'll be available in a read-only form. The Apache project will be archived in the "Apache Attic" when it becomes stale StepsThere are only a few simple steps to follow, some to do now, and some to do when you're ready.
1. Mailing ListsFirst, unsubscribe from the old mailing lists by sending an email to each one that you are signed up for. Most users of the Java framework will only be signed up for the user list.
There are no replacements for the developer or commits lists. Commits are easy to find with subversion or on the Source/Changes tab of the Google Projects page Now you're ready to sign up to the new MyBatis Google Group. If you already have a Google Account, you won't have much to do...
You can leave and re-join the group any time using the same page. You can also search the group right there on the discussion page. 2. Issue Tracking and WikiThe Google Code project site has a new unified wiki and issue tracker. Please do not use the old Jira and Confluence wiki pages. We won't necessarily see any issues or comments posted there (recently due to an infrastructure change at the ASF, all comments were lost on Confluence pages). We've moved all of the open issues (all new featurs) for iBATIS 3 to the new Google Code issue tracker. You can find the new Issue Tracker and Wiki here: Java .NET 3. Bookmarks and LinksOf course you don't want to be left with outdated or dead links. So be sure to update your browser bookmarks and any links to our site:
4. Update to the Latest Build (Java only at this time)There's no need to do this immediately. But when you're ready to upgrade to the latest release or the 3.0 GA release of MyBatis, you should do so from this site. There are no known plans to release any further from the Apache site. When the time comes, you'll find the new releases summarized here:
All future releases will be distributed via Google Code and archived here:
For Maven users, your new dependency coordinates are: <dependency>
<groupId>org.mybatis</groupId>
<artifactId>mybatis</artifactId>
<version>3.0.1</version>
</dependency>5. Update your DTD/Doctype Headers (Java only at this time)After you've updated to a build later than "3.0 GA Candidate", you can update your DOCTYPE headers in your Configuration and Mapper XML files. #
# DOCTYPE header for MyBatis XML Configuration file.
#
<!DOCTYPE configuration
PUBLIC "-//mybatis.org//DTD Config 3.0//EN"
"http://mybatis.org/dtd/mybatis-3-config.dtd">
#
# DOCTYPE header for MyBatis XML Mapper files.
#
<!DOCTYPE mapper
PUBLIC "-//mybatis.org//DTD Mapper 3.0//EN"
"http://mybatis.org/dtd/mybatis-3-mapper.dtd">
| |
TYPO
The only think that may need to be changed = The only thing that may need to be changed
What are the dtd locations for ibatis 2?
"The MyBatis? releases will be fully backward compatible". But i'm not able to find the SqlMapClient? class in MyBatis? 3.
So is it really backward compatible ?
i also found issues about backward compatibility: i built the mypetstore example, that is on the svn, and refers to ibatis 2.1.7.597. Now i'd like to switch it to use mybatis 3.0.1, but it seems a lot has changed. can you confirm that?
纠结啊
Guys, this page is about migrating from Apache iBATIS 3.0 to MyBatis? 3.x. And NOT from iBATIS 2.x to MyBatis?. MyBatis? is not backwards compatible with iBATIS 2.
I suppose it made sense when MyBatis? moved from Apache but maybe now it makes more confusion than help. Given that iBATIS 3.0 was not know becuse it lived for a short time and users think this is about iBATIS 2.0 -> MyBatis?.
I don't know whether there's a unexpected issue happen later for the switch from ibatis to mybatis, god bless ..
June 2011:
Does version 2.3.5 still get supported?
Thank you!
我靠啊~
源码在哪下啊???