jakartaee / jakartaee/messaging
JMSProducer#setJMSCorrelationIDAsBytes should be allowed to throw a java.lang.UnsupportedOperationException
- Dominant language
- Java
- Stars
- 49
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
In both JMS 1.1 and JMS 2.0, the method setJMSCorrelationIDAsBytes on Message is allowed to throw a java.lang.UnsupportedOperationException if the JMS provider does not support native correlation ID values. The javadoc states:
> If a provider supports the native concept of correlation ID, a JMS client may need to assign specific JMSCorrelationID values to match those expected by native messaging clients. JMS providers without native correlation ID values are not required to support this method and its corresponding get method; their implementation may throw a java.lang.UnsupportedOperationException.
The same rule needs to be added to the method setJMSCorrelationIDAsBytes on JMSProducer. Its omission is as an error in the spec.
#### Affected Versions
[2.0]
Contributor guide
Research direction
Start by locating the JMSProducer#setJMSCorrelationIDAsBytes API declaration and its Javadoc, then compare it with the corresponding Message method wording quoted in the issue. Done means the JMSProducer documentation states that providers without native correlation ID values may throw java.lang.UnsupportedOperationException.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100