commit | 21b0ac880166beaa42220e4d02c9f7b073130345 | [log] [tgz] |
---|---|---|
author | Tamas Cservenak <tamas@cservenak.net> | Mon Nov 14 11:31:59 2022 +0100 |
committer | GitHub <noreply@github.com> | Mon Nov 14 11:31:59 2022 +0100 |
tree | a2d1563415b36ab626cfa522117bed7f2fdf0d2f | |
parent | 7469aa25e781e30fbbb5158a1433108bc14956c3 [diff] |
[MRESOLVER-291] Undo params use (#219) Pull out ctor param injection, provide generic enough helper to allow anyone to customize as they want. Changes in short: Nor SyncContextFactory nor NamedLockFactoryAdapter should shut down. This was the problem, and I was mislead by it. NamedLockFactory instances are **singletons**, and **are inited in ctor**. Hence, if two adapters used same factory, in case one adapter is shut down, it would shut down the lock factory of the other one as well (unexpectedly). Hence, it is solely the adapter factory duty to shut down factories, but again, as we saw, they are inited in ctor, hence if we assume there is living HZ named lock factory, even if unused (as file lock is used for example), shutdown is still needed, to shut down the HZ instance (same applies to Redisson btw)! All in all, this new class is IMHO the most correct, while it allows overriding and changing things, if needed. Minor: do not create static initializers to be used in SL, make them methods invoked when needed. --- https://issues.apache.org/jira/browse/MRESOLVER-291
You have found a bug or you have an idea for a cool new feature? Contributing code is a great way to give something back to the open source community. Before you dig right into the code, there are a few guidelines that we need contributors to follow so that we can have a chance of keeping on top of things.
We accept Pull Requests via GitHub. The developer mailing list is the main channel of communication for contributors. There are some guidelines which will make applying PRs easier for us:
git diff --check
before committing.[MRESOLVER-XXX] - Subject of the JIRA Ticket Optional supplemental description.
mvn -Prun-its verify
to assure nothing else was accidentally broken.If you plan to contribute on a regular basis, please consider filing a contributor license agreement.
For changes of a trivial nature to comments and documentation, it is not always necessary to create a new ticket in JIRA. In this case, it is appropriate to start the first line of a commit with ‘(doc)’ instead of a ticket number.