You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Decision to use beginExclusive()/endExclusive() for locking comes from times before Java code existed. It was not quite applicable even when the library was in active development (early 2000s), and today it is completely obsolete; it makes the application fragile and prone to deadlocks.
Task Definition
As an Application Architect, I want to change the design so that the need to use beginExclusive()/endExclusive() pair is gone.
Acceptance Criteria
The library can be used exactly the way it is used today without beginExclusive()/endExclusive() being used.
The text was updated successfully, but these errors were encountered:
Background
Decision to use
beginExclusive()
/endExclusive()
for locking comes from times before Java code existed. It was not quite applicable even when the library was in active development (early 2000s), and today it is completely obsolete; it makes the application fragile and prone to deadlocks.Task Definition
As an Application Architect, I want to change the design so that the need to use
beginExclusive()
/endExclusive()
pair is gone.Acceptance Criteria
The library can be used exactly the way it is used today without
beginExclusive()
/endExclusive()
being used.The text was updated successfully, but these errors were encountered: