The abstract base classes supplied for the component system aren't strictly compatible with full thread-safety because access to the state they control isn't fully synchronized.

This isn't a problem for components which are @ThreadSafeAfterInit but it does prevent even in principle the building of components which are truly @ThreadSafe.

I think it's relatively cheap to fix this, so that these base classes can be used for either kind of component:

• In AbstractIdentifiedInitializableComponent:

  • The id field should be @GuardedBy("this")

  • Both getId and setId should be synchronized

• In AbstractInitializableComponent:

  • The isDestroyed field should be @GuardedBy("this")

  • The isInitialized field should be @GuardedBy("this")

  • The isDestroyed and isInitialized methods should both be synchronized

The {{@GuardedBy}} annotations are just documentation.

The isInitialized and isDestroyed methods are generally only called before the object becomes live, so I think any synchronization overhead can be ignored in practice.