Apache Empire-db: Difference between revisions

Revision as of 02:29, 9 January 2015

Revision as of 14:31, 27 August 2015

Line 8:

| developer = [[Apache Software Foundation]]

| status = incubation

| latest release version = 2.4.3

| latest release date = {{release date|2014|08|20}}

| latest preview version =

Line 19:

}}

'''Apache Empire-db''' is a Java library that provides a high level object -oriented API for accessing [[Relationalrelational database management system]]s (RDBMS) through [[JDBC]]. Apache Empire-db is Openopen Sourcesource and provided under the Apache 2.0 license from the [[Apache Software Foundation]].

Compared to [[Object-relational mapping]] (ORM) or other data persistence solutions such as [[Hibernate (Java)|Hibernate]], [[iBATIS]] or [[TopLink]] Empire-db does not use XML files or Java annotations to provide a mapping of plain (old) javaJava object ([[POJO]]'s) to database tables, views and columns. Instead Empire-db uses a Java object model to describe the underlying data model and an API that works almost solely with object references rather than [[string literal]]s.

Empire-db's aim is to provide better software quality and improved maintainability through increased compile-time safety and reduced redundancy of metadata. Additionally applications may benefit from better performance due to full control over [[SQL]] statements and their execution by the developer compared to most OR-Mappingmapping solutions.

== Major benefits ==

Empire-db’sdb's key strength is its API for dynamic SQL generation for arbitrary select, update, insert or delete statements, purely by using Java methods which reference the model objects. This provides type-safety and almost entirely eliminates the use of string literals for names or expressions in code. Additionally DBMS independence is achieved through a pluggable driver model.

Using references to table and column objects significantly improves compile-time safety and thus reduces the amount of testing. As a positive side effect the IDE’sIDE's code completion can be used to browse the data model, increases productivity and eliminates the need for other external tools or IDE-plugins.

Further the object model also provides safe and easy access to meta-information of the data model such as field data type, maximum field length, whether a field is mandatory and a finite choice of options for a field’s values. Metadata is user-extensible and not limited to DBMS related metadata. Availability of meta-information encourages more generic code and eliminates redundancies throughout application layers.

Line 102:

DBReader reader = new DBReader();

try {

reader.open(cmd, getConnection());

List<EmployeeInfo> empList = reader.getBeanList(EmployeeInfo.class);

} finally {

reader.close()

}

</source>

Line 115:

Empire-db was originally developed at ESTEAM Software a German software development company which used Empire-db to develop various applications for a variety of different branches.

In January 2008 Empire-db was made officially Openopen Sourcedource and first published though SourceForge.Netnet.

In June 2008 a proposal was submitted to the Apache Software Foundation for Empire-db to become an Apache Incubator project. In July 2008 Empire-db got accepted for incubation and all rights over the Software were transferred to the Apache Foundation.

Line 121:

In October 2008 Empire-db 2.0.4 was the first official Apache incubator release with all package names changed to begin with org.apache.empire.

== See also ==

{{Portal|Java}}

* [[Java Database Connectivity]] (JDBC)

* [[Object-relational mapping]]

* [[Hibernate (Java)|Hibernate]]

* [[iBATIS]]

* [[TopLink]]

* [[Apache Struts]]

== External links ==

* [http://incubator.apache.org/empire-db Empire-db project page at the Apache Foundation]

{{apache}}