Skip to content

Installation

Choose the dependency that matches your runtime. The core module is intended for Java SE applications, while the CDI and configuration integrations are for Jakarta EE-compatible runtimes.

Requirements

  • JDK 21 or later.
  • A Jakarta EE 11 / CDI-compatible runtime is required for the cdi and config modules, such as GlassFish 8 or WildFly 41.
  • The core module is usable in plain Java SE applications because it depends only on javax.sql.DataSource.

Using the core JdbcClient

Use the following dependency when only the core fluent JdbcClient API is required:

<dependency>
    <groupId>io.github.fludakit</groupId>
    <artifactId>fluda-jdbc-client-core</artifactId>
    <version>1.0.0-SNAPSHOT</version>
</dependency>

The core module has no runtime dependency beyond the JDK. It expects a DataSource supplied by the application or runtime environment.

Integrating with CDI

For a CDI-managed JdbcClient, add the CDI artifact:

<dependency>
    <groupId>io.github.fludakit</groupId>
    <artifactId>fluda-jdbc-client-cdi</artifactId>
    <version>1.0.0-SNAPSHOT</version>
</dependency>

This artifact depends on the core module and is intended for a Jakarta EE 11 runtime that provides the Jakarta EE APIs.

Integrating with MicroProfile Config

To configure the library from MicroProfile Config properties, add the optional configuration module:

<dependency>
    <groupId>io.github.fludakit</groupId>
    <artifactId>fluda-jdbc-client-config</artifactId>
    <version>1.0.0-SNAPSHOT</version>
</dependency>

All modules are published with the same version. Replace the snapshot version shown above with the release version used by the application.

After adding the appropriate module, start using the fluent API for executing queries and updates. See quickstart for the shortest path to using the client, and querying and result mapping for more detailed behavior.