Skip to content
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

Java EE support and cache configuration #393

Open
cruftex opened this issue Nov 24, 2017 · 0 comments
Open

Java EE support and cache configuration #393

cruftex opened this issue Nov 24, 2017 · 0 comments
Assignees

Comments

@cruftex
Copy link
Member

cruftex commented Nov 24, 2017

Originally JCache was meant to be included in the Java EE spec canon. When working on a next version of JCache that requirement is probably one of the "most wanted". Looking at the efforts so far I see a major conceptual problem:

a) The JCache spec says that the cache configuration is outside of the spec
b) An EE application should run on an EE server. If the application uses JCache for caching, there must be enough configuration information that is independent of the cache vendor to run the application

Solutions variants I can think of at the moment:

  1. no extra configuration. specify that a default cache should hold at least 1000 elements.
  2. standard configuration file that enlists the used caches in the application and parameters that are known in the JCache configuration object. Also it contains a description of the intended use, so an admin can configure a specific implementation properly.
  3. instead of naming the caches, introduce labels. this should allow the admin to set a vendor specific cache configuration of a group of caches with the same label.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant