JEPLayer

Simple persistent Object Relational Mapping (ORM) API on top of JDBC and JTA

News

• 2015-05-07 v1.3 Released. Release Notes. Updated Tutorial "JEPLayer, Java 8 and jOOQ ..."
• 2015-03-13 Tutorial JEPLayer, Java 8 and jOOQ a Match Made in Swiss Heaven.
• 2015-03-09 v1.2 Released. First release in JCenter and Maven Central. Release Notes.
• 2012-11-25 Source code now in GitHub
• 2012-10-27 JEPLayer 1.1 is out. Release Notes.
• 2012-03-28 JEPLayer 1.0.1 is out. Release Notes.

Download Binaries and Docs

Download

Distribution file includes binaries (jar), manual and javadocs.

Artefacts (as of v1.2) are uploaded to JCenter and Maven Central repositories

Maven:

<groupId>com.innowhere</groupId>
<artifactId>jeplayer</artifactId>
<version>(version)</version>
<type>jar</type>

Overview: Why another ORM tool?

JEPLayer was born to provide:

• A simple API to avoid the tedious tasks of JDBC and/or JTA.

• Several optional listeners to fully customize the lifecycle of JDBC persistence (simple and non-invasive IoC). Most of them Java 8 (lambdas) friendly.

• Methods to build simple and complex DAOs, automatic attribute-table field binding or fully customized.

• Object Relational Mapping based on absolutely pure POJOs, no dependencies and annotations in model, fully orthogonal.

• Database schema centric, no impositions of Java data model.

• An extremely simple, automatic, configurable and error-free way to demarcate transactions.

• Does not replace JDBC, instead of this, internal JDBC objects are exposed when required, no new methods provided when existing JDBC methods are enough.

• Ever using PreparedStatement, ever secure.

• PreparedStatement objects are automatically cached and reused.

• Fluid API for queries similar to JPA.

• Extremely simple, automatic, fully configurable, declarative and programmatic, non-invasive and error-free way to demarcate JDBC and JTA transactions

• JTA transaction declaration with the same semantics as JavaEE EJB beans

• Extremely simple and error-free two-phase commit JTA transactions for multiple databases

• False JTA transactions with pure JDBC infrastructure, change to real JTA with a simple method call.

What is Different In JEPLayer

• JEPLayer is simpler than Spring’s JdbcTemplate and transactions and has similar power, the persistent lifecycle can be fully configurable providing more interception points, it does not try to replace JDBC and JDBC/JTA transactions are built-in and tightly integrated. JTA transactions for multiple databases are built-in.

• JEPLayer is programmatic instead of the declarative path of iBatis/MyBatis. Transactions can be optionally declared in methods.

• JEPLayer allows getting the most of the database with no performance penalty and no waste of control typical of transparent persistence ORMs (like Hibernate or JPA).

Online Docs Last Version

Manual PDF

Manual HTML

JavaDocs

Tutorial (only non-JTA)

Examples

See the GitHub repository JEPLayer Examples

Questions and discussions

There is a Google Group for JEPLayer.

Bug Reporting

Use this GitHub project.

Articles/Blogs/Presentations

• 2015-05-21 Tutorial "JEPLayer, Java 8 and jOOQ ..." published in JavaLobby

• 2015-05-07 Tutorial ("JEPLayer, Java 8 and jOOQ ...") updated to v1.3.

• 2015-03-13 Tutorial JEPLayer, Java 8 and jOOQ a Match Made in Swiss Heaven.

• 2012-03-26 Tutorial Horizontal scaling of RDBMS with JTA and JEPLayer at JavaLobby. Spanish version at javaHispano

• 2011-12-18 Tutorial JEPLayer ORM v1.0, JTA Transactions and Fluid Query API at JavaLobby. Spanish version at javaHispano

• 2011-03-22 Tutorial (old version outdated) Java Easy Persistent Layer - JEPLayer

Related

JEPLDroid is a port of JEPLayer for Android, most of features are supported but JTA.