ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.

JMS

Standardised Java messaging API, a common application foundation for broker-based EDI hubs.

Definition

JMS specifies a client API (Connection, Session, Producer, Consumer) and two models: point-to-point queues and publish/subscribe topics. It decouples EDI code from the underlying broker — the same application runs on ActiveMQ Artemis, IBM MQ or Solace. It distinguishes persistent/non-persistent messages and acknowledgement modes (auto, client, transacted).

Origin

Standardised as JSR 343 (JMS 2.0) under the Java Community Process, then moved to the Eclipse Foundation as Jakarta Messaging (a Jakarta EE specification).

Example in context

Queue q = session.createQueue("EDI.INBOUND");
MessageProducer p = session.createProducer(q);
p.send(session.createTextMessage(edifactPayload));

  • AMQP 1.0 — a possible underlying wire protocol.
  • STOMP — multi-language text alternative.

Last updated: June 20, 2026