-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
concurrency: add SPI for context providers #16
Comments
To the best of my knowledge, the ThreadContextProvider SPI under pull #15 covers all of the above requirements and is conducive to context implementations that are stack-based as well as those that are not. The doc additions under that pull also specify that the ServiceLoader (META-INF/services) is the way to plug in a third-party provider. Can we close this issue if you are satisfied that everything is covered there? |
Yes, now that #15 has been merged, it appears to support this use-case. Thanks. |
Fix issue eclipse#26 and eclipse#16
Update to 0.1.1-SNAPSHOT
In order for mp-concurrency to replace Reactive Contexts which is currently used by RESTEasy to provide context propagation, we need to be able to define context providers via an SPI. Otherwise, context providers would be a fixed list and not support contexts that are external to MP/EE.
This can be as simple as defining a
ContextProvider
interface which supports:Where "the context" can be an opaque type that nobody outside of the context provider cares about (a type parameter would do).
Implementations of the
ContextProvider
can be listed with aMETA-INF/services
file.The text was updated successfully, but these errors were encountered: