SynonymsBot
Synonyms for ibatis or Related words with ibatis
nhibernate
jdom
xmlbeans
adodb
rdfa
msxml
mxml
postgis
yaml
jython
mybatis
sqlalchemy
oql
hsqldb
esql
powershell
eclipselink
angularjs
dtrace
symfony
jquery
hsql
xerces
xaml
powerbuilder
accumulo
cakephp
extremedb
microformats
dotnet
jdeveloper
libxml
zend
jdo
monetdb
xpcom
navicat
ironpython
postgres
mariadb
openjpa
libcurl
ironruby
schematron
xscript
precompiler
codeigniter
qml
laravel
xmi
Examples of "ibatis"
MyBatis is a fork of
iBATIS
3.0 and is maintained by a team that includes the original creators of
iBATIS
.
MyBatis project is a subsidiary of
iBATIS
3.0 and maintained by a team which includes the original creators of
iBATIS
.
JPetStore 1.0 had a big impact and the database layer that Clinton used attracted the attention of the community. Soon,
iBATIS
Database Layer 1.0 project started, composed by two components:
iBATIS
DAO and
iBATIS
SQL Maps.
iBATIS
2.0 was released in June 2004. It was a complete redesign while keeping the same features. Clinton donated the
iBATIS
name and code to Apache Software Foundation and the project stayed in the ASF for six years.
The founder of
iBATIS
has publicly stated his dismay with Java 5, but has continued to release new versions of
iBATIS
for Java. Versions 2.3.1 and 2.3.2 came out in April 2008, and 2.3.3 in July.
Eventually
iBATIS
DAO was deprecated, considering that better DAO frameworks were available, such as Spring Framework.
On June 16, 2010 Apache announced that
iBATIS
was retired and moved to the Apache's attic.
In 2001 a project called
iBATIS
was started by Clinton Begin. Originally the focus was on the development of cryptographic software solutions. The first product to be released by
iBATIS
was Secrets, a personal data encryption and signing tool much like PGP. Secrets was written entirely in Java and was released under an open source license.
The framework is currently available in Java, .NET, and Ruby (RBatis) versions. The jBati project is a JavaScript ORM inspired by
iBATIS
.
The Apache iBator tool is closely related: it connects to your database and uses its metadata to generate
iBATIS
mapping files and Java classes.
The project was created on May 19, 2010 when Apache
iBATIS
3.0 was published and the team announced that the development will continue under a new name and a new home at Google Code.
When AppFuse was first developed, it only supported Struts and Hibernate. In version 2.x, it supports Hibernate,
iBATIS
or JPA as persistence frameworks. For implementing the MVC model, AppFuse is compatible with JSF, Spring MVC, Struts 2 or Tapestry.
For example, assume there is a database table and a Java class . To read the product record having the key into a new POJO, the following mapping is added into an
iBATIS
XML mapping file:
On May 21, 2010 the development team forked the code creating a new project called MyBatis and making new releases there. As a consequence the Apache
iBATIS
project became inactive and was moved to the Apache Attic in June 2010.
On May 19, 2010
iBATIS
3.0 was published and simultaneously the development team decided to continue the development of the framework at Google Code. under a new project called MyBatis.
Other persistence frameworks such as Hibernate allow the creation of an object model (in Java, say) by the user, and create and maintain the relational database automatically.
iBATIS
takes the reverse approach: the developer starts with a SQL database and
iBATIS
automates the creation of the Java objects. Both approaches have advantages, and
iBATIS
is a good choice when the developer does not have full control over the SQL database schema. For example, an application may need to access an existing SQL database used by other software, or access a new database whose schema is not fully under the application developer's control, such as when a specialized database design team has created the schema and carefully optimized it for high performance.
Spring's data access framework addresses common difficulties developers face when working with databases in applications. Support is provided for all popular data access frameworks in Java: JDBC,
iBatis
/MyBatis, Hibernate, JDO, JPA, Oracle TopLink, Apache OJB, and Apache Cayenne, among others.
DAO coding paradigms can require some skill. Technologies like Java Persistence API and Enterprise JavaBeans come built into application servers and can be used in applications that use a JavaEE application server. Commercial products like TopLink are available based on Object-relational mapping (ORM). Popular open source ORM products include Doctrine, Hibernate,
iBATIS
and JPA implementations such as Apache OpenJPA.
iBATIS
is a persistence framework which automates the mapping between SQL databases and objects in Java, .NET, and Ruby on Rails. In Java, the objects are POJOs (Plain Old Java Objects). The mappings are decoupled from the application logic by packaging the SQL statements in XML configuration files. The result is a significant reduction in the amount of code that a developer needs to access a relational database using lower level APIs like JDBC and ODBC.
In March 2000, the Apache Struts project was released. This project formalized the division between View and Controller and claimed implementation of the "Model 2" pattern. Once again, the implementation of the "Model" was left undefined with the expectation that software developers would fill in an appropriate solution. Database interaction via JDBC and EJBs were options suggested on the Struts homepage. More recently, Hibernate,
iBatis
, and Object Relational Bridge were listed as more modern options that could be used for a model.