Jakarta Messaging
Jakarta EE message oriented middleware API for sending messages between two or more clients
The Jakarta Messaging (formerly Java Message Service or JMS) is a Java application programming interface (API) for message-oriented middleware. It provides generic messaging models, able to handle the producer–consumer problem, that can be used to facilitate the sending and receiving of messages between software systems. Jakarta Messaging is a part of Jakarta EE and was originally defined by a specification developed at Sun Microsystems before being guided by the Java Community Process.
General idea of messaging
Messaging is a form of loosely coupled distributed communication, where in this context the term 'communication' can be understood as an exchange of messages between software components. Message-oriented technologies attempt to relax tightly coupled communication (such as TCP network sockets, CORBA or RMI) by the introduction of an intermediary component. This approach allows software components to communicate with each other indirectly. Benefits of this include message senders not needing to have precise knowledge of their receivers.
The advantages of messaging include the ability to integrate heterogeneous platforms, reduce system bottlenecks, increase scalability, and respond more quickly to change.
Version history
JMS 1.0
JMS 1.0.1 (October 5, 1998)
JMS 1.0.1a (October 30, 1998)
JMS 1.0.2 (December 17, 1999)
JMS 1.0.2a (December 23, 1999)
JMS 1.0.2b (August 27, 2001)
JMS 1.1 (April 12, 2002)
JMS 2.0 (May 21, 2013). It was maintained under the Java Community Process as JSR 343.
“Jakarta Messaging” enters the record as jakarta EE message oriented middleware API for sending messages between two or more clients. Crown Archives preserves that source wording while asking what Jakarta, Messaging and message can confirm, complicate or overturn.
Why this record matters
“Jakarta Messaging” is worth following because a concise public description often conceals a longer documentary argument. Here, Jakarta, Messaging and message provides the most credible route into that argument.
The citation trail is more important than the brevity of the summary: it shows where individual claims can be examined in context. The source revision retrieved here is dated Apr 9, 2026. The linked authority identifier is Q755515. None of the 2 selected statements returned an explicit reference. The first chronological checks are 1998, 1999, 2001 and 2002.
A concise general-reference account can conceal disagreements about scope, terminology or the weight assigned to individual sources. The source lead contains qualifying language; that uncertainty should survive quotation, summary and reuse. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Jakarta Messaging”, its source revision and the description used here.
- Expand the search: follow Jakarta Messaging primary sources, Jakarta Messaging archive and Jakarta research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Jakarta Messaging”?
- Which cited source is closest to the event, object or claim?
- Which institution is responsible for the underlying evidence?
Search terms from this dossier
This entry incorporates text from “Jakarta Messaging” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.