Jakarta Messaging

Total Page：16

File Type：pdf, Size：1020Kb

Jakarta Messaging Jakarta Messaging Team, https://projects.eclipse.org/projects/ee4j.jms 3.0, October 23, 2020: Final Table of Contents Copyright. 1 Eclipse Foundation Specification License . 1 Disclaimers. 2 1. Introduction . 3 1.1. Overview of Jakarta Messaging . 3 1.1.1. What is messaging?. 3 1.1.2. The objectives of Jakarta Messaging. 3 1.1.3. Jakarta Messaging domains . 4 1.1.4. What Jakarta Messaging does not include . 4 1.1.5. Java SE and Jakarta EE support . 5 1.2. What is new in Jakarta Messaging 2.0? . 5 2. Architecture . 7 2.1. Overview. 7 2.2. What is a Jakarta Messaging application? . 7 2.3. Administration. 7 2.4. Two messaging styles. 8 2.5. Jakarta Messaging APIs . 8 2.6. Interfaces common to multiple APIs . 9 2.7. Classic API interfaces . 9 2.8. Simplified API interfaces. 10 2.8.1. Goals of the simplified API . 11 2.8.2. Key features of the simplified API. 12 2.9. Legacy domain-specific API interfaces . 12 2.10. Relationship between interfaces. 14 2.11. Terminology for sending and receiving messages . 15 2.12. Developing a Jakarta Messaging application . 15 2.12.1. Developing a Jakarta Messaging client . 15 2.13. Security . 16 2.14. Multi-threading . 16 2.15. Triggering clients . 18 2.16. Request/reply. 18 3. Jakarta Messaging message model. 19 3.1. Background . 19 3.2. Goals. 19 3.3. Jakarta Messaging messages . 19 3.4. Message header fields . 20 3.4.1. JMSDestination . 20 3.4.2. JMSDeliveryMode . 20 3.4.3. JMSMessageID . 20 3.4.4. JMSTimestamp . 21 3.4.5. JMSCorrelationID . 21 3.4.6. JMSReplyTo. 22 3.4.7. JMSRedelivered . 22 3.4.8. JMSType. 22 3.4.9. JMSExpiration . 23 3.4.10. JMSPriority . 23 3.4.11. How message header values are set. 23 3.4.12. Overriding message header fields . 25 3.4.13. JMSDeliveryTime . 25 3.5. Message properties. 25 3.5.1. Property names . 26 3.5.2. Property values . ..

170

Copy Link

Recommended publications

