jakartaee / jakartaee/messaging

Allow async delivery to temporary destinations in Java EE

Open
#141 5 comments 0 reactions 0 assignees View on GitHub
jms21-forreview-major Priority: Major Type: Improvement
Dominant language
Java
Stars
49
Forks
34
PR merge metrics
No merged PRs in 30d

Description

Currently there is no (legal) way for an application running in the Java EE web or EJB containers to consume messages asynchronously from a temporary queue or topic.

The use of setMessageListener to register a MessageListener is not permitted.

It is not possible to configure a MDB to consume messages from a temporary destination.

This was raised in the GlassFish forum recently. [https://www.java.net//node/900071](https://www.java.net//node/900071) Is this a common requirement?

It is proposed that the discussion elsewhere to make async message delivery in Java EE applications more flexible should (at least) consider this requirement.
#### Affected Versions
[2.0]

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the issue's discussion of setMessageListener, MessageListener, MDBs, and temporary queues or topics, then read the linked GlassFish forum thread for context. The issue provides no repository files or tests to run; done would require an agreed Java EE design that permits asynchronous delivery to temporary destinations.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend-api-design, distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.