Which Swing component methods are thread safe?

Question

According to Swing tutorial:

Some Swing component methods are labelled "thread safe" in the API specification; these can be safely invoked from any thread. All other Swing component methods must be invoked from the event dispatch thread. Programs that ignore this rule may function correctly most of the time, but are subject to unpredictable errors that are difficult to reproduce.

But what are these Swing component methods that are labelled "thread safe"? Are there actually any?

---

Update / bounty:

Is there a complete list of thread-safe swing methods? (The thread-safe Swing methods seems to be quite rare, so such list can't be too long...)

Answer 1

Google taught me that at least those are threadsafe. Here's an overview for the case that the link get broken again:

---

• JTextPane
  • replaceSelection()
  • insertComponent()
  • insertIcon()
  • setLogicalStyle()
  • setCharacterAttributes()
  • setParagraphAttributes()

---

• JTextArea
  • insert()
  • append()
  • replaceRange()

---

• JTextComponent
  • replaceSelection()
  • setText()
  • print()
  • getPrintable()

---

• UndoManager
  • All methods.

---

• DefaultStyledDocument
  • insert()
  • setLogicalStyle()
  • setCharacterAttributes()
  • setParagraphAttributes()

---

• StyleContext
  • addAttribute()
  • addAttributes()
  • removeAttribute()
  • removeAttributes()
  • reclaim()

---

• AbstractDocument
  • render()
  • remove()
  • insertString()
  • createPosition()

---

• PlainDocument
  • insertString()

---

• HTMLDocument
  • setParagraphAttributes()

Answer 2

But what are these Swing component methods that are labelled "thread safe"?

Most Swing components' methods are NOT thread safe. But some are. To find out which ones, you have no option but to peruse the javadocs for your target components. A carefully constructed google search might quicken the process.

Are there actually any?

Yes there are indeed. Generally speaking, if you are working with Swing components, it is likely that you are going to have to invoke both thread-safe and non-thread-safe methods. Since most methods are non-thread-safe, I prefer to err on the side of caution, and perform all actions on them in a thread-safe manner anyway.

HTH

---

Not exhaustive list.

DefaultStyledDocument:

• protected void insert(int offset, DefaultStyledDocument.ElementSpec[] data) throws BadLocationException
• public void setLogicalStyle(int pos, Style s)
• public void setCharacterAttributes(int offset, int length, AttributeSet s, boolean replace)
• public void setParagraphAttributes(int offset, int length, AttributeSet s, boolean replace)

javax.swing.text.AbstractDocument:

• public void render(Runnable r)
• public void remove(int offs, int len) throws BadLocationException
• public void insertString(int offs, String str, AttributeSet a) throws BadLocationException
• public Position createPosition(int offs) throws BadLocationException

javax.swing.undo.UndoManager:
Class is threadsafe