Introduce LockRequestHandlerAdvice based on the LockRegistry [INT-4112]

[spring-operator]

Artem Bilan opened INT-4112 and commented

There are some use-cases when we should keep mutual access to the underlying services.
Not synchronized, but based on some key extracted from the requestMessage.

Keep in General Backlog until real requirement.
Although solution is simple enough...

---

No further details from INT-4112

[spring-operator]

Gary Russell commented

Perhaps the advice can have a property lockKeyExpression (used to determine which lock to acquire).

Also, an optional discardChannel, used when the lockKeyExpression returns null.