Jakarta Messaging Next

This issue serves as effectively the JSR replacement, intended to give a high-level view of the Jakarta Messaging 3.0 road map and goals.

- Specific proposals should be filed separately and linked here.
- Only curated proposals that have had community discussion should be listed here.
- It is expected this issue will mutate and be updated frequently.

# Road Map

The community is still bootstrapping initial discussion. All items below should be viewed as tentative.

## New Features

- Annotation-Based API for Consuming Messages #243
- CDI Message Consumers #244
- CDI Stereotypes #245
- Property Conversions #246
- JSON-B Messages #247
- JAXB Messages #248
- MessagingClient #249

## Enhancements

TBD

## Bugs

TBD

# Resources

- [Jakarta Messaging 3.0, Redefining JMS | JakartaOne Livestream](https://www.youtube.com/watch?v=1E2_FE7ZQ64)

# Submit a Use Case or Proposal

For information on how to submit a use case or proposal, file a new issue labeled either `use case` or `proposal`. Do not file one issue labeled with both. See this for more guidance:

- https://github.com/eclipse-ee4j/jms-api/wiki#use-cases-and-proposals

Start by reading this roadmap and the linked proposals #243–#249, then review the use-case and proposal guidance in the Jakarta Messaging wiki. The issue contains no specific implementation entry point or acceptance criteria; completion is not defined until a concrete proposal is selected and scoped.

Written by the indexing model from the issue text.