[TAP5-84] Change proxy generation to use volatile fields rather than synchronized blocks

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 5.0.15
• Fix Version/s: 5.1.0.1
• Assignee: Howard Lewis Ship
• Reporter: Howard Lewis Ship
• Created: 09/May/08 18:58
• Updated: 04/Mar/09 17:35
• Resolved: 04/Mar/09 17:35

Description

As currently coded, the service proxies used for Tapestry services use a synchronized block to a) check to see if the Registry has shut down and b) obtain (if needed) the realized service implementation (wrapped by interceptors, etc.).

It seems that with some juggling, these could largely be replaced with AtomicBoolean and AtomicReferences.