Shulou(Shulou.com)06/02 Report--

In this issue, the editor will bring you what are the four aspects of the development direction of iBATIS. The article is rich in content and analyzes and narrates it from a professional point of view. I hope you can get something after reading this article.

IBATIS Development Direction 1Apache Software Foundation

Recently, iBATIS has become part of the Apache Software Foundation. We chose to turn to Apache because we believed in their mission and respected their attitude. Apache is not just a combination of servers and infrastructure, it is a system and the true home of open source software. Apache focuses more on the community around the software (that is, the user community) than on the technology behind the software, because without a community, the software is a dead project.

For iBATIS users, this means that iBATIS is not guided by a single group, nor is it dependent on a single group. IBATIS does not belong to any individual-it belongs to the entire community. Apache can always protect iBATIS and make sure it stays in the right direction. However, the Apache license does not restrict the use of open source software like the GPL might license. The Apache license is not a viral license, which means that you are free to use the software in a business environment without having to worry about many unreasonable conditions.

Although Apache doesn't care about infrastructure, they do have some very good infrastructure. At present, iBATIS uses Subversion source control (SVN) for version control, uses Atlassian's JIRA to track issues, uses Atlassian's Confluence to collaborate to write wiki documents, and uses Apache's mailing list server to communicate with development teams, users and the general community.

Apache has everything you need to protect iBATIS and ensures that as long as someone still wants to use iBATIS, it will be there.

IBATIS development direction 2 is simpler, smaller, and less dependent

Unlike other frameworks, the iBATIS project does not expect to branch into new areas, nor does it have any ambition to solve all the problems. IBATIS is a very focused project, and every time we release a new version, we expect to make it smaller, simpler, and less dependent on third-party libraries.

We believe that iBATIS still has a lot of room for innovation. IBATIS can benefit from many new technologies and design methods to make its configuration more concise and easier to use. For example, both C# and Java have built-in metadata (attribute, also known as "annotation") functionality. In future releases, it is possible for iBATIS to take advantage of this feature to reduce the amount of XML code required to configure the framework.

There are also many things that can be done in developing support tools for iBATIS. The design of iBATIS makes it easy to develop graphical tools like IDE for it. You can also consider creating tools that support the generation of iBATIS configuration files directly from the database framework (database schema), but there are already tools available at this point. You can see some examples of tools on our web page http://ibatis.apache.org.

IBATIS development direction 3 more extension points and plug-ins

IBATIS already has many extension points. We will delve deeper into the issue of expansion in Chapter 12. You can implement your own transaction processors, data sources, cache controllers (cache controller), and more. But we expect to make iBATIS easier to extend. We want to design almost every layer of the JDBC architecture as extensible, which will mean that you can implement your own ResultSet processor and SQL execution engine. This will help us support more complex systems, or legacy systems as well as proprietary systems. It will also enable developers to make better use of the customization features of specific databases or application servers.

IBATIS Development Direction 4 supports more platforms and languages

As you can see in chapters 1 and 2, we have discussed iBATIS in .NET and Java. The rest of the book will focus on API for the Java version of iBATIS, but most of the information can be translated into the .NET platform. In addition, we will discuss iBATIS.NET in more detail in the appendix. In fact, iBATIS has already been implemented by Ruby, but Ruby is a completely different language, so iBATIS implemented in Ruby is also very different. We will not discuss its Ruby implementation in this book.

In addition to Java and C #, the iBATIS team is discussing implementing iBATIS in other languages, including PHP 5 and Python. We believe that iBATIS can make a significant contribution to almost any platform that cannot or is unwilling to use the underlying database API and high-level object / relational mapping tools. IBATIS can help you find a compromise and allow you to implement all applications in a consistent way all the time.

We also talked about drafting a specification that would make it easier for users to port iBATIS to different platforms and ensure reasonable consistency. Of course, we want iBATIS to take full advantage of the features of a particular language and platform, and expect them to have a certain degree of similarity to ensure that they can all be called iBATIS and can be recognized at a glance by developers familiar with iBATIS in another language.

These are the four aspects of the iBATIS development direction shared by the editor. If you happen to have similar doubts, you might as well refer to the above analysis to understand. If you want to know more about it, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.