jakartaee / jakartaee/messaging
add MessageConsumer.getDestination() and JMSConsumer.getDestination() methods
Open
Nobody has claimed this yet.
New Feature
Priority: Minor
- Dominant language
- Java
- Stars
- 49
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
TopicSubscriber.getTopic() and QueueReceiver.getQueue() exist, so I think also MessageConsumer.getDestination() should be there.
That way an unnecessary type cast could be avoided and the provider's implementation is trivial.
#### 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 comparing the existing TopicSubscriber.getTopic() and QueueReceiver.getQueue() API declarations with MessageConsumer and JMSConsumer. Trace the provider implementation points affected by those interfaces, then verify that both new getDestination() methods are exposed consistently without requiring the caller's type cast.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100