jakartaee / jakartaee/messaging

Define a standard way to specify the resource adapter used by a JMS MDB

Open
#174 4 comments 0 reactions 0 assignees View on GitHub
bug CDI integration jms21-forreview-major Priority: Major Type: Bug
Dominant language
Java
Stars
49
Forks
34
PR merge metrics
No merged PRs in 30d

Description

The EJB 3.2 specification does not define a standard way to associate a JMS MDB (or any other type of MDB) with a resource adapter. Instead, if the application requires that a particular resource adapter be used, and the application server does not use it by default, then the application must specify this in the app-server-specific deployment descriptor (e.g. glassfish-ejb-jar.xml.

It is therefore proposed that a standard way is defined to associate a JMS MDB (or any other type of MDB) with a resource adapter, using either ejb-jar.xml or the MessageDriven annotation.

This will require a change to the EJB specification, not JMS, and is logged here for tracking purposes. The EJB spec issue is [EJB_SPEC-127](https://java.net/jira/browse/EJB_SPEC-127 "Define a standard way to specify the resource adapter used by a JMS MDB").
#### Affected Versions
[JMS 2.0 rev A]

Contributor guide

Open the contributing guide

Research direction

Start with the proposal in this issue and the referenced EJB_SPEC-127, since the change belongs to the EJB specification rather than JMS. Review how ejb-jar.xml and the MessageDriven annotation could associate an MDB with a resource adapter; done requires an agreed standard specification change.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.