Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 325796

Summary: Concurrency: Add @ThreadSafe, @NotThreadSafe, @GuardedBy and @Immutable annotations for thread safety specification
Product: z_Archived Reporter: Michael OBrien <michael.f.obrien>
Component: EclipselinkAssignee: Project Inbox <eclipselink.foundation-inbox>
Status: NEW --- QA Contact:
Severity: enhancement    
Priority: P3 CC: eclipselink.foundation-inbox, michael.f.obrien
Version: unspecifiedFlags: michael.f.obrien: documentation+
michael.f.obrien: iplog+
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
URL: http://www.javaconcurrencyinpractice.com/
Whiteboard:
Bug Depends on:    
Bug Blocks: 331094    

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