jakartaee / jakartaee/messaging

Fix JavaDocs to reflect missing NumberFormatException from API methods

Open
#3 6 comments 0 reactions 1 assignee Claimed by @nigeldeakin View on GitHub
jms21doc-minor Priority: Major Type: Bug
Dominant language
Java
Stars
49
Forks
34
PR merge metrics
No merged PRs in 30d

Description

---------------------------
NumberFormatException tests
---------------------------

For javax.jms.MapMessage and javax.jms.StreamMessage the JavaDoc's need to be updated for the string to numeric conversions. The String to numeric conversions must throw a
java.lang.NumberFormatException if the numerics valueOf() method does not accept the the String value as a valid representation.

Tests for (NumberFormatException) which is not listed in JavaDoc for the getXXX() methods. Test in question is: MapMessageConversionQTestsInvFormatString. The
(NumberFormatException) is mentioned in spec but missing in JavaDoc.

The JavaDoc's for the following methods below of class javax.jms.MapMessage and class javax.jms.StreamMessage need to be modified to add the NumberFormatException.

getBoolean, getByte, getShort, getInt, getLong, getFloat, getDouble, etc
#### Environment
N/A
#### Affected Versions
[1.1]

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.