Apache Empire-db: Difference between revisions

Revision as of 07:12, 18 December 2021

Latest revision as of 17:44, 30 December 2023

(5 intermediate revisions by 5 users not shown)

Line 1:

{{Short description|Open-source Java library}}

{{Unreferenced|date=May 2011}}

{{Notability|Products|date=March 2022}}

{{Infobox software

| name = Apache Empire-db

Line 7 ⟶ 8:

| caption =

| developer = [[Apache Software Foundation]]

| latest release version = 23.40.70

| latest release date = {{Start date and age|20182022|1003|3111}}

| latest preview version =

| latest preview date =

Line 22 ⟶ 23:

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) Java 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-mapping solutions.<ref>{{Cite web |title=Apache Empire-db |url=https://empire-db.apache.org/pages/home.html |access-date=2022-03-21 |website=empire-db.apache.org}}</ref>

== Major benefits ==

Line 124 ⟶ 125:

* [[TopLink]]

* [[Apache Struts]]

==References==

{{reflist}}

== External links ==

Line 131 ⟶ 135:

[[Category:Apache Software Foundation projects|Empire-db]]

[[Category:Java (programming language) libraries]]