Introduction¶
FluDa (Fluent Data Toolkit for Jakarta EE/CDI) is a lightweight, modular data-access suite designed for standard Jakarta EE and CDI environments. It provides a developer-friendly, fluent programming model that mirrors modern data APIs like Spring's JdbcClient — without requiring Spring or introducing bulky dependencies.
FluDa is organized into five standalone modules:
JDBC Client¶
A lightweight, type-safe, fluent query engine built directly over JDBC. The core module has zero framework dependencies — just JDBC and a DataSource.
- Fluent API with named and positional parameters
- POJO mapping with custom row mappers
- Generated key support
- CDI integration for dependency injection
Get started with JDBC Client →
SQL Initialization¶
Automates database schema management and data population on application startup. Perfect for development and testing scenarios where you need to set up database state automatically.
- Schema creation from SQL scripts
- Data population from SQL files
- CDI integration for automatic execution
Transaction Support¶
Container-agnostic declarative and programmatic transaction boundaries backed directly by a standard DataSource or JPA. Works in Java SE, Servlet containers, and Jakarta EE environments.
@Transactionalinterceptor for CDI beans- Resource-local transactions without JTA
- Transaction propagation control
- Transaction-phase callbacks and events
Get started with Transaction Support →
Mail¶
A simple mail abstraction with built-in Jakarta Mail (SMTP) support and pluggable providers for third-party services like SendGrid.
MailSenderinterface withJakartaMailSenderimplementation- Fluent
MailBuilderfor composing messages - Template support with FreeMarker and simple placeholder processing
- CDI integration with MicroProfile Config properties
- Pluggable providers — implement
MailSenderfor any email service
JMS Client¶
A fluent Jakarta Messaging client in the style of Spring's JmsClient, with CDI wiring and MicroProfile Config for Java SE and Jakarta EE.
JmsClientwith fluent send, receive, receive-selected and browse operationsMessageConverterSPI —SimpleMessageConverterby default, optional JSON-BCachingConnectionFactoryreuses oneJMSContextper thread- CDI producers that resolve a
JMSContext, aConnectionFactoryor a configured Artemis/Qpid section