Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 325796 - Concurrency: Add @ThreadSafe, @NotThreadSafe, @GuardedBy and @Immutable annotations for thread safety specification
Summary: Concurrency: Add @ThreadSafe, @NotThreadSafe, @GuardedBy and @Immutable annot...
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL: http://www.javaconcurrencyinpractice....
Whiteboard:
Keywords:
Depends on:
Blocks: 331094
  Show dependency tree
 
Reported: 2010-09-20 16:34 EDT by Michael OBrien CLA
Modified: 2022-06-09 10:06 EDT (History)
2 users (show)

See Also:
michael.f.obrien: documentation+
michael.f.obrien: iplog+

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael OBrien CLA 2010-09-20 16:34:22 EDT 
>We need some method of tracking which classes should be thread safe
>or are known not to be thread safe
>We also need a way to document what we are locking on.

It would be benificial to the developers and users to use some annotations to mark up our classes as currently it is difficult to determine which classes are required to maintain thread safety.

See the work by Brian Goetz an others in "Java Concurrency in Practice".
The annotation source and binary jar is available under the creativecommons.org license at

http://www.javaconcurrencyinpractice.com/

in the form of
@ThreadSafe
@NotThreadSafe
@Immutable
@GuardedBy
Comment 1 Eclipse Webmaster CLA 2022-06-09 10:06:10 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink