JDK-6463020 : JTextComponents incorrectly claim to be partly thread safe
  • Type: Bug
  • Component: client-libs
  • Sub-Component: javax.swing
  • Affected Version: 6
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2006-08-23
  • Updated: 2015-01-21
  • Resolved: 2015-01-21
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 9
9Resolved
Related Reports
Duplicate :  
JDK-4765383 - JTextArea.append(String) not thread safe
Description
Some methods of JTextComponens claim to be "thread safe", 
see for example JTextComponent.setText() its javadoc says:
<This method is thread safe, although most Swing methods are not>

But looking to its implementation it's quite obvious that it isn't thread safe
if I setText() on one thread and getText() on another thread 
it will likely cause a problem

Current situation: text package claim some of their methods as thread safe

Expected: No misleading note about thread safety