jakartaee / jakartaee/messaging
Jakarta Messaging API refresh: Update timings to support nanoseconds
Open
- Dominant language
- Java
- Stars
- 49
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Description
Currently, all timings (Timestamp, Expiration and Delay) are in milliseconds. API refresh should update timings to support nanosecond precision.
Contributor guide
Research direction
Start by reviewing the Jakarta Messaging API definitions for Timestamp, Expiration, and Delay, then identify how their current millisecond timing contracts are represented. Define the nanosecond-precision requirements and update the related API behavior and tests; done means all three timings consistently support nanoseconds.
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
- Mostly clear
- Newbie friendliness
- 35/100