-
Notifications
You must be signed in to change notification settings - Fork 304
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
Proposal: Use javax.cache.annotation.CacheDefaults when injecting JCache #1124
Comments
Do you fancy making a PR to demonstrate? |
I'll have a look at it. The main issue I can foresee is a potential clash with the official Java EE - JCache integration. If the EG decided to not use the |
Depends on: payara/Payara#1125 and payara/Payara#1124
Depends on: payara/Payara#1125 and payara/Payara#1124
Lets cross that bridge when we get to it. |
So there is currently no other way to |
Payara uses
CacheDefaults
for cache resolution in the CDI interceptor as the spec mandates.I believe it would make a lot of sense to use
CacheDefaults
as a cache resolution strategy when injecting JCache via@Inject
.Currently it does use name of a declaring class as a cache name. There is also the
@NamedCache
but that creates a dependency on Payara-specific code.The text was updated successfully, but these errors were encountered: