jakartaee / jakartaee/messaging
Introduce a programmatic API for creating destinations.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 49
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
Since we have the option of creating a temporary queue/topic, it should also be possible to create a permanent queue/topic. The idea being that this queue/topic could survive for a long period of time, perhaps even be persistent. Most common attributes for configuring them should be addressed (e.g. name, JNDI location, require role/user, perhaps even storage scheme).
Affected Versions
[2.0]
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing API for creating temporary queues and topics, then compare it with the Jakarta Messaging 2.0 context named in the issue. Clarify the required behavior and configuration attributes for permanent destinations, including names, JNDI locations, access requirements, and storage schemes. Done means a defined programmatic API covers these destination types and attributes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100