Red Hat Jboss Enterprise Application Platform 7.4 Developing Jakarta Enterprise Beans Applications
Red Hat JBoss Enterprise Application Platform 7.4 Developing Jakarta Enterprise Beans Applications Instructions and information for developers and administrators who want to develop and deploy Jakarta Enterprise Beans applications for Red Hat JBoss Enterprise Application Platform. Last Updated: 2021-09-10 Red Hat JBoss Enterprise Application Platform 7.4 Developing Jakarta Enterprise Beans Applications Instructions and information for developers and administrators who want to develop and deploy Jakarta Enterprise Beans applications for Red Hat JBoss Enterprise Application Platform. Legal Notice Copyright © 2021 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/ . In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
[Show full text]
Verteilte Systeme
Verteilte Systeme Interprozesskommunikation & Entfernter Aufruf 1 Interprozesskommunikation Applikationen, Dienste RemoteMethodInvocation und RemoteProcedureCall Middleware- Anforderung/Antwort-Protokoll (request-reply protocol) schichten Marshalling und externe Datendarstellung UniversalDatagramProtocol und TransmissionControlProtocol ACHTUNG: In der „Zweitliteratur“ wird RMI oft mit Java RMI gleichgesetzt! Korrekt ist: Java-RMI ist eine konkrete Realisierung des RMI-Konzeptes. 2 Interprozesskommunikation u Anwendungsprogramme laufen in Prozessen ab. u Ein Prozess ist ein Objekt des Betriebssystems, durch das Anwendungen sicheren Zugriff auf die Ressourcen des Computers erhalten. Einzelne Prozesse sind deshalb gegeneinander isoliert. (Aufgabe des Betriebssystems) u Damit zwei Prozesse Informationen austauschen können, müssen sie Interprozesskommunikation (interprocess- communication, IPC) verwenden. u IPC basiert auf (Speicher-/Nachrichtenbasierter) Kommunikation 1. gemeinsamen Speicher: für VS nicht direkt verwendbar 2. Austausch von Nachrichten (= Bytefolge) über einen Kommunikationskanal zwischen Sender und Empfänger. 3 Interprozesskommunikation •Betriebssystem: Koordiniert IPC innerhalb dieses BS. •IPC in verteilten Systemen geschieht ausschließlich über Nachrichten •Koordination der IPC durch Middleware oder/und durch Entwickler •Hierbei sind gewisse Normen zu beachten, damit die Kommunikation klappt!! •Protokoll := Festlegung der Regeln und des algorithmischen Ablaufs bei der Kommunikation zwischen zwei oder mehr Partnern Nachricht
[Show full text]
Metro User Guide Metro User Guide Table of Contents
Metro User Guide Metro User Guide Table of Contents Preface .............................................................................................................................. x 1. Introduction to Metro ....................................................................................................... 1 1.1. Required Software ................................................................................................ 1 1.2. What is WSIT? .................................................................................................... 1 1.2.1. Bootstrapping and Configuration ................................................................... 2 1.2.2. Message Optimization Technology ................................................................ 3 1.2.3. Reliable Messaging Technology .................................................................... 4 1.2.4. Security Technology ................................................................................... 4 1.3. How Metro Relates to .NET Windows Communication Foundation (WCF) ...................... 5 1.4. Metro Specifications ............................................................................................. 5 1.4.1. Bootstrapping and Configuration Specifications ............................................... 7 1.4.2. Message Optimization Specifications ............................................................. 8 1.4.3. Reliable Messaging Specifications ............................................................... 10 1.4.4. Security Specifications
[Show full text]
Oracle Utilities Testing Accelerator Licensing Information User Manual Release 6.0.0.3.0 F35952-01
Oracle Utilities Testing Accelerator Licensing Information User Manual Release 6.0.0.3.0 F35952-01 June 2021 Oracle Utilities Testing Accelerator Licensing Information User Manual, Release 6.0.0.3.0 Copyright © 2019, 2021 Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation"
[Show full text]
Jakarta EE Web Profile 8 Specification Document
Jakarta EE WebProfile Jakarta EE Platform Team, https://projects.eclipse.org/projects/ee4j.jakartaee- platform 8, August 26, 2019 Table of Contents Copyright. 1 Eclipse Foundation Specification License . 1 Disclaimers. 2 1. Introduction . 3 1.1. Target and Rationale for the Web Profile . 3 1.2. Determining Applicable Requirements . 4 1.3. Acknowledgements for Version 6 . 5 1.4. Acknowledgements for Version 7 . 5 1.5. Acknowledgements for Version 8 . 6 2. Web Profile Definition. 7 2.1. Required Components . 7 2.2. Optional Components. 7 2.3. Additional Requirements . 8 Appendix A: Revision History . 9 A.1. Changes in Final Release Draft . 9 A.1.1. Editorial Changes . 9 Appendix B: Related Documents. 10 Copyright Specification: Jakarta EE WebProfile Version: 8 Status: Final Release Release: August 26, 2019 Copyright Copyright (c) 2019 Eclipse Foundation. Eclipse Foundation Specification License By using and/or copying this document, or the Eclipse Foundation document from which this statement is linked, you (the licensee) agree that you have read, understood, and will comply with the following terms and conditions: Permission to copy, and distribute the contents of this document, or the Eclipse Foundation document from which this statement is linked, in any medium for any purpose and without fee or royalty is hereby granted, provided that you include the following on ALL copies of the document, or portions thereof, that you use: • link or URL to the original Eclipse Foundation document. • All existing copyright notices, or if one does not exist, a notice (hypertext is preferred, but a textual representation is permitted) of the form: "Copyright (c) [$date-of-document] Eclipse Foundation, Inc.
[Show full text]
Red Hat Jboss Enterprise Application Platform 7.3 Developing EJB Applications
Red Hat JBoss Enterprise Application Platform 7.3 Developing EJB Applications Instructions and information for developers and administrators who want to develop and deploy Enterprise JavaBeans (EJB) applications for Red Hat JBoss Enterprise Application Platform. Last Updated: 2021-08-27 Red Hat JBoss Enterprise Application Platform 7.3 Developing EJB Applications Instructions and information for developers and administrators who want to develop and deploy Enterprise JavaBeans (EJB) applications for Red Hat JBoss Enterprise Application Platform. Legal Notice Copyright © 2021 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/ . In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
[Show full text]
Jakarta EE – Present and Future
Jakarta EE – Present and Future Michael P. Redlich Senior Research Technician [email protected] @mpredli Jakarta EE • Java EE transitioned from JCP to Eclipse Foundation as Jakarta EE • Open governance, open source, open compatibility testing • Well defined specification process, clear IP flow, vendor-neutral open collaboration, level playing field • Key stakeholders maintained if not expanded including Oracle, IBM, Payara and Pivotal • Community participation and contribution key https://jakarta.ee Jakarta EE Evolution EJB 3, JPA, Servlet, CMP, JSF, JAXB, JSP, EJB, JCA JAX-WS JMS JAX-WS J2E J2E J2E Java EE JPE E E E 5 1.2 1.3 1.4 Profiles, CDI, WebSocket, JAX-RS, JSON, HTTP/2, SSE, Bean Concurrency, Security, Open source Validation Batch, pruning pruning governance Java EE Java EE Java EE Jakarta 6 7 8 EE 8 Namespace To be scoped transition by community Jakarta Jakarta EE 9 EE 10 Jakarta EE 8 At a Glance • Web Standards Alignment • HTTP/2, Server-Sent Events, JSON Binding, JSON Pointer, JSON Patch • CDI Alignment • CDI 2, Faces managed bean pruning, injecting Faces artifacts, CDI support in Persistence • Simplicity • Security, EJB pruning • Java SE Alignment • Repeatable annotations, Date-Time API, streams, completable futures • Jakarta Faces, Jakarta Persistence, Jakarta REST, Bean Validation Jakarta Servlet 4 • Principal goal to support HTTP/2 • Request/response multiplexing over single connection • Multiple streams, stream prioritization • Server push • Binary framing • Header compression • Most of it done without major API changes Jakarta JSON Binding • API to marshal/un-marshal POJOs to/from JSON • Very similar to Jakarta XML Binding in the XML world • Default mapping of classes to JSON • Annotations to customize default mappings • @JsonbProperty, @JsonbTransient • Provides Jakarta REST a built-in way to support “application/json” for POJOs • Providers already supported non–standard binding APIs JSON Binding Example @GET ..
[Show full text]
Jakarta EE Platform 9 Specification Document
Jakarta EE Platform Jakarta EE Platform Team, https://projects.eclipse.org/projects/ee4j.jakartaee- platform 9, November 06, 2020 Table of Contents Copyright. 2 Eclipse Foundation Specification License . 3 Disclaimers. 3 1. Introduction . 6 1.1. Acknowledgements for the Initial Version of Java EE . 6 1.2. Acknowledgements for Java EE Version 1.3 . 7 1.3. Acknowledgements for Java EE Version 1.4 . 7 1.4. Acknowledgements for Java EE Version 5 . 7 1.5. Acknowledgements for Java EE Version 6 . 8 1.6. Acknowledgements for Java EE Version 7 . 8 1.7. Acknowledgements for Java EE Version 8 . 8 1.8. Acknowledgements for Jakarta EE 8 . 9 1.9. Acknowledgements for Jakarta EE 9 . 9 2. Platform Overview. 10 2.1. Architecture . 10 2.2. Profiles. 11 2.3. Application Components. 13 2.3.1. Jakarta EE Server Support for Application Components. 13 2.4. Containers. 14 2.4.1. Container Requirements . 14 2.4.2. Jakarta EE Servers. 14 2.5. Resource Adapters . 15 2.6. Database . 15 2.7. Jakarta EE Standard Services. 15 2.7.1. HTTP. 15 2.7.2. HTTPS. 15 2.7.3. Jakarta Transaction API (JTA) . 15 2.7.4. RMI-IIOP (Optional) . 16 2.7.5. Java IDL (Optional) . 16 2.7.6. JDBC™ API . 16 2.7.7. Jakarta Persistence API . 16 2.7.8. Jakarta™ Messaging . 16 2.7.9. Java Naming and Directory Interface™ (JNDI). 16 2.7.10. Jakarta™ Mail. 17 2.7.11. Jakarta Activation Framework (JAF) . 17 2.7.12. XML Processing . 17 2.7.13.
[Show full text]
Eclipse Public License - V 2.0 the ACCOMPANYING PROGRAM IS PROVIDED UNDER the TERMS of THIS ECLIPSE PUBLIC LICENSE (“AGREEMENT”)
Eclipse Public License - v 2.0 THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS ECLIPSE PUBLIC LICENSE (“AGREEMENT”). ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAM CONSTITUTES RECIPIENT'S ACCEPTANCE OF THIS AGREEMENT. 1. DEFINITIONS “Contribution” means: a) in the case of the initial Contributor, the initial content Distributed under this Agreement, and b) in the case of each subsequent Contributor: o i) changes to the Program, and o ii) additions to the Program; where such changes and/or additions to the Program originate from and are Distributed by that particular Contributor. A Contribution “originates” from a Contributor if it was added to the Program by such Contributor itself or anyone acting on such Contributor's behalf. Contributions do not include changes or additions to the Program that are not Modified Works. “Contributor” means any person or entity that Distributes the Program. “Licensed Patents” mean patent claims licensable by a Contributor which are necessarily infringed by the use or sale of its Contribution alone or when combined with the Program. “Program” means the Contributions Distributed in accordance with this Agreement. “Recipient” means anyone who receives the Program under this Agreement or any Secondary License (as applicable), including Contributors. “Derivative Works” shall mean any work, whether in Source Code or other form, that is based on (or derived from) the Program and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. “Modified Works” shall mean any work in Source Code or other form that results from an addition to, deletion from, or modification of the contents of the Program, including, for purposes of clarity any new file in Source Code form that contains any contents of the Program.
[Show full text]
Jakarta EE 9 and Beyond Ivar Grimstad Jakarta EE Developer Advocate Eclipse Foundation
Jakarta EE 9 and Beyond Ivar Grimstad Jakarta EE Developer Advocate Eclipse Foundation COPYRIGHT (C) 2020, ECLIPSE FOUNDATION, INC. | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0) @ivar_grimstad https://github.com/ivargrimstad https://www.linkedin.com/in/ivargrimstad Background Jakarta EE 9 Beyond Jakarta EE 9 #JakartaEE COPYRIGHT (C) 2020, ECLIPSE FOUNDATION, INC. | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0) @ivar_grimstad #JakartaEE COPYRIGHT (C) 2020, ECLIPSE FOUNDATION, INC. | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0) @ivar_grimstad Java EE EE4J #JakartaEE COPYRIGHT (C) 2020, ECLIPSE FOUNDATION, INC. | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0) @ivar_grimstad Jakarta EE #JakartaEE COPYRIGHT (C) 2020, ECLIPSE FOUNDATION, INC. | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0) @ivar_grimstad https://jakarta.ee #JakartaEE COPYRIGHT (C) 2020, ECLIPSE FOUNDATION, INC. | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0) @ivar_grimstad Open Specifications #JakartaEE COPYRIGHT (C) 2020, ECLIPSE FOUNDATION, INC. | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0) @ivar_grimstad Jakarta EE Specification Process Code First Collaborative Documents and TCKs are open source One or more Compatible Implementations Self certification #JakartaEE COPYRIGHT (C) 2020, ECLIPSE FOUNDATION, INC. | THIS WORK IS LICENSED UNDER A CREATIVE COMMONS ATTRIBUTION 4.0 INTERNATIONAL LICENSE (CC BY 4.0) @ivar_grimstad #JakartaEE COPYRIGHT (C) 2020, ECLIPSE FOUNDATION, INC.
[Show full text]
Jakarta Transactions 2.0 Specification Document
Jakarta Transactions 2.0 Jakarta Transactions Team, https://projects.eclipse.org/projects/ee4j.jta 2.0, October 08, 2020 Table of Contents Copyright. 2 Eclipse Foundation Specification License . 2 Disclaimers . 2 Jakarta Transactions Specification, Version 2.0 . 4 1. Introduction. 5 1.1. Background . 5 1.2. Target Audience . 6 2. Relationship to Other Java APIs . 8 2.1. Java SE. 8 2.2. Jakarta Enterprise Beans . 8 2.3. JDBC . 8 2.4. Jakarta Messaging . 8 2.5. Java Transaction Service . 9 3. Jakarta Transactions API . 10 3.1. User Transaction Interface . 10 3.2. TransactionManager Interface . 11 3.2.1. Starting a Transaction . 12 3.2.2. Completing a Transaction. 12 3.2.3. Suspending and Resuming a Transaction. 12 3.3. Transaction Interface . 13 3.3.1. Resource Enlistment . 13 3.3.2. Transaction Synchronization. 15 3.3.3. Transaction Completion . 15 3.3.4. Transaction Equality and Hash Code. 15 3.4. XAResource Interface . 16 3.4.1. Opening a Resource Manager . 17 3.4.2. Closing a Resource Manager . 18 3.4.3. Thread of Control . 18 3.4.4. Transaction Association . 18 3.4.5. Externally Controlled connections . 19 3.4.6. Resource Sharing . 19 3.4.7. Local and Global Transactions . 20 3.4.8. Failure Recovery . 21 3.4.9. Identifying Resource Manager Instance . 21 3.4.10. Dynamic Registration . 22 3.5. Xid Interface . 22 3.6. TransactionSynchronizationRegistry Interface . 23 3.7. Transactional Annotation . 23 3.8. TransactionScoped Annotation. 25 4. Jakarta Transactions Support in the Application Server . 29 4.1.
[Show full text]
Java for the Enterprise: What to Expect in Jakarta EE 10
Menu Topics Archives Downloads Subscribe Java for the enterprise: What to JAKARTA EE expect in Jakarta EE 10 It’s all about CDI alignment Java for the enterprise: What to Jakarta Server Faces expect in Jakarta EE 10 The Jakarta Security API The release is only a year away. The Jakarta Servlet API Here’s what to expect. The Jakarta REST API by Arjan Tijms The Jakarta Concurrency API March 26, 2021 Variants of CDI Last year, Java EE completed its transfer to the Eclipse Other Jakarta EE 10 APIs Foundation and adopted a new name, Jakarta EE. While this is a great achievement in and of itself, perhaps the most interesting Conclusion part of that is that it’s now finally time to start looking forward. Dig deeper As a quick recap, Table 1 shows key historic and future Jakarta EE dates, some of which are tentative. There are some changes from the version of the table I presented in an article in February 2020. Table 1. The history and latest release projections for Java EE and Jakarta EE Comparing the table shown in the previous article to this one, you can see that the JDK 11 compatibility theme moved from Jakarta EE 9 to Jakarta EE 9.1, which is still to be released this year. While this obviously takes some time away from Jakarta EE 10, planning for that latter release has started to some degree nevertheless, and some of the individual specifications and API projects have started their discussions. Note that everything presented in this article is preliminary and represents the current state of what is thought to be the direction in which Jakarta EE 10 will be heading, but it provides no guarantees that any of this will actually end up in Jakarta EE 10.
[Show full text]