# JDBC Published articles for JDBC. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## JDBC batching can still issue one round trip per row unless driver statement rewriting is enabled DevFeed: [JDBC batching can still issue one round trip per row unless driver statement rewriting is enabled]() Original publisher: [Read original article]() Author: hello@ankit-rana.com Published: 2026-09-03T00:00:00Z Content type: tutorial Language: en Sources: [Ankit Rana | Mechanical Sympathy]() Topics: [Databases](), [Latency](), [client](), [Code]() Tags: [batching](), [bulk-load](), [client](), [cost](), [database](), [database-performance](), [durability](), [jdbc](), [latency](), [mysql](), [postgresql](), [server](), [sql]() ### AI overview For small database writes, network round trips and transaction overhead can dominate the actual insert work. The article explains that JDBC batching may accept rows into a client-side batch while still sending separate statements unless driver-side statement rewriting is enabled, and that autocommit adds a transaction and durability barrier per row. ### Source excerpt For small writes the per-statement overhead dominates the actual work, so throughput is set by round trips rather than by the database. JDBC batching is the usual fix and it silently does nothing on the wire unless the driver is told to rewrite the statements, so addBatch can look correct while still issuing one round trip per row. Autocommit compounds it by turning every row into its own transaction and its own durability barrier, which is the difference between one fsync and a hundred thousand. ## How INTEGER and INT Produced Different Schemas in Debezium DevFeed: [How INTEGER and INT Produced Different Schemas in Debezium]() Original publisher: [Read original article]() Author: Prathit Malik Published: 2026-09-02T07:02:02Z Content type: article Language: en Sources: [Grofers]() Topics: [MySQL](), [migration](), [Streaming](), [Kafka](), [SQL](), [Databases]() Tags: [big-data](), [blinkit](), [change](), [database](), [debezium](), [jdbc](), [kafka](), [migration](), [mysql](), [open-source](), [schema](), [sql](), [streaming]() ### AI overview This article investigates a Debezium CDC pipeline failure caused by MySQL INT and INTEGER synonyms being treated as different types. The resulting schema mismatch produced an Integer where a downstream consumer expected a Long, causing a ClassCastException on every batch. It explains how streaming and snapshot schema handling differ and how routine migrations exposed the problem. ### Source excerpt A Debezium investigation: how MySQL synonyms INT and INTEGER were treated as different types. One of our CDC pipelines started failing with a ClassCastException on every batch. java.lang.ClassCastException: class java.lang.Integer cannot be cast to class java.lang.Long The pipeline was producing an Integer, but the downstream consumer expected a Long. Every run failed in the same way, which pointed us toward a schema mismatch rather than an issue with individual records. Background: how CDC works To see why a mismatch like that can hide for years, it helps to know how CDC actually works. Most companies replicate their transactional database (MySQL, Postgres, something similar) into a separate data lake for analytics, rather than querying the source directly, and Change Data Capture (CDC) is what keeps that copy in sync: it tails the database's transaction log and replays every insert, update, and delete downstream. Debezium is the most widely used open-source CDC tool for MySQL, and it builds a table's schema in one of two ways that are supposed to agree but do not always. Streaming mode: the first time it sees a CREATE TABLE or ALTER TABLE in the binlog, it parses the raw SQL text and writes the result to its own internal Kafka topic, database.history.kafka.topic. Every restart after that rebuilds the in-memory schema by replaying that topic, not by re-reading the binlog. Snapshot mode: reads the table definition fresh through MySQL's JDBC metadata interface, which normalizes types, every time it runs. Schema Registry sits downstream of both: each connector writes whatever schema it built into the registry, but neither connector reads its own schema back from it. Keep that in mind; it matters later. The trigger: a routine migration With that in mind, here's what actually happened to us. Rewind two years: one of our upstream service teams added a few columns to a source table as part of a standard schema change. ALTER TABLE ADD COLUMN length double NU ## Keycloak 26.1.0 released DevFeed: [Keycloak 26.1.0 released]() Original publisher: [Read original article]() Author: Keycloak Team Published: 2025-01-15T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [Database](), [Cloud](), [OpenTelemetry](), [tracing](), [openjdk](), [version]() Tags: [cloud](), [database](), [deprecated](), [idm](), [jdbc](), [kerberos](), [keycloak](), [keycloak-release](), [kubernetes](), [ldap](), [openid-connect](), [openjdk](), [opentelemetry](), [release](), [saml](), [sso](), [tracing](), [version]() ### AI overview Keycloak 26.1.0 changes the default cluster transport stack to database-based discovery, simplifying cloud deployments by removing the need for multicast and dynamic TCP ports. The release also enables virtual threads on OpenJDK 21, makes OpenTelemetry tracing fully supported and enabled by default, and includes configuration and credential-issuance improvements. ### Source excerpt To download the release go to Keycloak downloads. Highlights Transport stack jdbc-ping as new default Keycloak now uses by default its database to discover other nodes of the same cluster, which removes the need of additional network related configurations especially for cloud providers. It is also a default that will work out-of-the-box in cloud environments. Previous versions of Keycloak used as a default UDP multicast to discover other nodes to form a cluster and to synchronize the replicated caches of Keycloak. This required multicast to be available and to be configured correctly, which is usually not the case in cloud environments. Starting with this version, the default changes to the jdbc-ping configuration which uses Keycloak's database to discover other nodes. As this removes the need for multicast network capabilities and UDP and no longer using dynamic ports for the TCP-based failure detection, this is a simplification and a drop-in replacement for environments which used the previous default. To enable the previous behavior, choose the transport stack udp which is now deprecated. The Keycloak Operator will continue to configure kubernetes as a transport stack. See the Configuring distributed caches guide for more information. Virtual Threads enabled for Infinispan and JGroups thread pools Starting from this release, Keycloak automatically enables the virtual thread pool support in both the embedded Infinispan and JGroups when running on OpenJDK 21. This removes the need to configure the JGroups thread pool, the need to align the JGroups thread pool with the HTTP worker thread pool, and reduces the overall memory footprint. OpenTelemetry Tracing supported In the previous release, the OpenTelemetry Tracing feature was preview and is fully supported now. It means the opentelemetry feature is enabled by default. There were made multiple improvements to the tracing capabilities in Keycloak such as: Configuration via Keycloak CR in Keycloak Operator Custom sp ## Maven Coordinates of the most popular JDBC Drivers DevFeed: [Maven Coordinates of the most popular JDBC Drivers]() Original publisher: [Read original article]() Author: lukaseder Published: 2023-12-13T11:25:44Z Content type: tutorial Language: en Sources: [jOOQ]() Topics: [Maven](), [Maven Central](), [Database]() Tags: [database](), [drivers](), [integration](), [java](), [jdbc](), [jdbc-drivers](), [jooq](), [maven](), [maven-central](), [sql]() ### AI overview A list of Maven coordinates for popular JDBC drivers used in jOOQ integration tests, with guidance to verify current versions on Maven Central and check driver licenses before downloading. ### Source excerpt Do you need to add a JDBC driver to your application, and don't know its Maven coordinates? This blog post lists the most popular drivers from the jOOQ integration tests. Look up the latest versions directly on https://central.sonatype.com/ with parameters g:groupId a:artifactId, for example, the H2 database and driver: https://central.sonatype.com/search?q=g%3Acom.h2database+a%3Ah2 The list only includes drivers ... Continue reading Maven Coordinates of the most popular JDBC Drivers -> ## JDBC Connection URLs of the Most Popular RDBMS DevFeed: [JDBC Connection URLs of the Most Popular RDBMS]() Original publisher: [Read original article]() Author: lukaseder Published: 2023-12-01T11:12:59Z Content type: tutorial Language: en Sources: [jOOQ]() Topics: [rdbms]() Tags: [connection-url](), [driver](), [jdbc](), [popular](), [rdbms](), [sql]() ### AI overview A reference for finding JDBC connection URLs and driver names for popular relational database management systems. ### Source excerpt Need to connect to your RDBMS with JDBC and don't have the JDBC connection URL or driver name at hand? No problem, just look up your RDBMS below: ## How to Pass a Table Valued Parameter to a T-SQL Function with jOOQ DevFeed: [How to Pass a Table Valued Parameter to a T-SQL Function with jOOQ]() Original publisher: [Read original article]() Author: lukaseder Published: 2023-04-25T12:16:30Z Content type: tutorial Language: en Sources: [jOOQ]() Topics: [sql-server](), [SQL](), [Java](), [Code]() Tags: [code](), [code-generation](), [code-generator](), [how-to](), [java](), [jdbc](), [jooq](), [jooq-in-use](), [sql-server](), [t-sql](), [table-valued-function](), [table-valued-parameter]() ### AI overview This tutorial explains how to pass a Microsoft T-SQL table-valued parameter to a function using jOOQ. It covers native T-SQL and JDBC usage, then shows how jOOQ's code generator produces Java types and methods for calling the function and accessing its result rows. ### Source excerpt Microsoft T-SQL supports a language feature called table-valued parameter (TVP), which is a parameter of a table type that can be passed to a stored procedure or function. For example, you may write: This function takes a table-valued parameter (TVP), and produces a result set containing the cross product of the parameter table with itself. ... Continue reading How to Pass a Table Valued Parameter to a T-SQL Function with jOOQ -> ## 3.18.0 Release with Support for more Diagnostics, SQL/JSON, Oracle Associative Arrays, Multi dimensional Arrays, R2DBC 1.0 DevFeed: [3.18.0 Release with Support for more Diagnostics, SQL/JSON, Oracle Associative Arrays, Multi dimensional Arrays, R2DBC 1.0]() Original publisher: [Read original article]() Author: lukaseder Published: 2023-03-08T16:34:56Z Content type: release Language: en Sources: [jOOQ]() Topics: [releases](), [SQL](), [JSON](), [Oracle Database](), [PostgreSQL](), [Kotlin]() Tags: [jdbc](), [jooq](), [kotlin](), [oracle](), [r2dbc](), [release](), [sql](), [sql-json](), [uncategorized]() ### AI overview jOOQ 3.18.0 is a release focused on expanded SQL diagnostics and SQL/JSON support, including vendor-specific MySQL and PostgreSQL features. It also adds improvements for the Query Object Model, Oracle associative arrays, PostgreSQL multidimensional arrays, Kotlin, and R2DBC 1.0. ### Source excerpt DiagnosticsListener improvements A lot of additional diagnostics have been added, including the automated detection of pattern replacements, helping you lint your SQL queries irrespective of whether you're using jOOQ to write your SQL, or if you're using it as a JDBC / R2DBC proxy for an existing application. A lot of these diagnostics are available ... Continue reading 3.18.0 Release with Support for more Diagnostics, SQL/JSON, Oracle Associative Arrays, Multi dimensional Arrays, R2DBC 1.0 -> ## How to use jOOQ's Converters with UNION Operations DevFeed: [How to use jOOQ's Converters with UNION Operations]() Original publisher: [Read original article]() Author: lukaseder Published: 2023-03-02T11:18:17Z Content type: tutorial Language: en Sources: [jOOQ]() Topics: [SQL](), [Databases]() Tags: [ad-hoc-converter](), [converter](), [how-to](), [jdbc](), [jooq](), [jooq-in-use](), [lambda](), [multiset](), [r2dbc](), [rdbms](), [sql](), [union]() ### AI overview This tutorial explains how jOOQ ad-hoc converters behave with UNION operations. Because conversion occurs on the client after JDBC retrieval, it does not affect server-side UNION processing, and jOOQ applies the result-fetching row type from the first subquery. The article recommends applying client-side conversions consistently across subqueries or moving the conversion to the server when appropriate. ### Source excerpt jOOQ 3.15 introduced the concept of an ad-hoc converter, a converter that is applied "ad-hoc" to a single query. It uses the same underlying mechanisms as any ordinary Converter that is attached to generated code for use in every query. An example of such an ad-hoc converter is this: While there are other ways to ... Continue reading How to use jOOQ's Converters with UNION Operations -> ## Why You Should Execute jOOQ Queries With jOOQ DevFeed: [Why You Should Execute jOOQ Queries With jOOQ]() Original publisher: [Read original article]() Author: lukaseder Published: 2023-01-18T11:46:25Z Content type: opinion Language: en Sources: [jOOQ]() Topics: [SQL](), [Java](), [Databases](), [Compiler]() Tags: [code-generation](), [crud](), [csv](), [execution](), [export](), [identity](), [import](), [java](), [jdbc](), [jooq](), [jooq-in-use](), [jpa](), [json](), [mapping](), [multiset](), [nested-collections](), [nested-records](), [orm](), [r2dbc](), [sql](), [stored-procedures](), [type-safety](), [udt](), [updatablerecord](), [user-defined-types](), [xml]() ### AI overview The article argues that queries built with jOOQ should generally also be executed with jOOQ. It explains that jOOQ preserves type safety and structured result mapping during execution, whereas extracting SQL and bind values for JDBC-level execution loses compiler knowledge of the result set. It acknowledges limited use cases for executing jOOQ-generated SQL elsewhere, such as a small number of dynamic queries in an otherwise JPA-based application. ### Source excerpt Previously on this blog, I've written a post explaining why you should use jOOQ's code generator, despite the possibility of using jOOQ without it. In a similar fashion, as I've answered numerous jOOQ questions on Stack Overflow, where someone used jOOQ to build a query, but then executed it elsewhere, including on: jOOQ itself isn't ... Continue reading Why You Should Execute jOOQ Queries With jOOQ -> ## jOOQ's R2DBC LoggingConnection to log all SQL statements DevFeed: [jOOQ's R2DBC LoggingConnection to log all SQL statements]() Original publisher: [Read original article]() Author: lukaseder Published: 2023-01-17T10:12:05Z Content type: article Language: en Sources: [jOOQ]() Topics: [SQL](), [reactive](), [Code]() Tags: [code](), [dependency](), [hibernate](), [jdbc](), [jdbctemplate](), [jooq](), [jooq-in-use](), [logging](), [native](), [r2dbc](), [reactive](), [sql]() ### AI overview The article introduces jOOQ's LoggingConnection for R2DBC clients, which logs reactive SQL queries. It notes that the utility is available in jOOQ versions 3.18.0, 3.17.7, and 3.16.13, and that standalone code is available on GitHub. ### Source excerpt jOOQ already has a LoggingConnection (see also the manual), which acts as a JDBC proxy Connection to log all SQL statements that are executed by any JDBC client (including Hibernate, MyBatis, JdbcTemplate, native JDBC, etc.). Starting from jOOQ 3.18.0, 3.17.7, and 3.16.13, a LoggingConnection is now also available for R2DBC clients to log all reactive ... Continue reading jOOQ's R2DBC LoggingConnection to log all SQL statements -> ## When to Use jOOQ and When to Use Native SQL DevFeed: [When to Use jOOQ and When to Use Native SQL]() Original publisher: [Read original article]() Author: lukaseder Published: 2022-12-08T13:53:02Z Content type: comparison Language: en Sources: [jOOQ]() Topics: [SQL](), [Databases](), [rdbms](), [Test-driven development](), [Testcontainers]() Tags: [cons](), [examples](), [jdbc](), [jdbctemplate](), [jdbi](), [jooq](), [jooq-in-use](), [native-sql](), [plain-jdbc](), [plain-sql-templating](), [rdbms](), [sql](), [sql-json](), [stored-procedures](), [tdd](), [testcontainers]() ### AI overview This comparison explains when to use the jOOQ API and when to use native SQL for complex queries. It describes jOOQ's advantages for dynamic SQL, multiple database dialects, type safety, data mapping, stored procedures, security, exports, and diagnostics, while noting usability drawbacks for large static queries with many CTEs or derived tables. ### Source excerpt A frequently encountered doubt people have when using jOOQ is to decide when a "complex" query should be written using jOOQ API vs. when it should be implemented using native SQL. The jOOQ manual is full of side by side examples of the same query, e.g. Using jOOQ: Using native SQL: In the native SQL ... Continue reading When to Use jOOQ and When to Use Native SQL -> ## Calling Procedures with Default Parameters using JDBC or jOOQ DevFeed: [Calling Procedures with Default Parameters using JDBC or jOOQ]() Original publisher: [Read original article]() Author: lukaseder Published: 2022-10-21T14:35:39Z Content type: tutorial Language: en Sources: [jOOQ]() Topics: [Code](), [Reason](), [SQL](), [Oracle Database](), [PostgreSQL]() Tags: [db2](), [default-parameters](), [java](), [jdbc](), [jooq](), [jooq-in-use](), [oracle](), [pl-pgsql](), [pl-sql](), [postgresql](), [sql-server](), [stored-functions](), [stored-procedures](), [syntax]() ### AI overview This tutorial explains how to call stored procedures with default parameters using JDBC or jOOQ. It shows how directly instantiating a procedure call allows Java code to omit parameters that have database-side defaults, and notes that syntax varies across supported relational database systems. ### Source excerpt Using jOOQ's code generator to call stored procedures is a popular reason to use jOOQ. For example, when you have a procedure like the following Oracle PL/SQL procedure: jOOQ will generate code for you to call very simply, like this: This will execute the following, taking care of binding all IN and OUT parameters for ... Continue reading Calling Procedures with Default Parameters using JDBC or jOOQ -> ## A Brief Overview over the Most Common jOOQ Types DevFeed: [A Brief Overview over the Most Common jOOQ Types]() Original publisher: [Read original article]() Author: lukaseder Published: 2022-09-06T12:30:37Z Content type: tutorial Language: en Sources: [jOOQ]() Topics: [SQL](), [API](), [Databases](), [Structured-data]() Tags: [api](), [api-design](), [cheat-sheet](), [configuration](), [context](), [dependency-injection](), [dsl](), [jdbc](), [jooq](), [jooq-3-17](), [jooq-in-use](), [logging](), [overview](), [queryparts](), [r2dbc](), [sql](), [syntax](), [type-system](), [types]() ### AI overview This tutorial provides a cheat sheet of the most important types in the jOOQ API, covering configuration, scopes, settings, and DSL APIs. It notes that jOOQ 3.17 includes more than 160 settings and explains how several type groups support query construction, execution, lifecycle management, and dependency injection. ### Source excerpt For new users working with jOOQ for the first time, the number of types in the jOOQ API can be overwhelming. The SQL language doesn't have many such "visible" types, although if you think about SQL the way jOOQ does, then they're there just the same, but hidden from users via an English style syntax. ... Continue reading A Brief Overview over the Most Common jOOQ Types -> ## The Many Ways to Return Data From SQL DML DevFeed: [The Many Ways to Return Data From SQL DML]() Original publisher: [Read original article]() Author: lukaseder Published: 2022-08-23T15:02:04Z Content type: tutorial Language: en Sources: [jOOQ]() Topics: [SQL](), [Databases](), [PostgreSQL](), [Oracle Database](), [CockroachDB]() Tags: [article](), [cockroachdb](), [data-change-delta-table](), [database](), [firebird](), [generated-keys](), [how-to](), [jdbc](), [jooq](), [mariadb](), [postgresql](), [return-generated-keys](), [returning](), [sql]() ### AI overview This article explains ways to return data from SQL DML statements using jOOQ across multiple SQL dialects and directly through JDBC. It covers RETURNING-style syntax, Oracle PL/SQL emulation, PostgreSQL support, and the SQL standard's data-change-table reference approach. ### Source excerpt Probably the hardest thing to standardise in SQL is RETURNING data from DML statements. In this article, we'll look at various ways of doing that with jOOQ, in many of jOOQ's supported dialects, and with JDBC directly. How to do it with jOOQ Assuming the usual table from the sakila database: jOOQ took syntactic inspiration ... Continue reading The Many Ways to Return Data From SQL DML -> ## The Best Way to Call Stored Procedures from Java: With jOOQ DevFeed: [The Best Way to Call Stored Procedures from Java: With jOOQ]() Original publisher: [Read original article]() Author: lukaseder Published: 2022-07-28T13:11:59Z Content type: tutorial Language: en Sources: [jOOQ]() Topics: [Code generation](), [Java](), [SQL](), [data-processing](), [Server]() Tags: [code-generation](), [code-generator](), [data-processing](), [java](), [jdbc](), [jdbc-drivers](), [jooq](), [jooq-in-use](), [oracle](), [pl-pgsql](), [pl-sql](), [postgresql](), [rdbms](), [schema](), [sql](), [stored-functions](), [stored-procedures](), [t-sql](), [udts]() ### AI overview This tutorial explains how to call stored procedures from Java using jOOQ-generated code. It contrasts JDBC calls with generated procedure stubs and convenience methods, covering parameter handling, database types, and support for procedures, functions, packages, and UDTs. ### Source excerpt jOOQ is mainly known for its powerful type safe, embedded, dynamic SQL capabilities that are made available through code generation. However, a secondary use case of code generation is to use it for stored procedures (possibly exclusively for stored procedures). Stored procedures are powerful ways of moving complex data processing logic to the server. This ... Continue reading The Best Way to Call Stored Procedures from Java: With jOOQ -> ## The Many Different Ways to Fetch Data in jOOQ DevFeed: [The Many Different Ways to Fetch Data in jOOQ]() Original publisher: [Read original article]() Author: lukaseder Published: 2022-05-19T07:29:09Z Content type: tutorial Language: en Sources: [jOOQ]() Topics: [jooq](), [Java](), [SQL]() Tags: [collections](), [collector](), [convenience](), [fetching](), [java](), [jdbc](), [joo-f6a0c60d3d07](), [jooq](), [jooq-in-use](), [optional](), [r2dbc](), [reactive-streams](), [sql](), [stream-api](), [streams]() ### AI overview This tutorial explains several ways to fetch data with jOOQ, including eager result-set fetching, external and internal iteration, single-record retrieval, optional results, and resource-managed fetching for large data sets. ### Source excerpt The jOOQ API is all about convenience, and as such, an important operation (the most important one?) like fetch() must come with convenience, too. The default way to fetch data is this: It fetches the entire result set into memory and closes the underlying JDBC resources eagerly. But what other options do we have? Iterable ... Continue reading The Many Different Ways to Fetch Data in jOOQ -> ## Setting the JDBC Statement.setFetchSize() to 1 for Single Row Queries DevFeed: [Setting the JDBC Statement.setFetchSize() to 1 for Single Row Queries]() Original publisher: [Read original article]() Author: lukaseder Published: 2022-05-11T08:55:41Z Content type: article Language: en Sources: [jOOQ]() Topics: [Benchmark](), [Databases](), [rdbms]() Tags: [benchmark](), [db2](), [fetch](), [fetch-size](), [fetchsize](), [jdbc](), [jooq](), [jooq-development](), [mysql](), [ojdbc](), [optimisation](), [oracle](), [postgresql](), [rdbms](), [sql](), [sql-server]() ### AI overview This article examines whether jOOQ should call JDBC Statement.setFetchSize(1) by default for queries expected to return at most one row. It proposes measuring the effect with a JMH benchmark and discusses limitations on comparing execution speed across RDBMS. ### Source excerpt An interesting hint by Vladimir Sitnikov has made me think about a new benchmark for jOOQ: The benchmark should check whether single row queries should have a JDBC Statement.setFetchSize(1) call made to them by default. The Javadoc of the method says: Gives the JDBC driver a hint as to the number of rows that should ... Continue reading Setting the JDBC Statement.setFetchSize() to 1 for Single Row Queries -> ## Clojure SQL library showdown DevFeed: [Clojure SQL library showdown]() Original publisher: [Read original article]() Published: 2015-12-28T00:00:00Z Content type: comparison Language: en Sources: [Adam Bard]() Topics: [Clojure](), [SQL](), [Library](), [Object-relational mapping]() Tags: [clojure](), [compare](), [dsls](), [jdbc](), [library](), [orm](), [sql]() ### AI overview A comparison of several Clojure SQL DSLs and libraries, including Korma and HoneySQL, against JDBC. The author discusses the trade-offs between writing SQL directly and using abstractions or ORM-style tools. ### Source excerpt When it comes to database access, I've become less particular over the years as I've gotten more and more comfortable with SQL. These days I'm happier to write the SQL to get just the thing I want, than wrestle with an ORM to produce the same thing. Nevertheless, there's something to be said for abstractions over SQL, and they seem to have lasting popularity. In this post, I'll compare a few popular SQL DSLs for Clojure, and contrast them all with their mutual pappy, clojure. ## JPA2 with Guice DevFeed: [JPA2 with Guice]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2013-06-26T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [Java](), [Maven](), [Database](), [Architecture & Design]() Tags: [bugs](), [database](), [dependencies](), [java](), [jdbc](), [maven](), [project](), [pull-requests]() ### AI overview A tutorial on using a Java persistence project base with Guice, Guava, EclipseLink, and Apache B-Val. It covers creating a Maven project, adding dependencies and a JDBC driver, defining a model and DAO, configuring bindings, and injecting repositories. ### Source excerpt Some time ago, I posted here about a simple project that I've done in my post-graduation classes. Since I need it in other projects, and also some friends ended up using it in small projects, I decided to evolve it a little bit.