FluDa JMS Client: Fluent Jakarta Messaging for Jakarta EE/CDI¶
FluDa JMS Client is a fluent, framework-agnostic client for Jakarta Messaging (JMS 3.1). It mirrors the developer experience of Spring's JmsClient — send, receive, browse, payload conversion and destination resolution — without requiring Spring or any other framework. The core module depends only on the Jakarta Messaging API; the cdi and config modules add CDI wiring and MicroProfile Config for Java SE and Jakarta EE.
The project is organized into five published modules:
| Module | Artifact | Description |
|---|---|---|
core |
fluda-jms-core |
The fluent JmsClient API, the MessageConverter and DestinationResolver SPIs, CachingConnectionFactory, and the JmsConfig value type. Depends only on the JDK and the Jakarta Messaging API. |
config |
fluda-jms-config |
Maps fluda.jms.* MicroProfile Config properties to a JmsConfig bean, and builds Artemis or Qpid JMS connection factories from provider-specific sections. |
cdi |
fluda-jms-cdi |
Produces the CachingConnectionFactory and JmsClient beans, resolving the underlying JMSContext, ConnectionFactory or a configured provider section, and applying any optional JmsConfig, MessageConverter and DestinationResolver beans. |
artemis |
fluda-jms-artemis |
Builds an Artemis ConnectionFactory from fluda.jms.artemis.* properties. |
qpid |
fluda-jms-qpid |
Builds a Qpid JMS ConnectionFactory from fluda.jms.qpid.* properties. |
Key concepts¶
JmsClient— the entry point. Build it from aConnectionFactoryin Java SE (the client creates the context) or from an existingJMSContexton Jakarta EE (the container owns it). A client is not thread-safe: it shares oneJMSContextacross all operations, so create one client per thread.DestinationSpec— whatclient.destination(...)returns. It carries the send, receive and browse operations for one destination; the client is immutable, so the spec is cheap to create per call.MessageConverter— turns payloads into JMS messages and back. The defaultSimpleMessageConverterhandlesString,byte[],MapandSerializablepayloads;JsonbMessageConverteris an opt-in JSON-B alternative, and you can plug in your own.DestinationResolver— turns a destination name into aDestination. The defaultSimpleDestinationResolvercreates a queue per name (atopic:prefix selects a topic) and caches the result.CachingConnectionFactory— aConnectionFactorydecorator that keeps oneJMSContextper thread, so clients reuse a connection instead of opening one each.JmsClientnever closes the context it is given; this decorator is how a Java SE application manages that lifecycle.JmsConfig— an immutable bundle of credentials, session mode and default destination name, applied to a builder withconfig(...). Theconfigmodule produces it fromfluda.jms.*properties.
v1 scope
v1 covers fluent send, receive and browse over a JMSContext, payload conversion, connection caching, and CDI wiring for Java SE and Jakarta EE. Annotation-driven @JmsListener containers and a CDI event bridge are deferred to 1.1; XA transactions are out of scope.
Reading order¶
- Start with getting started to add the dependencies and send your first message in Java SE or CDI.
- For Jakarta EE servers, see Jakarta EE.
- The runnable examples in fludakit/examples cover plain Java SE (
jms-client-vanilla), CDI with Artemis (jms-client-artemis), AMQP 1.0 with Qpid JMS (jms-client-qpid) and Jakarta EE on GlassFish and WildFly (jms-client-jakartaee).