-
Notifications
You must be signed in to change notification settings - Fork 45
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
avoid custom CreationalContext and Contextual implementations in the TCK #452
avoid custom CreationalContext and Contextual implementations in the TCK #452
Conversation
Since this PR adds a new TCK SPI, this can only be done in the next major/minor CDI TCK version (4.1/5.0 I believe). Hence this is a draft for now. |
0322c74
to
c7789ab
Compare
c7789ab
to
d83a1e3
Compare
I actually have a few more things locally, to avoid custom |
This commit also removes a few outdated references to Web Beans.
d83a1e3
to
329c666
Compare
Rebased, added a commit that removes obsolete TCK exclusions, force-pushed, and updated the title and summary of this PR. @manovotn my implementation of these SPIs for Weld is in https://github.com/Ladicek/weld-core/commits/new-tck-spi, feel free to steal that :-) I also have an implementation of these SPIs for ArC on a branch somewhere, I can dig that up if interested. |
Thanks but I already have my own draft. |
This commit also splits the `DestroyForSameCreationalContext2Test` test into a CDI Lite and Full parts.
329c666
to
8520eb8
Compare
On a small number of places, the CDI TCK creates its own implementations of
CreationalContext
andContextual
. These are extremely bare APIs that aren't sufficient for internal needs of CDI implementations or for interoperability. All CDI implementations that I know expose internally a much richer API and generally expect that theirCreationalContext
andContextual
implementations are used. It is possible to bend the implementations to accept aCreationalContext
orContextual
of outside provenance, but I believe there's exactly nothing in the CDI specification that makes this mandatory.Instead, I believe the CDI TCK should:
CreationalContext
andContextual
implementations;CreationalContext
andContextual
implementations, augmented with inspection capabilities for the tests that need it.This PR does exactly that.