jakartaee / jakartaee/rest

JavaDocs for Client, WebTarget and Invocation should clearly say whether invocations MUST be thread-safe

Open
#494 23 comments 6 reactions 1 assignee Claimed by @mkarg View on GitHub
Component: client enhancement javadoc
Dominant language
Java
Stars
400
Forks
143
PR merge metrics
No merged PRs in 30d

Description

JAX-RS 2.0 provides a Client API which is prepared for intense reuse of object instances of Client, WebTarget and Invocation. Unfortunately the JavaDocs of these classes do not say whether a caller can rely upon these instances are thread-safe. As a recent discussion on the user's mailing list has discovered, users abstain from the rist of concurrent usage of these instances as they fear risk of producing problems. Hence, the JAX-RS 2.1 specification should clearly point out (in PDF and / or JavaDocs) whether implementations of Client, WebTarget and Invocation MUST be thread-safe. This unambiguity would allow users to safely the same Client instance from different application threads for example.
#### Affected Versions
[2.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.